TMN Networking

9500 MPR TMN Networking
3DB 19353 AAAA

7-January-2016
1
3DB 19353 AAAA - 9500 MPR TMN Networking
COPYRIGHT © 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
Contents Table – Main Sections
1. TMN Interfaces
2. TMN Related Services
3 TMN IP Addresses
3.
4. The TMN Network
5. DCN Interconnections examples
6. Basic MPR Address Provisioning
7. Interconnecting Multiple MPR Shelves
8. Craft and Management Communication Requirements
9. Planning and Addressing a Network
10. Configuring the MPR
2
Contents Table – Annexes
A. Basics of IP Addressing
B. Communication in Networks
C MPR DHCP Overview
C.
D. MPR OSPF Overview
E. Comparison to TMN Networking in the MDR
MDR-8000
8000
F. MPR-e and MPR-1c differences
G. Default and Reserved addresses
H. NAT router
3
1. TMN Interfaces
4
9500MPR TMN Networking
Physical
y Interfaces
Dir #35
Dir #34
Dir #N
TMN In
In-Band
Band #1
VLAN Interface
TMN In-Band #2
VLAN Interface
Port #4 TMN TMN Ethernet
The 9500MPR supports a variety of interfaces for TMN traffic:
1. For transport across RF links, there are in

in-band
band PPPoE channels, one per Direction
2. The TMN Ethernet port, enabled by default. This interface is intended for local Craft access. For shelf-to-shelf
interconnect or backhaul of TMN Network traffic the recommended configuration is to use one of the other TMN
interfaces listed below.
3
3. As an option
A ti U User Eth
Ethernett P
Portt #4 can b
be configured
fi d ffor TMN
TMN. Wh
When provisioned
i i d ffor TMN thi
this iinterface
t f iis iintended
t d d
for connecting to external networks.
4. Optionally one or two TMN In-band interfaces. These interfaces can be associated with one or more User Ethernet
ports with a user specified VLAN Id. These interfaces are also intended for connecting with external networks.
Communicating with the NE using these interfaces requires VLAN aware external equipment.
5
Interface to the TMN Router Dir #35
Dir #34
Dir #N
TMN In-Band #1
VLAN Interface
TMN In-Band #2
VLAN Interface Port #4 TMN TMN Ethernet
TMN
In-Band #1
VLAN Subnet Dir #34
TMN
In-Band #2
VLAN Subnet
Dir #35
} RF PPPoE links
…
Dir #N
Port #4
TMN Subnet TMN Ethernet
Subnet
•Each TMN interface to the MPR is connected to an internal router.
•With the exception of the RF PPPoE links, all the other interfaces to the Router are Broadcast Ethernet interfaces. When these
interfaces are provisioned,
provisioned the subnets must all be unique.
unique
•TMN traffic passing between any two TMN Network Interfaces is routed at Layer 3.
•ALL TMN Interface subnets must be unique and not overlap. The router does not support Bridging.
•For
For TMN In-Band
In Band interfaces
interfaces, each individual interface VLAN may be associated with one or more User Ethernet ports on the Core
Core. All
traffic in common TMN VLANs will be switched between the member ports.
6
2. TMN Related Services
7
MPR TMN Addressing Support
Starting with R4.01.00 the MPR supports TMN Networking in either IPv4
or IPv6 mode.
Only one mode may be active at a time. Simultaneous support of both IPv4 and IPv6
(Dual Stack) for TMN Networking is not available.
Most of this p
presentation is written using
g IPv4 examples
p but the examples
p
apply equally to IPv6.
IPv6 specific behaviors are noted where applicable.
8
Services - OSPF
The 9500MPR provides two services related to TMN networking.
The first service is OSPF for dynamic routing of TMN network traffic
1. For IPv4 TMN Networks the MPR supports OSPFv2
2. For IPv6 TMN Networks the MPR supports OSPFv3
3. The MPR provides a very basic OSPF implementation
4
4. User configurable parameters are limited to:
 Enabling or disabling OSPF on each individual TMN interface.
 Assigning an OSPF Area ID to each interface (default Area is 0)
 Enabling or disabling the Stub Flag (indicates whether the interface is a member of an OSPF
Stub Area)
5. A single MPR can function as an Area Border Router (ABR) for up to four OSPF Areas, one of which
must be Area 0.
6. The MPR is able to interoperate with external OSPF capable devices such as an Alcatel-Lucent
7705.
Refer to the OSPF Appendix at the back of this presentation for additional information about
i t
interoperating
ti with
ith external
t l equipment.
i t
9
Services – Craft computer
p address assignment
g
In IPv4 mode a trivial DHCP server available only on the TMN Ethernet port.
1. This limited server is intended to support dynamic address configuration of directly connected Craft
computers.
2. Enabled by default, the DHCP server can be disabled.
 This is the only user configurable option
3
3. Th DHCP server uses an address
The dd pooll determined
d t i db by the
th TMN Local
L l Ethernet
Eth t IP address
dd and
d subnet.
b t
4. The maximum number of Addresses managed by the DHCP Server is 10. Clients are served the same
Netmask assigned to the TMN Local Ethernet interface and a Default Gateway set to be the TMN Local
Ethernet Port IP address.
5. The Lease Time is fixed to 10 minutes.
Refer to the DHCP Appendix for specifics on how the MPR reserves address spaces for leases.
In IPv6 mode DHCP is not supported. Instead the MPR supports the RFC4861 Neighbor Discovery Protocol
(NDP) and sends link-local announcements allowing Stateless Address Auto-configuration of external
devices.
10
3. TMN IP Addresses
11
9500MPR Networking
MPR Addresses
The 9500MPR can be configured with up to five addresses.
Local Address:10.0.36.9
1. The first
f and primary address is the NE Local Address:
a) This is the Address of the MPR itself.
b) This is the address the Craft and SNMP Managers must use when monitoring or
provisioning the
h NE.
c) All MPR SNMP Traps or Notifications are sent from this address
d) All RF PPPoE connections terminating in this shelf (one per Direction) use this
address
dd as their
h i PPP Endpoint
E d i Identifier.
Id ifi
e) The NE Local Address is reachable by using one of the TMN Interface addresses
as a gateway (see the next slide).
12
9500MPR Networking
MPR Addresses

Address: 192.168.10.0 Address: 172
172.22.64.86
22 64 86
Netmask: 255.255.255.192 Netmask: 255.255.255.248
2. The TMN Ethernet interface address
a) The default interface intended for local Craft access, it is enabled by default.
 Caution: Disabling this interface may prevent any direct Craft access to the MPR. Unless another
means of connectivity is available such as Port #4 TMN, TMN In-Band, or an RF-PPP link then recovery
will require scratching the MPR Database to return the system to defaults.
b) May be connected to a very small external network with a low volume of expected traffic.
 Caution: This interface should not be exposed to a large number of broadcast packets or high volumes
of traffic as this will disrupt Core operations and may trigger Core restarts. This is a known
limitation. Instead use the optional Port #4 TMN Ethernet interface (below) or TMN In-Band interfaces
(next slide).
3. Optional Port #4 TMN Ethernet interface address
a) This interface is disabled by default. When enabled Core User Ethernet port #4 is reconfigured as a
dedicated TMN interface.
b)) Recommended for use when connecting

g to external networks leaving
g the TMN Ethernet interface available
for direct Local Craft access.
13
9500MPR Networking
MPR Addresses: In-Band interfaces
TMN In-Band #2
TMN In-Band #1
VLAN Id: 3720
VLAN Id: 2152
User Port: 1,3
User Port: 2
Address: 10
10.139.22.6
139 22 6
Address: 172.22.65.132
Netmask: 255.255.255.248
Netmask: 255.255.255.224
4. Optional TMN In-Band #1 Ethernet interface address
Optional TMN In-Band #2 Ethernet interface address
a) These interfaces are disabled by default.
b) When a TMN IIn-Band

Wh B d interface
i t f is
i enabled
bl d a unique
i VLAN Id is
i specified
ifi d for
f ththe
interface and one or more User Ethernet ports are assigned as members of the
VLAN. Traffic in the In-Band VLAN will be switched between all member ports.
c) These interfaces are intended for connection to external networks.

networks
14
9500MPR Networking
MPR Addresses: In-Band interfaces
The primary differences between the In-Band interfaces and the
other TMN interfaces are:
1) In-Band TMN Traffic is always VLAN tagged with the user

specified VLAN Id.
Access to the TMN In-Band

In Band traffic requires interfacing with a
VLAN aware external device, one that can be configured to use
the same VLAN Id.
2) Port flexibility. The user can provision one or more User

Ethernet ports that will be used with the In-Band interface
a) When multiple User Ethernet ports are associated with a

TMN In-Band interface the associated TMN VLAN will be
switched between the member ports.
15
9500MPR Networking
MPR Addresses: In-Band interfaces ((Continued))
3) Ports used for TMN In-Band:
a) May not be port segregated.
b) May be associated with PDH cross-connections.
c) When in 802.1Q mode the ports are always a member of the MPR internal
VLAN 1 and may also be a member of additional User defined VLANs.
d) When in 802.1ad mode the ports are always a member of the MPR internal
S-VLAN 1 and may also be a member of additional User defined VLANs.
e) Are
e co
connected
ected d
directly
ectly to tthe
eMMPR L2 sw
switch
tc fabric
ab c in w
when
e tthe
e sshelf
el iss in
802.1D mode
 These features are useful when it is desirable to transport TMN Traffic in a

VLAN through the same physical interface used for interconnecting User
Ethernet traffic between stacked MPR shelves or for external backhaul.
16
9500MPR Networking
MPR Addresses – Tips
p and Limitations
1. Tip: When assigning addresses to TMN Interfaces, the Local Address may be set to
match the address of one external TMN Interface but no more than one.
2. The Local Address must match the address of an external TMN Interface if it is in
the same subnet.
3. The NE Local Address must be reachable from the external network. The NE Local
Address must be reachable from SNMP Management servers and from external NTP
servers. Iff the
h NE Locall Address
dd cannot b
be reached
h d then
h some types off SNMP
Management and provisioning operations will fail and the MPR NTP client will fail.
A TMN Interface address is not a substitute for the NE Local Address.
• In 9500MPR releases R03.03.00 and earlier MPR TMN interfaces connected to
external networks must also be reachable from the Manager (WebEML Craft,
5620 SAM, TSM-8000, etc). Assigning unreachable addresses to these interfaces
(as sometimes used with transit networks) can cause failures in Software
Download and DB Backups. This is a known limitation with these older releases.
17
4. The TMN Network
18
9500MPR Networking
The Basic TMN Network – RF PPP Links
Local Address:10.3.27.5 Local Address:172.22.37.49
RF PPP Link
•If
If enabled,
bl d the link
th RF PPP li k comes up as soon as th
the R
Radio
di channel
h l iis operational.
ti l
•It doesn’t matter what Local IP Address is assigned at either end, as long as it is unique
and the IP version is the same (IPv4 or IPv6). When the Radio link is up, the routers are
networked together
g and can exchange
g packets
p with each other.
•TMN packets exchanged between the routers travel over the RF link in a high priority
queue.
19
9500MPR Networking
The Basic TMN Network – RF PPP Links
Local Address:10.3.27.5 Local Address:172.22.37.49 Local Address:192.168.10.16
Site C
Site A Site B
RF PPP Link RF PPP Link
•If we move beyond a single hop, when the RF links are up:
•The NE at Site A can communicate with Site B
•The NE at Site B can communicate with Site C
•but A cannot communicate with C until routing is configured.
•For routing to function, the NE addresses must all be unique. If there are any duplicate
addresses, or if all addresses are the same (factory default), routing will fail!
•Routing can be configured dynamically or statically.
•The recommended configuration is to enable OSPF within the MPR network for dynamic routing.
20
9500MPR Networking
The Basic TMN Network
Local Address:192.168.25.66 Local Address:172.22.37.49
TMN Ethernet Port: 10.0.2.1
RF PPP Link
Craft Address:10.0.2.2
Default Gateway: 10.0.2.1
Craft TMN Ethernet

Computer Network
•Before external devices can gain access to this network, at least one external TMN interface must be configured somewhere
in this network.
•If we connect a properly addressed Craft computer to one of the TMN Ethernet Interfaces we should be able to communicate
with all the MPRs in the network, provided the Craft computer is configured to use the TMN Ethernet interface as the Gateway
to the MPR network and OSPF is enabled or suitable static routes have been provisioned in the MPRs
•To communicate with either NE specify the Local Address of each MPR when connecting with the Craft: 192.168.25.66 and
172.22.37.49 in this example.
By default the MPR DHCP service is enabled. If the network interface of the Craft computer is set to “Obtain an IP address
automatically”, the Craft computer will be configured correctly when connecting to the TMN Ethernet Port. No user action
will be required.
When configured for IPv6 the MPR provides link-local

link local announcements using the Neighbor Discovery Protocol (NDP).
(NDP) This
allows Craft computers to configure themselves through stateless auto-configuration.
21
9500MPR Networking
A Simple
p Linear Network
TMN
Port #4 In-Band
TMN Subnet RF PPP Link RF PPP Link Subnet
X TMN TMN Y
TMN
Ethernet Ethernet
Ethernet
Subnet Subnet
Subnet
A B
C
• To provide local access to the MPR and to connect external equipment to the TMN network, we
use TMN interfaces at each site. Each interface functions as gateway to the TMN Network.
• From a TMN perspective, we have a network of Routers interconnected with PPP links.
• Each TMN Interface subnet must be unique in the network. Subnets used at one interface
cannot be reused at another interface or site within the same Radio network. Subnets on
different interfaces must not overlap.
• All TMN traffic is routed. Bridging between Ethernet subnets is not supported.
22
9500MPR Networking
Supported
pp TMN Layer
y 3 Network Topologies
p g
R R R R R
R R R R R R
R R R R
R R
Ring
R R R R
R R
Linear and Tree R
R R R
R
R
Mesh
• The TMN Network operates entirely at Layer 3. This network can be configured in Linear, Tree,
Ri
Ring, or M
Mesh
h ttopologies.
l i
• With Ring and Mesh networks, OSPF can dynamically update the routing to take advantage of
alternate routes for TMN traffic in the event of a link failure.
• OSPF will manage routes to prevent Layer 3 loops in the TMN Network only.
Notice: The Ring and Mesh topologies depicted are ONLY applicable for TMN Networking at Layer 3.
All 9500MPR user data transport is performed at Layer 2. It is mandatory that the data transport
g
network be configured to prevent
p anyy Layer
y 2 Ethernet loops
p through
g the appropriate
pp p p
provisioningg
of 802.1Q or 802.1ad VLANs, Ethernet Ring Protection, Port Segregation, or other physical means.
23
9500MPR Networking
Supported
pp TMN Network Topologies
p g
Management Traffic
Path After a failure
R R R
R MPR TMN Router
R
External Router
R R X R R R R R
Linear
R
R R R
SNMP
Manager
External
Network
• MPR TMN Networks can have multiple external gateways that allow alternate management paths in
the event of an outage.
• To make the best use of multiple gateways, OSPF must be enabled throughout the MPR TMN Network.
• To maximize the availability of alternate TMN network paths, OSPF should be used to manage the
links between the MPR and any external routers and a suitable dynamic routing protocol should be
usedd iin th
the E
External
t lNNetwork.
t k
24
5. DCN Interconnections examples
25
9500MPR (MSS 8/4/1/O) Capability
IP parameters
p
Management Protocol:
9500 MPR
SNMPv2c/V3 for supervision
512 Kb/s Radio 512Kb/s Radio
FTP/sFTP
/ for download/backup/restore
/ p/
Telnet/SSH for WT-CLI
NTP for time synchronization
9500 MPR-MSS1c
10/100 Base T
Physical DCN Ports:
10/100 Base T
1x Ethernet RJ45 10/100 BaseT for local access with 10/100 Base T
DHCP (Out of Band)
1x Ethernet RJ45 10/100/1000 BaseT SW configurable
(Out of Band) - MSS 8/4/1/O all have routing capability.
capability From a
DCN/IP point of view it is a router.
Up to 4 x Ethernet RJ45 10/100/1000 BaseT (In Band)
- Each port can use OSPF or static routing ; for each
Up to 2 x Ethernet SFP (In Band)
MSS 8/4/1/O up to 3 different OSPF Areas can be
Nx Radio links 512 Kb/s provisioned excluding
p g the backbone.
- In case of OSPF each address must belong to an OSPF

