Networking 9500mpr 9500mxc 9400awy

All Rights Reserved Alcatel-Lucent 2006, #####1 October 2010 WT PU All Rights Reserved Alcatel-Lucent 2010

NETWORKING DCN rules

9500MPR & 9500MXC & 9400AWY

mixed network

October, 2010

2 October 2010 WT PU All Rights Reserved Alcatel-Lucent 2010

Content 1/2

Network diagram

Technical specifications

The management interfaces and interconnections:

MPR-AWY, MPR-MXC, MXC-AWY

OSPF network - 2 Areas with different IP address scheme

Addressing criteria:

Case 1: several AWY/LUX50, few MXC/MPR

Case 2: few AWY/LUX50, several MXC/MPR


Content 2/2

IP DCN interface: 6 different options

Using a SDH backbone to transport the IP management payload

Convey 3rd Party MW O&M traffic with 9500MPR

O&M 1 Harris -> Siemens -> Alcatel-Lucent

O&M 2 Siemens -> Harris -> Alcatel-Lucent

O&M 3 Alcatel-Lucent -> Harris -> Siemens

O&M 4 Alcatel-Lucent -> Siemens -> Harris

Backup slides


Example of mixed network topology

NOC

NMS center

9500MXC subnet9500MPR subnet9500MXC subnet9500MPR subnet

9400AWY9400AWY

9400AWY9400AWY

WAN subnetWAN subnet

DifferentLAN subnets


DCN

Network diagram (2 OSPF area are detailed: Max 50 NEs)

9500MPRWAN subnet

9500MPRWAN subnet

AREA 130.0.0.0

AREA 140.0.0.0

Case 1) MPR + AWY+ few MXC Case 2) MPR + MXC+

few AWYs


Technical specifications

Management Interfaces

9400AWY 9500MXC 9500MPR

MSS 8 / MSS 4 MSS 1c MPR-eEthernet

10/100 Base T1 1 (IDU),

4 (INU)

2 3 1

Native In Band Management

over GE traffic port

--- --- --- 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 local CT access

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

Ethernet -

EthernetProtocol/Routing

SNMP v.2c/

OSPF, Static

SNMP v.2c/

OSPF, Static

SNMP v.2c/

OSPF, Static

SNMP v.2c/

StaticIP addressing schema

VLSM VLSM Variable Lenght Subnet Mask


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

CT/NMS Ethernet RJ45

local interface

(always enabled)


LCT(initial setup)

CT Ethernet RJ45

local interface

(always enabled with fixed

IP 192.168.30.1)

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

2 Ethernet RJ45 Management ports:

Used to chain collocated equipment

or as GNE interface


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 craft terminal connection

9500MXC product


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

9500 MPR CSM

9400 AWY

LCT(initial setup)

NMS ETHERNET cable RJ45/RJ45

MPR - AWY common management (LAN connection)

NMS Ethernet RJ45 local interfaceNMS Ethernet RJ45 local interface

1 ports Ethernet connector assembly for NMS / RJ45


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


NMS Serial port v.24/RS232NMS Serial port v.24/RS2329500 MXC, NCC card (NMS function)

9400 AWY

LCT(initial setup)



MXC - AWY common management (LAN connection)


OSPF network - Case 1) MPR + AWY+ Few MXC - AREA 140.0.0.0

AWY 7

MPR 4

AWY 8

MPR 3

MPR 2MPR 1

Port 4TMN EthRF

151.98.99.245/22

1353NM

switch

L:130.1.1.3T:172.16.102.25/29

L:130.1.1.2T:172.16.102.9/29

L:130.1.1.1T:172.16.102.1/29P:151.98.97.5/22

151.98.96.182/22

P: Port 4 TMN IP addressT: TMN loc IP addressL: local IP address

Backbone

AWY 5AWY 6

L:130.1.1.8 L:130.1.1.6L:130.1.1.7 L:130.1.1.5E:172.16.102.42/29

L:130.1.1.4T:172.16.102.33/29P:172.16.102.41/29

NMS_V11

AREA 140.0.0.0Legenda

Legenda


OSPF network - Case 2) MPR + MXC+ Few AWYs - AREA 130.0.0.0

