tmn networking.pdf

7/24/2019 TMN Networking.pdf

1/113

AT THE SPEED OF IDEAS

TMN Networking

November 2012


2/113

Agenda

Synthetic view

1. 9500MPR

2. 9500MXC

3. 9400AWY

4. 9600LSY

5. 9500MPR & 9400AWYcollocated

Focus on MPR

6. TMN Interfaces

7. TMN Related Services

8. TMN IP Addresses

9. The TMN Network

10.MPR DCN example

11.ANNEX 1

1. SNMP management

2. OSI layer model

3. IP addressing4. Routing overview

5. OSPF routing

6. Planning and addressing a network

12.ANNEX 2

1. 9400LUX50 IOT


3/113

Notes

Modifications in respect to the previous version (April 2012)

1. Updated to the MPR 4.1 release

1. - MSS-1

2. - MPR-e/MSS-1c OSPF improvements

3. - IPv6 scenarios not considered


4/113

Alcatel-Lucent ConfidentialSolely for authorized persons having a need to knowProprietary Use pursuant to Company instruction

4 | Presentation Title | Month Year

TMN Networking

9500MPR


5/113


5 | TMN Networking | April 2012

9500MPR (MSS 8/4/1) Capability

IP parameters

! MSS 8/4/1 has routing capability. From DCN/IP point of view it is arouter.

! Each port can activate OSPF or static routing ; for each MSS 8/4/1 upto 3 different OSPF Areas can be provisioned excluding the backbone.

! In case of OSPF each address must belong to an OSPF area.

! The area can be Secondary or Totally Stub.

9500 MPR

10/100 Base T

Management Protocol:

SNMPv2c for supervision

FTP for download/backup/restore

Telnet for debug

NTP for time synchronization

Physical DCN Ports:

1x Ethernet RJ45 10/100 BaseT for local accesswith DHCP (Out of Band)

1x Ethernet RJ45 10/100/1000 BaseT SWconfigurable (Out of Band)

4 MAX x Ethernet RJ45 10/100/1000 BaseT (InBand)

2 MAX x Ethernet SFP (In Band)nx Radio 512 Kb/s

IP addressing

1x IP address for all the radio channels (/32);

that is the localIP address of the NE.

1x IP address and relevant net-mask for each usedEth port

512 Kb/s Radio

10/100 Base T

9500 MPR-MSS1c

512Kb/s Radio

10/100 Base T


6/113



9500MPR (MSS 1c) Capability

IP parameters

!MSS 1C has routing capability. From DCN/IP point of view it is a router.

! Each port can activate static routing ; OSPF routing available since 3.2release.

9500 MPR

10/100 Base T



FTP for download/backup/restore/provisioning

SNTP for time synchronization

Physical DCN Ports:

2x Ethernet RJ45 10/100 BaseT (Out of Band)1x Ethernet RJ45 10/100/1000 BaseT (In Band)

selectable

1 x Radio 512 Kb/s

IP addressing

1x IP address and relevant net-mask for each

Eth DCN ports1x IP address for the radio channel

that is the local IP address of the NE.

512 Kb/s Radio

10/100 Base T

9500 MPR-MSS1c

512Kb/s Radio

10/100 /1000Base T

10/100 Base T

10/100 Base T

10/100 /1000 Base T


7/113



9500MPR (MPR-e) Capability

IP parameters

9500 MPR

10/100 Base T



FTP for download/backup/restore/

SNTP for time synchronization

Physical DCN Ports:

1x Ethernet El./Opt. 1000 (In Band)1 x Radio 512 Kb/s

IP addressing

1x IP address and relevant net-mask for theEth DCN port

1x IP address for the radio channel

that is the local IP address of the NE.

512 Kb/s Radio

10/100 Base T

512Kb/s Radio

10/100 Base T

9500 MPR-e

!

MPR-e has routing capability. From DCN/IP point of view it is a router.! Each port can activate static routing ; OSPF available since 3.2

release.


8/113



9500 MPR

DCN Interconnection using Out of Band (OoB)

! Multiple MPR nodes can be chained without need for external switch

10/100 Base T

512Kb/s Radio

10/100

BT

512Kb/s Radio

512Kb/s Radio

9500 MPR

9500 MPR

9500 MPR

10/100

BT

10/100 Base T

512Kb/s Radio

9500 MPR-e

9500 MPR-MSS1c


9/113



9500 MPR

DCN Interconnection using In Band (InB)

! Multiple MPR nodes can be chained without need for externalswitch

10/100 Base T

512Kb/s Radio

10/100

BT

512Kb/s Radio

512Kb/s Radio

9500 MPR

9500 MPR

9500 MPR

10/100

BT

10/100 Base T

512Kb/s Radio

9500MPR-MSS1c

9500 MPR-e

In this case the Supervisionis tagged over a trafficflow saving- Ethernet ports- IP addresses


10/113



TMN Networking

9500MXC


11/113


11| TMN Networking | April 2012

MXC Capability

IP parameters

! MXC has routing capability but it cant work in ABR condition

(Area 0 is not managed on the Eth. Interface) while the ASBRconfiguration is allowed using the advance setting.

! Each port can activate OSPF or static routing ; up to 3 differentOSPF Areas can be provisioned excluding the backbone.


9500 MXC

10/100 Base T

512Kb/s Radio



FTP for download/backup/restore

Telnet for debug


Physical DCN Ports:2 x Ethernet bridge RJ45 10/100 BaseT (IDU)

(Out of Band)

4 x Ethernet bridge RJ45 10/100 BaseT (INUx)(Out of Band)

nx Radio 512 Kb/s

IP addressing

1x IP address with its net-mask (at least /29)for all the

- radio channels

- the used Eth port for supervision

512 Kb/s Radio

10/100 Base T


12/113



9500 MXC

DCN Interconnection

! Multiple MPR nodes can be chained without need for external switch

10/100 Base T

512Kb/s Radio

10/100

BT

512Kb/s Radio

512Kb/s Radio

9500 MXC

9500 MXC

10/100

BT

10/100 Base T

512Kb/s Radio

9500 MXC


13/113



TMN Networking

9400AWY


14/113



AWY Capability

IP parameters

!AWY has routing capability. From DCN/IP point of view it is arouter.

! Each port can activate OSPF or static routing.


! The area can be Secondary or Totally Stub.

