MPR TMN Networking

9500 MPR TMN Networking
3EM237181306BVZZA01p06 DRAFT March 3, 2010
9500MPR TMN Networking
1) 2) 3) 4) 5) 6) 7) 8)
TMN Interfaces TMN Related Services TMN IP Addresses The TMN Network MPR Addressing Craft and Management Communication Requirements Planning and Addressing a Network Configuring the MPR
-----------------------------------A. Basics of IP Addressing B. Communication in Networks C. MPR DHCP Overview D. MPR OSPF Overview E. Comparison to 8000 TMN Networking
2 3EM 23718 1306 BVZZA 9500 MPR TMN Networking March 3, 2010
All Rights Reserved Alcatel-Lucent 2009
9500MPR TMN Networking TMN Interfaces
9500MPR TMN Networking Physical Interfaces

Dir #34 Dir #35 Dir #N
Port #4 TMN
TMN Ethernet
The 9500MPR supports several interfaces for TMN traffic: 1. 2. 3. For transport across RF links, there are in-band PPPoE channels, one per Direction The TMN Ethernet port, enabled by default. This interface is intended primarily for local Craft access but can be connected to an external network. Optionally, User Ethernet Port #4 can be configured for TMN. This interface is intended for connecting to external networks for TMN backhaul.
9500MPR TMN Networking Interface to the Router

Dir #34 Dir #35 Dir #N
Port #4 TMN
TMN Ethernet Subnet
TMN Ethernet
Dir #34
R
Port #4 TMN Subnet
Dir #35 Dir #N
RF PPPoE links
Each TMN interface within the MPR is connected to an internal router. If the Port#4 TMN interface is enabled, the provisioned subnet must be different from the subnet defined at the TMN Ethernet interface. TMN traffic passing between any two interfaces is routed at Layer 3. The TMN interfaces do not support Bridging. This means the TMN subnets must be unique and not overlap.
9500MPR TMN Networking TMN Related Services
9500MPR TMN Networking Services - OSPF The 9500MPR provides two services related to TMN networking. The first service is OSPF for Dynamic Routing 1. 2. The MPR provides a basic implementation of OSPFv2 User configurable parameters are limited to: Enabling or disabling OSPF on each individual TMN interface. Setting the OSPF Area ID for each interface (default Area is 0) A single MPR can function as an Area Border Router (ABR) for up to four OSPF Areas. The MPR is able to interoperate with external OSPF capable devices such as a 7705.
3. 4.
9500MPR TMN Networking Services - DHCP The second service is a trivial DHCP server on the TMN Ethernet port 1. This limited server is intended to support dynamic address configuration of local Craft computers. 2. Enabled by default, it can be disabled. This is the only user configurable option. 3. The maximum number of DHCP Clients managed by the DHCP Server is 10. 4. The DHCP server uses an address pool based on the TMN Local Ethernet IP address and subnet. a) If the TMN Local Ethernet IP address lies in the upper half of the subnet, the pool starts at the first IP address of the subnet and continues up to the TMN Local Ethernet IP address minus one or a maximum of 10 addresses, whichever comes first. b) If the TMN Local Ethernet IP lies in the lower half of the subnet, the pool ranges from the TMN Local Ethernet IP address plus one to the last IP address of the subnet or a maximum of 10 addresses, whichever comes first. 5. Clients are served the same Netmask used on the TMN Local Ethernet interface with a Default Gateway set to the TMN Local Ethernet IP address. 6. The Lease Time is fixed to 10 minutes.
9500MPR TMN Networking TMN IP Addresses
9500MPR Networking MPR Addresses
The 9500MPR can be configured with up to three addresses.

Local Address:10.0.36.9
1.
The primary address is the NE Local Address: a) This is the Address of the MPR itself. Note: There is no Netmask setting associated with the Local Address. b) c) d) This is the address the Craft and SNMP Managers need to use when monitoring or provisioning the NE. All SNMP Traps and Notifications are issued from this address All RF PPPoE connections terminating in this shelf (one per Direction) use this address as their PPP Endpoint Identifier.
9500MPR Networking MPR Addressing
Port #4 TMN
Address: 192.168.10.0 Netmask: 255.255.255.192
TMN Ethernet
Address: 172.22.64.86 Netmask: 255.255.255.248
2.
3.
TMN Ethernet interface address a) Enabled by default. This interface is intended for local Craft access b) Can be connected to an external network. Optional Port #4 TMN Ethernet interface address a) Disabled by default. b) Intended for use when connecting to external networks to allow the TMN Interface to remain available for Local Craft access.
Tip: The Local Address can be set to match either the TMN Ethernet address or the Port#4 TMN Address, but not both.
9500MPR TMN Networking The TMN Network
9500MPR Networking The Basic TMN Network RF PPP Links
RF PPP Link
The RF PPP links come up as soon as the Radio channel is operational. It doesnt matter what Local IP Address is assigned at either end, when the Radio link is up, the routers are networked together and can exchange packets with each other.
9500MPR Networking The Basic TMN Network RF PPP Links
Site A RF PPP Link
Site B RF PPP Link
Site C
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. Routing can be configured dynamically or statically. The recommended configuration is to enable OSPF within the MPR network for dynamic routing.
9500MPR Networking The Basic TMN Network

Local Address:10.3.27.5 TMN Ethernet Port: 10.0.2.1 Local Address:172.22.37.49
Craft Address:10.0.2.2 Default Gateway: 10.0.2.1
R
TMN Ethernet Network
RF PPP Link
Craft Computer
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 Craft computer to an enabled TMN Ethernet Interface and configure the Craft computer to use the TMN Ethernet interface as the Default Gateway, we should be able to communicate with all the MPRs in the network. To connect with each NE using the Craft application, the Local Addresses for each NE are used: 10.3.27.5 and 172.22.37.49. If the MPR DHCP service is enabled and the Craft computer network interface is set to Obtain an IP address automatically, the Craft computer will require no user action for proper network configuration when connecting via the TMN Ethernet Port.
9500MPR Networking A Simple Linear Network
Port #4 TMN Subnet
R
TMN Ethernet Subnet
RF PPP Link
R
TMN Ethernet Subnet
RF PPP Link
R
TMN Ethernet Subnet
Port #4 TMN Subnet
To provide local access and to connect external equipment to the TMN network, we enable 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 site within the same Radio network. All TMN traffic is routed. Bridging between Ethernet subnets is not supported.
9500MPR Networking Supported TMN Network Topologies

R R R R R R R R R
Linear
R
Ring
R
R R
R R R R R
Mesh The TMN Network can be configured in Linear, Ring, or Mesh topologies. In 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 can also manage routes to prevent loops in the TMN Network. Note: This is in contrast to the 9500MPR Data transport layer which operates at Layer 2 where segregation must be used to prevent Ethernet loops.
9500MPR Networking Supported TMN Network Topologies