IP: 172.16.100.18/29

L:130.1.1.40

IP: 172.16.100.25/29

MXC100 17

MXC100 25

MPR100 1MPR100 9

151.98.99.245/22

1353NM

172.16.100.28/29

switch

hub

L:172.16.100.9T:172.16.100.9/29P:172.16.100.17/29

L:172.16.100.1T:172.16.100.1/29P:151.98.97.8/22

151.98.96.182/22

Backbone

AREA 130.0.0.0

AWY 41AWY 40

E:172.16.100.26/29L:130.1.1.41

Port 4TMN EthRF


Legenda

Legenda


OSPF network - 2 Areas with different IP address scheme

IP: 172.16.100.18/29

L:130.1.1.40

IP: 172.16.100.25/29

MXC100 17

MXC100 25

AWY 7

MPR 4

AWY 8

MPR 3

MPR 2MPR 1MPR100 1MPR100 9

Port 4TMN EthRF

151.98.99.245/22

1353NM

172.16.100.28/29

switch

L:130.1.1.3T:172.16.102.25/29

hub

L:130.1.1.2T:172.16.102.9/29

L:130.1.1.1T:172.16.102.1/29P:151.98.97.5/22

L:172.16.100.9T:172.16.100.9/29P:172.16.100.17/29

L:172.16.100.1T:172.16.100.1/29P:151.98.97.8/22

151.98.96.182/22


Backbone

AREA 130.0.0.0

AWY 41AWY 40 AWY 5AWY 6

E:172.16.100.26/29L:130.1.1.41 L:130.1.1.8 L:130.1.1.6L:130.1.1.7 L:130.1.1.5

E:172.16.102.42/29

L:130.1.1.4T:172.16.102.33/29P:172.16.102.41/29

NMS_V11

AREA 140.0.0.0

Legenda Legenda


Reccomendation

-It must be assured for each Network Element the local access for Maintenance purpose; it is not acceptable to have a DCN disconnection of a part of the Network in such case.So that, unless in case of a switch functionality is available in some site, for each considered NE type we have:

- 9400AWY: the preferred connection is performed using the local serial interface or the Ethernet one if available

- 9500MXC: the preferred connection is performed using the local serial interface or the Ethernet one if available

- 9500MPR: the preferred connection is performed using the local TMN Eth interface


Addressing scheme proposal

Defining an OSPF Area (IP address form) the Network Elements (NE) are linked together using MW link or NMS link

Each NE must have its own address in the network

Addresses must be booked according to available Private-Use Network address blocks (if PUBLIC addresses are not available):

10.0.0.0/8 (RFC1918) Class A basey that subnetting for 255.255.255.0 allows 65536 networks with 254 hosts for each

network

172.16.0.0/12 (RFC1918) Class B basey that subnetting for 255.255.255.0 allows 4096 networks with 254 hosts for each

network

192.168.0.0/16 (RFC1918) Class C basey that subnetting for 255.255.255.0 allows 256 networks with 254 hosts for each

network


Applied rules

9400AWY: defined by IP unnumbered PtP WAN scheme; when TMN Eth is used,a different subnet MUST be used9500MXC: defined by IP belonging to different subnet; mask /29 (255.255.255.248)is generally adopted to save IP addresses9500MPR:Case 1) MPR + AWY+ Few MXC - AREA 140.0.0.0defined by IP unnumbered PtP WAN scheme BUT-TMN Eth local interface to be configured on a different subnet-TMN Eth Port 4 to be configured (on request) on a different subnetAlso in the last two cases mask /29 (255.255.255.248) is generally adoptedCase 2) MPR + MXC+ Few AWYs - AREA 130.0.0.0defined by IP belonging to different subnet; mask /29 (255.255.255.248)is generally adopted to save IP addresses-TMN Eth local interface belongs to the same subnet-TMN Eth Port 4 to be configured (on request) on a different subnetAlso in this case mask /29 (255.255.255.248) is generally adopted


Addressing scheme proposal: Case 1: several AWY/LUX50, few MXC/MPR