9400 AWY

10/100 Base T V11 64Kbs

G.703 64Kbs

64Kb/s Radio



FTP for download, backup, restore

Telnet for debug


Physical DCN Ports:1x Ethernet RJ45 10/100 BaseT

1x V.11 64Kbs

1x G.703 64Kbs

1x Radio 64Kb/s

1x CT port DB9 RS232 19.2 Kbs

IP addressing

1x IP address for all the serial ports (/32);that is the IP address of the NE

1x IP address and relevant net-mask forthe Eth port


15/113



9400 AWY

DCN Interconnection

! Multiple AWY terminals can be chained without need for external switch

10/100 Base TV11 64Kbs

64Kb/s Radio

64Kb/s Radio

64Kb/s Radio

9400 AWY

9400 AWY

9400 AWY

G703 64Kbs

10/100 Base T


16/113



TMN Networking

9600LSY


17/113



LSY Capability

Q3 parameters

! LSY has routing capability based on IS-IS.

! Management function is carried over STM-1 payload; additional

protection is assured by chaining the Eth. OS port.

! In case of Gateway the OS port is deputed to the Managerconnection.

! In case of crossing IP network, OSI over IP is native available withboth OSPF or Static routing protocol.

9600 LSY

10/100 Base T

STM-1


OSI Q3 for supervision

FTP for download

ANTP for time synchronization

Physical DCN Ports:

1x Ethernet RJ45 10/100 BaseT (OS port)1x Radio 192 Kb/s

1x CT port DB9 RS232 19.2 Kbs

DCN In Band:

DCCR (D1-D3) 192 Kb/s on STM-1

NSAP addressing:

1x NSAP for each NE

192 Kb/s Radio


18/113



9600 LSY

DCN Interconnection

! Two LSY terminals can be chained without need for external switch

! For infield implementation pay attention to provide the right BW allocation for a securemanagement

9600 LSY (back to back)

10/100 Base T

192 Kb/s Radio192 Kb/s Radio

STM-1

9600 LSY (w/ ADM)

10/100 Base T

192 Kb/s Radio192 Kb/s Radio

STM-1

ADM

9600 LSY (GNE)

10/100 Base T

192 Kb/s Radio

STM-1

192 Kb/s Radio

IP cloud

OSIoverIP

OSIoverIP

NOC

1662 SMC


19/113



TMN Networking

9500MPR & 9400AWY co-located


20/113



9500 MPR & 9400 AWY collocated

DCN Interconnection

! Multiple MPR & AWY can be chained without need for external switch

512Kb/s Radio

10/100

BT

512Kb/s Radio

512Kb/s Radio

9500 MPR

9500 MPR

9500 MPR

10/100

BT

10/100 Base T

V11 64Kbs

64Kb/s Radio

64Kb/s Radio

64Kb/s Radio

9400 AWY

9400 AWY

9400 AWY

G703 64Kbs

10/100 Base T

10/100 Base T

9500 MPR-MSS1c

9500 MPR-e

10/100 Base T


21/113



9500MPR TMN Networking

TMN Interfaces


22/113


Technical specifications

ManagementInterfaces

9400AWY 9500MXC 9500MPR

MSS 8/4/1 MSS 1c MPR-e

Ethernet 1 1 (IDU),

4 (INU)

7

(2 OoB & 6 InB)

3

(2 OoB & 1 InB)

1

(InB)

Native In Band

Management

--- --- YES YES YES

Serial V11 RS 422

64 Kb/s (co-dir.,

contro-dir. DCE)

1 1 Only with

AUX board

(INU/INUe)

---

Serial G703 64

Kb/s for 9400AWY

1 --- ---

BW on the

embedded

radio channel

64 Kb/s 192 Kb/s min

512 Kb/s max

192 Kb/s min

512 Kb/s max

Dedicated localCT access

RS 232 19.2 Kb/s RS 232 19.2 Kb/s

Ethernet

-

Ethernet

Protocol/

Routing

SNMP v.2c/

OSPF, Static

SNMP v.2c/

OSPF, Static

SNMP v.2c/

OSPF, Static

IP addressingschema

VLSM VLSM Variable Lenght Subnet Mask



23/113


LCT

(initial setup)

CSM module

9500MPR product (IDU: MSS-8/MSS-4)

Ethernet RJ45 Traffic Port 4:

configurable as NMS Ethernet channel

used to chain collocated equipment

or as GNE interface

NMS Ethernet RJ45

local interface

(always enabled)



24/113


LCT

(initial setup)

9500MPR product (IDU: MSS-1)

Ethernet RJ45 Traffic Port 4:

configurable as NMS Ethernet channel

used to chain collocated equipment

or as GNE interface

NMS Ethernet RJ45

local interface

(always enabled)



25/113


LCT

(initial setup)

NMS Ethernet RJ45

Pure local interface

(always enabled with fixed IP)

9500MPR product: (IDU: MSS-1c)

2 OoB Ethernet RJ45 Management

ports: Used to chain collocated

equipment or as GNE interface


1 InB Ethernet RJ45 Management on a

selectable user ports (1..4): Used

to chain collocated equipment


26/113


LCT

(initial setup)

9500 MXC, INU/INUe modules - indoor

NCC Node Controller Card (NMS ports)

4 ports Ethernet connector assembly for

NMS / RJ45 for INU/INUe

Serial Interface v24 RJ 45 for Local craftterminal connection

9500MXC product



27/113


NMS Serial port v.24/RS232NMS Serial port v.24/RS232

9500 MPR CSM

9400 AWY

LCT

(initial setup)

NMS ETHERNET cable RJ45/RJ45

1 ports Ethernet connector assembly for NMS / RJ45

MPR - AWY common management (LAN connection)

NMS Ethernet RJ45 local interfaceNMS Ethernet RJ45 local interface



28/113


Serial Interface v24 RJ 45

local interface

Serial Interface v24 RJ 45

local interface

9500 MXC, NCC card (NMS function)

- config. also valid in case of IDU

9500 MPR

LCT

(initial setup)



MPR - MXC common management (LAN connection)

NMS Ethernet RJ45 local interfaceNMS Ethernet RJ45 local interface



29/113


NMS Serial port v.24/RS232NMS Serial port v.24/RS232

9500 MXC, NCC card (NMS function)

9400 AWY

LCT

(initial setup)