Management Traffic Path After a failure R External Router R R R R R R R R
Linear
R
External Network
SNMP Manager
Networks can have multiple external gateways that allow alternate management paths in the event of an outage. To take maximum advantage of multiple gateways, OSPF must be enabled throughout the radio network. To take full advantage of this capability, OSPF or some other dynamic routing protocol may be needed on the external network.
9500MPR TMN Networking MPR Addressing
How many addresses does an MPR need? A better question might be: How much address space does an MPR require? To answer these questions, we need to know how the interfaces are used in various configurations.
Port #4 TMN
Address: 192.168.10.0 Netmask: 255.255.255.192
TMN Ethernet
Address: 172.22.64.86 Netmask: 255.255.255.248
9500MPR Networking MPR Addressing Adding an MPR terminal to an existing Network

Existing Network
External Network
Optional DHCP Server
Router
192.168.64.1
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
If an MPR is connected to an 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. Craft connections access the MPR by connecting through the existing network. If an external DHCP server is present, the internal DHCP server on the TMN Ethernet interface should be disabled before connecting the MPR to the external network in order to prevent conflicts!

When an MPR installed at a location where no pre-existing external network is available, the MPR must, at a minimum, define a network that can be used for local Craft connections. The smallest useable Ethernet network that can be defined for this interface is a /30. In this sized network, only two useable addresses are available, one for the TMN Ethernet port and one for a Craft computer. The MPR internal DHCP server would normally be used to configure the network interface on the Craft computer when it connects. In this example, the Local Address happens to be set differently from the TMN Ethernet address. This means the MPR consumes the space of 5 IP addresses: 4 IP addresses for the TMN Ethernet 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.7 Broadcast Netmask: 255.255.255.252
Remember: To provision or manage this NE, the Craft or SNMP Manager must connect using the 172.22.46.51 Local Address regardless of whether the physical connection is local or remote!

If it is necessary to manage other external equipment at the site through the MPR TMN Network, Port #4 may be enabled in TMN mode and configured with a suitably sized network.
Port #4 TMN Ethernet Network 192.168.137.24 Network Number 192.168.137.25 MPR Port #4 192.168.137.26 Ext Eqpt 1 192.168.137.27 Ext Eqpt 2 192.168.137.28 Ext Eqpt 3 192.168.137.29 spare 1 192.168.137.30 spare 192.168.137.31 Broadcast Netmask: 255.255.255.248 Local Address: 192.168.137.25
Local Net 3 2
TMN Ethernet Network 10.3.27.4 Network Number 10.3.27.5 MPR TMN Ethernet 10.3.27.6 Craft 10.3.27.7 Broadcast Netmask: 255.255.255.252
In this example, we have three external devices requiring addresses. This requires a subnet large enough to a provide a total of four addresses: one for each of the three external devices plus the address for the Port#4 interface. The smallest subnet that can provide at least four useable 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 an SNMP management perspective. As shown, the MPR (with external equipment) consume the space of eight addresses for the Port#4 TMN network, plus the space of four addresses for the TMN Ethernet network for a total of space of 12 addresses. Note: The spare addresses left over cannot be deployed at another site. They remain part of this subnet. They are available for future expansion at this site. Be aware that all TMN traffic is carried through the MPR network in-band at high priority. MPR TMN traffic is relatively low bandwidth. A high volume of traffic to and from external equipment may impact revenue bearing traffic!

Connecting multiple MPR shelves at a site using the TMN Ethernet port
TMN Ethernet Network 10.3.27.64 Network 10.3.27.65 MPR #1 (DHCP server disabled) 10.3.27.66 MPR #2 (DHCP server disabled) 10.3.27.67 MPR #3 10.3.27.68 DHCP Assigned 10.3.27.69 DHCP Assigned 10.3.27.70 DHCP Assigned 10.3.27.71 Broadcast Netmask: 255.255.255.248 MPR #1 Dir #35
MPR #1
MPR #2 External Switch MPR #3 Local
In this configuration, all TMN Ethernet ports are addressed in the same subnet and connected together with an external switch. DHCP is disabled on MPR#1 and MPR#2 and enabled on MPR#3.
The IP Address of MPR#3 is assigned to be in the middle MPR #3 Dir #38 Craft of the subnet to minimize the number of DHCP addresses being reserved. Since the address of MPR#3 is in the lower half of the subnet, It will lease all the addresses above it to the end of the subnet. If each MPR Local Address matches the corresponding TMN Ethernet port address, the entire site will only consume the space of 8 addresses. TMN Traffic flowing through the site via MPR #1 Dir #35 and MPR #3 Dir #38 will pass through the external switch. Note: If the Core Card running the DHCP server (MPR#3) fails, manual configuration of the Craft computer interface will be required to access the other radios or the remaining radio network.

Connecting multiple MPR shelves at a site using the Port #4 TMN port
Port #4 TMN Network 10.3.27.64 Network 10.3.27.65 MPR #1 10.3.27.66 MPR #2 10.3.27.67 MPR #3 10.3.27.68 External Eqpt #1 10.3.27.69 External Epqt #2 10.3.27.70 Spare 10.3.27.71 Broadcast Netmask: 255.255.255.248 MPR #1 Dir #35
MPR #1 Local Craft External Switch Ext #1

Ext #2
MPR #2 Local Craft MPR #3 Local Craft
MPR #3 Dir #38
All Port #4 TMN ports are addressed in the same /29 subnet and connected together with an external switch. External site equipment is connected to the TMN Network. As before, TMN Traffic flowing through the site via MPR #1 Dir #35 and MPR #3 Dir #38 will pass through the external switch. Each TMN Ethernet interface is configured with its own unique /30 subnet and the DHCP server in each MPR is enabled (details not shown). Each Craft computer will have full access to the MPR TMN Network. This configuration also permits independent local Craft access to each MPR at the expense of slightly more address space. This solves the problem of the previous example of a Core failure taking out the only DHCP server. The site consumes 20 addresses, eight for the /29 and twelve for the three /30 networks.

