mpr tmn networking

9500 MPR TMN Networking

3EM237181306BVZZA01p06 DRAFT

March 3, 2010

2 3EM 23718 1306 BVZZA 9500 MPR TMN Networking

March 3, 2010All Rights Reserved © Alcatel-Lucent 2009

9500MPR TMN Networking

1) TMN Interfaces

2) TMN Related Services

3) TMN IP Addresses

4) The TMN Network

5) MPR Addressing

6) Craft and Management Communication Requirements

7) Planning and Addressing a Network

8) 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




TMN Interfaces




Physical Interfaces

The 9500MPR supports several interfaces for TMN traffic:

1. For transport across RF links, there are in-band PPPoE channels, one per Direction

2. The TMN Ethernet port, enabled by default. This interface is intended primarily for local Craft access but can be connected to an external network.

3. Optionally, User Ethernet Port #4 can be configured for TMN. This interface is intended for connecting to external networks for TMN backhaul.

Dir #34Dir #35

Port #4 TMN TMN Ethernet

Dir #N

KZiaulHoque

Highlight

KZiaulHoque

Highlight




Interface to the Router

• 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.

R

Dir #34

Dir #35

Dir #N…

TMN Ethernet Subnet

Port #4 TMN Subnet

Dir #34Dir #35

Port #4 TMN TMN Ethernet

Dir #N

}RF PPPoE links

KZiaulHoque

Sticky Note

'R' is the internal Router

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

Imp

KZiaulHoque

Highlight

KZiaulHoque

Highlight




TMN Related Services

KZiaulHoque

Highlight




Services - OSPF

The 9500MPR provides two services related to TMN networking.

The first service is OSPF for Dynamic Routing

1. The MPR provides a basic implementation of OSPFv2

2. 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)

3. A single MPR can function as an Area Border Router (ABR) for up to four OSPF Areas.

4. The MPR is able to interoperate with external OSPF capable devices such as a 7705.

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

IMP.




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.

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

'trivial' means small or sth that is not so important

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

Important




TMN IP Addresses



9500MPR Networking

MPR Addresses

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) This is the address the Craft and SNMP Managers need to use whenmonitoring or provisioning the NE.

c) All SNMP Traps and Notifications are issued from this address

d) All RF PPPoE connections terminating in this shelf (one per Direction) use this address as their PPP Endpoint Identifier.

Local Address:10.0.36.9

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

KZiaulHoque

Sticky Note

* no net mask is required for MPR/MSS local address.

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight



9500MPR Networking

MPR Addressing

2. TMN Ethernet interface address

a) Enabled by default. This interface is intended for local Craft access

b) Can be connected to an external network.

3. 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 orthe Port#4 TMN Address, but not both.

Port #4 TMNAddress: 192.168.10.0Netmask: 255.255.255.192

TMN EthernetAddress: 172.22.64.86Netmask: 255.255.255.248

KZiaulHoque

Sticky Note

* disabled by default. this port can be enabled graphically. * used to connect external network. Two MSS can be connected by this port by a crossover cable. *

KZiaulHoque

Sticky Note

*enabled by default. * used for local access of the MSS * this port support a trivial DHCP server. when a PC is connected to this port, DHCP automatically supply the IP for the host/PC.

KZiaulHoque

Highlight




The TMN Network



9500MPR Networking

The Basic TMN Network – RF PPP Links

•The RF PPP links come up as soon as the Radio channel is operational.

•It doesn’t 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.


R RRF PPP Link


KZiaulHoque

Sticky Note

Tips: Each MSS/MPR acts as a Router (R).

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

Imp.



9500MPR Networking

The Basic TMN Network – RF PPP Links

•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.


R RRF PPP Link

Local Address:10.3.27.5 Local Address:192.168.10.16

RRF PPP Link

Site A Site BSite C

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

Imp.

KZiaulHoque

Sticky Note

Imp.



9500MPR Networking

The Basic TMN 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 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.

Local Address:10.3.27.5TMN Ethernet Port: 10.0.2.1


R RRF PPP Link

TMN

Ethernet

Network

Craft Computer

Craft Address:10.0.2.2Default Gateway: 10.0.2.1

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