Example: Assigned address range from the customer for 1 OSPF area10.10.10.0 /24 = network mask 255.255.255.0Depending from the NE type and composition we foresee the following subnettingCase 1: several AWY/LUX50, few MXC/MPR

A WAN subnet (to define the consecutive IP addresses for AWY, LUX50, MPR) is defined by:

Available address range: 10.10.10.1 10.10.10.62Corresponding to 10.10.10.0 /26 including 62 hosts (/32 subnet address)

A Set of LAN subnets (AWY and MXC NMS_Eth is used, MPR NMS_Eth_L, MPR NMS_EthP4 if enabled )

Available address range: 10.10.10.65 10.10.10.254Corresponding to: 10.10.10.64 /26 including 8 /29 subnets (6 hosts for each subnet) 10.10.10.128 /26 including 8 /29 subnets (6 hosts for each subnet) 10.10.10.192 /26 including 8 /29 subnets (6 hosts for each subnet) 62_24 splitting utility


Addressing scheme proposal: Case 2: few AWY/LUX50, several MXC/MPR

Example: Assigned address range from the customer for 1 OSPF area10.10.10.0 /24 = network mask 255.255.255.0Depending from the NE type and composition we foresee the following subnettingCase 2: few AWY/LUX50, several MXC/MPR

A WAN subnet (AWY - no NMS_Eth enabled, LUX50) is defined by:Available address range: 10.10.10.1 10.10.10.14Corresponding to 10.10.10.0 /28 (.240) including 14 hosts (/32 subnet address)

A Set of LAN subnets (AWY and MXC NMS_Eth is used, MPR NMS_Eth_L, MPR NMS_EthP4 if enabled )

Available address range: 10.10.10.16 10.10.10.254Corresponding to: 10.10.10.16 /24 (.0) including 30 /29 subnets (6 hosts for each subnet)

m

14_30 splitting utility


IP DCN interface: 6 different options

N.Extra

router needAutonomous System (2) (5)

Area Border Router (4)

Max Nro of OSPF Area (max 50 NE for Area)

Additional routes on the Backbone

Stub Area NE selection

Summarisation Router

commandNote

1 NO YES 2 50 don't care NOT APPLICABLE (4)2 NO YES 3 50 YES NOT APPLICABLE (1) (4)3 NO YES don't care don't care don't care NOT APPLICABLE (2) (5)

4 YES YES don't care only router dimensioning YES OPTION (1)5 YES YES don't care only router dimensioning NO YES (3)6 YES YES don't care don't care don't care don't care (2) (3)

Note (1) Not to be used with mixed network where STUB option in not available (LUX 40, 9400AWY 2.X, 9500MXC)(2) Autonomous System implies the usage of Static routing on Ethernet interface facing the IP network - Default Gateway can be used

(3) Suggested configuration in case of mixed PDH-SDH (IP-OSI) network using IP over OSI tunneling

(4) Beside the routers, only 9400AWY and 9500MPR can support these functionalities as GNE

(5) Beside the routers, only 9500MPR, 9500MXC and 9400AWY can act as GNE


It is applicable only on dedicated small networks where AWY or 9500MPR is the GNEwith the NMS Eth enabled belonging to the IP subnet x defined by the customer gateway;

additional NEs can be chained as for LUX50 because the STUB option can be applied. Up to 3 OSPF Areas can be enabled

Gateway

Examples for case 1) and 2)

IP: 10.10.10.1 IP: 10.10.10.2

IP subnet # 1: 10.10.10.0 /26 IP subnet # xBackbone

OSPF Area 0

IP subnet # 2: 10.10.11.0 /26

IP subnet # 3: 10.10.12.0 /26


Examples for case 3)

Recommended configuration. OSPF Areas are isolated each other working as Autonomous System. Connection to a remote manager is obtained using Static Routes.

IP: 10.10.10.1 IP: 10.10.10.2

IP subnet # 1: 10.10.10.0 /26

IP subnet # 2: 10.10.11.0 /26

IP subnet # 3: 10.10.12.0 /26 TO APPLY STATIC ROUTINGON ETHERNET INTERFACE,ENABLING THE DEFAULT GATEWAY

DCN Gateway

DCN Gateway

DCN Gateway