Connecting multiple MPR shelves at a site without an external switch
IP Addr 10.3.27.64 10.3.27.65 10.3.27.66 10.3.27.67 10.3.27.68 10.3.27.69 10.3.27.70 10.3.27.71 10.3.27.72 10.3.27.73 10.3.27.74 10.3.27.75 10.3.27.76 10.3.27.77 10.3.27.78 10.3.27.79 Equipment Network MPR #1 TMN Eth Craft Broadcast Network MPR #1 Port #4 MPR #2 Port #4 Broadcast Network MPR #2 TMN Eth MPR #3 TMN Eth Broadcast Network MPR #3 Port #4 Ext #1 Broadcast Comment Netmask: 255.255.255.252 Also MPR #1 Local Address DHCP Assigned Netmask: 255.255.255.252 Ext #1 Netmask: 255.255.255.252 Also MPR #2 Local Address Also MPR #3 Local Address Netmask: 255.255.255.252 MPR #3 MPR #1 MPR #1 Dir #35
Local Craft
MPR #2
MPR #3 Dir #38
This example uses four /30 subnets, and connects three MPR shelves and one external device without the use of an external switch. The table shows the addresses of the four subnets being adjacent, but this is not a requirement. One TMN Ethernet port is dedicated for Craft use with DHCP enabled. The path for TMN Traffic flowing through the site via Dir #35 and Dir #38 is indicated. Unlike the previous example using an external switch, this traffic must pass through MPR #2 with an additional routing hop delay.
9500MPR TMN Networking Craft and Management Communication Requirements
9500MPR Networking Management
We know up to three addresses can be assigned to each MPR, Which address can be used for Craft Access? Which address can be used for Management?
Port #4 TMN
Address: 192.168.10.0 Netmask: 255.255.255.192
TMN Ethernet
Address: 10.0.36.9 Netmask: 255.255.255.248
9500MPR Networking Management
The Local Address is used to provision and Manage the MPR.

Regardless of how either the TMN Ethernet or the Port #4 TMN Interface are configured, the Local Address is the one to specify in NEtO when using the Craft, or at an SNMP Manager. NEtO Example Local Address:172.22.46.51
Port #4 TMN
Address: xxx.xxx.xxx.xxx Netmask: nnn.nnn.nnn.nnn
TMN Ethernet
Address: yyy.yyy.yyy.yyy Netmask: mmm.mmm.mmm.mmm
Connecting to the wrong address is the primary reason for provisioning problems with the MPR when using the Craft!
9500MPR Networking Management Why?

1. The MPR SNMP Agent appears to respond at all the MPR IP Addresses, but SNMP Traps and Notifications only originate from the Local Address. When the Craft performs complex SNMP operations such as cross-connections, it expects SNMP Notifications verifying completion. The Craft will be listening for these Notifications to come from the address specified in NEtO. It will ignore Notifications that come from other (unknown) addresses. If the Craft does not receive the proper responses, provisioning fails.
2.
SNMP Managers must know which IP Addresses will be sending Traps so that Alarms can be associated with the proper NE. The 5620SAM is aware of the MPR behavior. When the SAM identifies an MPR during discovery, it inspects the appropriate SNMP MIB object to determine the Local Address of that 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 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 unique interface IP address, or by Traps that arrive from unknown NEs, where the source address correlates with an MPR Local Address somewhere in the network.
9500MPR Networking Network Communication
Local Address 1
Port #4 TMN Subnet
Local Address 2 RF PPP Link
Local Address 3 RF PPP Link
R
TMN Ethernet Subnet
R
TMN Ethernet Subnet
R
TMN Ethernet Subnet
Port #4 TMN Subnet
A Local Craft
B Local Craft
C Local Craft
External Network
SNMP Manager
Communication requirements with external networks SNMP packets from the Local Address of each NE must have a route to the manager. This is usually provided by either a Static Default Route at the MPR Network 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 using OSPF.
9500MPR TMN Networking Planning and Addressing a Network
9500MPR TMN Networking TMN Network Planning

SNMP Manager
Fiber or other
R2 Site Network
External Network
E F A
R1 Site Network Ext DHCP Server Existing external equipment
1 2
B
1 2 3
D
1
Consider the above network. For TMN purposes, it is a combination of Linear and Ring topologies. External equipment to be managed is located at sites B, D, and E. How could this network be addressed?
9500MPR TMN Networking TMN Network Planning Definitions Site A is an existing site where other equipment is already installed. The 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 a junction. There are three external devices to manage via the TMN Network. Site C is a repeater with no external equipment. Site D is a repeater with one external devices. Site E is a repeater with two external devices. A new router (R2) connected via an external link will be added to provide an alternate pathway for TMN Traffic. The MPR DHCP server will provide DHCP services for all transient craft devices at the site. Site F is a repeater with no external equipment.

Assumptions OSPF will be enabled within the network1 The MPR network will be an Autonomous (isolated) OSPF network. It will use Static routing at the borders2 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 network will be created with router R2 providing an alternate external route for TMN traffic. The MPR at site E will be come a member of this network and will use Router R2 as the Default Gateway to reach other external networks The Local Address will be set to match the TMN Ethernet Port address at all sites. DHCP is used for configuration of Craft computers.3
1The
recommended configuration is to enable OSPF within the MPR network whenever possible. Correctly configuring Static routing can be complex for anything more than trivial linear networks. 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, if the link fails, it can reroute the TMN traffic to use any reachable alternate gateway provided one is available.
2The
the MPR internal DHCP server whenever possible is 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. The user only needs to know the Local Addresses of the equipment to use NEtO/Craft for local access.
3Using