IP addressing area.
1x IP address for all the radio channels (/32); - The area can be Secondary or Totally Stub.
that is the same as the LocalIP address of the NE.

1x IP address and associated net-mask for each used
Eth port
9500MPR (MSS-O/1/4/8) IPv6/OSPFv3 Capabilities Overview
IPv6 parameters and suggested dimensioning
512 Kb/s
Kb/ RRadio
di
Overview 512Kb/s Radio
• In line with IPv4 DCN. Some constraints detailed 9500 MPR

here
• IPv6 DCN cannot be managed by 1350/1353 NM 10/100 Base T
• No support for dual stack IPv4/IPv6 (only one active 10/100 Base T
stack is managed) 10/100 Base T
• IPv6 is supported only by MSS-O/1/4/8 Physical DCN Ports

• DHCPv6 is not supported. Instead, IPv6 Stateless • 1x Ethernet RJ45 10/100 BaseT for local
Auto-configuration is supported on TMN Local ETH access without support of DHCPv6 (Out of
interface Band) – IPv6 Stateless Auto
Auto-Configuration
Configuration is
supported (always enabled)
Management Protocols
• 1x Ethernet RJ45 10/100/1000 BaseT SW
• SNMPv2 and SNMPv3 for supervision configurable (Out of Band) – IPv6 Stateless
Auto-Configuration
g is supported
pp ((always
y
• FTP and SFTP for download/backup/restore
enabled for TMN interface)
• Telnet and SSH for Ethernet Features Shell
• 4 MAX x Ethernet RJ45 10/100/1000 BaseT (In
• Remark – SNMPv3, SSH and SFTP protocols are Band)
not managed by 1350 / 1353 NM
• 2 MAX x Ethernet SFP (In Band) Remark – max
• HTTP for Debugging (special page on Web Server) 2 TMN in-band interfaces can be configured for
• NTP for time synchronization each node
• nx Radio 512 Kb/s
9500MPR (MSS-O/1/4/8) IPv6/OSPFv3 Capabilities Overview
IPv6 parameters and suggested dimensioning
512 Kb/s Radio
IPv6 addressing 512Kb/s Radio
• 1x IPv6 address for all the radio channels (/128) that

9500 MPR
is the localIP address of the NE.
• 1x IPv6 address and relevant prefix for each used Eth
port 10/100 Base T
• Remark - refer to IANA spec for valid IPv6 10/100 Base T
addresses 10/100 Base T
IPv6 routing
• MSS-O/1/4/8 has routing capability. From DCN/IP point of view it is a router.
• Each port can activate OSPFv3 or static routing; for each MSS-O/1/4/8 up to 3 different
OSPF Areas can be provisioned excluding the backbone.
• Recommended deployment is with maximum 2 OSPFv3 areas per node (including
backbone))
• Remark – OSPFv3 Router ID shall be manually provisioned for each node (see
System Settings) – this is mandatory
• OSPFv3 areas can be either Totally Stub or “not Stub”.
• Recommended
R d d dimensioning
di i i g isi tto limit
li it th
the maximum
i number
b off di
directt neighbors
ighb
connected to an MPR Ethernet interface to 8
9500MPR (MSS 1c) Capability
IP parameters
p
9500 MPR
SNMPv2c for supervision
512 Kb/s
/ Radio 512Kb/s Radio
FTP/sFTP
FTP/ FTP for
f
download/backup/restore/provisioning
9500 MPR-MSS1c
10/100 Base T
Physical DCN Ports: 10/100 Base T
10/100 Base T
2x Ethernet RJ45 10/100 BaseT (Out 10/100 Base T
of Band) 10/100 /1000Base T 10/100 /1000 Base T
1x Ethernet RJ45 10/100/1000 BaseT

(In Band) selectable
1 x Radio 512 Kb/s
IP addressing:
- MSS 1C has routing capability
capability. From a
1x IP address and associated
netmask for each Eth DCN ports - Each port can use static routing ; OSPF
routing available since 3.2 release.
1x IP address for the radio channel
that is the same as the Local IP
address of the NE.
9500MPR (MPR-e) Capability
IP parameters
p
9500 MPR
512 Kb/s Radio 512Kb/s Radio
SNMPv2c for supervision
FTP/sFTP for 9500 MPR-e
download/backup/restore
y 10/100 Base T
10/100 Base T
10/100 Base T
Physical DCN Ports:
1x Ethernet El./Opt. 1000 (In Band)
1 x Radio 512 Kb/s
IP addressing  MPR-e has routing capability. From a

router
1x IP address and relevant net-mask  Each port can use static routing ; OSPF
for the Eth DCN port routing available since 3.2 release.
1x IP address for the radio channel
that
h isi the
h same as the
h Local
L l IP
address of the NE.
9500 MPR
DCN Interconnection using
g Out of Band ((OoB))
512Kb/s Radio 512Kb/s Radio
9500 MPR-e
9500 MPR
10/100 BT
10/100 Base T
512Kb/s Radio
9500 MPR
9500 MPR-MSS1c
MPR MSS1
10/100 BT
512Kb/s Radio
9500 MPR
10/100 Base T
- Multiple MPR nodes can be chained without need for external switch
9500 MPR
DCN Interconnection using
g In Band ((InB))
512Kb/s Radio 512Kb/s Radio
9500 MPR-e
9500 MPR
10/100 BT
10/100 Base T
On these links the Supervision
B
512Kb/s Radio is tagged and sent over the same
links as traffic saving:
9500 MPR
- Ethernet ports
9500MPR-MSS1c
9500MPR MSS1c - IP addresses
1
10/100
512Kb/s Radio
BT
9500 MPR
10/100 Base T
- Multiple
M l i l MPR nodes
d can be
b chained
h i d without
ih need
d ffor externall switch
i h
9500 MPR
DCN Interconnection using In Band (InB) w/ OEM (MPT-GS, MPT-GM, MPT-SUB6)
VID=XXX VID=XXX VID=XXX VID=XXX

IP=x.y.w.z /29
OSPF enabled
IP=x.y.w.z+1 /29
DG=x.y.w.z
DG x.y.w.z
IP=x.y.w.z+2 /29
DG=x.y.w.z
DG x.y.w.z
IP=x.y.w.z+3 /29
OSPF enabled
OEM
MPT-SUB6 PtP
MPT-GS
OEM OEM MPT-GM
9500 MPR 9500 MPR
VID=XXX VID=XXX
IP=x.y.w.z+2 /28 IP=x.y.w.z+4 /28
DG=x.y.w.z OSPF enabled
VID=XXX VID=XXX
IP
IP=x.y.w.z /28 IP +1 /28
IP=x.y.w.z+1
OSPF enabled DG=x.y.w.z
9500 MPR
OEM OEM
VID=XXX VID=XXX
IP x.y.w.z+3
IP=x y w z+3 /28 IP=x.y.w.z+5
IP=x y w z+5 /28
MPT-SUB6 PtMP
OEM
9500 MPR DG=x.y.w.z OSPF enabled
9500 MPR
OEM
- The OEMs use a LAN bridged addressing; they require a Default Gateway
provided by 9500MPR sharing the management channel.
6. Basic MPR Address Provisioning
34
9500MPR Networking
MPR Addressing
g
How many addresses does an MPR need?
A better question might be:
H
How much
h address
dd space d
does an MPR require?
i ?
To answer these questions, we need to know how the interfaces are used in
various configurations.
TMN In-Band #1
VLAN Id: 2152
User Port: 2
Address: Local Address:10.0.36.9
172.22.65.132 TMN In-Band #2
Netmask: VLAN Id: 3720
255.255.255.224
User Port: 1,5
Address: 10.139.22.6
10 139 22 6
Netmask: 255.255.255.248

Address: 192.168.10.0 Address: 172.16.1.86
Netmask: 255.255.255.192 Netmask: 255.255.255.248
35
9500MPR Networking
MPR Addressingg Examples
p – Adding
g an MPR terminal to an
existing Network
Existing Network
*External Local Address:192.168.64.10
Other Network DHCP Server
192.168.64.1
192.168.64.0/28
192 168 64 0/28 TMN Ethernet
Address: 192.168.64.10
Netmask: 255.255.255.240 (/28)
Default External Gateway:192.168.64.1
•In
In the simplest case if an MPR is connected to a small existing external network defined by an
external Router the MPR only requires one IP Address.
•In this configuration, the TMN Ethernet interface is assigned an address and netmask from the
existing subnet, and the MPR Local Address can be set to match. The MPR only will use only one IP
Address.
Address
•Craft computers must use the external network to connect to the MPR.
*If an External DHCP server is present, the internal DHCP server for the TMN Ethernet Port must be
disabled before connecting the MPR to the external network in order to prevent conflicts!
36
9500MPR Networking
MPR Addressing
g Examples
p – Basic Addressing
g
When an MPR is installed at a location where no pre-existing external network is available, the MPR
must, at a minimum, provide a network that can be used for local Craft connections.
All TMN user interfaces to the MPR are Ethernet Broadcast interfaces. The smallest network that can
be defined is a /30. This size network supports
pp two useable addresses one for the TMN Ethernet pport
and one for a Craft computer. If the TMN Ethernet interface is used for this function the MPR internal
DHCP server should be enabled to configure the network interface on the Craft computer when it
connects.
In this example
p the Local Address is set differentlyy from the TMN Ethernet address. This means the
MPR consumes the space of 5 IP addresses: 4 IP addresses for the TMN Ethernet (/30) network and one
for the (different) Local Address.
Local Address: 172.22.46.51
TMN Ethernet Network

10.3.27.4 Network
10.3.27.5 MPR TMN Ethernet Port
10 3 27 6 Craft
10.3.27.6
10.3.27.7 Broadcast
Netmask: 255.255.255.252
Remember: To provision or manage this NE, the Craft or SNMP Manager must specify the 172.22.46.51 Local Address
regardless of whether the physical connection is local or remote.
37
9500MPR Networking
MPR Addressing
g Examples
p – Basic Addressing
g
For larger networks where TMN traffic will be backhauled through an external network use either Port #4 in TMN mode
or one of the TMN In-Band interfaces.
Port #4 TMN Ethernet Network
192.168.137.24 Network Number
Local Address: 192 168 137 25
192.168.137.25
192.168.137.25 MPR Port #4 TMN Ethernet Network
192.168.137.26 Ext Eqpt 1 10.3.27.4 Network Number
192.168.137.27 Ext Eqpt 2 10.3.27.5 MPR TMN Ethernet
192.168.137.28 spare Local 10.3.27.6 Craft
Backhaul
Net
192.168.137.29 spare Net 10.3.27.7 Broadcast
192.168.137.30 Router 1 2 Netmask: 255.255.255.252
192.168.137.31 Broadcast
Netmask: 255.255.255.248
In this example we have an external router for TMN backhaul a few local external devices and use Port #4 in TMN mode. As
shown the smallest subnet that can provide these addresses is a /29. The figure above shows how the addresses could be
assigned.
By setting the Local Address and Port #4 address to be the same, the MPR will appear to be part of the same subnet as the
external equipment from a management perspective.
perspective
This configuration requires the space of eight addresses in the Port#4 TMN network, plus the space of four addresses for the TMN
Ethernet network for a total space of 12 addresses. Note: The spare addresses left over cannot be deployed at another site.
They remains part of this subnet but are available for future site expansion. If the router were the only external device and
addresses for future expansion with external equipment were not needed the router could connect directly to TMN Port #4 and a
/30 network could be used.
Be aware that all TMN traffic is transported through the MPR network at high priority. Normal MPR TMN traffic is relatively low
38
bandwidth. A high volume of Ethernet traffic to and from external equipment via the MPR TMN Network may impact revenue
bearing traffic.
COPYRIGHT © 2015 ThisALLshould
ALCATEL-LUCENT. be considered during the network design phase.
RIGHTS RESERVED.
9500MPR Networking
MPR Addressing
g – TMN In-Band Interface Example
p
SNMP
MPR Data traffic and TMN In-Band
Manager VLAN backhaul through a single Local Address:
172.22.65.132
Manager interface.
Network
Untagged
MPR TMN traffic
Ethernet Data TMN Ethernet Network

TMN In-Band #1
Core Data 10.3.27.4 Network Number
VLAN Id: 2152
Network 10.3.27.5 MPR TMN Ethernet
User Port: 5 (SFP)
802.1q tagged 10.3.27.6 Craft
TMN traffic Address: 172.22.65.132
10.3.27.7 Broadcast
VLAN Id: 2152 Netmask: 255.255.255.224
Netmask: 255.255.255.252
•This example shows TMN In-Band #1 configured to use Optical SFP Port #5
•The MPR data traffic also flows through this same interface. The TMN In-Band VLAN Id must be unique in
the data flow so the TMN traffic can be identified and controlled by the external equipment.
•Intermediate routers forward the combined TMN In-Band VLAN and MPR data traffic to appropriate
destinations. TMN In-Band traffic can be steered to the appropriate destination using the VLAN Id. The
final external router strips the TMN VLAN Id tags from the TMN packets on egress and sends them to the
Manager network.
TMN Traffic coming from the Manager and destined for the TMN Network must be tagged at ingress with
•TMN
the TMN VLAN Id before heading to the 9500MPR.
39
7. Interconnecting Multiple MPR
Shelves
40
9500MPR Networking
MPR Addressing – Shelf Interconnect using TMN Port #4
I t f
Interfaces MPR #1 Dir #35
Connecting TMN between two MPR shelves

MPR #1
Local
IP Addr Equipment Comment Craft
10.3.27.64 Network Netmask: 255.255.255.252
10.3.27.65 MPR #1 Port #4 Also MPR #1 Local Address MPR #2
10.3.27.66 MPR #2 Port #4 Also MPR #2 Local Address Local
10.3.27.67 Broadcast Craft
MPR #2 Dir #38
 P t #4 TMN ports
Port t are addressed
dd d in
i the
th same /30 subnet
b t and
d connected
t d together.
t th
 TMN Traffic flowing through the site via MPR #1 Dir #35 and MPR #2 Dir #38 will be routed through
the TMN Port #4 interfaces.

41 3EM 23718 1306 BVZZA
Any MPR Data traffic must be cabled separately between shelves.
shelves This interconnect method offers
Ed02it13
maximum 9500
flexibility withMPR TMN
respect to how data traffic is interconnected between the two shelves.
Networking
 Each TMN Ethernet interface is configured with it’s own unique /30 subnet and the DHCP server in