default GW should be the IP of TMN Eth. interface to which the computer is connected to.

KZiaulHoque

Highlight



9500MPR Networking

A Simple Linear Network

• 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.

TMN Ethernet Subnet

A

TMN Ethernet Subnet

C

TMN Ethernet Subnet

B

R R RRF PPP Link RF PPP Link

Port #4 TMN Subnet

X

Port #4 TMN Subnet

Y

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

Imp.

KZiaulHoque

Sticky Note

Imp.



9500MPR Networking

Supported TMN Network Topologies

• 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.

R R R R R R

R R

R R R

RR

R

R

RR

Linear

Ring

Mesh

R

R R

R

RRR

R R

R

RR

KZiaulHoque

Highlight

KZiaulHoque

Highlight



9500MPR Networking

Supported TMN Network Topologies

• 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.

R R R R R R

R R

R R R

LinearR

R

R

ExternalNetwork SNMP

Manager

X

Management Traffic Path After a failure

R External Router




MPR Addressing



9500MPR 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.






9500MPR Networking

MPR Addressing – Adding an MPR terminal to an existing Network

•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!

TMN EthernetAddress: 192.168.64.10Netmask: 255.255.255.240 (/28)Default External Gateway:192.168.64.1


Router

External

Network

192.168.64.1

Existing Network

192.168.64.0/28

OptionalDHCP Server



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.

9500MPR Networking

MPR Addressing

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!

Local Address: 172.22.46.51

TMN Ethernet Network10.3.27.4 Network10.3.27.5 MPR TMN Ethernet Port10.3.27.6 Craft10.3.27.7 BroadcastNetmask: 255.255.255.252



9500MPR Networking

MPR Addressing

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!

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.

Local Address: 192.168.137.25

Local

Net

1 3

2

Port #4 TMN Ethernet Network192.168.137.24 Network Number192.168.137.25 MPR Port #4192.168.137.26 Ext Eqpt 1192.168.137.27 Ext Eqpt 2192.168.137.28 Ext Eqpt 3192.168.137.29 spare192.168.137.30 spare192.168.137.31 BroadcastNetmask: 255.255.255.248

TMN Ethernet Network10.3.27.4 Network Number10.3.27.5 MPR TMN Ethernet10.3.27.6 Craft10.3.27.7 BroadcastNetmask: 255.255.255.252



Connecting multiple MPR shelves at a site using the TMN Ethernet port

9500MPR Networking

MPR Addressing

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.

MPR #1

TMN Ethernet Network10.3.27.64 Network10.3.27.65 MPR #1 (DHCP server disabled)10.3.27.66 MPR #2 (DHCP server disabled)10.3.27.67 MPR #310.3.27.68 DHCP Assigned10.3.27.69 DHCP Assigned10.3.27.70 DHCP Assigned10.3.27.71 BroadcastNetmask: 255.255.255.248

MPR #3

MPR #2

External Switch

Local Craft

MPR #1 Dir #35

MPR #3 Dir #38

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 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.



Connecting multiple MPR shelves at a site using the Port #4 TMN port

9500MPR Networking

MPR Addressing

�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 it’s 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.

MPR #1Port #4 TMN Network10.3.27.64 Network10.3.27.65 MPR #110.3.27.66 MPR #210.3.27.67 MPR #310.3.27.68 External Eqpt #110.3.27.69 External Epqt #210.3.27.70 Spare10.3.27.71 BroadcastNetmask: 255.255.255.248

MPR #3

MPR #2

External Switch

Local Craft

MPR #1 Dir #35

MPR #3 Dir #38

Ext #1

Ext #2

Local Craft

Local Craft



Connecting multiple MPR shelves at a site without an external switch

9500MPR Networking

MPR Addressing

�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.

MPR #1

MPR #3

MPR #2

MPR #1 Dir #35

MPR #3 Dir #38

Ext #1

Local Craft

CommentEquipmentIP Addr

Broadcast10.3.27.79

Ext #110.3.27.78

MPR #3 Port #410.3.27.77

Netmask: 255.255.255.252Network10.3.27.76

Broadcast10.3.27.75