It implies the usage of a router as Area Border Router facing the backbone OSPF Area 0 on the DCN and providing NMS Eth or Serial X21 connections towards the MW OSPF Areas different from 0.

Examples for case 4) and 5)

IP: 10.10.10.1 IP: 10.10.10.2

IP subnet # 1: 10.10.10.0 /26

BackboneOSPF Area 0

IP subnet # 2: 10.10.11.0 /26

IP subnet # 3: 10.10.12.0 /26


Examples for case 6)

OSPF Areas are isolated each other working as Autonomous System.Connection to a remote manager is obtained with a router that provides NMS Eth or Serial X21 connections towards the MW OSPF Areas while connection to a remote manager is obtained using Static Routes.

IP: 10.10.10.1 IP: 10.10.10.2

IP subnet # 1: 10.10.10.0 /26

IP subnet # 2: 10.10.11.0 /26

IP subnet # 3: 10.10.12.0 /26 TO APPLY STATIC ROUTINGON ETHERNET INTERFACE,ENABLING THE DEFAULT GATEWAY

DCN Gateway


Using a SDH backbone to transport the IP management payload

9500MXC 9500MPR subnet

9500MXC 9500MPR subnet

9400AWY9400AWY9400LUX509400LUX509400AWY9400AWY



NMS center

DCN9500MXC subnet9500MXC subnet

SDH OSI backbone


Provided that the SDH Q3 NEs, belonging to SDH backbone and adjacent to the IP cluster, are able to perform the IP over OSI tunnelling, it means the IP payload can be transported over the OSI packets.In this case it is feasible to have the following connection:

9500MXC9500MPR subnet

9500MXC9500MPR subnet

9400AWY9400AWY9400AWY9400AWY



SDH OSI backboneThe A-L WT Q3 NEsproviding this feature are:9600LSY: LHR/LHRC 2.0,9600USY: UHR/UHRC 2.1B, 2.2, 2.3UHRN 2.0; the same can be applied tothe A-L OMSN Q3 NEs (1650SMC, 1660SM,..).Warnings:-the OSI GNE can support a maximum of 4 tunnels terminations-Dimensioning rules could suggest to use (no available Bandwith over DCC) different solutions as Eth over SDH or mapping over E1.

IP over OSI tunnel

Note: the same feature is used in case of 9500MXC STM-1 transport!


Convey 3rd Party MW O&M traffic with 9500MPR

Some examples :

O&M 1 Harris -> Siemens -> Alcatel-LucentO&M 2 Siemens -> Harris -> Alcatel-LucentO&M 3 Alcatel-Lucent -> Harris -> SiemensO&M 4 Alcatel-Lucent -> Siemens -> Harris


9500MPR O&M

V11, 64K syncHarris

V11, 19.2K asyncHarris

RS485, 128K Siemens

10Base2 (T)Siemens

64K Sync Harris

10BaseT Siemens

Siemens O&M

Harris O&M

64K Sync Harris

RBS

Harris + Siemens O&M

ATM

ATM

HarrisMDLPDH

19.2KSupv1

64KAUX

HarrisMDLPDH

19.2KSupv1

64KAUX

HarrisSVUUnit

X7V11

X4V11

X5V11

SiemensSRALPDH

D1Ch

U-ChV11

VBUS

SiemensSRALPDH

D1Ch

VBUS

U-ChV11

SiemensSRALPDH

D1Ch

D2Ch

U-ChV11

VBUS

SiemensSRALPDH

D1Ch

D2Ch

VBUS

U-ChV11

Existing MW PDH Radio

SiemensDual QV

BUS 10B2

SiemensNMS

HarrisNMS

ExistingTransportNetwork

A-LNMS

A-LMPR

AU

X64K

V114 FE

IN O

UT

A-LMPR

AU

X64K

V114 FE

IN O

UT

O&M 1 Harris -> Siemens -> Alcatel-Lucent


O&M 2 Siemens -> Harris -> Alcatel-Lucent

9500MPR O&M

64K Sync Siemens

10BaseT Siemens

64K Sync Harris

64K Sync Siemens

64K Sync Harris

Harris O&M

Siemens O&M