each MPR S.
is enabled
Winslow(details not shown). This configuration permits independent local Craft access
to each MPR as well as the entire TMN Network
Network.
 The site consumes the space of 12 addresses, four for the Port #4 /30 and eight more for the two
/30 Craft networks.
9500MPR Networking
MPR Addressing
g – Stacked Shelves with External Equipment
q p
MPR #1 Dir #35
and Switch
Connecting multiple MPR shelves at a site using the Port #4 TMN interfaces
Port #4 TMN Network (/29) MPR #1

Local
10.3.27.64 Network
Craft
10.3.27.65 MPR #1 External
Switch MPR #2
10.3.27.66 MPR #2
Local
10.3.27.67 MPR #3 Ext #1 Craft
10.3.27.68 External Eqpt #1
Ext #2 MPR #3
10.3.27.69 External Epqt #2
10.3.27.70 Spare Local
Craft
10.3.27.71 Broadcast
MPR #3 Dir
Di #38
Netmask: 255.255.255.248
All Port #4 TMN ports are addressed in the same /29 subnet and connected together with an external switch. External
site equipment may be connected to the TMN Network using via the switch.
As before, TMN Traffic flowing through the site via MPR #1 Dir #35 and MPR #3 Dir #38 will pass through the external
switch. MPR Data traffic must be cabled separately between shelves.
As before local management is through the TMN Ethernet interfaces (details not shown).
The site consumes 20 addresses, eight for the /29 Port #4 network and twelve for the three /30 Craft networks.
42
9500MPR Networking
MPR Addressing – Stacked Shelves with External Equipment and Switch
MPR #1 Dir #35
Connecting multiple MPR shelves at a site using TMN In-Band interfaces
TMN In-Band Network
10.3.27.64 Network
10.3.27.65 MPR #1, VLAN Id 4079, optical Port #6
MPR #1
10 3 27 66 MPR #2,
10.3.27.66 #2 VLAN Id 4079
4079, optical Ports #5 and #6 Local
10.3.27.67 MPR #3, VLAN Id 4079, optical Port #5 Craft
10.3.27.68 Spare
MPR #2
10.3.27.69 Spare
Local
10.3.27.70 Spare
Craft
Netmask: 255.255.255.248 MPR #3
Similar to the previous slide but by using In-Band Interfaces Local

switch functionality can be moved into MPR #2. Shelf-to-shelf Craft
U
User D
Data
t traffic
t ffi iis able
bl tto fl
flow th
through
gh th
the same cables.
bl MPR #3 Dir
Di #38
 All TMN In-Band ports are addressed in the same /29 subnet and with the same VLAN 4079. Putting all In-Band ports in the same subnet
avoids an extra routing hop between MPR #1 and MPR #3. In larger sites having a single subnet for interconnecting all shelves will improve
address efficiency.
 MPR #2 shelf has two User ports associated with VLAN 4079 and provides the switch functionality to connect MPR#1 with MPR #3. TMN Traffic
flowing through the site via MPR #1 Dir #35 and MPR #3 Dir #38 will pass through the TMN In-Band VLAN 4079 optical switched ports in MPR #2
 Shelf-to-shelf MPR Data traffic can be carried across the same Layer 2 physical connections (but not in the TMN VLAN). See the notes on In-
Band interfaces in Section 3.
 Optical ports are shown in this example. A mix of Electrical and optical or all Electrical is possible. Since Data traffic also uses these
connections
ti using
i 1000Mb/s
1000Mb/ speed d is
i recommended
d d ffor El
Electrical
t i l ports.
t
 Local management is through the TMN Ethernet interfaces (details not shown).
43
 The site consumes the space of 20 addresses, eight for the /29 and twelve for the three /30 Craft networks.
9500MPR Networking
MPR Addressing – Another Shelf Interconnect using TMN In-Band Interfaces
MPR #1 Dir #35
Another variation connecting multiple MPR shelves at a site using TMN In-
Band interfaces, external equipment, and no external switch
Ext #1
IP Addr Equipment Comment
10.3.27.64 Network Netmask: 255.255.255.252 MPR #1
Local
10.3.27.65 MPR #1 Port #4 Also MPR #1 Local Address Craft
10.3.27.66 Ext #1 External Equipment Ext #2
10.3.27.68 Network Netmask: 255.255.255.252 MPR #2
Local
10.3.27.69 MPR #1 In-Band #1Eth Port #3, Vlan ID: 1001 Craft
10 3 27 70
10.3.27.70 MPR #2 In-band
I b d #1Eth P Portt #3,
#3 Vlan
Vl ID:
ID 1001
10.3.27.72 Network Netmask: 255.255.255.252 MPR #2 Dir #38
10.3.27.73 MPR #2 Port #4 Also MPR #2 Local Address
10.3.27.74 Ext #2 External Equipment
 This example uses a total of five /30 subnets. This configuration is expensive in terms of the
amount of address space required (Space of 20 addresses for 6 devices) but requires no external
switch while supporting one external TMN device per MPR shelf.
 The two TMN Ethernet ports are dedicated for Craft use with DHCP enabled. Craft addressing is not
shown, but would be the same as in other examples.
 The path for TMN Traffic flowing through the site via Dir #35 and Dir #38 is via the TMN In-Band
interconnection.
 Shelf-to-shelf MPR Data traffic will also flow across the same Layer2 physical connections. See the
notes on In-Band interfaces in Section 3.
8. Craft and Management
Communication Requirements
45
9500MPR Networking
Management
g
We know up to five addresses can be assigned to each MPR,
Which address must be used for Craft access?
Which address must be used for SNMP Management?
TMN In-Band Interface #1
? Add
Address: 10.78.101.0
0 8 0 0
Netmask: 255.255.255.192 Local Address:172.22.46.51?
TMN In-Band
In Band Interface #2
?
Address: 172.22.65.0
Netmask: 255.255.255.192 TMN Ethernet ?
Port #4 TMN Address: 10.0.36.9
?
Address: 192.168.10.0 Netmask: 255.255.255.248
Netmask: 255.255.255.192
46
9500MPR Networking
Management
g
The Local Address is used to provision and Manage the MPR.
Regardless of how either the TMN Ethernet, Port #4 TMN, or TMN In-Band Interfaces are
configured,
g , the Local Address is the one to specify
p y in NEtO when using
g the Craft,, or at an
SNMP Manager. NEtO Example
TMN In-Band
I B d #1
Address: z.z.z.z
Netmask: nnn.nnn.nnn.nnn
TMN In-Band #2
Address: w.w.w.w
TMN Ethernet
Netmask:nnn.nnn.nnn.nnn
Port #4 TMN Address: yyy.yyy.yyy.yyy
Address: xxx.xxx.xxx.xxx Netmask: mmm.mmm.mmm.mmm
Netmask: nnn.nnn.nnn.nnn
Connecting to the wrong address is the primary reason for

provisioning problems with the MPR !
47
9500MPR Networking
Management
g
When a Craft computer is directly connected to the TMN Ethernet subnet, NEtO will find
MPR Local Addresses through a Layer 2 MPR Discovery Protocol. Double-clicking on a
Discovered NE entry will copy the address to the correct location for connection.
NEtO Example
E l
L2 Discoverry Protocol
48
9500MPR Networking
Management
g –Using
g the Local Address
Why Must the Local Address be used for provisioning?
1 The MPR SNMP Agent responds at all the MPR IP Addresses
1. Addresses, but SNMP
Traps and Notifications only originate from the Local Address.
• When the Craft performs complex multi-step SNMP operations
such as cross-connections,
cross connections it expects SNMP Notifications
verifying completion of the intermediate steps. The Craft will
be listening for these Notifications to come from the address
specified in NEtO.
NEtO It will ignore Notifications that come from
other (unknown) addresses. If the Craft does not receive the
proper responses provisioning fails.
49
9500MPR Networking
Management
g –Using
g the Local Address ((Continued))
Why Must the Local Address be used for provisioning (continued)?
2. SNMP Managers need to know which IP Addresses will be sending Traps so
that Alarms can be associated with the proper NE.
NE
• The 5620SAM is aware of the MPR operation. When the SAM identifies
an MPR TMN Interface during discovery, it inspects the appropriate SNMP
MIB objects to determine the Local Address of that NE.
NE When Traps or
Notifications arrive, they can be correlated with the proper NE.
• Third party Managers using auto-discovery in an MPR network will likely
find a mix of various TMN Ethernet interface and Local Addresses unless
the discovery can be restricted to just the range of addresses used for
Local Addresses. The usual symptoms of simply auto-discovering in an
MPR network are multiple copies of each NE: one for each active TMN
i t f
interface IP address,
dd or by
b Traps
T that
th t arrive
i ffrom ‘‘unknown’
k ’ NE
NEs where
h
the source address can be correlated with an MPR Local Address
somewhere in the network.
50
9500MPR Networking
Network Communication
Local Address 1 Local Address 2 Local Address 3 TMN

Port #4
In-Band
TMN Subnet RF PPP Link RF PPP Link Subnet
TMN
X TMN TMN Y
Ethernet
Ethernet Ethernet
Subnet
VLA
Subnet Subnet
AN
A
Local B C
Non-VLAN Local
Craft Local Aware
Craft Craft
equipment
External
Network SNMP SNMP External
Network
M
Manager
Manager
• Communication requirements with external networks
• SNMP packets from the Local Address of each NE must have a route to the managers. This is
usually provided by either a Static Default Route at the MPR Network borders,
borders or learned via
OSPF from external Neighboring routers.
• External routers must be either manually configured to use an MPR as the gateway to the
network of Local Addresses or they must learn the gateways to the MPR network exchanging
routes with an MPR through OSPF.
51
• TMN In-Band interfaces must connect to VLAN aware equipment.
9. Planning and Addressing a
Network
52
TMN Network Planning
g
SNMP Fiber or other R2
Manager
Site
Network
External
Network
E 1 2
R1 A B D
1
Site 1 2 3
Network
Ext Existing C
DHCP external
Server
S equipment
i t
Consider the above network. For TMN purposes, it is a combination of Linear and Ring topologies.
External equipment [ 1 2 3 ] to be managed is located at sites B, D, and E.
H
How could
ld this
hi network
kbbe addressed?
dd d?
53
g
Definitions for the Example:
The type of addresses needed will depend on whether we use IPv4 or IPv6 and the
type of connectivity required with external networks.
If the management network is private we can use address space intended for
private networks.
For IPv4 addresses for private networks are defined in RFC1918:
10.0.0.0 /8
172.16.0.0 /12
192.168.0.0 /24
For IPv6 they are defined in RFC4193
Addresses typically assigned from the fd00:: /8 sub-range (L-bit set to

1). A suitable Locally Assigned Global ID will be required. Refer to the
RFC for more information.
For this example we will use IPv4 with Private Addressing
54
g
Definitions for the Example (continued):
Site A is an existing site where other equipment is already installed. An
MPR will be added to the site. The existing subnet is 192.168.19.0/27.
Router R1 is at 192.168.19.1. The address available for the MPR is
192.168.19.23. A local external DHCP server is available.
Site B is
Si i a junction.
j i There
h are three
h externall d
devices
i to b
be managed
d via
i
the TMN Network.
Site C is a repeater with no external equipment.
Site D is a repeater with one external device.
Site E is a repeater with two external devices. A new router (R2)
connected via an external link will be added to p provide an alternate
pathway for TMN Traffic. The MPR DHCP server will be used to provide
DHCP services for all transient craft devices at this site.
Site F is a repeater
p with no external equipment.
q p
55
g
Definitions for the Example (continued)
OSPF will be enabled within the network
The recommended configuration is to enable OSPF within the MPR
network whenever possible.
•Correctly configuring Static routing internally within the MPR
network
t k can be
b very complexl ffor anything
thi other
th ththan ttrivial
i i l li
linear
networks and is not recommended.
The MPR network will be an Autonomous OSPF network. It will use Static
routing
ti att th
the b
borders
d
The use of OSPF or Static routing between the MPR network border
and external networks is a network design choice. When OSPF
monitors the status of a link carrying TMN Traffic and the link fails it
may be possible for OSPF to reroute the TMN traffic to use an
alternate gateway provided one is available.
56
g
Definitions for the Example (continued)
At site A where an external network is available, the MPR will be a member of the
external network, using the Port #4 TMN interface. The MPR will be configured to
use router R1 as the Default Gateway for reaching all other external networks.
At site E, a new local network will be defined using router R2. This network will
provide an alternate external route for TMN traffic. The MPR at site E will be come
p
a member of this network and will use Router R2 as the Default Gateway to reach
the external networks
The MPR Local Address will be set to match the TMN Ethernet Port address at all
sites.
DHCP will be used for configuration of Craft computers.
Using the MPR internal DHCP server whenever possible is recommended.