Also MPR #3 Local AddressMPR #3 TMN Eth10.3.27.74


Netmask: 255.255.255.252Network10.3.27.72

Broadcast10.3.27.71

MPR #2 Port #410.3.27.70

MPR #1 Port #410.3.27.69

Netmask: 255.255.255.252Network10.3.27.68

Broadcast10.3.27.67

DHCP AssignedCraft10.3.27.66


Netmask: 255.255.255.252Network10.3.27.64

KZiaulHoque

Highlight




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?



Local Address:172.22.46.51?

? ?



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.

Port #4 TMNAddress: xxx.xxx.xxx.xxxNetmask: nnn.nnn.nnn.nnn

TMN EthernetAddress: yyy.yyy.yyy.yyyNetmask: mmm.mmm.mmm.mmm


Connecting to the wrong address is the primary reason for provisioning problems with the MPR when using the Craft!

NEtO Example



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

• 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 thegateways to the MPR network exchanging routes with an MPR using OSPF.

TMN Ethernet Subnet

A

TMN Ethernet Subnet

C

TMN Ethernet Subnet

B

R R RRF PPP Link RF PPP LinkPort #4

TMN Subnet

X

Port #4 TMN Subnet

Y

Local Address 1 Local Address 2 Local Address 3

R

ExternalNetwork SNMP

Manager

Local Craft

Local Craft

Local Craft




Planning and Addressing a Network




TMN Network Planning

�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?

A B

C

D

E

F

SiteNetwork

SiteNetwork

R1

R2

ExternalNetwork

SNMPManager

1 2 3

1 2

Fiber or other

ExtDHCPServer

1

Existing external equipment





�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.

2The 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.

3Using 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.





�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.

No external equipment. Direct craft connections only.(disabled)4 address subnet (/30)Site F

8 addresses40 addressesTotal

(disabled)

(disabled)

(disabled)

8 address subnet (/29)

0 new addresses (uses an

address from existing

external network)

Port #4 TMN Network

Extra addresses reserved to allow adding equipment as

the network expands.

16 address subnet (/28)Site E

External device connected to the TMN Eth Port. No

addressing advantage to splitting the subnet between

TMN Eth and Port #4 TMN

8 address subnet (/29)Site D

No external equipment. Direct craft connections only.4 address subnet (/30)Site C

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.

4 address subnet (/30)Site B

Port #4 TMN interface will be connected with the local

site network. TMN Ethernet port to remain active with

DHCP for emergency Local Craft access.

4 address subnet (/30)Site A

CommentsTMN Ethernet NetworkSite





�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.





Netmask: 255.255.255.252

MPR A TMN Ethernet Subnet

Broadcastxxx.xxx.xxx.3

DHCP Assignedxxx.xxx.xxx.2

A TMN Eth Portxxx.xxx.xxx.1

Network (/30)xxx.xxx.xxx.0

Netmask: 255.255.255.248

MPR D TMN Ethernet Subnet





D TMN Eth Portxxx.xxx.xxx.27

Sparexxx.xxx.xxx.26

D Ext Eqpt 1xxx.xxx.xxx.25


Netmask: 255.255.255.240

MPR E TMN Ethernet Subnet


Router R2xxx.xxx.xxx.33

E Ext Eqpt 1xxx.xxx.xxx.34

E Ext Eqpt 2xxx.xxx.xxx.35

Sparexxx.xxx.xxx.36

Sparexxx.xxx.xxx.37

Sparexxx.xxx.xxx.38

E TMN Eth Portxxx.xxx.xxx.39









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.

Netmask: 255.255.255.252

MPR C TMN Ethernet Subnet


C TMN Eth Portxxx.xxx.xxx.17



Netmask: 255.255.255.252

MPR F TMN Ethernet Subnet



F TMN Eth Portxxx.xxx.xxx.21


Netmask: 255.255.255.248

MPR B Port #4 TMN Subnet


Sparexxx.xxx.xxx.14

Sparexxx.xxx.xxx.13

B Ext Eqpt 3 xxx.xxx.xxx.12

B Ext Eqpt 2xxx.xxx.xxx.11

B Ext Eqpt 1xxx.xxx.xxx.10