Site Site A TMN Ethernet Network 4 address subnet (/30) Port #4 TMN Network Comments 0 new addresses (uses an Port #4 TMN interface will be connected with the local address from existing site network. TMN Ethernet port to remain active with DHCP for emergency Local Craft access. external network) 8 address subnet (/29) External eqpt connected to Port #4 TMN interface. Using TMN Eth for all external equipment would require a 16 address subnet since the MPR DHCP will reserve a minimum of half the subnet. No external equipment. Direct craft connections only. External device connected to the TMN Eth Port. No addressing advantage to splitting the subnet between TMN Eth and Port #4 TMN Extra addresses reserved to allow adding equipment as the network expands. No external equipment. Direct craft connections only.
Site B
4 address subnet (/30)
Site C Site D
4 address subnet (/30) 8 address subnet (/29)
(disabled) (disabled)
Site E Site F
16 address subnet (/28) 4 address subnet (/30)
(disabled) (disabled)
Total
40 addresses
8 addresses
The TMN Ethernet port with DHCP enabled is active at all sites. The Port #4 TMN interface is only enabled at one site, Site B At sites where there is external equipment, it is attached to the TMN Ethernet interface using an external switch.
9500MPR TMN Networking TMN Network Planning 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 addresses Netmasks force subnets start and end on specific boundaries. For example a subnet containing 8 addresses must start at an address that is evenly divisible by 8. Before we request address space, 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 Netmask: 255.255.255.252 xxx.xxx.xxx.0 xxx.xxx.xxx.1 xxx.xxx.xxx.2 xxx.xxx.xxx.3 Network (/30) A TMN Eth Port DHCP Assigned Broadcast MPR C TMN Ethernet Subnet Netmask: 255.255.255.252 xxx.xxx.xxx.16 xxx.xxx.xxx.17 xxx.xxx.xxx.18 xxx.xxx.xxx.19 Network (/30) C TMN Eth Port DHCP Assigned Broadcast MPR E TMN Ethernet Subnet Netmask: 255.255.255.240 xxx.xxx.xxx.32 xxx.xxx.xxx.33 xxx.xxx.xxx.34 xxx.xxx.xxx.35 xxx.xxx.xxx.36 MPR B TMN Ethernet Subnet Netmask: 255.255.255.252 xxx.xxx.xxx.4 xxx.xxx.xxx.5 xxx.xxx.xxx.6 xxx.xxx.xxx.7 Network (/30) B TMN Eth Port DHCP Assigned Broadcast MPR F TMN Ethernet Subnet Netmask: 255.255.255.252 xxx.xxx.xxx.20 xxx.xxx.xxx.21 xxx.xxx.xxx.22 xxx.xxx.xxx.23 Network (/30) F TMN Eth Port DHCP Assigned Broadcast xxx.xxx.xxx.37 xxx.xxx.xxx.38 xxx.xxx.xxx.39 xxx.xxx.xxx.40 xxx.xxx.xxx.41 xxx.xxx.xxx.42 xxx.xxx.xxx.43 xxx.xxx.xxx.44 xxx.xxx.xxx.45 xxx.xxx.xxx.46 xxx.xxx.xxx.47 Network (/28) Router R2 E Ext Eqpt 1 E Ext Eqpt 2 Spare Spare Spare E TMN Eth Port DHCP Assigned DHCP Assigned DHCP Assigned DHCP Assigned DHCP Assigned DHCP Assigned DHCP Assigned Broadcast
MPR B Port #4 TMN Subnet Netmask: 255.255.255.248 xxx.xxx.xxx.8 xxx.xxx.xxx.9 xxx.xxx.xxx.10 xxx.xxx.xxx.11 xxx.xxx.xxx.12 xxx.xxx.xxx.13 xxx.xxx.xxx.14 xxx.xxx.xxx.15 Network (/29) B Port #4 B Ext Eqpt 1 B Ext Eqpt 2 B Ext Eqpt 3 Spare Spare Broadcast
MPR D TMN Ethernet Subnet Netmask: 255.255.255.248 xxx.xxx.xxx.24 xxx.xxx.xxx.25 xxx.xxx.xxx.26 xxx.xxx.xxx.27 xxx.xxx.xxx.28 xxx.xxx.xxx.29 xxx.xxx.xxx.30 xxx.xxx.xxx.31 Network (/29) D Ext Eqpt 1 Spare D TMN Eth Port DHCP Assigned DHCP Assigned DHCP Assigned Broadcast
This shows how the required subnets could map into a block of 48 contiguous addresses. Other 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 addresses: we could be assigned a single /26 block with 64 addresses. If the availability of new addresses are 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. For this example, well assume weve been assigned 172.28.137.64 /26 The block contains 64 addresses ranging from 172.28.137.64 to 172.28.137.127 This block of addresses will be further divided into subnets following our plan.

MPR A TMN Ethernet Subnet Netmask: 255.255.255.252 172.28.137.64 172.28.137.65 172.28.137.66 172.28.137.67 Network (/30) A TMN Eth Port (L) DHCP Assigned Broadcast MPR C TMN Ethernet Subnet Netmask: 255.255.255.252 172.28.137.80 172.28.137.81 172.28.137.82 172.28.137.83 Network (/30) C TMN Eth Port (L) DHCP Assigned Broadcast MPR E TMN Ethernet Subnet Netmask: 255.255.255.240 172.28.137.96 172.28.137.97 172.28.137.98 172.28.137.99 172.28.137.100 MPR B TMN Ethernet Subnet Netmask: 255.255.255.252 172.28.137.68 172.28.137.69 172.28.137.70 172.28.137.71 Network (/30) B TMN Eth Port (L) DHCP Assigned Broadcast MPR F TMN Ethernet Subnet Netmask: 255.255.255.252 172.28.137.84 172.28.137.85 172.28.137.86 172.28.137.87 Network (/30) F TMN Eth Port (L) DHCP Assigned Broadcast 172.28.137.101 172.28.137.102 172.28.137.103 172.28.137.104 172.28.137.105 172.28.137.106 172.28.137.107 172.28.137.108 172.28.137.109 172.28.137.110 172.28.137.111 Network (/28) Router R2 E Ext Eqpt 1 E Ext Eqpt 2 Spare Spare Spare E TMN Eth Port (L) DHCP Assigned DHCP Assigned DHCP Assigned DHCP Assigned DHCP Assigned DHCP Assigned DHCP Assigned Broadcast Address assignments from the existing subnet at Site A.
MPR B Port #4 TMN Subnet Netmask: 255.255.255.248 172.28.137.72 172.28.137.73 172.28.137.74 172.28.137.75 172.28.137.76 172.28.137.77 172.28.137.78 172.28.137.79 Network (/29) B Port #4 B Ext Eqpt 1 B Ext Eqpt 2 B Ext Eqpt 3 Spare Spare Broadcast
MPR D TMN Ethernet Subnet Netmask: 255.255.255.248 172.28.137.88 172.28.137.89 172.28.137.90 172.28.137.91 172.28.137.92 172.28.137.93 172.28.137.94 172.28.137.95 Network (/29) D Ext Eqpt 1 Spare D TMN Eth Port (L) DHCP Assigned DHCP Assigned DHCP Assigned Broadcast
MPR A Port #4 TMN Subnet Netmask: 255.255.255.224 192.168.19.1 192.168.19.23 Router R1 MPR A Port #4
Merging our assigned addresses into the tables shows how to address our equipment. MPR Local addresses were set to match the TMN Ethernet Port as specified in the Assumptions and are labeled (L).
9500MPR TMN Networking TMN Network Planning Growing the Network
172.28.137.112 172.28.137.113 172.28.137.114 172.28.137.115 172.28.137.116 172.28.137.117 172.28.137.118 172.28.137.119 172.28.137.120 172.28.137.121 172.28.137.122 172.28.137.123 172.28.137.124 172.28.137.125 172.28.137.126 172.28.137.127
Unused Unused Unused Unused Unused Unused Unused Unused Unused Unused Unused Unused Unused Unused Unused Unused
Sixteen addresses out of the assigned 64 remain unused.

The MPR at Site A will be configured with a static route to use R1 as its default gateway.
This is required so that TMN traffic destined to leave the MPR TMN Network will have a way out!
Conversely, External router R1 must be configured to use MPR A as a gateway to access the network 172.28.137.64 /26
The MPR at site E will be configured with a static route to use R2 as its default gateway
This defines an alternate gateway for traffic leaving the MPR TMN network.
External router R2 must also be configured to use MPR E as a gateway for network 172.28.137.64 /26
This route provides an alternate way into the MPR TMN Network.
9500MPR TMN Networking TMN Network Planning Growing the network