MXC - AWY common management (LAN connection)



30/113



Physical Interfaces for MSS 8/4/1

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 (Out of Band) but can be connected to an external network.

3. Optionally, User Ethernet Port #4 (Out of Band) can be configured for TMN. This interface is intended

for connecting to external networks for TMN backhaul or to chain collocated MPRs.

4. Optionally supports one or two TMN In-band interfaces

configurable for access on user Ethernet ports and tagged with a user specified VLAN



31/113


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

When the Port#4 TMN or TMN In-Band interfaces are enabled, the provisioned subnets must all beunique.

TMN traffic passing between any two interfaces is routed at Layer 3. The TMN interfaces support Bridging only in case they belongs to a common TMN In-Band group. Thismeans the TMN subnets must be unique and not overlap.


Interface to the Router



32/113



Focus on TMN In-Band: Single Port Configuration

Eth Port#1

is part of TMN In-Band #1

Specific VLAN ID, IP

Address, IP Mask,

IP Routing (OSPF or Static)

can be selected.



33/113



Focus on TMN In-Band: Multiple Port Configuration (Bridge mode)

Eth Port#1, #3, #5

are part of TMN In-Band #2

Specific VLAN ID, IP

Address, IP Mask,

IP Routing (OSPF or Static)

can be selected.



34/113



MPR TMN Networking

TMN Related Services


35/113



Services OSPF & Static

The 9500MPR provides two services related to TMN networking.

The first service is OSPF for dynamic routing of TMN network traffic

1. The MPR provides the implementation in according to OSPFv2

2. User configurable parameters are :

Enabling or disabling OSPF on each individual TMN interface.

Setting the OSPF Area ID for each interface (default Area is 0)

Enabling or disabling the Stub Flag (indicates whether the interface

is a member of an OSPF Stub Area)

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

OSPF Areas, one of which must be Area 0.

4. A single MPR can also function as an Autonomous System Border Router (ASBR)

meaning the routes are externally exported via the Static routing.



36/113



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, for security purpose.

3. The DHCP server uses an address pool determined by the TMN Local Ethernet

IP address and subnet.

4. The maximum number of Addresses managed by the DHCP Server is 10.Clients are served the same Netmask assigned to the TMN Local Ethernet

interface and a Default Gateway set as the TMN Local Ethernet IP address.

5. The Lease Time is fixed to 10 minutes.

.



37/113



MPR TMN Networking

TMN IP Addresses


38/113


9500MPR Networking

MPR (MSS 8/4/1) addresses

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

1. The first and primary address is the NE Local Address:

a) This is the Address of the MPR itself (IP Local).

Note: There is no Netmask (i.e. /32) setting associated with the LocalAddress.

b) This is the address the Craft and SNMP Managers must use when

monitoring or provisioning the NE.

c) All SNMP Traps or 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.


9500MPR N t ki


39/113


9500MPR Networking

MSS 8/4/1 addresses

2. The TMN Ethernet interface address

a) This interface is 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) This interface is disabled by default.

b) Intended for use when connecting to external networks or to chainco-located MPR to allow the TMN Interface to remain available for Local Craftaccess.


9500MPR Networking


40/113


9500MPR Networking

MSS 8/4/1 addresses: In-Band interfaces

4. Optional #1 TMN In-Band Ethernet interface address - since MPR 3.0 (MSS 8- MSS 4)

5. Optional #2 TMN In-Band Ethernet interface address - since MPR 3.0 (MSS 8- MSS 4)

Both interfaces are disabled by default.

These interfaces are intended for use when it is desirable to backhaul TMN traffic in an dedicated VLANthrough the same physical interface that is used for revenue bearing Traffic. The primary differencebetween these interfaces and the TMN Port #4 interface is that these have user configurable Ethernetinterface ports and the traffic flow is identified with a user specified VLAN.

Access to the TMN In-band traffic in the VLAN requires interfacing with a VLAN aware external device.

Most Laptop and Desktop computer Ethernet interfaces DO NOT meet this requirement and are unable tocommunicate directly with the TMN In-Band interfaces.

Tip: The Local Address may be set to match the address of one of the four possible TMN Interfaces, butno more than one. The Local Address and interface address must match if they are in the same subnet.


9500MPR Net orking


41/113


9500MPR Networking

MSS 8/4/1 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.

41| TMN Networking | January 2011

9500MPR N t ki


42/113


9500MPR Networking

MPR (MSS 1C) addresses

The 9500MPR-1C can be configured with up to five addresses.

1. The first and primary address is the NE Local Address:

a) This is the Address of the MSS 1C itself.

Note: There is no Netmask (i.e. /32) setting associated with the LocalAddress.

b) The Craft and SNMP Managers must use this address whenmonitoring or provisioning the NE. For the releases less than 3.3 NMS1or NMS2 or TMN InB LAN IP must be used in case the equipment is notreached via radio side.

c) SNMP Traps or Notifications are issued accordingly to the previousassumption.

d) The RF PPPoE connection terminating in this shelf

uses the NE Local address as its PPP Endpoint Identifier.

Tip: In case of static routing the Local Address may be set to match the address of one of thepossible TMN Interfaces, but no more than one. The Local Address and interface address mustmatch if they are in the same subnet.


Local Address: 10.0.36.9

9500MPR Networking


43/113


9500MPR Networking


2. The TMN Ethernet interface address (CT)

a) This interface is enabled by default and is intended for local Craft accesswith fixed IP 192.168.30.1 Netmask: 255.255.255.252

b) It cant be connected to an external network; only the local management isallowed.


2) 192.168.30.1/30

4) 172.22.64.86/30

3) 192.168.10.1/30

5) 192.168.100.1/30


9500MPR Networking


44/113


9500MPR Networking


3. Optional NMS1 TMN Ethernet interface addresses

a) This interface is disabled by default, enabling it is service affecting whileattach/detach no.

b) Intended for use when connecting to external networks or to chainco-located devices or to connect a PC to have a remote access to the far enddevices.

c) Static or OSPF routing can be enabled on it. In case of OSPF its IPaddress cant be equal to the Local IP address.

d) In any case the associated subnet must be unique in the network andvisible from the NOC or any CT that wants to perform a remote access.

e) Trap are sourced by this IP address too up to MSS-1C 3.2 included.


2) 192.168.30.1/30

4) 172.22.64.86/30