B Port #4xxx.xxx.xxx.9


Netmask: 255.255.255.252

MPR B TMN Ethernet Subnet



B TMN Eth Portxxx.xxx.xxx.5






�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, we’ll assume we’ve 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.





Netmask: 255.255.255.252


Broadcast172.28.137.67

DHCP Assigned172.28.137.66

A TMN Eth Port (L)172.28.137.65

Network (/30)172.28.137.64

Netmask: 255.255.255.248






D TMN Eth Port (L)172.28.137.91

Spare172.28.137.90

D Ext Eqpt 1172.28.137.89

Network (/29)172.28.137.88

Netmask: 255.255.255.240


Network (/28)172.28.137.96

Router R2172.28.137.97

E Ext Eqpt 1172.28.137.98

E Ext Eqpt 2172.28.137.99

Spare172.28.137.100

Spare172.28.137.101

Spare172.28.137.102

E TMN Eth Port (L)172.28.137.103








Broadcast172.28.137.111

Netmask: 255.255.255.252


Network (/30)172.28.137.80

C TMN Eth Port (L)172.28.137.81



Netmask: 255.255.255.252




F TMN Eth Port (L)172.28.137.85

Network (/30)172.28.137.84

Netmask: 255.255.255.248



Spare172.28.137.78

Spare172.28.137.77

B Ext Eqpt 3 172.28.137.76

B Ext Eqpt 2172.28.137.75

B Ext Eqpt 1172.28.137.74

B Port #4172.28.137.73

Network (/29)172.28.137.72

Netmask: 255.255.255.252




B TMN Eth Port (L)172.28.137.69

Network (/30)172.28.137.68

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).

MPR A Port #4 TMN Subnet

MPR A Port #4192.168.19.23

Router R1192.168.19.1

Netmask: 255.255.255.224

Address assignments from the existing subnet at Site A.




TMN Network Planning – Growing the Network

Sixteen addresses out of the assigned 64 remain unused.

Unused172.28.137.127

Unused172.28.137.126

Unused172.28.137.125

Unused172.28.137.124

Unused172.28.137.123

Unused172.28.137.122

Unused172.28.137.121

Unused172.28.137.120

Unused172.28.137.119

Unused172.28.137.118

Unused172.28.137.117

Unused172.28.137.116

Unused172.28.137.115

Unused172.28.137.114

Unused172.28.137.113

Unused172.28.137.112





�The MPR at Site A will be configured with a static route to use 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!

�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 it’s 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.




TMN Network Planning – Growing the network

�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 don’t have enough addresses for all the equipment. We’ll have to request additional address space.

A B

C

D

E

F

G H

SiteNetwork

SiteNetwork

R1

R2

ExternalNetwork

SNMPManager

1 2 3

1 2

1

J

K

1

Fiber or other

ExtDHCPServer

3 4 5

1

1




TMN Network Planning – Growing the network

�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

(disabled)8 address subnet (/29)Site K

(Keep existing subnet)

Extra address space no longer needed. Split 16

address subnet, allocating 8 addresses to Port #4 TMN and 4 addresses to TMN Ethernet. Redeploy recovered 4 addresses to site F.

8 address subnet (/29)Original 16 address subnet now a 4 address subnet (/30)

Site E

8 new addresses

(disabled)


(disabled)


Port #4 TMN Network

24 new addressesTotal

8 address subnet (/29)Site J

External eqpt connected to Port #4 TMN interface. 4 address subnet (/30)Site H

No external equipment. Direct craft connections

only.

4 address subnet (/30)Site G

Add subnet to Port #4 TMN interface for new

equipment, using the address space recovered from

Site E.

Site F

CommentsTMN Ethernet NetworkSite

Here’s the new plan:





Netmask: 255.255.255.252




A TMN Eth Port (L)172.28.137.65

Network (/30)172.28.137.64

Netmask: 255.255.255.248






D TMN Eth Port (L)172.28.137.91

Spare172.28.137.90

D Ext Eqpt 1172.28.137.89

Network (/29)172.28.137.88

Netmask: 255.255.255.252


Network (/30)172.28.137.80

C TMN Eth Port (L)172.28.137.81