SNMP Manager
R2
Fiber or other
Site Network
G
External Network
H
3 4 5
E F A
R1 Site Network Ext DHCP Server
1 2
J D
1 1
B
1 2 3
K C
1
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 allowed for no expansion needs a new external device? What if previous expansion plans change, and additional external equipment that was originally going to be deployed at E will now be deployed at H, leaving site E, which had extra addresses for expansion, with unused addresses? We know we can assign some of the addresses from space left over from the original /26, but we dont have enough addresses for all the equipment. Well have to request additional address space.
9500MPR TMN Networking TMN Network Planning Growing the network

Heres the new plan:
Site Site E TMN Ethernet Network Port #4 TMN Network Comments Original 16 address subnet now 8 address subnet (/29) Extra address space no longer needed. Split 16 a 4 address subnet (/30) address subnet, allocating 8 addresses to Port #4 TMN and 4 addresses to TMN Ethernet. Redeploy recovered 4 addresses to site F. (Keep existing subnet) 4 address subnet (/30) Add subnet to Port #4 TMN interface for new equipment, using the address space recovered from Site E. (disabled) No external equipment. Direct craft connections only.
Site F
Site G
4 address subnet (/30)
Site H Site J Site K Total
4 address subnet (/30) 8 address subnet (/29) 8 address subnet (/29) 24 new addresses
8 address subnet (/29) External eqpt connected to Port #4 TMN interface. (disabled) (disabled) 8 new addresses
Expansion of the network will require the space of 32 addresses, 16 of which are available from our original assignment, and 16 new addresses. We request a new block of 16 addresses. 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 Netmask: 255.255.255.252 172.28.137.64 172.28.137.65 172.28.137.66 172.28.137.67 Network (/30) A TMN Eth Port (L) DHCP Assigned Broadcast MPR C TMN Ethernet Subnet Netmask: 255.255.255.252 172.28.137.80 172.28.137.81 172.28.137.82 172.28.137.83 Network (/30) C TMN Eth Port (L) DHCP Assigned Broadcast
MPR B TMN Ethernet Subnet Netmask: 255.255.255.252 172.28.137.68 172.28.137.69 172.28.137.70 172.28.137.71 Network (/30) B TMN Eth Port (L) DHCP Assigned Broadcast
MPR D TMN Ethernet Subnet Netmask: 255.255.255.248 172.28.137.88 172.28.137.89 172.28.137.90 172.28.137.91 172.28.137.92 172.28.137.93 172.28.137.94 172.28.137.95 Network (/29) D Ext Eqpt 1 Spare D TMN Eth Port (L) DHCP Assigned DHCP Assigned DHCP Assigned Broadcast
MPR B Port #4 TMN Subnet Netmask: 255.255.255.248 172.28.137.72 172.28.137.73 172.28.137.74 172.28.137.75 172.28.137.76 172.28.137.77 172.28.137.78 172.28.137.79
Network (/29) B Port #4 B Ext Eqpt 1 B Ext Eqpt 2 B Ext Eqpt 3 Spare Spare Broadcast
MPR F TMN Ethernet Subnet Netmask: 255.255.255.252 172.28.137.84 172.28.137.85 172.28.137.86 172.28.137.87 Network (/30) F TMN Eth Port (L) DHCP Assigned Broadcast

OLD
MPR E TMN Ethernet Subnet Netmask: 255.255.255.240 172.28.137.96 172.28.137.97 172.28.137.98 172.28.137.99 172.28.137.100 172.28.137.101 172.28.137.102 172.28.137.103 172.28.137.104 172.28.137.105 172.28.137.106 172.28.137.107 172.28.137.108 172.28.137.109 172.28.137.110 172.28.137.111 Network (/28) Router R2 E Ext Eqpt 1 E Ext Eqpt 2 Spare Spare Spare E TMN Eth Port (L) DHCP Assigned DHCP Assigned DHCP Assigned DHCP Assigned DHCP Assigned DHCP Assigned DHCP Assigned Broadcast
NEW
MPR E Port #4 TMN Subnet Netmask: 255.255.255.248 172.28.137.96 172.28.137.97 172.28.137.98 172.28.137.99 172.28.137.100 172.28.137.101 172.28.137.102 172.28.137.103 Network (/29) Router R2 E Ext Eqpt 1 E Ext Eqpt 2 MPR E Port #4 Spare Spare Broadcast
MPR E TMN Ethernet Subnet Netmask: 255.255.255.248 172.28.137.104 172.28.137.105 172.28.137.106 172.28.137.107 Network (/30) MPR E TMN Eth (L) DHCP Assigned Broadcast
MPR F Port #4 TMN Subnet Netmask: 255.255.255.252 172.28.137.108 172.28.137.109 172.28.137.110 172.28.137.111 Network (/30) MPR F Port #4 DHCP Assigned Broadcast
This is how the old subnet E is split to recover some unused address space. Half the address space moves to the E Port #4 TMN subnet. Four addresses from the old subnet are remain assigned to the new E TMN Eth subnet with a new netmask. The remaining four addresses are moved to the site F Port #4 subnet. New or changed addressing parameters are highlighted in red.

MPR G TMN Ethernet Subnet Netmask: 255.255.252 172.28.137.112 172.28.137.113 172.28.137.114 172.28.137.115 Network (/30) MPR G TMN Eth (L) DHCP Assigned Broadcast
MPR H TMN Ethernet Subnet Netmask: 255.255.255.252 172.28.137.116 172.28.137.117 172.28.137.118 172.28.137.119 Network (/30) MPR H TMN Eth (L) DHCP Assigned Broadcast
MPR H Port #4 TMN Subnet Netmask: 255.255.255.248 172.28.137.120 172.28.137.121 172.28.137.122 172.28.137.123 172.28.137.124 172.28.137.125 172.28.137.126 172.28.137.127 Network (/29) MPR H Port #4 H Ext Eqpt 1 H Ext Eqpt 2 H Ext Eqpt 3 Spare Spare Broadcast
The unused 16 addresses from the original /26 are split into subnets and assigned at sites G and H.