recommended The
internal DHCP server will correctly configure external Craft computers to
communicate with the local MPR and the greater TMN Network. This eliminates
the need for users to know how to manually configure a laptop at each site.
57
TMN Network Planning – New Addresses Requirements
Site TMN Ethernet Network Port #4 TMN Network Comments
Interface Interface
Site A 4 address subnet (/30) 0 new addresses (MPR assigned Port #4 TMN interface will be connected with the local site
a spare address from the network. The separate TMN Ethernet port will remain active
g external network))
existing g
with DHCP for emergencyy Local Craft access.
Site B 4 address subnet (/30) 8 address subnet (/29) Connect external equipment to the Port #4 TMN interface.
Site C 4 address subnet (/30) (disabled) No external equipment. Direct craft connections only.
Site D 8 address subnet (/29) (disabled) External device connected to the TMN Eth Port. No
g advantage
addressing g to splitting
p g the subnet between TMN
Eth and Port #4 TMN
Site E 16 address subnet (/28) (disabled) Extra addresses reserved to allow adding equipment as the
network expands.
Site F 4 address subnet (/30) (disabled) No external equipment. Direct craft connections only.
Total 40 addresses 8 addresses
The TMN Ethernet port with DHCP enabled will be active at all sites.
The Port #4 TMN interface is only enabled at two sites: A and B
The Addressing for the Port #4 interface at Site A is not shown here. This interface is connected
to and uses a spare address from the existing external site network. This was stated in the
Definitions near the beginning of this example.
At sites where there is external equipment it is attached to the MPR TMN interface using an external
switch.
With the network plan shown in the previous table, this network requires the
space of at least 48 addresses.
Of the 48:
6 addresses are assigned as MPR Local Address/TMN Ethernet addresses
1 address is assigned as a TMN Port #4 address
7 addresses are assigned to external equipment (including router R2)
14 addresses are reserved for use by the internal MPR DHCP servers
6 Spare
S addresses
dd
Netmasks force subnets to start and end on specific boundaries. For example
a subnet of 8 addresses must start at an address that is evenly divisible by 8.
Before we request address space from our Network Administrator, we first
need to verify what size address block will hold all our subnets. This is shown
on the next slide.
MPR A TMN Ethernet Subnet MPR C TMN Ethernet Subnet MPR E TMN Ethernet Subnet
Netmask: 255.255.255.252 Netmask: 255.255.255.252 Netmask: 255.255.255.240
xxx.xxx.xxx.0 Network (/30) xxx.xxx.xxx.16 Network (/30) xxx.xxx.xxx.32 Network (/28)
xxx.xxx.xxx.1 A TMN Eth Port xxx.xxx.xxx.17 C TMN Eth Port xxx.xxx.xxx.33 DHCP Assigned
xxx xxx xxx 2
xxx.xxx.xxx.2 DHCP Assigned xxx xxx xxx 18
xxx.xxx.xxx.18 DHCP Assigned xxx xxx xxx 34
xxx.xxx.xxx.34 DHCP Assigned
xxx.xxx.xxx.3 Broadcast xxx.xxx.xxx.19 Broadcast xxx.xxx.xxx.35 DHCP Assigned
xxx.xxx.xxx.36 DHCP Assigned
MPR B TMN Ethernet Subnet MPR F TMN Ethernet Subnet xxx.xxx.xxx.37 DHCP Assigned
Netmask: 255.255.255.252 Netmask: 255.255.255.252 xxx.xxx.xxx.38 DHCP Assigned
xxx.xxx.xxx.4 Network (/30) xxx.xxx.xxx.20 Network (/30) xxx.xxx.xxx.39
39 DHCP Assigned
A ig d
xxx.xxx.xxx.5 B TMN Eth Port xxx.xxx.xxx.21 F TMN Eth Port xxx.xxx.xxx.40 E TMN Eth Port
xxx.xxx.xxx.6 DHCP Assigned xxx.xxx.xxx.22 DHCP Assigned xxx.xxx.xxx.41 E Ext Eqpt 1
xxx.xxx.xxx.7 Broadcast xxx.xxx.xxx.23 Broadcast xxx.xxx.xxx.42 E Ext Eqpt 2
xxx.xxx.xxx.43 Spare
MPR B Port #4 TMN Subnet MPR D TMN Ethernet Subnet
xxx.xxx.xxx.44
44 S
Spare
Netmask: 255.255.255.248 Netmask: 255.255.255.248
xxx.xxx.xxx.45 Spare
xxx.xxx.xxx.8 Network (/29) xxx.xxx.xxx.24 Network (/29)
xxx.xxx.xxx.46 Router R2
xxx.xxx.xxx.9 B Port #4 xxx.xxx.xxx.25 DHCP Assigned
xxx.xxx.xxx.47 Broadcast
xxx.xxx.xxx.10 B Ext Eqpt 1 xxx.xxx.xxx.26 DHCP Assigned
xxx.xxx.xxx.11 B Ext Eqpt 2 xxx.xxx.xxx.27 DHCP Assigned
xxx.xxx.xxx.12 B Ext Eqpt 3 xxx.xxx.xxx.28 D TMN Eth Port
xxx.xxx.xxx.13 Spare xxx.xxx.xxx.29 D Ext Eqpt 1
xxx.xxx.xxx.14 Spare xxx.xxx.xxx.30 Spare
xxx.xxx.xxx.15 Broadcast xxx.xxx.xxx.31 Broadcast
This shows
Thi h how
h the
h required
i d subnets
b could
ld map iinto an arbitrary
bi bl
block
k off 48 contiguous
i addresses.
dd O
Other
h
arrangements are possible. Notice the addresses for MPR F are between the addresses of MPR C and MPR
D. With OSPF enabled, there will be no routing complications resulting from this choice.
The previous slide shows how this network design will fit within the total space of 48
addresses. This is the minimum sized block number of addresses we must request to
deploy this network.
Depending on the availability of IP address space:
we could be assigned a single /26 block with 64 addresses.
If the availability of new address space is limited, we might be assigned exactly 48
addresses broken down as:
a /27 block (32 addresses) plus
a /28 (16 addresses)
If assigned separately like this, the address blocks might not be contiguous.
With OSPF enabled this requires no special configuration for routing.
For this example, we’ll assume we’ve been assigned 172.28.137.64 /26
The block contains 64 contiguous addresses ranging from 172.28.137.64 to
172.28.137.127
We’ll further divide this block of addresses into our own subnets following the
plan.
MPR A TMN Ethernet Subnet MPR C TMN Ethernet Subnet MPR E TMN Ethernet Subnet
Netmask: 255.255.255.252 Netmask: 255.255.255.252 Netmask: 255.255.255.240
172.28.137.64 Network (/30) 172.28.137.80 Network (/30) 172.28.137.96 Network (/28)
172.28.137.65 A TMN Eth Port (L) 172.28.137.81 C TMN Eth Port (L) 172.28.137.97 DHCP Assigned
172 28 137 66
172.28.137.66 DHCP Assigned 172 28 137 82
172.28.137.82 DHCP Assigned 172 28 137 98
172.28.137.98 DHCP Assigned
172.28.137.67 Broadcast 172.28.137.83 Broadcast 172.28.137.99 DHCP Assigned
MPR B TMN Ethernet Subnet MPR F TMN Ethernet Subnet 172.28.137.101 DHCP Assigned
Netmask: 255.255.255.252 Netmask: 255.255.255.252 172.28.137.102 DHCP Assigned
172.28.137.68 Network (/30) 172.28.137.84 Network (/30) 172 28 137 103
172.28.137.69 B TMN Eth Port (L) 172.28.137.85 F TMN Eth Port (L) 172.28.137.104 E TMN Eth Port (L)
172.28.137.70 DHCP Assigned 172.28.137.86 DHCP Assigned 172.28.137.105 E Ext Eqpt 1
172.28.137.71 Broadcast 172.28.137.87 Broadcast 172.28.137.106 E Ext Eqpt 2
172.28.137.107 Spare
MPR B Port #4 TMN Subnet MPR D TMN Ethernet Subnet
172 28 137 108
172.28.137.108 S
Spare
Netmask: 255.255.255.248 Netmask: 255.255.255.248
172.28.137.109 Spare
172.28.137.72 Network (/29) 172.28.137.88 Network (/29)
172.28.137.110 Router R2
172.28.137.73 B Port #4 172.28.137.89 DHCP Assigned
172.28.137.111 Broadcast
172.28.137.74 B Ext Eqpt 1 172.28.137.90 DHCP Assigned
172.28.137.75 B Ext Eqpt 2 172.28.137.91 DHCP Assigned
MPR
PR A Port
P #4
# TMN Subnet
S b Address
172.28.137.76 B Ext Eqpt 3 172.28.137.92 D TMN Eth Port (L) assignments from
Netmask: 255.255.255.224
172.28.137.77 Spare 172.28.137.93 D Ext Eqpt 1 the existing
192.168.19.1 Router R1 external network
172.28.137.78 Spare 172.28.137.94 Spare
192.168.19.23 MPR A Port #4 at Site A.
172.28.137.79 Broadcast 172.28.137.95 Broadcast
Merging our assigned addresses into the tables shows how to address our equipment.
MPR Local addresses will be set to match the TMN Ethernet Port as specified in the Plan and are labeled (L)
for easy identification.
g
172.28.137.112 Unused
172.28.137.113 Unused
172 28 137 114
172.28.137.114 Unused
172.28.137.115 Unused
172.28.137.116 Unused
172.28.137.117 Unused
172.28.137.118 Unused
172 28 137 119
172.28.137.119 Unused
172.28.137.120 Unused
172.28.137.121 Unused
172.28.137.122 Unused
172.28.137.123 Unused
172 28 137 124
172.28.137.124 U
Unused
d
172.28.137.125 Unused
172.28.137.126 Unused
172.28.137.127 Unused
Sixteen addresses out of the assigned 64 remain unused.
Th
These will
ill b
be reserved
d ffor ffuture
t expansion
i off th
the network.
t k
63
Per the plan:
A. The MPR at Site A will be configured as an ASBR with a static route to pointing
to R1 as it’s default gateway.
 This is required so that TMN traffic destined to leave the MPR TMN
Network will have a way out
B. Conversely, External router R1 must be configured to use MPR A as a gateway to
access the network 172.28.137.64 /26
C. The MPR at site E will be configured as an ASBR with a static route to use R2 as
it’s default gateway
 This defines an alternate gateway for traffic leaving the MPR TMN
network.
D. External router R2 must also be configured to use MPR E as a gateway for
network 172
172.28.137.64
28 137 64 /26
 This route provides an alternate way into the MPR TMN Network.
g – Growing
g the network
SNMP R2
Fiber or other
Manager
Site
Network
G H
External
Network
E 1 2 3 4 5
1
F J
D
R1 A B 1
1
Site 1 2 3 K
Network
Ext C 1
DHCP
Server
 What if the network grows and we need to expand by adding Sites G, H, J, and K?
 What if Site F, where we originally had no plans for expansion suddenly needs a new external device?
 What if the old expansion plans change

change, and the additional external equipment planned for site E will now be
deployed at site H, leaving site E with an excess of unused addresses?
 We
65
know we can assign some of the addresses from space left over from the original /26, but we don’t have
enough addresses
COPYRIGHT © 2015 for
ALCATEL-LUCENT. ALL all
RIGHTS new the equipment. We’ll have to request additional address space.
RESERVED.
TMN Network Planning – Growing the network
Here’s the new plan:
Site TMN Ethernet Network Port #4 TMN Network Comments
Site E Original 16 address subnet now 8 address subnet (/29) Extra address space no longer needed. So we split
a 4 address subnet ((/30)) (local reallocation) the 16 address subnet,
subnet allocating 8 addresses to Port
#4 TMN and 4 addresses to TMN Ethernet. The four
recovered addresses are moved to site F.
Site F (Keep existing subnet) 4 address subnet (/30) Add subnet to Port #4 TMN interface for new
(reallocated addresses equipment, using the address space recovered from
from Site E) Site E
E.
Site G 4 address subnet (/30) (disabled) No external equipment. Direct craft connections
only.
Site H 4 address subnet (/30) 8 address subnet (/29) External eqpt connected to Port #4 TMN interface.
Site J 8 address subnet (/29) (disabled)
Site K 8 address subnet (/29) (disabled)
Total 24 new addresses 8 new addresses
Expansion of the network will require the space of 32 addresses, 16 of which were left over from our
original allocation, and 16 new addresses.
We request a new block of 16 addresses from our Network Administrator:
Our new address block assigned is: 172.30.10.0 /28

With the new expanded network plan, original subnets at site A, B,C, D, and the TMN
Ethernet subnet at site F remain unchanged. The addresses are repeated here:
MPR A TMN Ethernet Subnet MPR C TMN Ethernet Subnet
N t
Netmask:
k 255
255.255.255.252
255 255 252 N
Netmask:
k 255
255.255.255.252
255 255 252
172.28.137.64 Network (/30) 172.28.137.80 Network (/30)
172.28.137.65 A TMN Eth Port (L) 172.28.137.81 C TMN Eth Port (L)
172.28.137.66 DHCP Assigned 172.28.137.82 DHCP Assigned
MPR B TMN Ethernet Subnet MPR D TMN Ethernet Subnet

Netmask: 255.255.255.252 Netmask: 255.255.255.248
172.28.137.68 Network (/30) 172.28.137.88 Network (/29)
172.28.137.69 B TMN Eth Port (L) 172.28.137.89 DHCP Assigned
172 28 137 70
172.28.137.70 DHCP Assigned 172 28 137 90
172.28.137.71 Broadcast 172.28.137.91 DHCP Assigned
172.28.137.92 D TMN Eth Port (L)
MPR B Port #4 TMN Subnet 172.28.137.93 D Ext Eqpt 1
Netmask: 255.255.255.248 172.28.137.94 Spare
172.28.137.72 Network ((/29)) 172 28 137 95
172.28.137.95 Broadcast
172.28.137.73 B Port #4
172.28.137.74 B Ext Eqpt 1 MPR F TMN Ethernet Subnet
172.28.137.75 B Ext Eqpt 2 Netmask: 255.255.255.252
172.28.137.76 B Ext Eqpt 3 172.28.137.84 Network (/30)
172.28.137.77 Spare 172.28.137.85 F TMN Eth Port ((L))
172.28.137.78 Spare 172.28.137.86 DHCP Assigned
TMN Network Planning NEW
OLD MPR E TMN Ethernet Subnet
Netmask: 255.255.255.248
MPR E TMN Ethernet Subnet
172.28.137.96 Network (/30)
Netmask: 255.255.255.240
172.28.137.97 MPR E TMN Eth (L)
172.28.137.96 Network (/28)
172 28 137 97
A ig d
172.28.137.99 Broadcast
172.28.137.99 DHCP Assigned MPR F Port #4 TMN Subnet
172.28.137.100 DHCP Assigned Netmask: 255.255.255.252
172.28.137.101 DHCP Assigned 172.28.137.100 Network (/30)
172 28 137 102
A i d 172.28.137.101 MPR F Port #4
172.28.137.103 DHCP Assigned 172.28.137.102 F Ext Eqpt 1
172.28.137.104 E TMN Eth Port (L) 172.28.137.103 Broadcast
172.28.137.105 E Ext Eqpt 1
172.28.137.106 E Ext Eqpt 2 MPR E Port #4 TMN Subnet
172.28.137.107 Spare Netmask: 255.255.255.248
255 255 255 248
172.28.137.108 Spare 172.28.137.104 Network (/29)
172.28.137.109 Spare 172.28.137.105 E Ext Eqpt 1
172.28.137.110 Router R2 172.28.137.106 E Ext Eqpt 2
172.28.137.111 Broadcast 172.28.137.107 Spare
172 28 137 108
172.28.137.108 S
Spare
172.28.137.109 MPR E Port #4
172.28.137.110 Router R2
172.28.137.111 Broadcast
This is how the old subnet E can be split

p to recover some unused address space.
p Half the address space
p
with the external equipment moves to the Site E Port #4 TMN subnet with a new netmask. Four
addresses from the original subnet remain assigned to the MPR E TMN Eth subnet with a new netmask.
The remaining four addresses are relocated to Site F as a new Port #4 subnet. New or changed
addressing parameters are highlighted in red.
TMN Network Planning – Growing the Network
MPR G TMN Ethernet Subnet
Netmask: 255.255.252
172.28.137.112 Network (/30)
172.28.137.113 MPR G TMN Eth (L)
172.28.137.115 Broadcast
MPR H TMN Ethernet Subnet

Netmask: 255.255.255.252
172.28.137.116 Network (/30)
172.28.137.117 MPR H TMN Eth (L)
172.28.137.119 Broadcast
MPR H Port #4 TMN Subnet

N
Netmask:
k 255
255.255.255.248
255 255 248
172.28.137.120 Network (/29)
172.28.137.121 MPR H Port #4
172.28.137.122 H Ext Eqpt 1
172.28.137.123 qp 2
H Ext Eqpt
172.28.137.124 H Ext Eqpt 3
172.28.137.125 Spare
172.28.137.126 Spare
172.28.137.127 Broadcast
The unused 16 addresses from the original /26 allocation are split into subnets and assigned
at sites G and H.
g – Growing
g the Network
MPR J TMN Ethernet Subnet MPR K TMN Ethernet Subnet
Netmask: 255.255.255.248 Netmask: 255.255.255.248
172.30.10.0 Network (/29) 172.30.10.8 Network (/29)
172.30.10.4 MPR J TMN Eth (L) 172.30.10.12 MPR K TMN Eth (L)
172.30.10.5 J Ext Eqpt 1 172.30.10.13 K Ext Eqpt 1
172.30.10.6 Spare 172.30.10.14 Spare
172 30 10 7
172.30.10.7 Broadcast 172 30 10 15
•This slide shows address assignments using the new block of 16 addresses
•OSPF will provide the necessary route changes within the MPR TMN Network.
•External routers R1 and R2 will need additional static routes using MPR A and MPR E
respectively as gateways to reach the new 172.30.10.0/28 addresses.
•With OSPF managing routes within the MPR network and DHCP configuring the Craft
computers these are the only routing changes required.
70
10. Configuring the MPR
71
9500MPR Networking
MPR Addressing
g – Setting
g the Local Address
Th Local
The L l Address
Add is
i set in
i the
h Local
L lCConfiguration
fi i didialog
l b box.
a) Access the Local Configuration from the Menu by selecting:
Configuration->Network Configuration->Local Configuration
b) Enter the Local Address and click Apply
• Note: There is no Netmask setting associated with the Local Address, but the Craft utility restricts
Local Address provisioning as if a /24 netmask was in effect. This means Local Addresses ending in .0
or .255
255 cannot be
b assigned!
i d! This
Thi iis a k
known li
limitation.
i i
• The MPR will reboot after this address is changed.