Netmask: 255.255.255.248



Spare172.28.137.78

Spare172.28.137.77

B Ext Eqpt 3 172.28.137.76

B Ext Eqpt 2172.28.137.75

B Ext Eqpt 1172.28.137.74

B Port #4172.28.137.73

Network (/29)172.28.137.72

Netmask: 255.255.255.252




B TMN Eth Port (L)172.28.137.69

Network (/30)172.28.137.68

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:

Netmask: 255.255.255.252




F TMN Eth Port (L)172.28.137.85

Network (/30)172.28.137.84





Netmask: 255.255.255.240


Network (/28)172.28.137.96

Router R2172.28.137.97

E Ext Eqpt 1172.28.137.98

E Ext Eqpt 2172.28.137.99

Spare172.28.137.100

Spare172.28.137.101

Spare172.28.137.102

E TMN Eth Port (L)172.28.137.103








Broadcast172.28.137.111

MPR E Port #4 TMN Subnet

Netmask: 255.255.255.248

Broadcast172.28.137.103

Spare172.28.137.102

Spare172.28.137.101

MPR E Port #4172.28.137.100

E Ext Eqpt 2172.28.137.99

E Ext Eqpt 1172.28.137.98

Router R2172.28.137.97

Network (/29)172.28.137.96


Netmask: 255.255.255.248

Broadcast172.28.137.107


MPR E TMN Eth (L)172.28.137.105

Network (/30)172.28.137.104

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 F Port #4 TMN Subnet

Netmask: 255.255.255.252

Broadcast172.28.137.111


MPR F Port #4172.28.137.109

Network (/30)172.28.137.108

OLD

NEW





MPR G TMN Ethernet Subnet

Netmask: 255.255.252

Broadcast172.28.137.115


MPR G TMN Eth (L)172.28.137.113

Network (/30)172.28.137.112

MPR H Port #4 TMN Subnet

Netmask: 255.255.255.248

Broadcast172.28.137.127

Spare172.28.137.126

Spare172.28.137.125

H Ext Eqpt 3 172.28.137.124

H Ext Eqpt 2172.28.137.123

H Ext Eqpt 1172.28.137.122

MPR H Port #4172.28.137.121

Network (/29)172.28.137.120

The unused 16 addresses from the original /26 are split into subnets and assigned at sites G and H.

MPR H TMN Ethernet Subnet

Netmask: 255.255.255.252

Broadcast172.28.137.119


MPR H TMN Eth (L)172.28.137.117

Network (/30)172.28.137.116





MPR J TMN Ethernet Subnet

Netmask: 255.255.255.248





MPR J TMN Eth (L)172.30.10.3

Spare172.30.10.2

J Ext Eqpt 1172.30.10.1

Network (/29)172.30.10.0

•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.

MPR K TMN Ethernet Subnet

Netmask: 255.255.255.248





MPR K TMN Eth (L)172.30.10.11

Spare172.30.10.10

K Ext Eqpt 1172.30.10.9

Network (/29)172.30.10.8




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

KZiaulHoque

Highlight

KZiaulHoque

Highlight



9500MPR Networking

MPR Addressing – Setting the TMN Ethernet interface addresses

The TMN Ethernet interfaces:

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 TMN Interface tab. Current interface settings are shown on the right side of the panel

3. Highlight the interface to configure, either the TMN Ethernet or Port #4 TMN Ethernet*

4. To change the parameters, select the Settings tab at the bottom of the panel

1

2

3

4

*If Port #4 TMN is needed and is not an available choice, see the ‘Preparing Port #4 for TMN mode’ on the next slide .

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight



9500MPR Networking

MPR Addressing – Preparing Port #4 for TMN mode

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.

1

2

3

5

4

7

6

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

Imp.

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight



9500MPR Networking

MPR Addressing – Configuring the RF PPPoE Links

For MPT-HL RF PPPoE interfaces:

1. In the Craft Equipment View double-click on the P8ETH 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. In the PPP RF area configure as needed. No IP Address is assigned, the Local Address will be used.

5. Click on Apply

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.

1

2

3

4

5



9500MPR Networking

MPR Addressing – Configuring the RF PPPoE Links