3) 192.168.10.1/30

5) 192.168.100.1/30


9500MPR Networking


45/113


9500MPR Networking


4. Optional NMS2 TMN Ethernet interface addresses

a) This interface is disabled by default, enabling it is service affecting whileattach/detach no.

b) Intended for use when connecting to external networks or to chainco-located devices or to connect a PC to have a remote access to the far enddevices.


d) In any case the associated subnet must be unique in the network andvisible from the NOC or any CT that wants to perform a remote access.



2) 192.168.30.1/30

4) 172.22.64.86/30

3) 192.168.10.1/30

5) 192.168.100.1/30


9500MPR Networking


46/113


9500MPR Networking


5. Optional TMN In Band Ethernet interface addresses

a) This interface is disabled by default.b) This interface can be allocated in 1 of the indicated user ports.

c) Intended to chain co-located devices.


d) In any case the associated subnet must be unique in the network and visible from theNOC or any CT that wants to perform a remote access.


f) Access to the TMN In-band traffic in the VLAN requires interfacing with a VLAN awareexternal device. Most Laptop and Desktop computer Ethernet interfaces DO NOT meetthis requirement and are unable to communicate directly with the TMN In-Band

interfaces


2) 192.168.200.1/30

4) 172.22.64.86/30

3) 192.168.10.1/30

5) 192.168.100.1/30


47/113



MPR TMN Networking

The TMN Network

9500MPR Networking


48/113


g

The Basic TMN Network RF PPP Links

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


49/113


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.


9500MPR Networking


50/113


A Simple Linear Network

To provide local access and to connect external equipment to the TMN network,

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


9500MPR Networking


51/113


Supported TMN Network Topologies

The TMN Network can be configured in Linear, Tree, 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

- In case some devices is managed via Static routing, only Linear and Tree configurationis allowed..


9500MPR Networking


52/113


Supported TMN Network Topologies

Networks can have multiple external gateways that allow alternate management

paths in the event of an outage.

To take 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 should be used for links external to the MPR network.



53/113



MPR TMN Networking

MPR DCN example

DCN structure


54/113


Autonomous Systems

Autonomous System

Routing protocol : not OSPF (Static)

9500MPR(ASBR) Autonomous System BoundaryRouter

Autonomous System

Routing protocol : OSPF

ASBR

An Autonomous System is made at least of one single area. It must include less than 50NE (Network Element) as for generic DCN rules.

(If needed, multiple Areas can be configured to reach up to 150 9500MPR for eachproject)

(See Annexes for details about the IP routing for 9500MPR)

Autonomous System


ASBR



55/113


MSS 8/4/1 IP addressing

IP addresses rules according to the selected scenario.

To manage the 9500MPR MSS 8/4/1 the following unique IP addresses are needed:

" One Local address (/32 address) to identify the equipment; better if it is part of a

sub/29 or larger subnet to facilitate the addressing using static routes from external

devices (i.e. manager). OSPF protocol must be enabled.

" For the TMN Local Ethernet port the default IP address / netmask can be used. The

default enabled DHCP server helps the user to have the local connection. These

addresses dont need to be visible from the NOC. Special cases will be later

mentioned.

" For the optional (configurable) Port#4 TMN Ethernet a dedicated sub/30 must be

provided in case a chain of collocated MSS must be obtained. OSPF protocol must be

enabled. Special cases will be later mentioned.

All the mentioned IP addresses and the associated subnets, with the exception tothose used for the local access to the 9500MPR, must be visible from the NOC.


MSS1C IP addressing


56/113


MSS1C IP addressing

IP addresses rules according to the selected scenario.

To manage the 9500MPR MSS 1C the following unique IP addresses are needed:

" One Local address (/32 address) to identify the equipment; better if it is part of a

sub/29 or larger subnet to facilitate the addressing using static routes. If available

OSPF protocol must be enabled.

" For the CT port Local Ethernet port the default IP address / netmask can be used.

The default enabled DHCP server helps the user to have the local connection. These

addresses dont need to be visible from the NOC.

" For the optional (configurable) NMS1/NMS2, TMN Ethernet a dedicated sub/30 must

be provided in case a chain of collocated MSS must be obtained. OSPF protocol must

be enabled. In case of static routing these subnets must be referenced in the far end

devices to allow the CT to supervise the remote device radio connected (far end MSS

1C or MSS 8/4/1)

All the mentioned IP addresses, with the exception to those used for the local

access to the 9500MPR, must be visible from the NOC.


9500MPR Capability

S i l t i f i d OSPF d St ti ti t k


57/113


Special notes in case of mixed OSPF and Static routing networks

-The following rules find applications in the following cases:

-- Mixed 9500MPR (MSS 8/4/1) and MSS-1C / MPR-e using the static routing

-- Mixed 9500MPR with other vendor SNMP devices supporting the static routing.

-On both cases it is assumed

-- to use the same TMN flow, having tested the compatibility

-- to use a compatible IP addressing plan (no overlapping)

-- to grant the needed BW (no overbooking, no bottlenecks)

-


9500MPR Capability

S i l t i f i d OSPF d St ti ti g t k


58/113



-Default Gateway: A special case of a static route in which the address is 0.0.0.0 and thesubnet mask is 0.0.0.0. It matches any destination address that is not matched by anyother static route. Default gateway routes are typically used in conjunction with staticroutes to reduce data entry requirements.

-i. Towards the NOC a single default gateway route (0.0.0.0) is entered on eachterminal instead of static routes.

-ii. Away from the NOC static entries are required in the normal way - each terminalmust have an entry for all other terminals that are on its away side only.

-


9500MPR Capability



59/113



-iii. For static routing, the routing entries specify:

-1. Destination: The IP network address of the destination network, where for aMSS 1c or MPR-e C network the destination network is a single terminal or a

group of terminals at one site (two or more terminals at one site connected ona common Ethernet LAN). Only the network portion of the IP address isrequired.

-2. Subnet Mask: The subnet mask or netmask delineates the network portion ofthe IP address.

-3.Interface: The interface must specify the port used to exit the terminal toget to its destination network. Obviously it can also be a radio link.

-4. Next Hop: A next hop entry is only required where the next IP hop is via theEthernet port to another network. Next hop defines the exit point or 'gateway'from one network to the destination network.

-


9500 MPR

DCN Interconnection : topology example