MPR J TMN Ethernet Subnet Netmask: 255.255.255.248 172.30.10.0 172.30.10.1 172.30.10.2 172.30.10.3 172.30.10.4 172.30.10.5 172.30.10.6 172.30.10.7 Network (/29) J Ext Eqpt 1 Spare MPR J TMN Eth (L) DHCP Assigned DHCP Assigned DHCP Assigned Broadcast
MPR K TMN Ethernet Subnet Netmask: 255.255.255.248 172.30.10.8 172.30.10.9 172.30.10.10 172.30.10.11 172.30.10.12 172.30.10.13 172.30.10.14 172.30.10.15 Network (/29) K Ext Eqpt 1 Spare MPR K TMN Eth (L) DHCP Assigned DHCP Assigned DHCP Assigned Broadcast
This slide shows address assignments using the new block of 16 addresses External routers R1 and R2 will need additional static routes to use MPR A and MPR E respectively as gateways to access the new 172.30.10.0/28 network OSPF will manage the necessary route changes within the MPR TMN Network.
9500MPR TMN Networking Configuring the MPR
9500MPR Networking MPR Addressing Setting the Local Address
The Local Address is set in the Local Configuration dialog box. a) Access the Local Configuration from the Menu by selecting: Configuration->Network Configuration->Local Configuration b) Enter the Local Address and click Apply The MPR will reboot when this address is changed. After the reboot, you will need to reconnect using the new Local Address
9500MPR Networking MPR Addressing Setting the TMN Ethernet interface addresses
2 1 3 The TMN Ethernet interfaces:

1. In the Craft Equipment View, doubleclick on the Core Main module. This opens the Core Main View In the View, select the TMN Interface tab. Current interface settings are shown on the right side of the panel Highlight the interface to configure, either the TMN Ethernet or Port #4 TMN Ethernet* To change the parameters, select the Settings tab at the bottom of the panel
2.
3.
4.
*If Port #4 TMN is needed and is not an available choice, see the Preparing Port #4 for TMN mode
slide .
on the next
9500MPR Networking MPR Addressing Preparing Port #4 for TMN mode

2 1 4
3
Before Port #4 can be configured for TMN, the User port settings must be disabled and returned to defaults. 1. In the Craft Equipment View, double-click on the Core Main module. This opens the Core Main View 2. In the View, select the Ethernet Physical Interface tab. 3. Highlight the Ethernet Port#4 interface. 4. Verify Port #4 status shows Disabled. The port status shown here must be Disabled before TMN mode can be set. 5. If it is necessary to Disable the port, select the Settings tab at the bottom of the panel. 6. Uncheck Auto Negotiation Status if needed, and click Apply 7. Uncheck the Enabled box and click Apply.
5 7 6
9500MPR Networking MPR Addressing Configuring the RF PPPoE Links

2
For MPT-HL RF PPPoE interfaces:

1. In the Craft Equipment View doubleclick on the P8ETH EAS Board. This opens the EAS Main View. In the View panel select the desired MPT-HL Port Click on the Settings Tab In the PPP RF area configure as needed. No IP Address is assigned, the Local Address will be used. Click on Apply
2. 3. 4.
5.
When both ends of the link are configured and the link comes up, the detected far end MPR Local Address will show in the Remote Address box.
9500MPR Networking MPR Addressing Configuring the RF PPPoE Links

2
For ODU300 RF PPP interfaces:

1. In the Craft Equipment View doubleclick on the MD300 Board. This opens the Radio Main View. In the View panel click on the Settings Tab Click on the sub-panel resize arrows to expand the PPP RF area. In the PPP RF area configure as needed. No IP Address needs to be assigned, the Local Address will be used. Click on Apply
2. 3. 4.
5.
When both ends of the link are configured and the link comes up, the detected far end MPR Local Address will show in the Remote Address box.
www.alcatel-lucent.com www.alcatel-lucent.com
9500MPR TMN Networking Appendix Basics of IP Addressing
9500MPR TMN Networking IP Addressing Primer Addressing 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 only support IPv4 addressing
9500MPR TMN Networking IP Addressing Primer IPv4 Addresses
IPv4 ADDRESS IPv4 addresses are a 32 bit binary number: 1010 1100 0001 0110 1000 1010 1100 1111 The most common representation uses dotted decimal notation such as: 172.22.138.207 Each of the four decimal numbers represents 8 bits of the 32 bit address. This means each of the four numbers can range from 0 to 255.
9500MPR TMN Networking IP Addressing Primer IP Address 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 -> 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. If 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 network prefix host number
If 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 network prefix
host number
9500MPR TMN Networking IP Addressing Primer The 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. Netmasks consists of: a contiguous string of ones at the more significant end for the Network prefix portion a contiguous string of zeros at the less significant end for the Host number portion No intervening bits Table 1 Using the example address from before, the corresponding Acceptable mask values netmask is shown: HEX BIN DEC 172.22.138.207 -> 1010 1100 . 0001 0110 . 1000 1010 . 1100 1111 network prefix host number
00 0000 0000 0 80 1000 0000 128 C0 1100 0000 192 E0 1110 0000 224 F0 1111 0000 240 F8 1111 1000 248 FC 1111 1100 252 FE 1111 1110 254 FF 1111 1111 255
255.255.252.0 -> 1111 1111 . 1111 1111 . 1111 1100 . 0000 0000 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 network and host portions to be defined in 1 bit increments. The table to the right shows allowed values.
9500MPR TMN Networking IP Addressing Primer Derivation of related network parameters
Netmask are utilized for ease of hardware computation of related Network parameters. A logical AND of the Netmask and Address gives the Network Number. 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.100.49.255 Broadcast
9500MPR TMN Networking IP Addressing Primer Describing Networks

There are two ways to describe networks: 1. Long Hand method: Requires 3 numbers, only two of which are needed to determine the third. Network Address (all 0s host) Broadcast Address (all 1s host) Netmask (leading 1s, trailing 0s) 2. Short hand method: Network number/Netmask length Trailing zeros in the Network Number are often dropped. The Netmask Length corresponds to the number of ones defining the Network Prefix Long Hand
Loop back Network NET 127.0.0.0 MASK 255.0.0.0 BCAST 127.255.255.255
Short Hand
127/8
Binary
0111 1111.0000 0000.0000 0000.0000 0000 1111 1111.0000 0000.0000 0000.0000 0000 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 MASK 255.255.0.0 BCAST 192.168.255.255 Sample Network Info 143.209.100/22 NET 143.209.100.0 MASK 255.255.252.0 BCAST 143.209.103.255
1100 0000.1010 1000.0000 0000.0000 0000 1111 1111.1111 1111.0000 0000.0000 0000 1100 0000.1010 1000.1111 1111.1111 1111
1000 1111.1101 0001.0110 0100.0000 0000 1111 1111.1111 1111.1111 1100.0000 0000 1000 1111.1101 0001.0110 0111.1111 1111
9500MPR TMN Networking IP Addressing Primer Possible Network Sizes