For ODU300 RF PPP interfaces:

1. In the Craft Equipment View double-click on the MD300 Board. This opens the Radio Main View.

2. In the View panel click on the Settings Tab

3. Click on the sub-panel resize arrows to expand the PPP RF area.

4. In the PPP RF area configure as needed. No IP Address needs to be assigned, the Local Address will be used.

5. Click on Apply

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.

1

2

3

4

5



www.alcatel-lucent.comwww.alcatel-lucent.com



A9500MPR TMN Networking Appendix

Basics of IP Addressing




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 IPv4Authority : IANA - Internet Assigned Number Authorityhttp://www.iana.org

The 9500MPR TMN Management interfaces only support

IPv4 addressing




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.




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


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





IP Addressing Primer – The Netmask

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

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.

HEX BIN DEC

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

Table 1

Acceptable mask valuesUsing the example address from before, the corresponding netmask is shown:

172.22.138.207 -> 1010 1100 . 0001 0110 . 1000 1010 . 1100 1111


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.




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

KZiaulHoque

Highlight

KZiaulHoque

Highlight




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 0’s host)

• Broadcast Address (all 1’s host)

• Netmask (leading 1’s, trailing 0’s)

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

Loop back Network

127/8 NET 127.0.0.0

MASK 255.0.0.0

BCAST 127.255.255.255

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

Short Hand Long Hand

0111 1111.0000 0000.0000 0000.0000 0000

1111 1111.0000 0000.0000 0000.0000 0000

0111 1111.1111 1111.1111 1111.1111 1111

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

Binary




IP Addressing Primer – Possible Network Sizes

Two hosts are reserved in any Ethernet 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 two less than the total number of addresses in the network. The smallest Ethernet

network with useable address space is highlighted in RED.

Table 2Network 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

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

… … … …




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/



B9500MPR TMN Networking Appendix

Basic Networking Concepts




Basic Networking Concepts - Communication within a Network

Network

Computer 1 Computer 2

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, twisted-pair (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.

KZiaulHoque

Highlight

KZiaulHoque

Highlight





Network

Computer 1

00:C0:F8:34:19:C0

Computer 2

00:F8:62:CF:8A:B3

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.

KZiaulHoque

Highlight





Network

Computer 1

10.0.0.1

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

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

With communication with MAC address/Ethernet communication, both end should have IP on the same subnet.





Network

Computer 1

10.0.0.1Computer 2

10.0.0.2

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)

Who has 10.0.0.2?

I’m at 00:C0:DF:48:F3:47

KZiaulHoque

Highlight




Basic Network Concepts – TCP Stack

SNMP ManagerLayer 5

SNMP Agent

TCP, UDP PacketsLayer 4

IP DatagramLayer 3

Ethernet FramesLayer 2

Copper, Fiber, etcLayer 1

Application Layer

Transport Layer

Network Layer

Data Link Layer

Physical Network

Sender Receiver

Application Layer

Transport Layer

Network Layer

Data Link Layer

Physical Network

Virtual

Connection

Physical

Connection

So how do the addressing methods fit together?

IP Addresses used at this layer

MAC Addresses used at this layer

•MAC addresses are used at Layer 2

•IP Addresses are used at Layer 3




Basic Networking Concepts – Connecting Networks

Network A

Computer 1

Computer 2

Network B

Computer 3

Computer 4

In this situation we have two isolated networks. Computer 1 cancommunicate with Computer 2, and Computer 3 can communicate withComputer 4.

But what if Computer 1 needs to send a message to Computer 4?

We need a way to interface the two Networks.




Basic Networking Concepts - Router and Bridge Comparison

There are two common ways to connect networks together

Layer 3

Layer 2

Layer 1

Sender ReceiverApplication Layer

Transport Layer

Network Layer

Data Link Layer

Physical Network

Virtual

Connection

Physical

Connection

Application Layer

Transport Layer

Network Layer

Data Link Layer

Physical Network

Data Link Layer

Physical Network

Data Link Layer

Physical Network

Physical

Connection

Layer 3

Layer 2

Layer 1

Sender ReceiverApplication Layer

Transport Layer

Network Layer