60/113



DCN Interconnection : topology example

10/100

BT

9500 MPR MSS 8/4/1

9500 MPR MSS 8/4/1

10/100 Base T

9500 MPR-MSS1c

9500 MPR-e

9500 MPR-MSS1c

N

MS1 N

MS2

9500 MPR MSS 8/4/1

10/100 Base T

9500 MPR-MSS1c

9500 MPR

DCN Interconnection : subnetting example


61/113



DCN Interconnection : subnetting example

10/100

BT

10/100 Base T

9500 MPR-MSS1c

9500 MPR-e

9500 MPR-MSS1c

N

MS1 N

MS2

.1

.2.6

.4.5

.17.21

.18.19

.22.25

.26 .29

.30

172.26.66.16/28

172.26.66.0/28

OSPF Area x.y.z.w and Static routingMixed

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR-MSS1c

9500 MPR

DCN Interconnection : mixed static routes and OSPF example


62/113



DCN Interconnection : mixed static routes and OSPF example

10/1

00

BT

10/100 Base T

9500 MPR-MSS1c

9500 MPR-e

9500 MPR-MSS1c

NMS

1NMS2

.2.6

.4

.5

.17.21

.18

.19

.22

172.26.66.16/28

172.26.66.0/28


.29

.30.25

.26

NOC

DGradio

DGradio

Local: x.x.x.1/32

P#3 (InB) =Local /30

CT: 10.0.1.5/30

# Static: x.x.x.16/28 by Radio

Local: x.x.x.17/32

NMS: x.x.x.30/30

Static: default by Radio $

# Static: x.x.x.16/28 by x.x.x.29

Tow

a

rdNOC

Local: x.x.x.18/32

NMS2: x.x.x.29/30

NMS1: x.x.x.26/30

Static: default by x.x.x.30$

#Static: x.x.x.20/30 by x.x.x.25

Local: x.x.x.22/32


Local: x.x.x.19/32


Local: x.x.x.21/32

NMS: x.x.x.25/30


.1

.1

.2

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR-MSS1c

CT settings for 1, 2, 3 to enable the local supervision

Note: PC address = 192.168.30.2 GW 192.168.30.1


63/113



Note: PC address 192.168.30.2 GW 192.168.30.1

10/1

00

BT

10/100 Base T

9500 MPR-MSS1c

9500 MPR-e

9500 MPR-MSS1c

NMS1

NMS2

.2.6

.4

.5

.17.21

.18

.19

.22

172.26.66.16/28

172.26.66.0/28


.29

.30.25

.26

NOC

DGradio

DGradio

Local: x.x.x.1/32

P#3 (InB) =Local /30CT: 10.0.1.5/30


Local: x.x.x.17/32

NMS: x.x.x.30/30


Static: x.x.x.16/28 by x.x.x.29

CT3(CT):192.168.30.1/30

Tow

a

rdNOC

Local: x.x.x.18/32

NMS2: x.x.x.29/30

NMS1: x.x.x.26/30



Local: x.x.x.22/32


Local: x.x.x.19/32


CT1(CT):192.168.30.1/30

Local: x.x.x.21/32

NMS: x.x.x.25/30


CT2(CT):192.168.30.1/30

.1

.1

.2

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR-MSS1c

1

23

CT settings for 1, 2, 3 to enable the far end supervision

Note: PC address = 192.168.10x.2 GW 192.168.10x.1


64/113



Note: PC address 192.168.10x.2 GW 192.168.10x.1

10/1

00

BT

10/100 Base T

9500 MPR-MSS1c

9500 MPR-e

9500 MPR-MSS1c

NMS1

NMS2

.2.6

.4

.5

.17.21

.18

.19

.22

172.26.66.16/28

172.26.66.0/28


.29

.30.25

.26

NOC

DGradio

DGradio

Local: x.x.x.1/32

P#3 (InB) =Local /30CT: 10.0.1.5/30


#Static: 192.168.103.0/30 by Radio

Local: x.x.x.17/32

NMS2: x.x.x.30/30


Static: x.x.x.16/28 by x.x.x.29

CT3(NMS1): 192.168.103.1/30

Tow

a

rdNOC

Local: x.x.x.18/32

NMS2: x.x.x.29/30

NMS1: x.x.x.26/30



#Static: 192.168.101.0/30 by Radio

Local: x.x.x.22/32


Local: x.x.x.19/32


CT1(NMS):192.168.101.1/30

Local: x.x.x.21/32

NMS1: x.x.x.25/30


CT2(NMS2): 192.168.102.1/30

.1

.1

.2

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR-MSS1c

1

23

9500 MPR

DCN Interconnection : OSPF routes example


65/113



p

ALL OSPF: Area x.y.z.w

10/100

BT

10/100 Base T

9500 MPR-MSS1c

9500 MPR-e

9500 MPR-MSS1c

N

MS1 N

MS2

.1

.2.6

.4.5

.17.19

.18.22

.21.25

.26 .29

.30

172.26.66.16/28

172.26.66.0/28

NOC

.1

.2

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR-MSS1c

Tow

ardNOC

9500 MPR up to 3.2 release included

DCN Interconnection : declared IP in the NOC (5620SAM or 1350OMS) in red


66/113



( )

Also valid in case of the mixed routing

10/100

BT

10/100 Base T

9500 MPR-MSS1c

9500 MPR-e

9500 MPR-MSS1c

N

MS1 N

MS2

.1

.2.6

.4.5

.17.21

.18.19

.22.25

.26 .29

.30

NOC

.1

.2

172.26.66.16/28

172.26.66.0/28

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR-MSS1c It takes into account from which portthe traps are sourced.

Tow

ardNOC

9500 MPR since 3.3 release included (just the IP local must be used)

DCN Interconnection : declared IP in the NOC (5620SAM or 1350OMS) in red


67/113

Alcatel-Lucent Confidential

Solely for authorized persons having a need to knowProprietary Use pursuant to Company instruction


Also valid in case of the mixed routing

10/100

BT

10/100 Base T

9500 MPR-MSS1c

9500 MPR-e

9500 MPR-MSS1c

N

MS1 N

M

S2

.1

.2.6

.4.5

.17.21

.18.19

.22.25

.26 .29

.30

NOC

.1

.2

172.26.66.16/28

172.26.66.0/28

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR-MSS1c It takes into account from which portthe traps are sourced.