RBS

Siemens + Harris O&M

ATM

ATM

HarrisMDLPDH

19.2KSupv1

64KAUX

HarrisMDLPDH

19.2KSupv1

64KAUX

HarrisSVUUnit

X7V11

X4V11

X5V11


SiemensNMS

HarrisNMS

SiemensSRALPDH

D1Ch

U-ChV11

VBUS

SiemensSRALPDH

D1Ch

VBUS

U-ChV11

HarrisMDLPDH

19.2KSupv1

64KAUX

HarrisMDLPDH

19.2KSupv1

64KAUX

A-LNMS


A-LMPR

AU

X64K

V114 FE

IN O

UT

A-LMPR

AU

X64K

V114 FE

IN O

UT

10Base2 (T)Siemens

SiemensDual QV

BUS 10B2


O&M 3 Alcatel-Lucent -> Harris -> Siemens

Alcatel-Lucent MW O&M

10Base2 Siemens

Alcatel-Lucent + Harris O&M

64K Sync Harris

RBS

Alcatel-Lucent + Harris + Siemens O&M

ATM

ATM

HarrisMDLPDH

19.2KSupv1

64KAUX

HarrisMDLPDH

19.2KSupv1

64KAUX

HarrisSVUUnit

X7V11

X4V11

X5V11

SiemensSRALPDH

D1Ch

U-ChV11

VBUS

SiemensSRALPDH

D1Ch

VBUS

U-ChV11

SiemensSRALPDH

D1Ch

D2Ch

U-ChV11

VBUS

SiemensSRALPDH

D1Ch

D2Ch

VBUS

U-ChV11


SiemensDual QV

BUS 10B2

SiemensNMS

HarrisNMS

A-LNMS


1 case) Alcatel-Lucent MW O&Musing the FE transport

A-LMPR

AU

X64K

V114 FE

IN O

UT

A-LMPR

AU

X64K

V114 FE

IN O

UT

2 case) Alcatel-Lucent MW O&Musing the E1 transportA-L

MPR

AU

X64K

V114 FE

IN O

UT

A-LMPR

AU

X64K

V114 FE

IN O

UT

Eth/E1adapter

E1/Ethadapter

A-LMPR

AU

X64K

V114 FE

IN O

UT

A-LMPR

AU

X64K

V114 FE

IN O

UT


O&M 4 Alcatel-Lucent -> Siemens -> Harris

10Base2 Siemens

Alcatel-Lucent O&M

64K Sync Harris

Alcatel-Lucent + Siemens O&M

RBS

Alcatel-Lucent + Siemens + Harris O&M

ATM

ATM

HarrisMDLPDH

19.2KSupv1

64KAUX

HarrisMDLPDH

19.2KSupv1

64KAUX

HarrisSVUUnit

X7V11

X4V11

X5V11


SiemensNMS

HarrisNMS

SiemensSRALPDH

D1Ch

U-ChV11

VBUS

SiemensSRALPDH

D1Ch

VBUS

U-ChV11

HarrisMDLPDH

19.2KSupv1

64KAUX

HarrisMDLPDH

19.2KSupv1

64KAUX

A-LNMS


SiemensDual QV

BUS 10B2

A-LMPR

AU

X64K

V114 FE

IN O

UT

A-LMPR

AU

X64K

V114 FE

IN O

UT

1 case) Alcatel-Lucent MW O&Musing the FE transport

A-LMPR

AU

X64K

V114 FE

IN O

UT

A-LMPR

AU

X64K

V114 FE

IN O

UT

2 case) Alcatel-Lucent MW O&Musing the E1 transportA-L

MPR

AU

X64K

V114 FE

IN O

UT

A-LMPR

AU

X64K

V114 FE

IN O

UT

Eth/E1adapter

E1/Ethadapter


www.alcatel-lucent.com


BACKUP SLIDES


IP DCN interface: example

8

5

6

34

7 AB

101 102

108

107

7u

8u5i

9i

10i

3i

4i

6i8i 7i

14i

15i

1i2i

12i

13i

17i16i

11i

i means that it is part of I&V validation network, otherwise it is part of Network Integration Lab