72
• After the reboot, you will need to reconnect using the new Local Address
9500MPR Networking
MPR Addressing – Preparing Port #4 for TMN mode
2
3
Before Port #4 can be configured for TMN any User port settings must
be disabled and returned to defaults.
5
1. In the Craft Equipment View, double-click on the Core Main
module. This opens the Core Main View
7
2. In the View, select the Ethernet Physical Interface tab.
3. Highlight the Ethernet Port#4 interface.

6
4. Verify Port #4 status shows Disabled. The port status shown
here must be Disabled before TMN mode can be used.
used
5. If it is necessary to Disable the port, select the Settings tab at

the bottom of the panel.
6. Uncheck Auto Negotiation Status, and click Apply at the

b tt
bottom.
7. Uncheck the Enabled box in the Port Status area and click
73 Apply.
9500MPR Networking
MPR Addressing – Configuring MPT RF PPPoE Links
2
1 3
For RF PPPoE interfaces:
1. In the Craft Equipment View double-click on the

associated EAS Board. This opens the EAS Main
View.
2. In the View panel select the desired MPT-HL Port
3. Click on the Settings Tab 4

4. In the PPP RF area Enable the interface and
configure as needed. No IP Address is assigned,
the Local Address will be used.
5. Click on Apply
6. After both ends of the radio hop have been 6

configured and the RF PPP link comes up the
detected far end MPR Local Address will show in 5
the Remote Address box.
74
9500MPR Networking
MPR Addressing – Configuring the TMN In-Band Interfaces in R03.00.00 and later
2
1
The TMN In-Band interfaces:
1. In the Craft Equipment View, double-click on the

Core Main module. This opens the Core Main View
4
2. In the View select the TMN Interface tab. Current
interface settings are shown in the table.
table
3. Highlight a TMN In-Band interface in the equipment

tree or table to configure.
4. To change the parameters, select the Settings tab

in the
h bbottom panel.l Parameters unique to theh
TMN In-Band interfaces are the VLAN ID and the
Associated Ethernet Ports. Selection of multiple
Ethernet ports is allowed. All selected ports will 5
become members of the specified VLAN.
5. Click on Apply.
75
9500MPR Networking
MPR Addressing – Configuring Static Routes
2
Static Route Configuration:
1
1. Access the
A th panell tto configure
fig static
t ti routing
ti g ffrom th
the ffrom th
the M
Main
i MMenu b
by
3
selecting Configuration->Network Configuration ->IP Configuration ->IP Static
Routing Configuration
2. To add a new static route select the type of route. Use Network for a route
to a range of addresses, use Host for a route to a single device.
4a 4b
3. Enter the destination network number and mask or else the destination host
IP Address as appropriate.
4. Configure the Interface Choice

5
a) If the gateway is an IP address,
address chose Gateway IP Address and enter
the address.
b) If the gateway is a radio direction choose the Point to Point Interface

and select the appropriate interface from the dropdown. See the
detail
Point to Point interfaces are
Gateways must always be on a directly attached network. selected from a dropdown
5. Click Create.
76
9500MPR Networking
MPR Addressing – Defining MPR OSPF Areas
1
2
OSPF A
Areas are configured
fi d in
i the
th OSPF A
Area C
Configuration
fi ti panel:
l
1. Access the OPSF Area Configuration from the from the

Main Menu by selecting Configuration->Network
Configuration ->IP Configuration ->OPSF Area Configuration
2. To add a new OSPF Area, check the ‘New’ checkbox, and

fill in the OSPF Area parameters. OSPF Area Addresses on
the MPR are entered as dotted quads like an IP Address. If 3
you are defining a Stub Area, set the Stub Flag to True
3
3. Cli k on Create.
Click C
4. Id values at the top left (0..3) will be used when

associating a particular OSPF area with an interface: TMN
Ethernet, TMN Port #4, TMN In-Band, or Radio. See the
next slide
77
9500MPR Networking
MPR Addressing
g – Selecting
g an OSPF Area for a TMN Interface
1. When provisioning a TMN
Interface, the OSPF Area is
assigned using the associated Id
from the OSPF Area Configuration
g
window.
2. In the Craft, select the appropriate

Id value from the drop down lists.
TMN Ethernet Port TMN RF PPP Link

Interface Drop Down Drop Down
78
A. Basics of IP Addressing
79
IP Addressing
g Basics – Addressing
g Standards
There are two types of IP addressing schemes:
•IPv4 - Internet Protocol version 4
•Most widely used addressing type
•IPv6 - Internet Protocol version 6

•Replacement for IPv4
Authority : IANA - Internet Assigned Number Authority
http://www.iana.org
The 9500MPR TMN Management interfaces can be configured for

either IPv4 (default) or IPv6. Simultaneous support for both IPv4 and
IPv6 (dual stack) is not supported.
80
IP Addressing
g Basics – IPv4 Addresses
IPv4 ADDRESS
IP 4 addresses
IPv4 dd are a 32 bi
bit bi
binary number:
b
1010
0 0 1100
00 000
0001 0
0110
0 1000
000 1010
0 0 1100
00 1111
The most common representation uses dotted decimal notation such as:
172.22.138.207
Each of the four decimal numbers represents an octet

octet, or 8 bits
bits, of the 32 bit
address. Each of the four numbers can range from 0 to 255. IPv4 provides an
addressing capability of 232 or about 4.3 billion addresses.
81
IP Addressing
g Basics – IPv4 Address p
parameters
The 32 bit IP addresses are divided into a Network prefix and a Host number. This
particular example shows a 22 bits allocated for the network prefix and 10 bits for the host
number:
172 22 138 207 ->
172.22.138.207 > 1010 1100 0001 0110 1000 1010 1100 1111
network prefix host number
There are two numbers reserved in each network, the first number and the last number.
When the Host number portion of an IP address is all zeros it is called the Network Number.
This is the first number in a Network:
1010 1100 0001 0110 1000 1000 0000 0000 ->
> 172.22.136.0
172 22 136 0
When the Host number portion of an IP address is all ones it is called a Broadcast Address.
This is the last number in a Network:
1010 1100 0001 0110 1000 1011 1111 1111 -> 172.22.139.255
82
IP Addressing
g Basics – IPv4 Netmask
The division between the network prefix and host number in an IP Address is specified using a Netmask. Like IP
Addresses, Netmasks are 32 bit numbers and the usual representation is four dotted decimal numbers. Netmasks
define the size or the number of hosts within a network.
N t
Netmasks
k consists
i t of:
f
a contiguous string of ones starting from the left end for the Network prefix portion
a contiguous string of zeros starting from the end of the Network prefix all the way to the right end for the Host
number portion
No intervening bits
Table 1
Using the example address from before with a 22 bit network prefix, the corresponding
netmask is shown: Acceptable mask values
HEX BIN DEC
172.22.138.207 -> 1010 1100 . 0001 0110 . 1000 1010 . 1100 1111
00 0000 0000 0
80 1000 0000 128
255.255.252.0 -> 1111 1111 . 1111 1111 . 1111 1100 . 0000 0000
C0 1100 0000 192
E0 1110 0000 224
F0 1111 0000 240
F8 1111 1000 248
The MPR supports recommendations in RFC1812 section 2.2.5.2: Net Mask Requirements
for Classless Inter Domain Routing(CIDR) which allows the boundary between the FC 1111 1100 252
network and host portions to be defined in 1 bit increments. The table to the right FE 1111 1110 254
shows the allowed netmask values for any octet.
octet
FF 1111 1111 255
83
IPv4 Addressing
g Basics – Derivation of related network
parameters
Netmask are utilized for ease in computation of related Network parameters.
A logical
l l““AND”
” off the
h Netmask
k and
d Address
dd gives the
h Network
k Number.
b
A logical “OR” of the Address with the inverse of the Netmask gives the
Broadcast Address.
For example:
If my address were 10.100.49.30 and my netmask was 255.255.254.0 then I am a member of network
10.100.48.0, and my broadcast address is 10.100.49.255
10.100.49.30 ->
> 0000 1010 . 0110 0100 . 0011 0001 . 0001 1110 IP Address
255.255.254.0 -> 1111 1111 . 1111 1111 . 1111 1110 . 0000 0000 Netmask
---------------------------------------------
Logical AND 0000 1010 . 0110 0100 . 0011 0000 . 0000 0000 -> 10.100.48.0 Network
10.100.49.30 -> 0000 1010 . 0110 0100 . 0011 0001 . 0001 1110 IP Address
255.255.254.0 -> 0000 0000 . 0000 0000 . 0000 0001 . 1111 1111 Inverted Netmask
---------------------------------------------
Logical OR 0000 1010 . 0110 0100 . 0011 0001 . 1111 1111 ->
> 10
10.100.49.255
100 49 255 Broadcast
84
IPv4 Addressing
g Basics – Describing
g Networks ((1/2))
There are two ways to describe networks:

1
1. Long method:
Requires 3 numbers, only two of which are needed to determine the
third.
• Network
k Address
dd (all
ll 0’s
’ hhost)
• Broadcast Address (all 1’s host)
• Netmask (leading 1
1’s,
s, trailing 0
0’s)
s)
2. A shorthand method also called CIDR (from RFC 4632):

• In the form of the Network Number followed by a slash ‘/’ and the
Netmask length in decimal
• g zeros in the Network Number are often dropped.
Trailing pp
85
IPv4 Addressing
g Basics – Describing
g Networks ((2/2))
CIDR Shorthand Long method Binary
Loop back Network
127/8 NET 127.0.0.0 0111 1111.0000 0000.0000 0000.0000 0000
MASK 255.0.0.0 1111 1111.0000 0000.0000 0000.0000 0000
BCAST 127.255.255.255 0111 1111.1111 1111.1111 1111.1111 1111
One of the Reserved networks for private

address space
192.168/16 NET 192.168.0.0 1100 0000.1010 1000.0000 0000.0000 0000
MASK 255.255.0.0 1111 1111.1111

1111 1111 1111.0000
1111 0000 0000
0000.0000
0000 0000
1100 0000.1010 1000.1111 1111.1111 1111
BCAST 192.168.255.255
Sample Network Info

143.209.100/22 NET 143.209.100.0
1000 1111.1101 0001.0110 0100.0000 0000
MASK 255.255.252.0
1111 1111.1111 1111.1111 1100.0000 0000
BCAST 143.209.103.255 1000 1111.1101 0001.0110 0111.1111 1111
86
IP Addressing Basics – IPv4 Possible Network Sizes
Two hosts are reserved in any Ethernet Broadcast network for the Network Number, and the Broadcast address: the all 0’s host and
the all 1’s host respectively. This means the number of useable hosts is always two less than the total number of addresses in the
network.
The smallest Broadcast Ethernet network supported by the MPR is highlighted in RED*.
Table 2
Network bits host bits useable hosts Decimal mask
31 1 0 255.255.255.254
30 2 2 255.255.255.252
29 3 6 255 255 255 248
255.255.255.248
28 4 14 255.255.255.240
27 5 30 255.255.255.224
26 6 62 255.255.255.192
25 7 126 255.255.255.128
24 8 254 255.255.255.0
23 9 510 255.255.254.0
22 10 1022 255.255.252.0
21 11 2046 255.255.248.0
20 12 4094 255.255.240.0
19 13 8190 255.255.224.0
18 14 16382 255.255.192.0
17 15 32766 255.255.128.0
16 16 65534 255.255.0.0
… … … …
87
3DB 19353 AAAARFC
•Although 3021
- 9500 MPR allows using /31 for point to point networks the MPR does not support this extension.
TMN Networking
IP Addressing
g Basics – Subnet Calculators
Calculating network parameters can be difficult for those not familiar
with the process.
The are various online Network subnet calculators available that make
derivation of all the related numbers relatively easy.
Here are examples of such tools:
http://www.subnet-calculator.com
http://www.subnetmask.info
p
88
IP Addressing
g Basics – IPv6 Addresses
IPv6 addresses are a 128 bits long. The most common representation uses eight groups of
four hexadecimal words separated by colons (:)
2001 0db8 5160 058 0000 8fd1 0513 f 0b
2001:0db8:5160:c058:0000:8fd1:0513:fa0b
Each of the colon separated hexadecimal numbers represents one 16 bit word of the 128 bit
address Each of the eight words can range from 0000 to ffff (decimal: 0 to 65535)
address. 65535).
Addresses are case-insensitive but the recommendation is to use only lower case hex digits.
The binary representation of the above address is shown below:

0010 0000 0000 0001 0000 1101 1011 1000 0101 0001 0110 0000 1100 0000 0101 1000 0000 0000 0000 0000 1000 1111 1101 0001 0000 0101 0001 0011 1111 1010 0000 1011
2 0 0 1 : 0 d b 8 : 5 1 6 0 : c 0 5 8 : 0 0 0 0 : 8 f d 1 : 0 5 1 : 3 f a 0 b
The 128 bits provide for an address space of 2128 or about 3.4x1038 addresses. Most of the
potential address space is unused by design. The longer addresses simplify the allocation of
addresses, enable efficient route aggregation, and enable the implementation of special
features like Stateless Auto Configuration.
89
IP Addressing
g Basics – IPv6 Address Simplification
p Techniques
q
Due to the long length of IPv6 addresses there are methods to simplify written or displayed addresses. There are
two basic rules:
1) Leading zeros may be removed from any hexadecimal word.
2) Consecutive words of zero may be replaced with a double colon (::). The double colon may only be used
once in an address otherwise it becomes impossible to figure out how many zeros have been removed. This
would make the address ambiguous.
Consider the following IPv6 addresses:

2001:0db8:0000:000b:0000:0000:0000:001a
0000:0000:0000:0000:0000:0000:0000:0001 (IPv6 loopback address)
After applying rule 1)

2001:0db8:0000:000b:0000:0000:0000:001a becomes 2001:db8:0:b:0:0:0:1a
0000:0000:0000:0000:0000:0000:0000:0001 becomes 0:0:0:0:0:0:0:1
After applying rule 2)

2001:db8:0:b:0:0:0:1a becomes 2001:db8:0:b::1
0:0:0:0:0:0:0:1 becomes ::1
90
RFC 5952
3DB 19353 AAAA - recommends
9500 MPR TMN Networking that a double colon not be used to eliminate a single zero.
IP Addressing
g Basics – Networks
As with IPv4 the 128 bit IPv6 addresses are divided into a Network prefix and a Host number using a
Netmask.
IPv6 Netmasks use the CIDR (Classless Inter-Domain Routing) shorthand notation of a slash (/) followed by
a decimal number specifying the number of bits used for the network prefix.
For example the network written as:

2001:db8:5160:c058::/64
indicates 64 bits allocated for the network prefix and defines a network covering the range:
2001:db8:5160:c058:0000:0000:0000:0000
2001:db8:5160:c058:ffff:ffff:ffff:ffff
In the same manner the address and netmask for an interface in the above network can be written as:
2001:db8:5160:c058::1/64
91
IP Addressing
g Basics – Literal IPv6 addresses
When using IPv6 addresses with resource identifiers such as URLs the colon (:) conflicts
with the established syntax of using a colon to designate a port number at the end of the
host address. The workaround for this problem is to enclosed IPv6 addresses in square
brackets [ ]
Web Browsers are probably the most often used application requiring square brackets with
IPv6 addresses.
Example:
http://[fec0:0:0:1::1]/
If the URL requires a port number it goes outside the square brackets:
http://[2001:db8:5160:c058:0:8fd1:513:fa0b]:80/
Square
q brackets are needed around an IPv6 address when connecting
g to the MPR with a
web browser.
92
IP Addressing
g Basics – IPv6 alternative forms
The hexadecimal representation for IPv6 addresses is the most frequently
used.
Some hybrid dual-stack IPv6/IPv4 implementations support IPv4-mapped IPv6

addresses. This is a transition technology to aid the migration to IPv6.
These addresses are typically written with a 96-bit prefix in standard IPv6
notation and the remaining 32 bits using a dotted decimal format:
::ffff:172.22.100.10
The MPR does not support dual-stack or IPv4-mapped IPv6 addressing.
93
IP Addressing
g Basics – IPv6 Multicast
IPv6 does not implement broadcast addressing.
The traditional role of a Broadcast address is replaced by Multicast addressing to the All
N d multicast
Nodes lti t ggroup.
In general it is not necessary to communicate with all nodes in a network so most IPv6
protocols that need to talk with multiple nodes use a dedicated multicast group to avoid
disturbing all the devices in the network.
Multicast addresses generally take the form: ff0x::y
Common multicast addresses are:

ff02::1 – All Nodes address
ff02::2 – All Routers address
ff02::5 – OSPFIGP
ff02::6 – OSPFIGP Designated Routers
94
IP Addressing
g Basics - MPR Addressing
g
•For IPv4
•Private networks often use Addresses from those defined in RFC1918:
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
•Globally unique addresses could be used if they are available.
•It is possible to choose a globally unique address for the Local Address and use
RFC1918 addresses for the TMN interfaces
•For IPv6
Globally unique addresses can be used.
•Globally
•For private networks a suggestion would be to follow the recommendations in
RFC4193 and choosing addresses from the fd00::/8 block (L bit set to 1) and
selecting a suitable Locally Assigned Global ID.
95
B. Communication in Networks
96
Basic Networking
g Concepts
p - Communication within a Network
Computer 1 Computer 2
Network
A simple
i l local
l l network
t k using
i Ethernet
Eth t to
t allow
ll Computer
C t 1
and Computer 2 to communicate with each other.
The network could be implemented
p with fiber, twisted-pair
p
(such as CAT-5) or some other technology.
The connection between the two computers could be direct
using a single crossover cable
cable, or via a switch or hub.
hub
97
Basic Networking
g Concepts
00:C0:F8:34:19:C0 00 F8 62 CF 8A B3
00:F8:62:CF:8A:B3
Network
So how do two devices communicate using Ethernet?

A physical address is used to distinguish the two devices. This
address is often referred to as the MAC address, but is sometimes
referred to as the hardware address or the Ethernet address. The
MAC address is a 48 bit address assigned by the manufacturer of the
network interface before it is shipped, it is intended to be unique, and
is used to help identify a machine on a network
network.
98
Basic Networking
g Concepts
10.0.0.1 10.0.0.2
Network
MAC addressing is OK for direct Ethernet communication,

but…
• the end user has no control over the address
• it is impractical outside a local network.
To make things easier for users, another communication layer
is added:
•IP Addressing
99
Basic Networking
g Concepts
Computer 1
Computer 2
10.0.0.1 I’m at
Who has 00:C0:DF:48:F3:47 10.0.0.2
10.0.0.2? Network
Even with IP Addressing, any time one device needs to talk

with another using Ethernet, it still needs to know the MAC
address for that device.
MAC addresses are resolved by queries on the local network
asking the device you are trying to communicate with to send
back its MAC address.
The Address Resolution Protocol (ARP) is used with IPv4
For IPv6 this is part of the Neighbor Discovery (ND) protocol.
100
Basic Network Concepts
p – TCP Stack
So how do the addressing methods fit together?
Sender Receiver
SNMP Manager
g Application
pp Virtual Application
pp
SNMP Agent
Layer Layer
Connection
Layer 5
TCP, UDP Packets Transport Transport
Layer Layer
Layer 4
IP Datagram Network Network IP Addresses used
Layer Layer
at this layer
Layer 3
Ethernet Frames Data Link Data Link MAC Addresses
L
Layer Layer
used at this layer
Layer 2
Copper, Fiber, etc Physical Physical Physical
Network Network
Connection
Layer 1
•MAC addresses are used at Layer 2

•IP
IP Addresses are used at Layer 3
101
Basic Networking
g Concepts
p – Connecting
g Networks
Network A Network B
In this situation we have two isolated networks. Computer 1 can communicate

with Computer 2, and Computer 3 can communicate with Computer 4.
But what if Computer 1 needs to send a message to Computer 4?
We need a way to interface the two Networks.
102
Basic Networking
g Concepts
p - Router and Bridge
g Comparison
p
There are two common ways to connect networks together
Sender Receiver
Application Virtual Application
Layer Layer
Connection
Transport Transport
Bridges connect at Layer Layer
Layer 2 Layer 3 Network

Bridge Network
Layer Layer
Data Link Data Link Data Link
Layer 2 Data Link Layer
Layer Layer Layer
Physical Physical Physical

Layer 1 Physical Physical
Network Network
Physical
Network
Network
Connection Connection
Sender Receiver
Application Virtual Application
Layer Layer
Connection
Transport
Router Transport
Routers connect at Layer Layer
Network
e o Network
L
Layer 3 Layer 3 Network Layer Layer Network
Layer Layer
Data Link Data Link Data Link
Layer 2 Data Link Layer
Layer Layer Layer
Physical Physical Physical

y 1 Physical
Layer Physical Physical
Net o k
Network Network Network Network
Connection Connection
103
Basic Networking
g Concepts
p – Connecting
g Networks
10.0.0.2 10.0.0.4
Network A Switch Network B
10.0.0.1 10.0.0.3
The common Ethernet Switch is a form of bridge. The interfaces on a bridge have no IP
address. Bridges are convenient when all network devices share the same IP address
space. Packets
P k received
i d at one port are essentially
i ll repeated
d on the
h other
h port(s).
( ) Most
M
bridging devices are somewhat more intelligent about which packets they forward and
where, but that’s beyond the scope of this presentation.
The 9500MPR TMN Network is not bridged between TMN Ports or across RF Links!
104
Basic Networking
g Concepts
p – Connecting
g Networks
IP 172.22.64.2 IP 192.168.10.4
Gateway 172.22.64.38 Gateway 192.168.10.137
Gateway Interface
192.168.10.137
Network A
Network B
Gateway Interface
172.22.64.38
Co
Computer
pu 1 Computer 3
IP 172.22.64.1 IP 192.168.10.4
Gateway 172.22.64.38 Gateway 192.168.10.137
Routers are another way to connect two networks together

together. Routers are used when the two
networks use different IP address space.
Unlike bridges, interfaces on a router need an address within the networks they are attached
to. The interface IP address of a router is a ‘gateway’ to other networks. Most network
d
devices are configured
f d to use a nearby
b router as a Default
f l Gateway.
105
Route Configuration
g
In the Previous slide, Router A needs to know that addresses in the 192.168.64.0/18 network can be
reached by using Router B as a gateway.
There are two methods considered:
1. Static Routing where all routes are manually provisioned.
2. Dynamic Routing where routers exchange route information using a Dynamic Routing Protocol.
A Dynamic routing message exchange is depicted below:
II’m
m Router B
B.
I know how to reach 192.168.0.0/20
addresses in the range:
4094 addresses
192.168.64.0/18 192.168.16.0/20
Use my gateway at: 4094 addresses

Router
172
172.16.0.2
16 0 2 Router
A B
External Networks
192.168.32.0/20
4094 addresses
I’m Router A.
Use me for your 192.168.48.0/20
Default Route 4096 addresses
My gateway is at:
172.16.0.1
 106
There are several Dynamic Routing Protocols. The protocol used by the 9500 MPR is called OSPF (Open
Shortest
3DB 19353 Path
AAAA - 9500 MPR First). Operational details of dynamic routing protocols is beyond the scope of this presentation.
TMN Networking
Basic Networking
g Concepts
p - Routers
192.168.0.0/18
92 68 0 0/ 8 Address
dd Range
External 192.168.0.0/16
Network Router
65534 addresses 192.168.0.0/20
4094 addresses
192 168 16 0/20
192.168.16.0/20
4094 addresses
Router
External Router 192.168.0.0/18 B
Network From A
F 192 168 32 0/20
192.168.32.0/20
A 16346 addresses
4094 addresses
192.168.192.0/18 192.168.128.0/18 192.168.48.0/20

16346 addresses 16346 addresses 4096 addresses
 A Router with multiple interfaces can also be used to divide address space into smaller networks. This process of
division can be repeated to get the desired network size
size, optimizing use of the available address space.
space Each
division is called a sub-network.
 In the above example, the original 192.168.64.0/16 network at the top left is divided into four subnets as the
length of the netmask is increased from 16 to 18 bits. Three of the new subnets are directly attached to Router
A One
A. O /18 subnet
b t has
h been
b further
f th divided
di id d into
i t four
f /20 subnets
b t using
i Router
R t B as shown h with
ith the
th ddetail.
t il
 Router A doesn’t need to know that Router B has divided the 192.168.64.0/18 network into subnets, it only needs
107
to3DBknow
19353 AAAA -that
9500 MPRthe 192.168.64.0/18 aggregate address space is accessible via Router B.
TMN Networking
Route Configuration
g
In the Previous slide, Router A needs to know that addresses in the 192.168.64.0/18
network can be reached by using Router B as a gateway.
There are two methods considered:
1. Static Routing where all routes are manually provisioned.
2. Dynamic Routing where routers exchange route information using a Dynamic

Routing Protocol. A Dynamic routing message exchange is depicted below:
I’m Router B.
I know how to reach 192.168.0.0/20
addresses in the range: 4094 addresses
192.168.16.0/20
192.168.64.0/18
Router 4094 addresses
Use my gateway at: Router
A 172.16.0.2 B
External Networks
192.168.32.0/20
4094 addresses
I’m Router A.
Use me for your 192.168.48.0/20
Default Route 4096 addresses
My gateway is at: 172.16.0.1
 108 There are several Dynamic Routing Protocols. The protocol used by the 9500 MPR is called
OSPF (Open Shortest Path First). Refer to the OSPF Appendix for more information.
C. MPR DHCP Overview
109
Basic Networking
g Concepts
p - DHCP
There are two address assignment methods:
1. Static assignment
2. Dynamic assignment
With Static Assignment,

Assignment addresses are configured manually:
IP Address:
172.22.88.175
Netmask:
255.255.224.0
Default Gateway:
172.22.64.1
110
Basic Networking
g Concepts
p - Address Assignment
g for IPv4
With Dynamic Addressing equipment on a network is configured using the
Dynamic Host Configuration Protocol (DHCP) as documented in RFC2131. The
9500MPR provides a simple DCHP server on the TMN Ethernet port for configuring
C ft computers.
Craft t Thi
This DHCP server iis enabled
bl d by
b Default.
D f lt
Hello! I’d like to I offer to configure

configure my your network DHCP
network interface. interface
interface. Se e
Server
Network
With DCHP, when clients connect to a network, they send a broadcast asking if there is a
server that can provide networking configuration.
If a DHCP Server is available,, the client can then request
q its network configuration
g
parameters.
When a DHCP Server provides an IP Address to a client it is called a Lease. The typical
parameters provided usually include: IP Address, Netmask, Default Gateway, and Lease
Timeout
Timeout.
111
Basic Networking
g Concepts
g for IPv4
•The DHCP Server is responsible for keeping track of which IP Addresses are
currently Leased and not hand out duplicates.
•When a client is finished with an IP address,, it is supposed
pp to inform the Server
the address is no longer needed. The Server will then mark the address as
available for reuse.
•Leases have an associated timeout specified by the server. The Lease timeout is
part of the configuration parameter message. This timeout is the maximum time
the client is allowed to use the IP Address. Timeouts are specified in seconds and
usually range from minutes to days.
•If a client disconnects without informing the server or otherwise fails to renew
the Lease then when the timeout arrives the Server will mark the address as
available for reuse.
•If a client needs an IP Address for an extended period, it must negotiate with the
DHCP server to renew the Lease prior to timeout. If the Lease expires, the client
must request a new Lease and may be assigned a different IP Address.
112
Basic Networking
g Concepts
g for IPv4
•DHCP is based on the Bootstrap Protocol RFC951(BOOTP)
DHCP can be relayed between networks by a BOOTP Relay Agent.
These are sometimes called DHCP Relay Agents
Agents.
A BOOTP Relay allows DHCP clients and servers to be in different
Networks.
Some routers incorporate BOOTP Relay Agents.
The 9500MPR TMN Network router does NOT Relay DHCP or BOOTP
messages!
113
Basic Networking
g Concepts
g for IPv4
• Multiple DHCP Servers on a Network:
1) This is possible provided either:
• The multiple DHCP Servers share a common Lease database so they do
not serve duplicate addresses
or
• The Servers are configured to offer Leases from non-overlapping address
ranges.
2) When a client broadcasts a request looking for a DHCP server and multiple
servers respond, the client chooses the server it will use for configuration.
Frequently this is the first server to respond, but this behavior is not required.
114
Basic Networking
g Concepts
p – DHCP in the 9500MPR
 9500MPR DHCP is only available with IPv4.
 When configured for IPv6 the MPR provides link-local announcements using the Neighbor
Discovery Protocol (NDP)
(NDP). This allows Craft computers to configure themselves through stateless
autoconfiguration.
 The 9500MPR DHCP server Leases addresses based on a very specific set of
rules. These rules, defined on the following pages, are unique to the 9500MPR
andd are not user configurable.
fi bl
 The 9500MPR DHCP server defaults to Enabled and must be disabled before