Tow

ardNOC

9500 MPR Warning about to set up protection schemas in respect of the TMN

supervision (OSPF case): restriction removed since MSS-1C 4.1


68/113




10/100

BT

10/100 Base T

9500 MPR-MSS1c

9500 MPR-e

9500 MPR-MSS1c

NMS1 N

M

S2

.1

.2.6

.4.5

.17.21

.18.19

.22.25

.26 .29

.30

NOC

.1

.2

172.26.66.16/28

172.26.66.0/28

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR MSS 8

9500 MPR-MSS1c

Redundancy using a TMN chain must be

avoided as soon as MSS-1C is involved

see

Tow

ardNOC

.33 .34

NMS2 NMS1

.33 .34

NMS2 NMS1


69/113




ANNEX 1

SNMP management

OSI layer model

IP addressing

Routing overview

OSPF routing

Planning and addressing a network


70/113



70 | Presentation Title | Month 2009

SNMP management

SNMP management

Introduction


71/113



In a network with several equipments to be managed and one or more systems managing

them, a agent embedded on the equipment to be managed exchanges information with

the managing system using SNMP.

SNMP : Simple Network Management Protocol.

SNMP protocol mainly allows:

" The managing system to retrieve information from the agent (SNMP GET operation)

" The managing system to send configuration to the agent (SNMP SET operation)

" The agent to warn the managing system (SNMP trap operation)

Available variables to be exchanged are defined in a MIB.

MIB : Management Information Base


SNMP management

MIB


72/113



MIB is a type of database used to describe the device in a communication

network. Its a hierarchical structure (tree-structured) containing OID.

OID : Object IDentifier

Each OID identifies a variable that can be read or set by SNMP.

Example:

1.3.6.1.4.1.637.54.1.11.2.1.2.0 is the OID given for AWY capacity. This object

specifies the PDH frame structure (Number of E1)


SNMP management

MIB


73/113



1 20

1 20 3

2 31 40 5 6

1

3 42 51 6

ISO

Identified Organization

DoD

Internet

Management Private

1 2 3 4 5 6 7 8 10 11

system

interface

at icmp udp transmission

ip tcp egp snmp

MIB-1 RFC1156

MIB-2 RFC1213

1 enterprise

2 9 637 2117

IBM Cisco Alcatel Telspace

54 1

9400

MW product

Melodie1tsdim

ltt

Optics MIB

1


SNMP management

SNMP commands


74/113



SNMP mainly allows 3 types of commands: GET, SET and TRAP

GET request is sent by the managing system to the equipment to be managed.

GET response is sent by the equipment with the parameter requested.

SET request is sent by the managing system to the equipment to be configured.SET response is sent by the equipment to acknowledge the request.

TRAP is sent by the equipment without being asked. There is no response to a trap.

TRAP are sent to all the managers registered on the equipment. A registered manager

is referenced in the MIB as a IP address. TRAP are used by SNMP agent to warn the

manager about an incoming alarm.

MIBSNMPAgent

SNMP SET request

SNMP SET response

SNMP GET requestSNMP GET response

SNMP Trap

Manager



75/113




OSI layer model

OSI layer model


76/113



Layer Unit Function Example

7 Application Data Network process to

application

SNMP, FTP, HTTP,

Telnet

6 Presentation Data Data representation andencryption

5 Session Data Interhost communication

4 Transport Segment End-to-end connections

and reliability

TCP, UDP

3 Network Packet Path determination and

logical addressing

IP, OSPF, RIP

2 Data Link Frame Physical addressing Ethernet, PPP

1 Physical Bit Media, signal and binary

transmission



77/113




IP addressing

IP addressing


78/113



IP address is a binary number:

" 32 bits for IPv4

" 128 bits for IPv6

We will play here only with IPv4.

IPv4 address is usually displayed in human-readable notation such as doted-

decimal notation: 4 bytes displayed in decimal separated by a dot (1 byte = 8

bits, in decimal a byte value is from 0 to 255).

IP address 172.26.64.132

172 . 26 . 64 . 132

10101100 . 00011010 . 01000000 . 10000100

1 byte = 8 bits

4 bytes = 32 bits


IP addressing

Subnet


79/113



An IP address belongs to a sub network (subnet). A subnet is described by an IP

address and a subnet mask.

172 . 26 . 64 . 132

10101100 . 00011010 . 01000000 . 10000100255 . 255 . 255 . 248

11111111 . 11111111 . 11111111 . 11111000

172 . 26 . 64 . 128

10101100 . 00011010 . 01000000 . 10000000

172 . 26 . 64 . 135

10101100 . 00011010 . 01000000 . 10000111

255 . 255 . 255 . 248

11111111 . 11111111 . 11111111 . 11111000

IP address

Subnet mask

Subnet

address

Broadcastaddress

Subnet mask

In a subnet the first address is dedicated for the subnet address and the last is

dedicated for the broadcast address


IP addressing

Subnet


80/113



A subnet is often expressed in the standardized CIDR (Classless Inter-Domain

Routing) notation consisting of the subnet address and the mask length.

172 . 26 . 64 . 128

10101100 . 00011010 . 01000000 . 10000000

255 . 255 . 255 . 248

11111111 . 11111111 . 11111111 . 11111000

Subnet

address

Subnet mask

Subnet 172.26.64.128 mask 255.255.255.248 is also expressed as

172.26.64.128/29.

This subnet contains 6 IP addresses: 232-29 = 8 minus 2 addresses (subnet

address and broadcast address).

Subnet 172.26.128.0 mask 255.255.128.0 is also expressed as 172.26.128.0/17

contains (232-17 2) = 32766 addresses.

29 bits



81/113


Solely for authorized persons having a need to knowProprietary Use pursuant to Company instruction81 | Presentation Title | Month 2009

Routing overview

Routing overview


82/113



To carry packets between a manager and a equipment to be supervised a path must be

found. IP routing is used.

There are two main types of routing:

! Static routing: All the routes are manually written by the network administrator.

! Dynamic routing: Router are able to find themselves a route.

Static routing can be used in our networks, just in case few elements are addressed. Its

impossible to maintain manually the routing table of a network with several hundreds

or thousands of equipments.


Routing overview

Static routing


83/113



N2 N3

N1N4

N6

N7

N5