9500MPR 1.0

9600 AWY 2.0/2.1

9500MXC 1.0

P4TMNRF

1353NM

F0/0

F0/1F0/1

F0/0UP DOWN

AREA0.0.0.0

AREA0.0.0.1

0.0.0.3AREA

AREA130.0.0.0

151.98.96.0/22

172.20.20.0/22

AREA stub0.0.0.2

AREA stub0.0.0.4

u means that it is a 9400AWY 2.0(ULS) NE

Static routing

NE

AREA0.0.0.0

N.3N.2N.5


IP DCN interface: exampleName Element Type Local IP TMN IP Core Port 4 IP

HP/UX server 1353NM 151.98.99.245 / 22 --- ---Router UP --- 151.98.96.249 / 22 (F0/0) 20.20.20.5 / 30 (F0/1) ---Router DOWN --- 172.20.20.20 / 22 (F0/0) 20.20.20.6 / 30 (F0/1) ---5 9500MPR 172.20.20.66 172.20.20.66 / 22 172.16.118.5 / 298 9500MPR 172.16.108.2 172.16.108.2 / 29 172.16.118.1 / 297 9500MPR 172.16.107.1 172.16.107.1 / 29 172.16.117.1 /296 9500MPR 172.16.106.6 172.16.106.6 / 29 172.16.116.6 / 294 9500MPR 172.16.114.4 172.16.115.4 / 29 172.16.104.4 / 293 9500 MPR 172.16.103.3 172.16.103.3 / 29 172.16.116.3 / 29101 9400 AWY 2.1.1 130.1.1.101 172.16.104.1 / 29 ---102 9400 AWY 2.1.1 130.1.1.102 172.16.120.3 / 29 ---107 9400 AWY 2.1.1 130.1.1.107 172.16.130.1 / 29 ---108 9400 AWY 2.1.1 130.1.1.108 172.16.120.2 / 29 ---7u 9400 AWY 2.0.5 130.1.1.7 172.16.110.1 / 29 ---8u 9400 AWY 2.0.5 130.1.1.8 172.16.130.2 / 29 ---A 9500MXC 1.0 172.16.110.2 --- ---B 9500MXC 1.0 172.16.117.2 --- ---


IP DCN interface: exampleName Element Type Local IP TMN IP Core Port 4 IP

1i 9500MPR 192.168.66.2 192.168.66.2 / 24 192.168.60.2 / 242i 9500MPR 192.168.7.1 192.168.7.1 / 24 ---3i 9500MPR 192.168.15.1 192.168.1.1 / 24 192.168.15.1 / 244i 9500MPR 192.168.200.1 192.168.15.2 / 24 ---5i 9500MPR 10.0.10.5 172.20.20.5 / 22 ---6i 9500MPR 10.0.10.6 172.20.20.6 / 22 ---7i 9500MPR 10.0.10.7 192.168.40.1 / 24 192.168.50.1 / 248i 9500MPR 10.0.10.8 192.168.97.12 / 24 192.168.40.2 / 249i 9500MPR 192.168.30.1 192.168.3.1 / 24 192.168.30.1 / 2410i 9500MPR 192.168.20.2 192.168.30.2 / 24 192.168.20.2 / 2411i 9500MPR 192.168.9.2 192.168.9.2 / 24 192.168.90.2 / 2412i 9500MPR 172.20.20.4 172.20.20.4 / 22 192.168.90.1 /2413i 9500MPR 192.168.88.2 192.168.88.2 / 24 192.168.80.2 / 2414i 9500MPR 192.168.5.2 192.168.5.2 / 24 192.168.50.2 / 2415i 9500MPR 192.168.6.1 192.168.6.1 / 24 192.168.60.1 / 2416i 9500MPR 192.168.8.1 192.168.8.1 / 24 192.168.80.1 / 2417i 9500MPR 192.168.77.2 192.168.77.2 / 24 ---


IP over OSI tunnel: example 1 (Only 1 OSPF Area)

AWY6

AWY 5

MXC Basso

MXC Alto

Area OSPF 1 = 130.0.0.0

Eth. crossed or straight cable130.1.1.3/24

130.1.1.6/24 130.1.10.1/24