Two hosts are reserved in any Ethernet network for the Network Number, and the Broadcast address: the all 0s host and the all 1s host respectively. This means the number of useable hosts is two less than the total number of addresses in the network. The smallest Ethernet network with useable address space is highlighted in RED.
Table 2
Network bits 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 host bits 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 useable hosts 0 2 6 14 30 62 126 254 510 1022 2046 4094 8190 16382 32766 65534 Decimal mask 255.255.255.254 255.255.255.252 255.255.255.248 255.255.255.240 255.255.255.224 255.255.255.192 255.255.255.128 255.255.255.0 255.255.254.0 255.255.252.0 255.255.248.0 255.255.240.0 255.255.224.0 255.255.192.0 255.255.128.0 255.255.0.0
9500MPR TMN Networking IP Addressing Primer 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 easy. Here are links to two such tools:
http://www.subnetmask.info/ http://www.subnet-calculator.com/
9500MPR TMN Networking Appendix Basic Networking Concepts
9500MPR TMN Networking Basic Networking Concepts - Communication within a Network
Computer 1
Computer 2
Network
A simple local network using Ethernet to allow Computer 1 and Computer 2 to communicate with each other. The network could be implemented with fiber, twistedpair (such as CAT-5) or some other technology. The connection between the two computers could be direct using a single crossover cable, or via a switch or hub.
Computer 1
00:C0:F8:34:19:C0
Computer 2
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 designed to be unique, and is used to help identify a machine on a network.
Computer 1 10.0.0.1 Network
Computer 2 10.0.0.2
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

Computer 1 10.0.0.1
Who has 10.0.0.2? Im at 00:C0:DF:48:F3:47
Computer 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. This is normally resolved using a broadcast that queries every system on the local network asking the device you are trying to communicate with to send back its MAC address. This process is handled in TCP/IP by Address Resolution Protocol (ARP)
9500MPR TMN Networking Basic Network Concepts TCP Stack
So how do the addressing methods fit together?

Sender Receiver
Virtual Connection Application Layer
SNMP Manager Layer 5 TCP, UDP Packets Layer 4 IP Datagram Layer 3 Ethernet Frames Layer 2 Copper, Fiber, etc Layer 1
Application Layer
SNMP Agent
Transport Layer
Transport Layer
Network Layer
Network Layer
IP Addresses used at this layer MAC Addresses used at this layer
Data Link Layer
Data Link Layer
Physical Network
Physical Connection
Physical Network
MAC addresses are used at Layer 2 IP Addresses are used at Layer 3

9500MPR TMN Networking Basic Networking Concepts Connecting Networks
Computer 2
Computer 4
Network A
Network B
Computer 1
Computer 3
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.
9500MPR TMN Networking Basic Networking Concepts - Router and Bridge Comparison
There are two common ways to connect networks together
Sender
Applicati on Layer Virtual Connection
Receiver
Applicati on Layer Transport Layer
Bridges connect at Layer 2
Transport Layer
Layer 3 Layer 2 Layer 1
Network Layer Data Link Layer
Bridge
Data Link Layer Data Link Layer
Physical Physical Physical Network Connection Network
Sender
Applicati on Layer
Receiver
Routers connect at Layer 3 Layer 3

Layer 2 Layer 1
Transport Layer Network Layer Data Link Layer
Router
Virtual Connection
Applicati on Layer Transport Layer Network Layer Data Link Layer

Computer 2 10.0.0.2 Computer 4 10.0.0.4
Network A
Switch
Network B
Computer 1 10.0.0.1
Computer 3 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 address space. Packets received at one port are essentially repeated on the other port(s). Most bridges are somewhat smarter about which packets they forward and where, but thats beyond the scope of this presentation. The 9500MPR TMN Network does not bridge between TMN Ports or across RF Links!

Computer 2 IP 172.22.64.2 Gateway 172.22.64.38 Computer 4 IP 192.168.10.4 Gateway 192.168.10.137
Network A
Interface 172.22.64.38
Router
Interface 192.168.10.137
Network B
Computer 1 IP 172.22.64.1 Gateway 172.22.64.38
Computer 3 IP 192.168.10.3 Gateway 192.168.10.137
Routers are another way to connect two networks together. Routers are used when the two networks use different addressing space. Unlike bridges, interfaces on a router have an address within the networks they are attached to. The interface IP address of a router is a gateway to other networks. Most network devices are configured to use a nearby router as a Default Gateway.
9500MPR TMN Networking Basic Networking Concepts - Routers

192.168.64.0/18 External Network Router 192.168.0.0/16 65534 addresses
192.168.0.0/20 4094 addresses 192.168.16.0/20 4094 addresses
192.168.0.0/18 16346 addresses
External Network
Router A
192.168.128.0/18 16346 addresses
Router B
192.168.32.0/20 4094 addresses
192.168.192.0/18 16346 addresses
192.168.48.0/20 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, allowing more optimal use of the available address space. Each division is called a sub-network. In the above example, the original 192.168.64.0/16 network is divided into four subnets by increasing the length of the netmask for the new subnets from 16 to 18 bits. Three of the new subnets are directly attached to Router A. One /18 subnet has been further divided into four /20 subnets using Router B. Router B has an interface in the 192.168.0.0/18 network. Router A doesnt need to know that Router B has divided the 192.168.64.0/18 network into subnets, it only needs to know that the 192.168.64.0/18 aggregate address space is accessible via Router B.
9500MPR TMN Networking Route Configuration

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. The Dynamic routing message exchange is depicted below:
I know how to reach addresses in the space: 192.168.64.0/18 Use my gateway at: 192.168.0.35 192.168.0.0/20 4094 addresses 192.168.16.0/20 4094 addresses
External Networks
Router A
192.168.0.0/18 16346 addresses
Router B
192.168.32.0/20 4094 addresses
Use me for your Default Route My gateway is at: 192.168.0.1
192.168.48.0/20 4096 addresses
There are several Dynamic Routing Protocols. The one used by the 9500 MPR is called Open Shortest Path First (OSPF)
9500MPR TMN Networking Appendix DHCP
9500MPR TMN Networking Network Services - DHCP
There are two address assignment methods: 1. Static assignment 2. Dynamic assignment With Static Assignment, addresses are configured manually:
IP Address: 172.22.88.175 Netmask: 255.255.224.0 Default Gateway: 172.22.64.1
9500MPR TMN Networking Basic Networking Concepts - Address Assignment With Dynamic Addressing, equipment on a network is configured using the Dynamic Host Configuration Protocol (DHCP) and is documented in RFC2131. The 9500MPR provides a DCHP server on the TMN Ethernet port for configuring Craft computers. This server is enabled by Default.
Hello! Id like to configure my network interface.
Network
I offer to configure your 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 its network configuration 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.
9500MPR TMN Networking Basic Networking Concepts - Address Assignment 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 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.
9500MPR TMN Networking Basic Networking Concepts - Address Assignment
DHCP is based on the Bootstrap Protocol RFC0951(BOOTP) DHCP can be relayed between networks by a BOOTP Relay Agent. These are sometimes called DHCP Relay Agents. A BOOTP Relay allows DHCP clients and servers to be in different Networks. BOOTP Relay Agents can be incorporated into routers. The 9500MPR TMN Network router does NOT support BOOTP Relay
9500MPR TMN Networking Basic Networking Concepts - Address Assignment
Multiple DHCP Servers on a Network: or The Servers are configured to offer Leases from nonoverlapping address blocks. The multiple DHCP Servers share a common Lease database so they do not serve duplicate addresses
1) This is possible provided either:
2) When a client broadcasts a request looking for a DHCP server and multiple servers respond, the client chooses which server it will use for configuration. Frequently this is the first server to respond, but this behavior is not required.
9500MPR TMN Networking Appendix OSPF
9500MPR TMN Networking Network Services - OSPF Open Shortest Path First (OSPF) is the dynamic routing protocol used with the 9500MPR. It is defined in RFC 2328. 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 its relation to other routers. The link state would include such info as: IP Address of the interface Netmask The type of network The routers connected to that interface
A collection of these link-states for several interfaces would form a linkstate database
9500MPR TMN Networking Network Services - OSPF 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. Routers exchange link states by means of flooding. Whenever a router receives a link state update, it stores a copy in its local database and propagates the update to other 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. To control the flooding of link state updates, OSPF uses Areas. All routers within an Area have the same link state database.
9500MPR TMN Networking Network Services - OSPF