If router R3 is down the route from router R1 to network N8 is lost.

R1

R2

R4

R6R3

R5

N8

N8 R3

Network Next hop

Router R1routing table


Routing overview

Dynamic routing


84/113



N2 N3

N1N4

N6

N7

N5

If router R3 is down the route from router R1 to network N8 is available.

R1

R2

R4

R6R3

R5

N8

N8

Network Next hop

Router R1routing table

R3

R5


Routing overview

Dynamic routing


85/113



It exists two types of dynamic routing:

! Distance Vector routing (RIP, BGP, ) based on number of hops to reach the

destination.

" Convergence time to slow" Bandwidth used by protocol to important

" Dedicated for little network

! Link state routing (OSPF, IS-IS, ) based on link state between routers.

" Convergence time faster

" Can support huge network

We use OSPF (Open Short Path First) routing protocol in our network.



86/113


Solely for authorized persons having a need to knowProprietary Use pursuant to Company instruction86 | Presentation Title | Month 2009

OSPF Routing

OSPF Routing

Link state routing


87/113



N2 N3

N1N4

N6

N7

N5

R1

R2

R4

R6R3

R5

N8

a b

c

d

e

OSPF is a protocol based on Link State.

Hello

Hello

Hello

HelloHello

By sending Hello packet routers discover their neighbors.

R1Port a : N1Port b : N4Port c : N6Port d : nothingPort e : nothing


OSPF Routing

LSA


88/113



N2 N3

N1N4

N6

N7

N5

R1

R2

R4

R6R3

R5

N8

ab

cd

e

LSA : Link state advertisement.

LSAR1Port a : N1Port b : N4Port c : N6Port d : nothing

Port e : nothing

Routers broadcast LSA to advertise about their link state.

R1Port a : N1Port b : N4Port c : N6Port d : nothingPort e : nothing


OSPF Routing

Database

D t b


89/113


N2 N3

N1N4

N6

N7

N5

R1

R2

R4

R6R3

R5

N8

Database is built with all LSA.

Each router have got the same database

DatabaseR1Port a : N1Port b : N4Port c : N6Port d : nothingPort e : nothing

R2Port a : nothingPort b : N2Port c : N1Port d : nothingPort e : nothing

Database

Database

Database

Database

Database

Database

ab

cd

e


OSPF Routing

Routing table

From Database each router computes its routing tableDatabase


90/113


N2 N3

N1N4

N6

N7

N5

R1

R2

R4

R6R3

R5

N8

From Database each router computes its routing tableusing Short Path First algorithm.

Each router have got its own routing table

DatabaseR1Port a : N1Port b : N4Port c : N6Port d : nothingPort e : nothing

R2Port a : nothingPort b : N2Port c : N1Port d : nothingPort e : nothing

Database

Database

Database

Database

Database

Database

Routing table

Routing table

Routing table

Routing tableRouting table

Routing table

N3 R2N2

N1

Network Next hop

R2

direct

a

Port

a

a

N7 R5N6

N5 N4 direct

direct

R3

c

b

c

b

N8 R3 b

R1 routing tablea

b

cd

e


OSPF Routing