151.98.170.190/23

44 AWY chain from AWY_7 to AWY_50

V11

For Windows XP SP2 the following setting is needed:HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\tcpip\parameters \EnablePMTUBHDetect 1 (enabled)

UHRAlto

UHR Basso

Eth. Straight cable

130.1.10.68/24151.98.171.20/23

IP over OSI tunnel

Osi over IP tunnel

151.98.171.240/23

130.1.1.70/24130.1.1.5/24

CT 1353NM


IP over OSI tunnel: example 2 (The backbone is build over the SDH ring)

AWY6

AWY 5

MXC Basso

MXC Alto

Area OSPF 1 = 130.0.0.0

Eth. crossed or straight cable130.1.1.3/24

130.1.1.6/24 130.1.10.1/24

151.98.170.190/23

44 AWY chain from AWY_7 to AWY_50

V11

For Windows XP SP2 the following setting is needed:

HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\tcpip\parameters \EnablePMTUBHDetect 1 (enabled)

UHRAlto

UHR Basso

Eth. Straight cable

130.1.10.68/24151.98.171.20/23

IP over OSI tunnel

Osi over IP tunnel

151.98.171.240/23

130.1.1.70/24130.1.1.5/24

Area OSPF 0= 0.0.0.0

CT 1353NM


www.alcatel-lucent.com

NETWORKING DCN rules9500MPR & 9500MXC & 9400AWY mixed networkContent 1/2Content 2/2Network diagram (2 OSPF area are detailed: Max 50 NEs)Technical specifications9500MPR product (IDU: MSS-8/MSS-4)9500MPR product: (IDU: MSS-1c)9500MXC productMPR - AWY common management (LAN connection)MPR - MXC common management (LAN connection)MXC - AWY common management (LAN connection)ReccomendationAddressing scheme proposalApplied rulesAddressing scheme proposal: Case 1: several AWY/LUX50, few MXC/MPR Addressing scheme proposal: Case 2: few AWY/LUX50, several MXC/MPR IP DCN interface: 6 different options Using a SDH backbone to transport the IP management payload IP over OSI tunnel Convey 3rd Party MW O&M traffic with 9500MPR O&M 1 Harris -> Siemens -> Alcatel-Lucent O&M 2 Siemens -> Harris -> Alcatel-Lucent O&M 3 Alcatel-Lucent -> Harris -> Siemens O&M 4 Alcatel-Lucent -> Siemens -> HarrisBACKUP SLIDES IP DCN interface: example IP DCN interface: example IP DCN interface: example IP over OSI tunnel: example 1 (Only 1 OSPF Area) IP over OSI tunnel: example 2 (The backbone is build over the SDH ring)NETWORKING DCN rules9500MPR & 9500MXC & 9400AWY mixed networkContent 1/2Content 2/2Network diagram (2 OSPF area are detailed: Max 50 NEs)Technical specifications9500MPR product (IDU: MSS-8/MSS-4)9500MPR product: (IDU: MSS-1c)9500MXC productMPR - AWY common management (LAN connection)MPR - MXC common management (LAN connection)MXC - AWY common management (LAN connection)ReccomendationAddressing scheme proposalApplied rulesAddressing scheme proposal: Case 1: several AWY/LUX50, few MXC/MPR Addressing scheme proposal: Case 2: few AWY/LUX50, several MXC/MPR IP DCN interface: 6 different options Using a SDH backbone to transport the IP management payload IP over OSI tunnel Convey 3rd Party MW O&M traffic with 9500MPR O&M 1 Harris -> Siemens -> Alcatel-Lucent O&M 2 Siemens -> Harris -> Alcatel-Lucent O&M 3 Alcatel-Lucent -> Harris -> Siemens O&M 4 Alcatel-Lucent -> Siemens -> HarrisBACKUP SLIDES IP DCN interface: example IP DCN interface: example IP DCN interface: example IP over OSI tunnel: example 1 (Only 1 OSPF Area) IP over OSI tunnel: example 2 (The backbone is build over the SDH ring)ANCILLARY DOCUMENTATION

Documents

Networking 9500mpr 9500mxc 9400awy