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 subnet
9500MPR subnet
9500MXC subnet
9500MPR subnet
9400AWY
9400AWY
9400AWY
9400AWY
WAN subnet
WAN subnet
Different
LAN subnets
WAN subnet
WAN subnet
DCN
Network diagram (2 OSPF area are detailed: Max 50 NEs)
9500MPR
WAN subnet
9500MPR
WAN 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-e
Ethernet
10/100 Base T
1 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
-
Ethernet
Protocol/
Routing
SNMP v.2c/
OSPF, Static
SNMP v.2c/
OSPF, Static
SNMP v.2c/
OSPF, Static
SNMP v.2c/
Static
IP 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/RS232
9500 MPR CSM
9400 AWY
LCT
(initial setup)
NMS ETHERNET cable RJ45/RJ45
MPR - AWY common management (LAN connection)
NMS Ethernet RJ45 local interface
1 ports Ethernet connector
assembly for NMS / RJ 45
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)
1 ports Ethernet connector assembly for NMS / RJ 45
MPR - MXC common management (LAN connection)
9500 MXC, NCC card (NMS function)
9400 AWY
LCT
(initial setup)
1 ports Ethernet connector
assembly for NMS / RJ 45
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 2 MPR 1
Port 4
TMN Eth
RF
151.98.99.245/22
1353NM
switch
L:130.1.1.3
T:172.16.102.25/29
L:130.1.1.2
T:172.16.102.9/29
L:130.1.1.1
T:172.16.102.1/29
P:151.98.97.5/22
151.98.96.182/22
P: Port 4 TMN IP address
T: TMN loc IP address
L: local IP address
Backbone
AWY 5 AWY 6
L:130.1.1.8
L:130.1.1.6
L:130.1.1.7 L:130.1.1.5
E:172.16.102.42/29
L:130.1.1.4
T:172.16.102.33/29
P:172.16.102.41/29
NMS_V11
AREA 140.0.0.0
Legenda
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 1
MPR100 9
151.98.99.245/22
1353NM
172.16.100.28/29
switch
hub
L:172.16.100.9
T:172.16.100.9/29
P:172.16.100.17/29
L:172.16.100.1
T:172.16.100.1/29
P:151.98.97.8/22
151.98.96.182/22
Backbone
AREA 130.0.0.0
AWY 41 AWY 40
E:172.16.100.26/29
L:130.1.1.41
Port 4
TMN Eth
RF
L: local IP address
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 2 MPR 1
MPR100 1
MPR100 9
Port 4
TMN Eth
RF
151.98.99.245/22
1353NM
172.16.100.28/29
switch
L:130.1.1.3
T:172.16.102.25/29
hub
L:130.1.1.2
T:172.16.102.9/29
L:130.1.1.1
T:172.16.102.1/29
P:151.98.97.5/22
L:172.16.100.9
T:172.16.100.9/29
P:172.16.100.17/29
L:172.16.100.1
T:172.16.100.1/29
P:151.98.97.8/22
151.98.96.182/22
L: local IP address
Backbone
AREA 130.0.0.0
AWY 41 AWY 40 AWY 5 AWY 6
E:172.16.100.26/29
L:130.1.1.41
L:130.1.1.8
L:130.1.1.6
L:130.1.1.7 L:130.1.1.5
E:172.16.102.42/29
L:130.1.1.4
T:172.16.102.33/29
P: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 base
that subnetting for 255.255.255.0 allows 65536 networks with 254 hosts for each
network
172.16.0.0/12 (RFC1918) Class B base
network
192.168.0.0/16 (RFC1918) Class C base
network
Applied rules
9400AWY: defined by IP unnumbered PtP WAN scheme; when TMN Eth is used,
a different subnet MUST be used
9500MXC: defined by IP belonging to different subnet; mask /29 (255.255.255.248)
is generally adopted to save IP addresses
9500MPR:
Case 1) MPR + AWY+ Few MXC - AREA 140.0.0.0
defined 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 subnet
Also in the last two cases mask /29 (255.255.255.248) is generally adopted
Case 2) MPR + MXC+ Few AWYs - AREA 130.0.0.0
defined 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 subnet
Also 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 area
10.10.10.0 /24 = network mask 255.255.255.0
Depending from the NE type and composition we foresee the following subnetting
Case 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.62
Corresponding 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 )
Corresponding to:
10.10.10.64 /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 area
10.10.10.0 /24 = network mask 255.255.255.0
Depending from the NE type and composition we foresee the following subnetting
Case 2: few AWY/LUX50, several MXC/MPR
A WAN subnet (AWY - no NMS_Eth enabled, LUX50) is defined by:
Corresponding 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 )
Corresponding 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 need
Autonomous
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
command
Note
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 GNE
with 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 # x
Backbone
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 ROUTING
ON 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
Backbone
OSPF 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 ROUTING
ON ETHERNET INTERFACE,
ENABLING THE DEFAULT GATEWAY
DCN Gateway
Using a SDH backbone to transport the IP management payload
9500MXC
9500MPR
subnet
9500MXC
9500MPR
subnet
9400AWY
9400AWY
9400LUX50
9400LUX50
9400AWY
9400AWY
WAN subnet
WAN subnet
WAN subnet
WAN subnet
NMS center
DCN
9500MXC
subnet
9500MXC
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:
9500MXC
9500MPR subnet
9500MXC
9500MPR subnet
9400AWY
9400AWY
9400AWY
9400AWY
WAN subnet
WAN subnet
WAN subnet
WAN subnet
SDH OSI backbone
The A-L WT Q3 NEs
providing this feature are:
9600LSY: LHR/LHRC 2.0,
9600USY: UHR/UHRC 2.1B, 2.2, 2.3
UHRN 2.0; the same can be applied to
the 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 :
9500MPR O&M
V11, 64K sync
Harris
V11, 19.2K async
Harris
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
Harris
MDL
PDH
19.2K
Supv1
64K
AUX
Harris
MDL
PDH
19.2K
Supv1
64K
AUX
Harris
SVU
Unit
X7
V11
X4
V11
X5
V11
Siemens
SRAL
PDH
D1
Ch
U-Ch
V11
V
BUS
Siemens
SRAL
PDH
D1
Ch
V
BUS
U-Ch
V11
Siemens
SRAL
PDH
D1
Ch
D2
Ch
U-Ch
V11
V
BUS
Siemens
SRAL
PDH
D1
Ch
D2
Ch
V
BUS
U-Ch
V11
Existing MW
PDH Radio
Siemens
Dual Q
V
BUS
10B2
Siemens
NMS
Harris
NMS
Existing
Transport
Network
A-L
NMS
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
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
Harris
MDL
PDH
19.2K
Supv1
64K
AUX
Harris
MDL
PDH
19.2K
Supv1
64K
AUX
Harris
SVU
Unit
X7
V11
X4
V11
X5
V11
Existing MW
PDH Radio
Siemens
NMS
Harris
NMS
Siemens
SRAL
PDH
D1
Ch
U-Ch
V11
V
BUS
Siemens
SRAL
PDH
D1
Ch
V
BUS
U-Ch
V11
Harris
MDL
PDH
19.2K
Supv1
64K
AUX
Harris
MDL
PDH
19.2K
Supv1
64K
AUX
A-L
NMS
Existing
Transport
Network
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
10Base2 (T)
Siemens
Siemens
Dual Q
V
BUS
10B2
Al catel-Lucent MW O&M
10Base2
Siemens
Al catel-Lucent + Harris O&M
64K Sync Harris
RBS
Al catel-Lucent + Harris + Siemens O&M
ATM
ATM
Harris
MDL
PDH
19.2K
Supv1
64K
AUX
Harris
MDL
PDH
19.2K
Supv1
64K
AUX
Harris
SVU
Unit
X7
V11
X4
V11
X5
V11
Siemens
SRAL
PDH
D1
Ch
U-Ch
V11
V
BUS
Siemens
SRAL
PDH
D1
Ch
V
BUS
U-Ch
V11
Siemens
SRAL
PDH
D1
Ch
D2
Ch
U-Ch
V11
V
BUS
Siemens
SRAL
PDH
D1
Ch
D2
Ch
V
BUS
U-Ch
V11
Existing MW
PDH Radio
Siemens
Dual Q
V
BUS
10B2
Siemens
NMS
Harris
NMS
A-L
NMS
Existing
Transport
Network
1 case) Alcatel-Lucent MW O&M
using the FE transport
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
using the E1 transport
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
Eth/E1
adapter
E1/Eth
adapter
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
10Base2
Siemens
Al catel-Lucent O&M
64K Sync Harris
Al catel-Lucent + Siemens O&M
RBS
Al catel-Lucent + Siemens + Harris O&M
ATM
ATM
Harris
MDL
PDH
19.2K
Supv1
64K
AUX
Harris
MDL
PDH
19.2K
Supv1
64K
AUX
Harris
SVU
Unit
X7
V11
X4
V11
X5
V11
Existing MW
PDH Radio
Siemens
NMS
Harris
NMS
Siemens
SRAL
PDH
D1
Ch
U-Ch
V11
V
BUS
Siemens
SRAL
PDH
D1
Ch
V
BUS
U-Ch
V11
Harris
MDL
PDH
19.2K
Supv1
64K
AUX
Harris
MDL
PDH
19.2K
Supv1
64K
AUX
A-L
NMS
Existing
Transport
Network
Siemens
Dual Q
V
BUS
10B2
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
using the FE transport
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
using the E1 transport
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
A-L
MPR
A
U
X
6
4
K