connecting the TMN Ethernet interface to an external network controlled by
another DHCP server otherwise conflicts will occur including possible loss of
connectivity in the external network.
115
MPR Addressing – DHCP: 9500MPR DHCP Leased Address Assignment Behavior
For simplicity, the built-in DHCP server in the 9500MPR operates using a fixed set of rules. This fixed behavior
puts restrictions on the way addresses in the TMN Ethernet Port subnet can be used whenever the DHCP
server is enabled.
1
1. The DHCP Server uses an address pool based on the TMN Ethernet IP address and subnet.
subnet
2. Up to 0 addresses are reserved for Leases in the following manner:
a) If the TMN Ethernet Port address is the first address in the subnet, reserve addresses immediately
above
b th Port
the P t to
t the
th endd off the
th subnet
b t or a maximum
i off 10 addresses,
dd whichever
hi h comes fi
first.
t
b) If the TMN Ethernet Port address is NOT the first address of the subnet but there are 10 IP
addresses above it before the end of the subnet reserve those 10 addresses for the DHCP pool.
c)) If the
h TMN Ethernet
Eh P
Port address
dd is
i NOT the
h fi
first address
dd iin the
h subnet,
b and
d there
h are ffewer than
h 10
addresses above it before the end of the subnet then reserve addresses immediately prior to the
port up to a maximum of 10 addresses or the start of the subnet whichever comes first.
p
NOTE: The behavior described here has been updated from what was described in older editions of this
document.
If the MPR DHCP Server is enabled, the addresses reserved for DHCP Leases should not be statically assigned to
other equipment.
The manner in which DHCP addresses are reserved and assigned by the MPR is shown with examples on the
following slides.
116
MPR Addressing – DHCP: 9500MPR DHCP Address Assignment Behavior
T bl 1
Table T bl 2
Table
IP Addr Equipment IP Addr Equipment
192.168.1.14 192.168.1.14
192.168.1.13 DHCP Assigned 10 192.168.1.13
192 168 1 12
192.168.1.12 DHCP Assigned 9 192.168.1.12 TMN Ethernet Port
192.168.1.11 DHCP Assigned 8 192.168.1.11 DHCP Assigned 10
192.168.1.3 TMN Ethernet Port 192.168.1.3 DHCP Assigned 2
192.168.1.2 192.168.1.2 DHCP Assigned 1
192 168 1 1
192.168.1.1 192 168 1 1
192.168.1.1
192.168.1.0 Network (/28) 192.168.1.0 Network (/28)
In Table 1, there are 10 addresses available above the TMN Ethernet Port address and they
are reserved for the DHCP address pool (Rule 2b). Addresses not used by the TMN
Ethernet Port or reserved for DHCP Leases can be statically assigned to other equipment
equipment.
In Table 2, there are fewer than 10 addresses available above the TMN Ethernet Port, but
there are 10 available below it and they are reserved for the DHCP address pool (Rule 2c).
Addresses not used byy the TMN Ethernet Port or reserved for DHCP Leases can be staticallyy
assigned to other equipment.
MPR Addressing – DHCP: 9500MPR DHCP Address Assignment Behavior
Table 3 Table 4 Table 5

IP Addr Equipment IP Addr Equipment IP Addr Equipment
192.168.1.7 Broadcast 192.168.1.7 Broadcast 192.168.1.7 Broadcast
192.168.1.6 DHCP Assigned 5 192.168.1.6 192.168.1.6
192 168 1 5
192.168.1.5 DHCP Assigned 4 192 168 1 5
192.168.1.5 TMN Ethernet Port 192 168 1 5
192.168.1.5
192.168.1.4 DHCP Assigned 3 192.168.1.4 DHCP Assigned 4 192.168.1.4
192.168.1.3 DHCP Assigned 2 192.168.1.3 DHCP Assigned 3 192.168.1.3
192.168.1.2 DHCP Assigned 1 192.168.1.2 DHCP Assigned 2 192.168.1.2 TMN Ethernet Port
192.168.1.1 TMN Ethernet Port 192.168.1.1 DHCP Assigned 1 192.168.1.1 DHCP Assigned 1
192.168.1.0 Network (/29) 192.168.1.0 Network (/29) 192.168.1.0 Network (/29)
( )
In Table 3, the TMN Ethernet Port address is the first address in the subnet so addresses
above the port will be reserved. Since there are fewer than 10 addresses to the end of the
subnet all are reserved for the DHCP address pool (Rule 2a). This leaves NO addresses
available for static assignment to other equipment.
In Tables 4 and 5, the TMN Ethernet Port address is not the first address in the subnet and
there are fewer than 10 addresses available above the port so addresses below the port will
be reserved. With fewer than 10 addresses available below the port all are reserved for the
DHCP address pool (Rule 2c).
2c) Addresses not used by the TMN Ethernet Port or reserved
for DHCP Leases may be statically assigned to other equipment.
D. MPR OSPF Overview
119
Network Services – OSPF Overview
 Open Shortest Path First (OSPF) is the dynamic routing protocol used
with the 9500MPR.
 In IPv4 mode the MPR uses OSPFv2 as defined in RFC 2328.
2328
 In IPv6 mode the MPR uses OSPFv3 as defined in RFC 5340.
 OSPF is a link-state protocol. We can think of a link as an interface to a
router, and the associated link state as a description of that interface and
it’s relation to other routers. The link state includes such info as:
• IP Address of the interface
• Netmask
• The type of network
• The routers connected to that interface
 The collection of these link-states for several interfaces would form a link-
state database
120
 Routers running OSPF advertise their link state to neighboring routers at
initialization and again whenever any link state information changes. The
advertisement represents the collection of all link states on that router
router.
 Routers exchange link states by means of flooding. Whenever a router
receives a link state update, it stores a copy in it’s local database and
propagates the update to other routers
routers.
 After the database is updated, the router will calculate the Shortest Path
tree to all destinations. The destinations, the cost, and the next hop to
reach those destinations form the IP routing table
table.
 To control the flooding of link state updates, OSPF uses Areas. All routers
within an Area have the same link state database.
121
Area Border Router
(ABR)
Autonomous System
Boundary Router (ASBR)
Internal
Routers
Static
External
Router
 Routers
R that
h have
h allll off their
h i interfaces
i f in
i the
h same area are called
ll d Internal
I l
Routers.
 Routers that belong to one or more areas and connect to the backbone must keep
a link state database for all attached areas plus the Backbone Area. These routers
are called Area Border Routers (ABR)
 A router that act as a gateway between OSPF and another routing protocol
(including Static routes) is called an Autonomous System Boundary Router (ASBR).
122
Inter-Area
Route Area 2
Intra-Area
Routes
Area 1 Backbone
Area 0 Area 3
External
External
Static
Static
Routes
Routes
OSPF has special restrictions when multiple Areas are involved:

• If more than one area is configured, ONE of these areas must be Area 0. This area is
defined as the Backbone.
Backbone When designing networks,
networks itit’ss good practice to start with Area
0 and expand into other areas later on.
• The backbone has to be at the center of all other areas. All other areas must be
physically
p y y attached to the backbone. OSPF expects
p all non-zero areas to inject
j routes into
the backbone and the backbone will redistribute this information to the other areas.
123
Network Services - OSPF
Stub Area 2
External
Static
Routes
ASBR
ABR
Area 1 Backbone
Area 0 Area 3
ASBR
External
Static
Stub Areas:
Routes
• OSPF allows certain areas to be defined as Stub Areas. Routes to external networks, including those
learned through other protocols are not allowed to be flooded into these areas
areas. Routing from Stub
areas to the outside world is based on a default route to the nearest ABR. Configuring an area as a
Stub reduces the size of the routing database within the area.
• An area could be qualified as a Stub if there is a single exit point from the area or if routing to
d ti ti
destinations outside
t id the
th area do
d nott need d to
t take
t k an optimal
ti l path.
th InI the
th examplel above,
b Area
A 2 is
i
shown as a Stub, Area 3 could be a candidate for a Stub.
• Stub areas can have more than one ABR but must not contain any ASBR.
• All routers within

i hi a Stub
S b area must have
h the
h Stub
S b Flag
Fl set.
124
Network Services – OSPF
9500MPR OSPF Features
 Each 9500MPR supports up to 3 non-zero user defined OSPF Areas, for a total of 4 Areas.
 Area 0 is always defined in each MPR and cannot be deleted. Area 0 does not have to be associated with any interface.
• The MPR becomes an Area Border Router (ABR) when at least one TMN interface is associated with Area 0 and one or
more other TMN interfaces are active in non-zero Areas.
• The MPR becomes an Autonomous System Border Router (ASBR) if:
1) OSPF is selected as the Routing Protocol for a TMN Interface
2) A Static Route is configured to reach a Gateway through a TMN Interface
3) There is no OSPF Adjacency with the Gateway router
 Stub Area support
 Set the Stub Flag to True on each MPR in the area.
 The MPR has no options

p to suppress
pp Type
yp 3 Summaryy LSAs ((Totallyy Stubby)
y) or configuring
g g route summarization. To limit
the size of the route table in a Stub area use a more configurable external router for the ABR and restrict the routes
advertised into the MPR OSPF Areas or configure it for Totally Stubby operation.
 The MPR does not support Not So Stubby Areas (NSSA)
 No support for creating Virtual Links
 Authentication is not supported.

125
9500MPR OSPF Features cont.
 RouterID (RID)
 For OSPFv2 the Local Address is used as the RID
 For OSPFv3 the RID must be explicitly set and must be unique within the
autonomous system.
system
 Router Priority fixed to 1.
 Router Priorityy affects the Designated

g Router (DR)
( ) Election process.
p
 If you want external routers to have a greater chance of becoming the DR

configure them to have a Router Priority greater than 1.
 Note
N t th
thatt if th
the DR goes d
down or b
becomes unreachable
h bl an MPR might
i ht
become the DR. If it is possible for an MPR to become the DR the
recommended maximum number of direct neighbors on the same LAN is
eight.
126
9500MPR OSPF Deployment Hints
 The recommended maximum number of entries in the MPR routing table, including both Static and
Dynamic entries, is around 200.
 While this is not a hard limit, large route tables consume excessive Core resources and degrade
performance.
• To estimate the size of the OSPF routing table in an Area sum together:
• 1 entry for each active PPP RF interface in each MPR node.
• 1 entry for each active TMN In-Band interface in each MPR (up to two)
• 1 entry for each active TMN Port #4 interface in each MPR
• 1 entry for each active Local TMN Ethernet Interface in each MPR
• 1 entry for the NE Local Address (only if it does not match an interface address)
• 1 entry for each static route provisioned in the MPR network.
• 1 entry for each route distributed into the Area from the backbone
• S th
See the example
l on the
th nextt page
127
9500MPR OSPF Deployment Hints cont.
• Example: A typical repeater supporting:
• two Radio Directions
• an active TMN Port #4 interface with a matching Local Address
• an active TMN Ethernet port
• will contribute 4 route entries to the OSPF routing tables.
• A general Rule of Thumb is to put no more than about 50 MPRs in an autonomous OSPF system
• This is based on a target route table size of about 200 entries and an average of about 4 active
interfaces per MPR: (200 / 4 = 50 )
• If th
the MPR OSPF area iis attached
tt h d tto an external
t l OSPF system
t it may b
be necessary tto restrict
ti tT Type 3
Summary LSAs flooded into the MPR area or use route summarization to keep the size of the route
table within recommended limits. This can be achieved using route summarization at the ABR or by
configuring the Area as a Total Stub (stub, no-summaries). Either of these methods will require an
external ABR that is more configurable
g than the MPR.
128
Other 9500MPR OSPF Fixed Parameters
It may be necessary to configure several OSPF parameters on external routers
to match the values in the 9500MPR before an adjacency can be formed.
The 9500 MPR OSPF parameters are:
 Hello Interval: 10 seconds
 Router Dead Interval: 40 seconds
 MTU: 1500 bytes
 Retransmit Interval: 5 seconds
 Interface Transit Delay: 1 second
 Router Priority: Fixed to 1 (lowest priority)
 Note: In an IPv6 environment, the maximum size LSA supported by
the 9500 MPR is 1280 bytes. LSAs larger than this will be discarded.
129
Other 9500MPR OSPF Deployment Hints
 RouterID (RID)
 For OSPFv2 the Local Address is used as the RID
 For OSPFv3 the RID must be explicitly set and must be unique within the
autonomous system.
system
 Router Priority fixed to 1.
 Router Priorityy affects the Designated

g Router (DR)
( ) Election process.
p
 If you want an external router to have higher priority configure them for a
priority greater than 1.
 If an MPR could
ld b
become the
th designated
d i t d router
t the
th recommended
d d maximum
i
number of direct neighbors on the same LAN is eight.
130
Other 9500MPR OSPF Deployment Hints cont.
• The 9500MPR will not form Full adjacency with a neighboring OSPF router if:
• The Area IDs do not match
• There is a mismatch in Hello Interval, Dead Time, or MTU size
• The neighboring router is configured to require authentication.
• or other incompatible settings.
• Deleting an unused OSPF area can lead to loss of remote connectivity. An NE Restart is
required to restore normal operation.
• Caution: Once OSPF Adjacency has been established changing the OSPF Area Id associated with an
MPR TMN interface will cause a loss of Adjacency through that interface. Changing the Area Id of the
opposite end of the link to match will restore Adjacency but if the router at either end is an ABR an
NE Restart may be required at both ends of the link before routes will be exchanged correctly. This
may lead
l d to
t loss
l off remote
t connectivity
ti it and d require
i a site
it visit
i it to
t correctt any problems
bl andd restart
t t the
th
MPRs.
• An NE Restart can be performed using the ‘Supervision ->Restart NE’ function in the Craft.
131
Network Services - 9500MPR OSPF Deployment
p y Hints
• Attaching a 9500MPR OSPF Area to an external OSPF network.
• When the MPR neighbors with a more fully featured external router (such as
an Alcatel-Lucent 7705 or 7750,, or other)) at an OSPF Area border the best
results will be obtained when the external router is configured as the ABR.
ABR
Preferred Area 1 Area 0
Configuration MPR
7705/7750
or other
router
ABR
Less robust Area 1 Area 0
MPR
7705/7750
or other
router
132
Other 9500MPR OSPF Deployment Hints
• Autonomous 9500MPR OSPF systems with more than one ASBR may exhibit
external reachability issues in the event of a link failure
failure.
• Workarounds:
1) Use more fully featured external routers for the ASBRs.
2) Configure the MPR OSPF network to be part of an external OSPF system.
a) Configure the MPR OSPF area as a Stub to reduce the number of
routes advertised into the area.
b) In some cases it may be necessary to use an external ABR and
configure the interface attached to the MPR Area for Totally Stubby
operation (stub with no summaries).
133
Network Services - 9500MPR OSPF Deployment
p y Hints
• Connecting an MPR Autonomous OSPF network to external networks.
• Autonomous networks will normally require a static route in the ASBR.
• If a more ffully
ll ffeatured
t d external
t l router
t iis available
il bl (such
( h as a 7705 or 7750 or
other) configuring the external router as the ASBR will improve the
performance.
• If there will be multiple ASBRs, using external routers is preferred.
ASBR
External
OK Area 0 Network
MPR
ASBR
External
Better Area 0 Network
MPR
7705/7750
or other
router
134
E. Comparison to TMN
Networking in the MDR
MDR-8000
8000
135
Comparison
p of 9500MPR and MDR8000 TMN Networking
g using
g IPv4
1) The MDR8000 TMN offers only one external Ethernet interface (feeding a 4 port switch).
2) The MDR8000 uses the same Local Address and TMN Ethernet address concept as the 9500MPR where the Local Address is used for PPP
endpoint identifiers, the Local Address can be set the same as the TMN Ethernet address, and Traps originate from the Local Address.
3) MDR8000 TMN Craft port is a serial interface. The LLMAN utility is used to obtain a PPP connection through this interface in contrast to
the Ethernet craft interface of the 9500MPR.
4) The MDR8000 TMN PPP interfaces are:

a)) PPP Front Access interface
b) Repeater PPP interface.
c) RF PPP interface
These serial interfaces are functionally equivalent to the PPP RF links in a 9500 MPR network and serve the same purpose: providing a
point to p
p point connection to another NE. It's mainlyy a hardware interface difference not a networking
g difference.
4) The MDR8000 TMN supports RIPv1, RIPv2 and OSPFv2 as dynamic routing protocols whereas the 9500MPR supports OSPFv2 and OSPFv3
5) The MDR8000 TMN offers no built-in mini-DCHP server. Use of the LLMAN utility and the serial Craft port allow direct NE connections
with minimal user configuration.
6) MDR8000 TMN transport operates at 64kb/s in a dedicated out-of-band overhead channel. The 9500 MPR TMN transport uses an in-band
dedicated VLAN at a high priority supporting much higher transfer rates across the RF link.
7) The MDR8000 TMN supports a hard limit of 250 entries in the routing table vs. approximately 200 for the 9500MPR. Despite the larger
number of routing table entries, the practical number of MDR8000 NEs in an autonomous MDR8000 TMN Network is limited primarily by
the slow transport channel and the number of hops (delay) to the farthest NE. The recommended maximum number of MDR8000 NEs in
an contiguous TMN Network is around 30.
136
Otherwise, from a TMN Networking and Addressing standpoint, the two systems are equivalent.
F. MPR-e and MPR-1c
differences
137
Primary differences in IPv6 TMN vs IPv4 TMN
The major differences when running IPv6 are:

1) No DHCP support for the TMN Ethernet port when in IPv6 mode. Instead the
MPR uses the IPv6 Stateless Address Auto Configuration (SLAAC)
(SLAAC). As a side
benefit, all TMN ports support SLAAC.
2) In IPv4 mode, alarming of the TMN Ethernet port was automatically
suppressed
pp whenever DHCP was enabled. When using g IPv6 it is necessaryy to
manually provision the alarm for suppression if the port will not normally be
connected. Alarm suppression is configured by changing the Alarm Profile on
the TMN Ethernet port provisioning screen to No Alarms.
3) IPv6
IP 6 uses OSPF
OSPFv3.
3 With IP
IPv44 and
d OSPF
OSPFv22 th
the OSPF R Router
t ID was
automatically set to match the MPR Local Address. With IPv6 this is no longer
possible. The OSPFv3 Router ID is still 32 bits long, but IP addresses are 128
bits. The Router ID must be manually set to a unique value in the overall
OSPF system.
4) No dual stack operation. The MPR TMN management will be either all IPv4 or
all IPv6. There are no settings for User traffic, both IPv4 and IPv6 can be
carried simultaneously.
138
The MPRe and MPR-1c
The MPR-e, MSS-1c, and MSS-O are compact

components of the 9500 family of equipment.
These units offer a subset of the full 9500MPR
TMN features
features.
The following pages highlight the TMN differences

and p
provide suggestions
gg on TMN network
deployment.
139
MPRe and MPR1c Supported
pp Interfaces
TMN In-Band RF PPPoE
VLAN Interface NMS1
TMN In-Band RF PPPoE

VLAN Interface
TMN
CT Connector NMS2
RF PPPoE
In-Band TMN
VLAN Subnet In-Band
VLAN Subnet
MSS-1c
SS c
Dedicated Only accessible TMN RF-PPPoE
Craft with special NMS1
Subnet Maintenance Subnet
cable
MPR-e TMN
NMS2
Subnet
CT
Connector
• The MPR-e and MSS-1c support fewer interfaces. Subnet
• The MPR-e supports one TMN In-Band VLAN interface and an RF-PPPoE link
• The MSS-1c supports:
• One TMN In-Band VLAN Interface
• Two TMN NMS interfaces for connecting to external networks
• One dedicated CT Connector for Local Craft connections

140
• An RF PPPoE link
MSS-O Supported
pp Interfaces
TMN Local
Management
Ethernet port
In-Band VLAN #1
RF PPPoE
In-Band VLAN #2
MSS-O
MSS O TMN
In-Band #1
VLAN Subnet
RF-PPPoE
TMN
In-Band#2
I B d#2
VLAN Subnet
TMN
Ethernet
Subnet
• The MSS-O supports:
• Two TMN In-Band VLAN Interfaces
• One dedicated TMN Management Ethernet port for Local Craft connections
• RF PPPoE links
141
Differences between the 9500MPR MSS and the MPR-e
MPRe:
1. Starting in R03.02.00 the MPRe supports OSPF.
a) Older releases only supported static routing.
2. The MPR-e has a dedicated Craft interface that can only be accessed using a special
service cable. This interface may be used at initial NE turn-up and is not designed to
be connected with an external network, only to a Craft computer. This dedicated
interface is configured as a DHCP server with a fixed address and subnet. The DHCP
server, NE address, and netmask are not user configurable.
a)) Fi d address:
Fixed dd 192.168.10.1
192 168 10 1
b) Fixed netmask: 255.255.255.0
3
3. When the radio is in service,
service all TMN network access is via the TMN InIn-Band
Band VLAN
Interface. The VLAN Id is user configurable, but the interface is always associated
with the MPR-e Traffic interface. Accessing the TMN In-Band interface requires that
the external equipment be VLAN aware.
142
Differences between the 9500MPR MSS and the MPR-1c
MPR-1c:
1. Starting with R03.02.00 the MPR-1c supports OSPF.
a) Older releases only support static routing.
2. The CT Connector port is a dedicated Craft interface. It is not designed to be

connected with an external network, only to a Craft computer. The NE is configured
on this
thi interface
i t f as a DHCP server with
ith a fixed
fi d address
dd andd subnet.
b t Th The DHCP server,
NE address and netmask are not configurable.
a) Fixed address: 192.168.30.1
b) Fixed netmask: 255.255.255.252
3. NMS1 and NMS2 ports are dedicated TMN ports. They are functionally equivalent to
the 9500MPR Port #4 in TMN Mode. If both NMS1 and NMS2 are enabled,, theyy must
be in different subnets.
4. One TMN In-Band interface is supported. It may be associated with the User Ethernet
ports on the MSS-1c. The VLAN Id is user configurable. Accessing the TMN In-Band
interface requires that the external equipment be VLAN aware.
143
Differences between the 9500MPR MSS and the MSS-O
MSS-O:
1. The MSS-O does not support TMN Port #4. Otherwise its networking
capabilities are identical to the MSS
144
G. Default and Reserved addresses
145
Default 9500MPR NE Addressing
g
MSS-1/4/8 Shelf and MSS-O
• IPv4
• 10 0 1 2 NE Local Address
10.0.1.2
• 10.0.1.2/24 TMN Ethernet port
• 10.0.2.2/24 Port #4 in TMN Mode (MSS-1/4/8 only)
• 10.0.3.2/24 TMN In-Band #1
• 10.0.4.2/24 TMN In-Band #2
• IPv6
• FEC0:0:0:1::1/128 Local Address
• FEC0:0:0:1::1/64 TMN Ethernet port
• FEC0:0:0:2::1/64 Port #4 in TMN Mode (MSS-1/4/8 only)
• FEC0:0:0:3::1/64 TMN In-Band #1
• FEC0:0:0:4::1/64 TMN In-Band #2
146
Default 9500MPR NE Addressing
g ((Continued))
9500MPR-e Standalone
• 10 0 1 2 NE Local Address
10.0.1.2
• 192.168.100.1/24 TMN In-Band in VLAN 4080
• 192.168.10.1/24 Service (Maintenance) cable interface (Fixed, not configurable)
9500MPR-1c Shelf
• 10.0.1.2 Network Element (Local Address)
• 192.168.30.1/30 CT Port (Fixed, not configurable)
• 10.0.1.2/24 NMS Management port 1
• 10.0.2.2/24 NMS Management port 2
147
Reserved Addresses
The following address ranges are used internally by the 9500MPR. Addresses from the
following ranges should not be assigned as a Local Address or used for an interface address.
9500MSS:
• 127.0.0.0/8 Loopback
• 100.1.0.0/24 Internal Core Main to Core Spare communications
• 100.1.0.1 Core Main
• 100.1.0.2 Core Spare
• 100.2.0.0/24 Internal MSS to MPT communications
• 100 2 0 1 Core
100.2.0.1
• 100.2.0.x one for each MPT, depending on slot/port
MPR-e
• 192.168.10.1/24 Dedicated service cable interface and subnet (Fixed, not user
configurable
9500MPR-1c
• 192.168.30.1/30 Dedicated CT Connector Port Address and subnet (Fixed, not user
configurable)
148
MTU
TMN Interfaces do not support jumbo frames.

The MTUs:
• TMN PPP RF links
• 1492 Byte Layer 2 MTU
• TMN Broadcast Ethernet interfaces
• 1522 Byte Layer 2 MTU for TMN In-Band with 802.1q VLAN tag.
149
H. NAT router
150
NAT Router
What is the NAT router

The Network Address Translation allows a single device, such as a router, to act as agent
between the Internet ((or "public
p network")) and a local ((or "private")
p ) network. This means
that only a single unique IP address is required to represent an entire group of
computers
to anything outside their network. The shortage of IP addresses is the main reason to use
NAT.
NAT R t
Router
Outgoing Outgoing
Private Public
Network Incoming Incoming Network
Local Area Internet

Network
151
NAT Router
NAT Operational
p Characteristics:
NAT devices are application unaware and the translations are limited to
IP/TCP/UDP/ICMP headers and ICMP error messages only.
This means NAT devices are transparent to applications in many cases.
NAT devices
d i do
d nott change
h the
th payload
l d off th
the packets
k t as payloads
l d ttendd tto b
be application
li ti
specific. Applications and protocols that are not supported transparently may require
the use of Application Level Gateways (ALGs).
Those that want to deploy NAT based solutions need to determine their application
requirements first and assess the need for NAT extensions (i.e., ALGs) necessary to
provide application transparency for their environment.
152
NAT Router
What are the NAT router
ro ter limitations
As described in RFC 2663 – IP Network Address Translator (NAT) Terminology and
Considerations, there are several areas where NAT devices often cause difficulties:
1)) When an application payload includes an IP address,
2) FTP applications
3) When end-to-end security is needed (ex. IPSec transport mode or the TCP MD5
Signature Option)
SNMP is one such application where IP Addresses are contained within the payload. NAT
routers do not translate IP Addresses within SNMP payloads.
It is possible to have an SNMP specific ALG residing on a NAT router to perform SNMP MIB
translations that are proprietary to the private network. These will likely be custom
ALGs and NAT device dependent.
The following slides describe how NAT impacts the MPR.

The scenarios are for a remote manager that wants to access the MPR through a NAT
router. We recommend not using NAT devices because of the consequences that are
described.
153
NAT Router
How MPR equipment
q p is impacted
p
-MPR Manager IP Address and Access Control Security
MPR uses Access Control Security based on the IP Address of the manager.
Access Control restricts access from anyy manager
g that is not registered.
g
MPR WebEML Craft applications are manager applications. During the “Start Supervision”
sequence a manager registers its IP Address with the MPR. The IP address to be registered is
sent within an SNMP message.
message During subsequent management communication the MPR
checks the source IP address of packets against the list of IP Addresses for registered
managers. If there is a match, communication is allowed. If there is no match, access is
denied.
Consider the scenario where a Manager is on the Private side of a NAT router and the MPR is
on the Public side. During the Start Supervision sequence the manager will register its Private
address with the MPR but the Source IP Address of the packets will be the NAT Public address.
In subsequent communication when the MPR compares the source address of packets to the
list of registered IP Addresses it will not find a match and access will be denied.
This means there is no way to access or manage the MPR through NAT.
154
NAT Router:
How MPR equipment
q p is impacted
p
-FTP application
The MPR uses FTP by default for:
Software Download
Backup and Restore
FTP through a NAT router requires use of an ALG. NAT implementations often provide
an ALG supporting
ti FTP for
f the
th case where
h the
th FTP Client
Cli t isi llocated
t d on th
the P
Private
i t side
id
of the NAT and the FTP Server is located on the Public side.
During
g Software Download,, the MPR acts as an FTP Client. If the FTP Server hosting
g the
MPR software for download is behind a NAT router a suitable AGL will be needed.
During Backup and Restore the FTP role of the MPR depends on the model. MSS-1/4/8
and MSS-O act as FTP Servers.
Servers The MPR-e acts as an FTP Client.
Client If the FTP transfer for
the Backup and Restore passes through a NAT router, a suitable AGL will be required.
Due to the varying FTP Client/Server roles the use of NAT with the MPR is not
recommended.
155
156

TMN Networking

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

TMN Networking

Transféré par

Droits d'auteur :

Formats disponibles

9500 MPR TMN Networking

3DB 19353 AAAA

1. For transport across RF links, there are in

•Each TMN interface to the MPR is connected to an internal router.

2. For IPv6 TMN Networks the MPR supports OSPFv3

3. The MPR provides a very basic OSPF implementation

 Enabling or disabling OSPF on each individual TMN interface.

 Assigning an OSPF Area ID to each interface (default Area is 0)

2. Enabled by default, the DHCP server can be disabled.

 This is the only user configurable option

5. The Lease Time is fixed to 10 minutes.

Port #4 TMN TMN Ethernet

2. The TMN Ethernet interface address

3. Optional Port #4 TMN Ethernet interface address

b)) Recommended for use when connecting

4. Optional TMN In-Band #1 Ethernet interface address

Optional TMN In-Band #2 Ethernet interface address

a) These interfaces are disabled by default.

b) When a TMN IIn-Band

c) These interfaces are intended for connection to external networks.

1) In-Band TMN Traffic is always VLAN tagged with the user

Access to the TMN In-Band

2) Port flexibility. The user can provision one or more User

a) When multiple User Ethernet ports are associated with a

a) May not be port segregated.

b) May be associated with PDH cross-connections.

 These features are useful when it is desirable to transport TMN Traffic in a

Local Address:10.3.27.5 Local Address:172.22.37.49

RF PPP Link RF PPP Link

•The NE at Site A can communicate with Site B

•The NE at Site B can communicate with Site C

•but A cannot communicate with C until routing is configured.

•Routing can be configured dynamically or statically.

Craft TMN Ethernet

When configured for IPv6 the MPR provides link-local

- In case of OSPF each address must belong to an OSPF

that is the same as the LocalIP address of the NE.

Overview 512Kb/s Radio

• In line with IPv4 DCN. Some constraints detailed 9500 MPR

• IPv6 DCN cannot be managed by 1350/1353 NM 10/100 Base T

• IPv6 is supported only by MSS-O/1/4/8 Physical DCN Ports

• 1x IPv6 address for all the radio channels (/128) that

• Remark - refer to IANA spec for valid IPv6 10/100 Base T

addresses 10/100 Base T

1x Ethernet RJ45 10/100/1000 BaseT

IP addressing  MPR-e has routing capability. From a

VID=XXX VID=XXX VID=XXX VID=XXX

Port #4 TMN TMN Ethernet

TMN Ethernet Network

Ethernet Data TMN Ethernet Network

Connecting TMN between two MPR shelves

MPR #2 Dir #38

Port #4 TMN Network (/29) MPR #1

Similar to the previous slide but by using In-Band Interfaces Local

Connecting to the wrong address is the primary reason for

Local Address 1 Local Address 2 Local Address 3 TMN

Addresses typically assigned from the fd00:: /8 sub-range (L-bit set to

For this example we will use IPv4 with Private Addressing

DHCP will be used for configuration of Craft computers.

Using the MPR internal DHCP server whenever possible is recommended.

Total 40 addresses 8 addresses

The Port #4 TMN interface is only enabled at two sites: A and B

Sixteen addresses out of the assigned 64 remain unused.

 What if the old expansion plans change