Area Border Router (ABR) Autonomous System Boundary Router (ASBR)
Internal Routers
Static R
External Router
Routers that have all of their interfaces in the same area are called Internal 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. 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).
9500MPR TMN Networking Network Services - OSPF

Inter-Area Route Area 2 Intra-Area Routes
Area 1
Backbone Area 0
Area 3
External Static Routes
External Static 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. When designing networks, its 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 attached to the backbone. This is because OSPF expects all other areas to inject routes into the backbone and the backbone will redistribute this information to the other areas.
9500MPR TMN Networking Network Services - OSPF 9500MPR OSPF Features OSPFv2 RouterID (RID) is the same as the Local Address Priority fixed to 1 Able to function as Area Border Router (ABR) Autonomous System Border Router (ASBR) when Static routing is used Each 9500MPR NE Supports up to 4 OSPF Areas, one of which must be Area 0 Stub support all interfaces in the Stub Area must have the Stub Flag set Maximum of 200 entries in the routing table, including both Static and Dynamic entries No provisions for creating Virtual Links
9500MPR TMN Networking Appendix Comparison to the MDR8000 TMN Networking
9500MPR TMN Networking Comparison to MDR8000 TMN Networking

The differences between the 8000 TMN Networking and the 9500MPR TMN Network are basically: 1) The 8000 TMN provides only one external Ethernet interface (feeding a 4 port switch). 2) The 8000 TMN Interface provides a serial Craft interface for PPP connections using the LLMAN utility. 3) The 8000 TMN PPP interfaces: 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 point connection to another NE. It's mainly a hardware interface difference not a networking difference. 4) The 8000 TMN supports RIPv1 and RIPv2 in addition to OSPF as dynamic routing protocols whereas the 9500MPR only supports OSPF. 5) The 8000 TMN offers no built-in mini-DCHP server. Using the LLMAN utility and the serial Craft port provides similar capability for Text User Interface (TUI) connectivity. 6) 8000 TMN transport is at 64kb/s in a dedicated out of band overhead channel. The 9500 MPR TMN transport uses an in-band dedicated VLAN at a relatively high priority supporting much higher transfer rates over the RF link. 7) The 8000 TMN supports a maximum of 250 entries in the routing table vs. only 200 for the 9500MPR. Note that the limit on the number of 8000 NEs in a TMN Network is affected more by the slow transport channel and topology (Ring, Mesh, Linear) than by the routing table size. The practical limit for the number of 8000 NEs in an autonomous TMN Network is around 30. Otherwise, from a TMN Networking and Addressing standpoint, the two systems are equivalent.
www.alcatel-lucent.com www.alcatel-lucent.com

MPR TMN Networking

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

MPR TMN Networking

Diunggah oleh

Hak Cipta:

Format Tersedia

9500 MPR TMN Networking

3EM237181306BVZZA01p06 DRAFT March 3, 2010

9500MPR TMN Networking

All Rights Reserved Alcatel-Lucent 2009

9500MPR TMN Networking TMN Interfaces

All Rights Reserved Alcatel-Lucent 2009

9500MPR TMN Networking Physical Interfaces

All Rights Reserved Alcatel-Lucent 2009

9500MPR TMN Networking Interface to the Router

Dir #35 Dir #N

9500MPR TMN Networking TMN Related Services

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

9500MPR TMN Networking TMN IP Addresses

All Rights Reserved Alcatel-Lucent 2009

9500MPR Networking MPR Addresses

The 9500MPR can be configured with up to three addresses.

All Rights Reserved Alcatel-Lucent 2009

9500MPR Networking MPR Addressing

All Rights Reserved Alcatel-Lucent 2009

9500MPR TMN Networking The TMN Network

All Rights Reserved Alcatel-Lucent 2009

9500MPR Networking The Basic TMN Network RF PPP Links

All Rights Reserved Alcatel-Lucent 2009

9500MPR Networking The Basic TMN Network RF PPP Links

Site A RF PPP Link

Site B RF PPP Link

All Rights Reserved Alcatel-Lucent 2009

9500MPR Networking The Basic TMN Network

Craft Address:10.0.2.2 Default Gateway: 10.0.2.1

9500MPR Networking A Simple Linear Network

Port #4 TMN Subnet

Port #4 TMN Subnet

All Rights Reserved Alcatel-Lucent 2009

9500MPR Networking Supported TMN Network Topologies

All Rights Reserved Alcatel-Lucent 2009

9500MPR Networking Supported TMN Network Topologies

9500MPR TMN Networking MPR Addressing

All Rights Reserved Alcatel-Lucent 2009

9500MPR Networking MPR Addressing

All Rights Reserved Alcatel-Lucent 2009

9500MPR Networking MPR Addressing Adding an MPR terminal to an existing Network

9500MPR Networking MPR Addressing

9500MPR Networking MPR Addressing

9500MPR Networking MPR Addressing

MPR #2 External Switch MPR #3 Local

9500MPR Networking MPR Addressing

MPR #1 Local Craft External Switch Ext #1

MPR #2 Local Craft MPR #3 Local Craft

MPR #3 Dir #38

9500MPR Networking MPR Addressing

MPR #3 Dir #38

9500MPR TMN Networking Craft and Management Communication Requirements

All Rights Reserved Alcatel-Lucent 2009

9500MPR Networking Management

All Rights Reserved Alcatel-Lucent 2009

9500MPR Networking Management

The Local Address is used to provision and Manage the MPR.

9500MPR Networking Management Why?

9500MPR Networking Network Communication

Local Address 2 RF PPP Link

Local Address 3 RF PPP Link

Port #4 TMN Subnet