V
1
1
4

F
E
I
N

O
U
T
Eth/E1
adapter
E1/Eth
adapter
www.alcatel-lucent.com
BACKUP SLIDES
IP DCN interface: example
8
5
6
3 4
7 A B
101 102
108
107
7u
8u
5i
9i
10i
3i
4i
6i 8i 7i
14i
15i
1i 2i
12i
13i
17i 16i
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
P4
TMN
RF
1353NM
F0/0
F0/1
F0/1
F0/0
UP DOWN
AREA
0.0.0.0
AREA
0.0.0.1
0.0.0.3
AREA
AREA
130.0.0.0
151.98.96.0/22
172.20.20.0/22
AREA stub
0.0.0.2
AREA stub
0.0.0.4
u means that it is a 9400AWY 2.0(ULS) NE
Static routing
NE
AREA
0.0.0.0
N.3
N.2
N.5
Name 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 / 29
8 9500MPR 172.16.108.2 172.16.108.2 / 29 172.16.118.1 / 29
7 9500MPR 172.16.107.1 172.16.107.1 / 29 172.16.117.1 /29
6 9500MPR 172.16.106.6 172.16.106.6 / 29 172.16.116.6 / 29
4 9500MPR 172.16.114.4 172.16.115.4 / 29 172.16.104.4 / 29
3 9500 MPR 172.16.103.3 172.16.103.3 / 29 172.16.116.3 / 29
101 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 --- ---
Name 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 / 24
2i 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 / 24
4i 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 / 24
8i 9500MPR 10.0.10.8 192.168.97.12 / 24 192.168.40.2 / 24
9i 9500MPR 192.168.30.1 192.168.3.1 / 24 192.168.30.1 / 24
10i 9500MPR 192.168.20.2 192.168.30.2 / 24 192.168.20.2 / 24
11i 9500MPR 192.168.9.2 192.168.9.2 / 24 192.168.90.2 / 24
12i 9500MPR 172.20.20.4 172.20.20.4 / 22 192.168.90.1 /24
13i 9500MPR 192.168.88.2 192.168.88.2 / 24 192.168.80.2 / 24
14i 9500MPR 192.168.5.2 192.168.5.2 / 24 192.168.50.2 / 24
15i 9500MPR 192.168.6.1 192.168.6.1 / 24 192.168.60.1 / 24
16i 9500MPR 192.168.8.1 192.168.8.1 / 24 192.168.80.1 / 24
17i 9500MPR 192.168.77.2 192.168.77.2 / 24 ---
IP over OSI tunnel: example 1 (Only 1 OSPF Area)
AWY
6
AWY
5
MXC
Basso
MXC
Alto
Area
OSPF 1 =
130.0.0.0
Eth. crossed or straight cable
130.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\param
eters \EnablePMTUBHDetect 1 (enabled)
UHR
Alto
UHR
Basso
Eth. Straight cable
130.1.10.68/24
151.98.171.20/2
3
IP over OSI tunnel
Osi over IP tunnel
151.98.171.240/23
130.1.1.70/24
130.1.1.5/24
CT
1353NM
IP over OSI tunnel: example 2 (The backbone is build over the SDH ring)
AWY
6
AWY
5
MXC
Basso
MXC
Alto
Area
OSPF 1 =
130.0.0.0
Eth. crossed or straight cable
130.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\param
eters \EnablePMTUBHDetect 1 (enabled)
UHR
Alto
UHR
Basso
Eth. Straight cable
130.1.10.68/24
151.98.171.20/2
3
IP over OSI tunnel
Osi over IP tunnel
151.98.171.240/23
130.1.1.70/24
130.1.1.5/24
Area
OSPF 0=
0.0.0.0
CT
1353NM
www.alcatel-lucent.com

Networking 9500mpr 9500mxc 9400awy

Uploaded by

Copyright:

Available Formats

Networking 9500mpr 9500mxc 9400awy

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Networking 9500mpr 9500mxc 9400awy

Uploaded by

Copyright:

Available Formats

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

NETWORKING DCN rules

You might also like