Data Link Layer

Physical Network

Virtual

Connection

Physical

Connection

Application Layer

Transport Layer

Network Layer

Data Link Layer

Physical Network

Data Link Layer

Physical Network

Data Link Layer

Physical Network

Physical

Connection

Network Layer

Network Layer

Bridge

Router

Bridges connect at Layer 2

Routers connect at Layer 3

KZiaulHoque

Highlight





Network A

Computer 1

10.0.0.1

Computer 2

10.0.0.2

Network B

Computer 3

10.0.0.3

Computer 4

10.0.0.4

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 that’s beyond the scope of this presentation.

The 9500MPR TMN Network does not bridge between TMN Ports or across RF Links!

Switch

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

In bridge/switch, all devices should have IP on the same subnet.





Network ANetwork B

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.

Router

Computer 1

IP 172.22.64.1Gateway 172.22.64.38

Computer 2

IP 172.22.64.2Gateway 172.22.64.38

Computer 4

IP 192.168.10.4Gateway 192.168.10.137

Interface172.22.64.38

Interface192.168.10.137

Computer 3

IP 192.168.10.3Gateway 192.168.10.137

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

IMP.

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight




Basic Networking Concepts - Routers

�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 doesn’t 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.

External

Network

192.168.0.0/16

65534 addressesRouter

External

Network

192.168.0.0/1816346 addresses

RouterA

192.168.128.0/1816346 addresses

192.168.192.0/1816346 addresses

192.168.0.0/204094 addresses

192.168.16.0/204094 addresses

Router B

192.168.32.0/204094 addresses

192.168.48.0/204096 addresses

192.168.64.0/18




Route Configuration

External

Networks

RouterA

192.168.0.0/1816346 addresses

RouterB

I know how to reach addresses in the space:

192.168.64.0/18Use my gateway at:

192.168.0.35

Use me for yourDefault Route

My gateway is at: 192.168.0.1

� There are several Dynamic Routing Protocols. The one used by the 9500 MPR is called Open Shortest Path First (OSPF)

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:

192.168.0.0/204094 addresses

192.168.16.0/204094 addresses

192.168.32.0/204094 addresses

192.168.48.0/204096 addresses



C9500MPR TMN Networking Appendix

DHCP




Network Services - DHCP

There are two address assignment methods:

1. Static assignment

2. Dynamic assignment

IP Address: 172.22.88.175

Netmask: 255.255.224.0

Default Gateway: 172.22.64.1

With Static Assignment, addresses are configured manually:

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight




Basic Networking Concepts - Address Assignment

Network

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.

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.

Hello! I’d like to configure my network

interface.

I offer to configure your network.

KZiaulHoque

Highlight





•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.

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight





•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 differentNetworks.

•BOOTP Relay Agents can be incorporated into routers.

•The 9500MPR TMN Network router does NOT support BOOTP Relay





• Multiple DHCP Servers on a Network:

1) This is possible provided either:

• The multiple DHCP Servers share a common Lease databaseso they do not serve duplicate addresses

or

• The Servers are configured to offer Leases from non-overlapping address blocks.

2) When a client broadcasts a request looking for a DHCP server andmultiple 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.

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

IMP.



D9500MPR TMN Networking Appendix

OSPF




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 it’s 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 link-state database

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

VVI Concept





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 it’s 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.

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

VVI Concept





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).

Static

Autonomous System Boundary Router (ASBR)

Area Border Router (ABR)

InternalRouters

RExternalRouter

KZiaulHoque

Highlight





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, it’s 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.

R

Backbone Area 0

Area 1

Area 2

Area 3

External StaticRoutes

Inter-Area Route

Intra-Area Routes

RExternal StaticRoutes

KZiaulHoque

Highlight

KZiaulHoque

Sticky Note

IMP.





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

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight

KZiaulHoque

Highlight



E9500MPR TMN Networking Appendix

Comparison to the MDR8000 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.comwww.alcatel-lucent.com

mpr tmn networking

Documents

core main module

rf pppoe links2

rights reserved alcatel

rf ppp link

9500mpr networking management

tmn traffic flowing

dynamic routing protocols

tmn ethernet port