OSPF operates within an Autonomous System (This is an Interior Gateway Protocol : IGP


91/113


OSPF operates within an Autonomous System (This is an Interior Gateway Protocol : IGP

in opposition to External Gateway Protocol : EGP), although it is capable of receiving

routes from and sending routes to other Autonomous Systems.

An Autonomous System using OSPF protocol is divided in areas. An area's topology should

not be known outside the area.

Each area must be linked to a special area named Backbone . Each area is identifying

by a number (IP address form).

OSPF protocol uses different types of LSA:

" LSA Type 1 : Point-to-point connection to another router

" LSA Type 2 : Connection to a transit network

" LSA Type 3 : Connection to a stub network

" LSA Type 4 : Virtual link (announced to entire network)

"


OSPF routing

Area Type


92/113


Backbone : Area 0.0.0.0

Area0.0.0.1

Area0.0.0.2 Area

0.0.0.3

Area Border Router

Autonomous System

Routing protocol : OSPFArea

0.0.0.4

Virtual Link


OSPF routing

Area types

" Backbone area 0.0.0.0


93/113


Backbone area 0.0.0.0

Mandatory path from an area to another

Backbone area is unique in an Autonomous System

" Secondary or Standard areas

Made up contiguous sub-network in order to facilitate summarization.

Connected to backbone either directly by an Area Border Router (ABR) or by avirtual link.

" Stub areas

Identical to secondary areas

Each ABR connected to the backbone inserts its own default route

Cannot announce external routes

Cannot be used to create a virtual link

" Totally stubby areas (AWY/MPR case)

Identical to stub areas but only the default route is known (The route by thebackbone are not announced)

" Not so stubby areas (RFC 1587)

Identical to stub areas but can announce external routes


OSPF routing

ASBR


94/113


Autonomous System Boundary Router

Autonomous System


Autonomous System


Autonomous System


Autonomous System

Routing protocol : not OSPF (Static, IS-IS, RIP, BGP, )

94 |TMN Networking | April 2012


95/113

Alcatel-Lucent ConfidentialSolely for authorized persons having a need to know

Proprietary Use pursuant to Company instruction95 | Presentation Title | Month 2009



SCOPE

To clarify the operations needed to plan in a proper way the addressing of a network


96/113


Proprietary Use pursuant to Company instruction

To clarify the operations needed to plan in a proper way the addressing of a network

composed by MPR and external devices leveraging the available features. Considerations

regarding the efficiency of the used IP addresses and how the knowledge of the project

can help in optimizing the resourced are highlighted too.

The project that is going to beanalyzed is reported in the below

picture, taking into account the

global network will be composed

by several projects. 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.



DESCRIPTION OF THE PROJECT

Site A is an existing site where other equipment is already installed. An MPR will be


97/113



g q p y

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 be managed via the TMNNetwork.

Site C is a repeater with no external device.

Site D is a repeater with one external device.

Site E is a repeater with two external devices. A new router (R2) connected via an

external link will be added to provide an alternate pathway for TMN Traffic.

Site F is a repeater with no external device.



ASSUMPTIONS 1/3

OSPF will be enabled within the network.


98/113



The recommended configuration is to enable OSPF within the MPR network whenever

possible. Correctly configuring Static routing internally within the MPR network can be

very complex for anything other than trivial linear networks and is not recommended.

The MPR network will be an Autonomous (isolated) OSPF network. It will use Staticrouting at the borders.

The use of OSPF or Static routing between the MPR network border and external

networks is a network design choice. When OSPF monitors the status of a link carrying

TMN Traffic, if the link fails, it can reroute the TMN traffic to use an alternate gateway

provided one is available.

In this condition the sizing of the project can be up to 150 NEs leveraging the multi OSPF

area support allowed by MPR while for the single OSPF area is still valid the 50 NEs

constrain.



ASSUMPTIONS 2/3

We remind the main MPR rules regarding the TMN management:


99/113



The IP Local address must be unique in the network

The local TMN Ethernet interface subnet must unique at least for each project

Other provision able TMN Ethernet interfaces (OoB P#4, InB #1, InB #2) subnets must be

unique at least for each project (since MPR 3.4)Optionally just one of the available TMN Ethernet interfaces IP can match the MPR IP

Local address (used in Example1)



ASSUMPTIONS 3/3

At site A where an external network is available, the MPR will be a member of the


100/113



external network, using the Port #4 TMN interface. The MPR will be configured to use

router R1 as the Default Gateway for reaching all other external networks.

At site E, a new local network will be defined using router R2. This network will provide

an alternate external route for TMN traffic. The MPR at site E will become a member ofthis network and will use Router R2 as the Default Gateway to reach the external

networks.

DHCP will be used for configuration of Craft computers.

Using 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 connect using the Craft.



DIFFERENT METHODS

Example 1:


101/113



The MPR Local Address is set to match the TMN Ethernet Port address at all sites.

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

Example 2:

The MPR Local Address is not matching the TMN Ethernet Port subnet.The TMN Ethernet subnets are considered unique just in the project, it means they will

be reused in the other projects of the network, while the next ones are considered

unique for the network:

- The Port #4 TMN interface is only enabled at sites: A (R1), E (R2) and D (Ext Eqpt 1

OoB).

- The TMN InB #1 bridge Subnets are enabled on B and E, replacing the need of the

switch (i.e. ext Eqpt are MPR, TMN flows are the same as for the traffic).

Example 3:

As for Example 2, but all the TMN Ethernet subnets are considered just unique in theprojects, it means can be reused in the other projects of the network.



PARAMETERS

Parameters to take into considerations are:


102/113



Variety of the size of the projects

- To uniform the minimum size address block to assign

Number of occurrence of the project growing

- To avoid a re-planning of the previous allocated IP addressesNumber of different topologies to be considered

- To have an estimation of the multiple connections on a single site per project

Need to have an easy summarization of the IP addresses for each project

-To minimize the effort to reprovision the external devices with new static routes

Optimize the used IP addresses

- To reduce the maintenance of the global planning and to match the customer need.



SIMULATION

Regarding the last point, a simulation is provided assuming a network composed by 120


103/113



projects for a total of 1880 MPRs; note that even better results can be achieved in case

the size of the project and of the network are larger.

The assumptions for such simulation are:

and the result are herebelow reporterd both in tabular and graphical formats.


Network size 1880 MPR 120 projects

Max project size 60 MPR

Number of sites 1600

Sites with 2 MPR 200 12,5% of total sites




RESULTS

The used reference criteria is the ratio in % between the used IP addresses and the


104/113



number of supervised MPR; a result closer to 100% means a better usage of the IP

addressing schema. It is evident that the Example 3 shows better results.


number of MPR

unique

reserved IPaddresses

reused IP

addresses

used IP

addresses vs

n.MPR ratio

(%)

Example 3 1880 1880 282 115,0

Example 2 1880 3000 240 172,3

Example 1 1880 8640 0 459,6


105/113




ANNEX 2

9500LUX50 IOT


106/113




9500LUX50 IOT

Technical specifications

ManagementInterfaces 9400LUX50 9400AWY 9500MPRMSS 8/4/1 MSS 1c MPR-e


107/113



Ethernet --- 1 7

(2 OoB & 6 InB)

3

(2 OoB & 1 InB)

1

(InB)

Native In Band

Management

--- --- YES YES YES

Serial V11 RS 422

64 Kb/s (co-dir.,

contro-dir. DCE)

2 1 ---

Serial G703 64

Kb/s for 9400AWY

---- 1 ---

BW on the

embeddedradio channel

64 Kb/s 64 Kb/s 192 Kb/s min

512 Kb/s max

Dedicated localCT access

RS 232 19.2 Kb/s RS 232 19.2 Kb/s -

Ethernet

Protocol/

Routing

SNMP v.2c/

OSPF, Static

SNMP v.2c/

OSPF, Static

SNMP v.2c/

OSPF, Static

IP addressingschema

VLSM VLSM Variable Lenght Subnet Mask



108/113

LUX50

DCN Interconnection

64Kb/s Radio


109/113




! Multiple 9400LUX50 terminals can be chained without need for external switch

V11 64Kbs

64Kb/s Radio

64Kb/s Radio

9400 LUX50

9400 LUX50

9400 LUX50

V11 64Kbs

V11 64Kbs

V11 64Kbs

LUX50

DCN Interconnection


110/113




Example of mixed network topology

NMS center

9500MPR subnet9500MPR subnet

9400AWY9400AWY

9400LUX509400LUX50

9400AWY9400AWY

WAN subnetWAN subnet

Unique

LAN subnets

WAN subnetWAN subnet

DCN

LUX50 & AWY

DCN Interconnection

9400 AWY


111/113




9400 UX LUX 501320CT

(initial setup)

NMS_V11 signal 64Kbps

Synchronous RS-422

9500 MPR & 9400 AWY & 9400LUX50 collocated

DCN Interconnection

512Kb/s Radio64Kb/s Radio


112/113




! Multiple MPR & AWY & LUX50 can be chained without need for externalswitch

512Kb/s Radio

1

0/100

BT

512Kb/s Radio

9500 MPR

9500 MPR

9500 MPR

10

/100

BT

10/100 Base T

V11 64Kbs

64Kb/s Radio

64Kb/s Radio

9400LUX50

9400 AWY

9400 AWY

V11 64Kbs

10/100 Base T

10/100 Base T

9500 MPR-MSS1c

9500 MPR-e

10/100 Base T


113/113




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

tmn networking.pdf

Documents