TMN Networking PDF

AT THE SPEED OF IDEAS
TMN Networking
November 2012
Agenda
Synthetic view
1. 9500MPR
2. 9500MXC
3. 9400AWY
4. 9600LSY
5. 9500MPR & 9400AWY
collocated
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
12.ANNEX 2
1.
2.
3.
4.
5.
6.
SNMP management
OSI layer model
IP addressing
Routing overview
OSPF routing
Planning and addressing a network
1.
9400LUX50 IOT
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
TMN Networking
9500MPR
4 | Presentation Title | Month Year
Alcatel-Lucent Confidential
Solely for authorized persons having a need to know
Proprietary Use pursuant to Company instruction
9500MPR (MSS 8/4/1) Capability

IP parameters
Management Protocol:
9500 MPR
SNMPv2c for supervision

FTP for download/backup/restore
Telnet for debug
NTP for time synchronization
512 Kb/s Radio
Physical DCN Ports:

1x Ethernet RJ45 10/100 BaseT for local access
with DHCP (Out of Band)
1x Ethernet RJ45 10/100/1000 BaseT SW
configurable (Out of Band)
4 MAX x Ethernet RJ45 10/100/1000 BaseT (In
Band)
2 MAX x Ethernet SFP (In Band)
nx Radio 512 Kb/s
512Kb/s Radio
9500 MPR-MSS1c
10/100 Base T
10/100 Base T
10/100 Base T
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 used
Eth port
! MSS 8/4/1 has routing capability. From DCN/IP point of view it is a
router.
! Each port can activate OSPF or static routing ; for each MSS 8/4/1 up
to 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.
5 | TMN Networking | April 2012
9500MPR (MSS 1c) Capability

IP parameters
FTP for download/backup/restore/provisioning
SNTP for time synchronization
9500 MPR
512 Kb/s Radio
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 ports
1x IP address for the radio channel
that is the local IP address of the NE.
512Kb/s Radio
9500 MPR-MSS1c
10/100 Base T
10/100 Base T
10/100 Base T
10/100 Base T
10/100 /1000Base T
10/100 /1000 Base T
! 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.2
release.
9500MPR (MPR-e) Capability

IP parameters
FTP for download/backup/restore/
SNTP for time synchronization
9500 MPR
512 Kb/s Radio
512Kb/s Radio
Physical DCN Ports:

1x Ethernet El./Opt. 1000 (In Band)
1 x Radio 512 Kb/s
9500 MPR-e
IP addressing
1x IP address and relevant net-mask for the
Eth DCN port
1x IP address for the radio channel
that is the local IP address of the NE.
10/100 Base T
10/100 Base T
10/100 Base T
! 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.
9500 MPR
DCN Interconnection using Out of Band (OoB)
512Kb/s Radio
512Kb/s Radio
9500 MPR-e
9500 MPR
512Kb/s Radio
10/100 BT
10/100 Base T
9500 MPR
512Kb/s Radio
10/100 BT
9500 MPR-MSS1c
9500 MPR
10/100 Base T
! Multiple MPR nodes can be chained without need for external switch
9500 MPR
DCN Interconnection using In Band (InB)
512Kb/s Radio
512Kb/s Radio
9500 MPR-e
9500 MPR
10/100 BT
10/100 Base T
512Kb/s Radio
9500 MPR
512Kb/s Radio
10/100 BT
9500MPR-MSS1c
In this case the Supervision

is tagged over a traffic
flow saving
- Ethernet ports
- IP addresses
9500 MPR
10/100 Base T
! Multiple MPR nodes can be chained without need for external

switch
TMN Networking
9500MXC
MXC Capability
IP parameters
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
9500 MXC
512 Kb/s Radio
512Kb/s Radio
10/100 Base T
10/100 Base T
IP addressing
1x IP address with its net-mask (at least /29)
for all the
- radio channels
- the used Eth port for supervision
! MXC has routing capability but it cant work in ABR condition

(Area 0 is not managed on the Eth. Interface) while the ASBR
configuration is allowed using the advance setting.
! Each port can activate OSPF or static routing ; up to 3 different
OSPF Areas can be provisioned excluding the backbone.
9500 MXC
DCN Interconnection
512Kb/s Radio
512Kb/s Radio
9500 MXC
512Kb/s Radio
10/100 BT
10/100 Base T
9500 MXC
10/100 BT
512Kb/s Radio
9500 MXC
10/100 Base T
! Multiple MPR nodes can be chained without need for external switch
TMN Networking
9400AWY
AWY Capability
IP parameters
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 for
the Eth port
9400 AWY
64Kb/s Radio
10/100 Base T
V11 64Kbs
G.703 64Kbs
! AWY has routing capability. From DCN/IP point of view it is a

router.
! Each port can activate OSPF or static routing.
! The area can be Secondary or Totally Stub.
9400 AWY
DCN Interconnection
64Kb/s Radio
9400 AWY
10/100 Base T
V11 64Kbs
64Kb/s Radio
9400 AWY
G703 64Kbs
64Kb/s Radio
9400 AWY
10/100 Base T
! Multiple AWY terminals can be chained without need for external switch
TMN Networking
9600LSY
LSY Capability
Q3 parameters
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
DCN In Band:
DCCR (D1-D3) 192 Kb/s on STM-1
9600 LSY
192 Kb/s Radio
STM-1
10/100 Base T
NSAP addressing:
1x NSAP for each NE
! 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 Manager
connection.
! In case of crossing IP network, OSI over IP is native available with
both OSPF or Static routing protocol.
9600 LSY
DCN Interconnection
9600 LSY (back to back)
192 Kb/s Radio
192 Kb/s Radio

STM-1
9600 LSY (GNE)

192 Kb/s Radio
192 Kb/s Radio
10/100 Base T
STM-1
9600 LSY (w/ ADM)

OSI over IP
OSI over IP
10/100 Base T
192 Kb/s Radio
192 Kb/s Radio

STM-1
IP cloud
10/100 Base T
NOC
ADM
1662 SMC
! Two LSY terminals can be chained without need for external switch
! For infield implementation pay attention to provide the right BW allocation for a secure
management
TMN Networking
9500MPR & 9400AWY co-located
9500 MPR & 9400 AWY collocated

DCN Interconnection
512Kb/s Radio
64Kb/s Radio
9500 MPR
9400 AWY
10/100 Base T
64Kb/s Radio
10/100 BT
V11 64Kbs
10/100 BT
G703 64Kbs
9500 MPR-MSS1c
512Kb/s Radio
9500 MPR
9400 AWY
10/100 Base T
512Kb/s Radio
9500 MPR
9400 AWY
64Kb/s Radio
10/100 Base T
10/100 Base T
! Multiple MPR & AWY can be chained without need for external switch
9500 MPR-e
9500MPR TMN Networking

TMN Interfaces
Technical specifications
Management
Interfaces
9400AWY
Ethernet
1 (IDU),
Native In Band
Management
---
4 (INU)
---
Serial V11 RS 422

64 Kb/s (co-dir.,
contro-dir. DCE)
Serial G703 64
Kb/s for 9400AWY
1
1
9500MXC
9500MPR
MSS 8/4/1
MSS 1c
7
3
(2 OoB & 6 InB) (2 OoB & 1 InB)
YES
1 Only with
AUX board
(INU/INUe)
---
OSPF, Static
VLSM
OSPF, Static
VLSM
YES
-----
BW on the
64 Kb/s
192 Kb/s min
embedded
512 Kb/s max
radio channel
Dedicated local RS 232 19.2 Kb/s RS 232 19.2 Kb/s
CT access
Ethernet
Protocol/
SNMP v.2c/
SNMP v.2c/
Routing
IP addressing
schema
YES
MPR-e
1
(InB)
192 Kb/s min

512 Kb/s max
Ethernet
SNMP v.2c/
OSPF, Static
Variable Lenght Subnet Mask
9500MPR product (IDU: MSS-8/MSS-4)
LCT
(initial setup)
NMS Ethernet RJ45

Ethernet RJ45 Traffic Port 4:
configurable as NMS Ethernet channel
local interface
(always enabled)
used to chain collocated equipment

or as GNE interface
CSM module
9500MPR product (IDU: MSS-1)
LCT
(initial setup)
NMS Ethernet RJ45

Ethernet RJ45 Traffic Port 4:
configurable as NMS Ethernet channel
local interface
(always enabled)
used to chain collocated equipment

or as GNE interface
9500MPR product: (IDU: MSS-1c)
2 OoB Ethernet RJ45 Management

ports: Used to chain collocated
equipment or as GNE interface
NMS Ethernet RJ45
Pure local interface
(always enabled with fixed IP)
LCT
1 InB Ethernet RJ45 Management on a

selectable user ports (1..4): Used
to chain collocated equipment
(initial setup)
9500MXC product
9500 MXC, INU/INUe modules - indoor
4 ports Ethernet connector assembly for

NMS / RJ45 for INU/INUe
Serial Interface v24 RJ 45 for Local craft
terminal connection
LCT
(initial setup)
NCC Node Controller Card (NMS ports)

MPR - AWY common management (LAN connection)
9400 AWY
1 ports Ethernet connector assembly for NMS / RJ45

NMS ETHERNET cable RJ45/RJ45
NMS Serial port v.24/RS232

LCT
(initial setup)
9500 MPR CSM
NMS Ethernet RJ45 local interface
MPR - MXC common management (LAN connection)
9500 MPR

NMS Ethernet RJ45 local interface

LCT
(initial setup)
Serial Interface v24 RJ 45

local interface
9500 MXC, NCC card (NMS function)

- config. also valid in case of IDU
MXC - AWY common management (LAN connection)
9400 AWY

LCT
(initial setup)
NMS Serial port v.24/RS232

9500 MXC, NCC card (NMS function)

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

Interface to the Router
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 be
unique.
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. This
means the TMN subnets must be unique and not overlap.

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.

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.
MPR TMN Networking

TMN Related Services

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.

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.
.
MPR TMN Networking

TMN IP Addresses
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 Local
Address.
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 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 chain
co-located MPR to allow the TMN Interface to remain available for Local Craft
access.
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 VLAN
through the same physical interface that is used for revenue bearing Traffic. The primary difference
between these interfaces and the TMN Port #4 interface is that these have user configurable Ethernet
interface 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 to
communicate 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, but
no more than one. The Local Address and interface address must match if they are in the same subnet.
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 Networking
MPR (MSS 1C) addresses
The 9500MPR-1C can be configured with up to five addresses.
Local Address: 10.0.36.9
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 Local
Address.
b) The Craft and SNMP Managers must use this address when
monitoring or provisioning the NE. For the releases less than 3.3 NMS1
or NMS2 or TMN InB LAN IP must be used in case the equipment is not
reached via radio side.
c) SNMP Traps or Notifications are issued accordingly to the previous
assumption.
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 the
possible TMN Interfaces, but no more than one. The Local Address and interface address must
match if they are in the same subnet.
9500MPR Networking
3) 192.168.10.1/30
4) 172.22.64.86/30
5) 192.168.100.1/30
2) 192.168.30.1/30
2. The TMN Ethernet interface address (CT)

a) This interface is enabled by default and is intended for local Craft access
with fixed IP 192.168.30.1 Netmask: 255.255.255.252
b) It cant be connected to an external network; only the local management is
allowed.
9500MPR Networking
3) 192.168.10.1/30
4) 172.22.64.86/30
5) 192.168.100.1/30
2) 192.168.30.1/30
3. Optional NMS1 TMN Ethernet interface addresses

a) This interface is disabled by default, enabling it is service affecting while
attach/detach no.
co-located devices or to connect a PC to have a remote access to the far end
devices.
c) Static or OSPF routing can be enabled on it. In case of OSPF its IP
address cant be equal to the Local IP address.
d) In any case the associated subnet must be unique in the network and
visible 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.
9500MPR Networking
3) 192.168.10.1/30
4) 172.22.64.86/30
5) 192.168.100.1/30
2) 192.168.30.1/30
4. Optional NMS2 TMN Ethernet interface addresses

a) This interface is disabled by default, enabling it is service affecting while
attach/detach no.
co-located devices or to connect a PC to have a remote access to the far end
devices.
d) In any case the associated subnet must be unique in the network and
visible from the NOC or any CT that wants to perform a remote access.
9500MPR Networking
3) 192.168.10.1/30
4) 172.22.64.86/30
5) 192.168.100.1/30
2) 192.168.200.1/30
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 the
NOC or any CT that wants to perform a remote access.
interfaces
f) 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 to communicate directly with the TMN In-Band
MPR TMN Networking

The TMN Network
9500MPR Networking
The Basic TMN Network RF PPP Links
The RF PPP links come up as soon as the Radio channel is operational.

It doesnt matter what Local IP Address is assigned at either end,
when the Radio link is up, the routers are networked together and can exchange
packets with each other.
9500MPR Networking
The Basic TMN Network RF PPP Links
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
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
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 configuration
is allowed..
9500MPR Networking
Supported TMN Network Topologies
Networks can have multiple external gateways that allow alternate management
paths in the event of an outage.
To take 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.
MPR TMN Networking

MPR DCN example
DCN structure
Autonomous Systems
Autonomous System
Autonomous System
Routing protocol : OSPF
ASBR
ASBR
Autonomous System
Routing protocol : not OSPF (Static)
(ASBR) Autonomous System Boundary

Router
9500MPR
An Autonomous System is made at least of one single area. It must include less than 50
NE (Network Element) as for generic DCN rules.
(If needed, multiple Areas can be configured to reach up to 150 9500MPR for each
project)
(See Annexes for details about the IP routing for 9500MPR)
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 to
those used for the local access to the 9500MPR, must be visible from the NOC.
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
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
-Default Gateway: A special case of a static route in which the address is 0.0.0.0 and the
subnet mask is 0.0.0.0. It matches any destination address that is not matched by any
other static route. Default gateway routes are typically used in conjunction with static
routes to reduce data entry requirements.
-i. Towards the NOC a single default gateway route (0.0.0.0) is entered on each
terminal instead of static routes.
-ii. Away from the NOC static entries are required in the normal way - each terminal
must have an entry for all other terminals that are on its away side only.
9500MPR Capability
-iii. For static routing, the routing entries specify:

-1. Destination: The IP network address of the destination network, where for a
MSS 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 on
a common Ethernet LAN). Only the network portion of the IP address is
required.
-2. Subnet Mask: The subnet mask or netmask delineates the network portion of
the IP address.
-3.Interface: The interface must specify the port used to exit the terminal to
get 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 the
Ethernet 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
NM
NMS2
S1
9500 MPR-MSS1c
9500 MPR-e
9500 MPR-MSS1c
9500 MPR MSS 8/4/1
9500 MPR-MSS1c
10/100 BT
10/100 Base T
9500 MPR MSS 8/4/1

9500 MPR MSS 8/4/1
10/100 Base T
9500 MPR
DCN Interconnection : subnetting example
172.26.66.16/28
.19
.18
9500 MPR-MSS1c
9500 MPR-e
.21
NM
.22
NMS2
S1
.26 .29
.25
.30
9500 MPR-MSS1c
.17
.1
9500 MPR MSS 8
9500 MPR-MSS1c
10/100 BT
172.26.66.0/28
.6
.2
9500 MPR MSS 8
9500 MPR MSS 8

9500 MPR MSS 8
.5
.4
10/100 Base T
9500 MPR MSS 8
Mixed
OSPF Area x.y.z.w
and Static routing
9500 MPR
DCN Interconnection : mixed static routes and OSPF example
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
.19
DG radi
o
172.26.66.16/28
Local: x.x.x.19/32
9500 MPR-MSS1c
Static: default by Radio $
Local: x.x.x.22/32
.29
.26
NM
S1
NMS2
.22
DG radi
o
9500 MPR-e
.21
.18
.30
.25
9500 MPR-MSS1c
.17
9500 MPR-MSS1c
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
.1
9500 MPR MSS 8
Local: x.x.x.21/32
NMS: x.x.x.25/30
.1
.2
10/100 BT
172.26.66.0/28
Local: x.x.x.17/32
NMS: x.x.x.30/30
# Static: x.x.x.16/28 by x.x.x.29
.6
.2
9500 MPR MSS 8
9500 MPR MSS 8
rd
wa
To
.4
9500 MPR MSS 8
.5
10/100 Base T
Mixed
OSPF Area x.y.z.w
C
NO
9500 MPR MSS 8
and Static routing

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

Note: PC address = 192.168.30.2 GW 192.168.30.1
Local: x.x.x.18/32
NMS2: x.x.x.29/30
NMS1: x.x.x.26/30
.19
DG radi
o
172.26.66.16/28
Local: x.x.x.19/32
9500 MPR-MSS1c
CT1(CT):192.168.30.1/30
Local: x.x.x.22/32
.29
.26
S1
NM
.30
.25
9500 MPR-MSS1c
.17
9500 MPR-MSS1c
Local: x.x.x.1/32
CT: 10.0.1.5/30
.1
9500 MPR MSS 8
.1
3
.2
10/100 BT
172.26.66.0/28
Local: x.x.x.21/32
NMS: x.x.x.25/30
CT2(CT):192.168.30.1/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
NMS2
.22
DG radi
o
9500 MPR-e
.21
.18
.6
.2
9500 MPR MSS 8
9500 MPR MSS 8
rd
wa
To
.4
9500 MPR MSS 8
.5
10/100 Base T
Mixed
OSPF Area x.y.z.w
C
NO
9500 MPR MSS 8
and Static routing

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

Note: PC address = 192.168.10x.2 GW 192.168.10x.1
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
.19
DG radi
o
172.26.66.16/28
Local: x.x.x.19/32
9500 MPR-MSS1c
CT1(NMS):192.168.101.1/30
Local: x.x.x.22/32
.29
.26
S1
.30
.25
9500 MPR-MSS1c
.17
9500 MPR-MSS1c
Local: x.x.x.21/32
NMS1: x.x.x.25/30
CT2(NMS2): 192.168.102.1/30
.1
Local: x.x.x.1/32
CT: 10.0.1.5/30
#Static: 192.168.103.0/30 by Radio
9500 MPR MSS 8
.1
3
.2
10/100 BT
172.26.66.0/28
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
NMS2
.22
DG radi
o
9500 MPR-e
.21
.18
NM
.6
.2
9500 MPR MSS 8
9500 MPR MSS 8
rd
wa
To
.4
9500 MPR MSS 8
.5
10/100 Base T
Mixed
OSPF Area x.y.z.w
C
NO
9500 MPR MSS 8
and Static routing

NOC
9500 MPR
DCN Interconnection : OSPF routes example
172.26.66.16/28
.22
.18
9500 MPR-MSS1c
9500 MPR-e
.19
NM
.21
NMS2
S1
.26 .29
.25
.30
9500 MPR-MSS1c
.1
.17
9500 MPR MSS 8
9500 MPR-MSS1c
10/100 BT
.1
172.26.66.0/28
.6
.2
.2
9500 MPR MSS 8
9500 MPR MSS 8
.5
.4
10/100 Base T
C
NO
9500 MPR MSS 8
ALL OSPF: Area x.y.z.w
rd
wa
To
9500 MPR MSS 8
NOC
9500 MPR up to 3.2 release included

DCN Interconnection : declared IP in the NOC (5620SAM or 1350OMS) in red
172.26.66.16/28
.19
.18
It takes into account from which port
the traps are sourced.
9500 MPR-MSS1c
9500 MPR-e
.21
NM
.22
NMS2
S1
.26 .29
.25
.30
9500 MPR-MSS1c
.1
.17
9500 MPR MSS 8
9500 MPR-MSS1c
10/100 BT
.1
172.26.66.0/28
.6
.2
.2
9500 MPR MSS 8
9500 MPR MSS 8
.5
.4
10/100 Base T
C
NO
9500 MPR MSS 8
Also valid in case of the mixed routing
rd
wa
To
9500 MPR MSS 8
NOC
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
172.26.66.16/28
.19
.18
It takes into account from which port
the traps are sourced.
9500 MPR-MSS1c
9500 MPR-e
.21
NM
.22
NMS2
S1
.26 .29
.25
.30
9500 MPR-MSS1c
.1
.17
9500 MPR MSS 8
9500 MPR-MSS1c
10/100 BT
.1
172.26.66.0/28
.6
.2
.2
9500 MPR MSS 8
9500 MPR MSS 8
.5
.4
10/100 Base T
C
NO
9500 MPR MSS 8
Also valid in case of the mixed routing
rd
wa
To
9500 MPR MSS 8
NOC
9500 MPR Warning about to set up protection schemas in respect of the TMN
supervision (OSPF case): restriction removed since MSS-1C 4.1
172.26.66.16/28
.19
Redundancy using a TMN chain must be

avoided as soon as MSS-1C is involved
.18
9500 MPR-MSS1c
NMS2
see .33
9500 MPR-e
.21
NM
.22
NMS2
S1
.26 .29
.25
.30
NMS2 NMS1
9500 MPR-MSS1c
.34
.1
.17
9500 MPR MSS 8
9500 MPR-MSS1c
.34
.1
10/100 BT
.33
NMS1
172.26.66.0/28
.6
.2
.2
9500 MPR MSS 8
9500 MPR MSS 8
.5
.4
10/100 Base T
rd
wa
To
9500 MPR MSS 8
C
NO
9500 MPR MSS 8
NOC
ANNEX 1
SNMP management
OSI layer model
IP addressing
Routing overview
OSPF routing
SNMP management
70 | Presentation Title | Month 2009
SNMP management
Introduction
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
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
0
0
1
1
ISO
2
1
3
2
Identified Organization
DoD
1
1
Internet
Management
1
system
at
interface
icmp
ip
8 10 11
udp transmission
tcp
egp
IBM
Cisco
snmp
enterprise
637
ltt
54
9400
Optics MIB
2117
Alcatel Telspace
tsdim
MIB-2 RFC1213
Private
MIB-1 RFC1156
MW product
Melodie
SNMP management
SNMP commands
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.
Manager
SNMP SET request

SNMP SET response
SNMP GET request
SNMP GET response
SNMP
Agent
SNMP Trap
MIB
OSI layer model
OSI layer model
Layer
Unit
Function
Example
Application
Data
Network process to
application
SNMP, FTP, HTTP,

Telnet
Presentation
Data
Data representation and

encryption
Session
Data
Interhost communication
Transport
Segment
End-to-end connections
and reliability
TCP, UDP
Network
Packet
Path determination and

logical addressing
IP, OSPF, RIP
Data Link
Frame
Physical addressing
Ethernet, PPP
Physical
Bit
Media, signal and binary

transmission
IP addressing
IP addressing
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 doteddecimal 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
An IP address belongs to a sub network (subnet). A subnet is described by an IP
address and a subnet mask.
IP address
Subnet mask
Subnet
address
Broadcast
address
Subnet mask
172
26
64
132
10101100
00011010
01000000
10000100
255
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
In a subnet the first address is dedicated for the subnet address and the last is
dedicated for the broadcast address
IP addressing
Subnet
A subnet is often expressed in the standardized CIDR (Classless Inter-Domain
Routing) notation consisting of the subnet address and the mask length.
Subnet
address
Subnet mask
172
26
64
128
10101100
00011010
01000000
10000000
255
255
255
248
11111111
11111111
11111111
11111000
29 bits
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.
Routing overview
Routing overview
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
R4
R2
N3
N2
R6
R3
N8
N5
N1
Router R1
routing table
Network Next hop
N8
R3
R1
N4
R5
N7
N6
If router R3 is down the route from router R1 to network N8 is lost.
Routing overview
Dynamic routing
R4
R2
N3
N2
R6
R3
N8
N5
N1
Router R1
routing table
R1
Network Next hop
R5
N8
R3
N4
R5
N7
N6
If router R3 is down the route from router R1 to network N8 is available.
Routing overview
Dynamic routing
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.
OSPF Routing
OSPF Routing
Link state routing
OSPF is a protocol based on Link State.

R4
R2
N3
N2
R6
R3
R1
Port
Port
Port
Port
Port
Hello
N1
a : N1
b : N4
c : N6
d : nothing
e : nothing
R1
Hello
N8
N5
b
c
Hello
N4 Hello
R5
N7
N6
Hello
By sending Hello packet routers discover their neighbors.
OSPF Routing
LSA
LSA : Link state advertisement.

R4
R1
Port
Port
Port
Port
Port
R2
a : N1
b : N4
c : N6
d : nothing
e : nothing
R6
R3
N8
N5
N1
LSA
R1
Port
Port
Port
Port
Port
N3
N2
a : N1
b : N4
c : N6
d : nothing
e : nothing
R1
N4
R5
c
N7
N6
Routers broadcast LSA to advertise about their link state.
OSPF Routing
Database
Database
R1
Port
Port
Port
Port
Port
R2
Port
Port
Port
Port
Port
Database is built with all LSA.
a : N1
b : N4
c : N6
d : nothing
e : nothing
a : nothing
b : N2
c : N1
d : nothing
e : nothing
R4
R2
N2
Database
a
e
R6
R3
N1
N3
Database
Database
Database
R1
N4
Database
d
R5
c
N6
Database
Each router have got the same database
N8
N5
N7
OSPF Routing
Routing table
Database
R1
Port
Port
Port
Port
Port
R2
Port
Port
Port
Port
Port
a : N1
b : N4
c : N6
d : nothing
e : nothing
a : nothing
b : N2
c : N1
d : nothing
e : nothing
From Database each router computes its routing table

using Short Path First algorithm.
Routing table
R4
Routing table
R2
N2
Database
R1 routing table
Network Next hop Port
N1
direct
a
N2
R2
a
N3
R2
a
N4
direct
b
N5
R3
b
N6
direct
c
N7
R5
c
N8
R3
b
N1
Database
Routing table
R3
Database
d
N5
Routing table
R6
N8
Database
Database
Routing table N4
R1 b
a
e
N3
Routing table N7
R5
N6
Database
Each router have got its own routing table
OSPF Routing
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
Autonomous System
Area
0.0.0.4
Area
0.0.0.2
Area
0.0.0.1
Backbone : Area 0.0.0.0
Area Border Router
Virtual Link
Area
0.0.0.3
OSPF routing
Area types
" 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 a
virtual 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 the
backbone are not announced)
" Not so stubby areas (RFC 1587)
Identical to stub areas but can announce external routes
OSPF routing
ASBR
Autonomous System
Autonomous System
Autonomous System
Autonomous System
Routing protocol : not OSPF (Static, IS-IS, RIP, BGP, )
Autonomous System Boundary Router

SCOPE
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 be
analyzed 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
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 TMN
Network.
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.

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 Static
routing 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:

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
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 of
this 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:
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 the
projects, it means can be reused in the other projects of the network.

PARAMETERS
Parameters to take into considerations are:
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 addresses
Number 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
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:
Network size
Max project size
Number of sites
Sites with 2 MPR
Sites with 3 MPR
Sites with 4 MPR
1880
60
1600
200
40
0
MPR
MPR
120
12,5%
2,5%
0,0%
projects
of total sites
of total sites
of total sites
and the result are herebelow reporterd both in tabular and graphical formats.

RESULTS
The used reference criteria is the ratio in % between the used IP addresses and the
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.
unique
number of MPR reserved IP
addresses
Example 3
Example 2
Example 1
1880
1880
1880
1880
3000
8640
reused IP
addresses
282
240
0
used IP
addresses vs
n.MPR ratio
(%)
115,0
172,3
459,6
ANNEX 2
9500LUX50 IOT
9500LUX50 IOT
Technical specifications
Management
Interfaces
9400LUX50
9400AWY
9500MPR
Ethernet
---
Native In Band
Management
---
---
Serial V11 RS 422

64 Kb/s (co-dir.,
contro-dir. DCE)
Serial G703 64
Kb/s for 9400AWY
---
----
---
MSS 8/4/1
MSS 1c
7
3
(2 OoB & 6 InB) (2 OoB & 1 InB)
YES
BW on the
64 Kb/s
64 Kb/s
embedded
radio channel
Dedicated local RS 232 19.2 Kb/s RS 232 19.2 Kb/s
CT access
YES
MPR-e
1
(InB)
YES
192 Kb/s min

512 Kb/s max
-
Protocol/
SNMP v.2c/
SNMP v.2c/
Ethernet
SNMP v.2c/
Routing
IP addressing
schema
OSPF, Static
VLSM
OSPF, Static
VLSM
OSPF, Static
Variable Lenght Subnet Mask
LUX50 Capability
IP parameters
FTP for download, backup, restore
Telnet for debug
9400 LUX50
64Kb/s Radio
Physical DCN Ports:

2x V.11 64Kbs
1x Radio 64Kb/s
V11 64Kbs
IP addressing
1x IP address for all the serial ports (/32);
that is the IP address of the NE
V11 64Kbs
! LUX50 has routing capability. From DCN/IP point of view it is a

simple router
! Each port can activate OSPF or static routing.
! In case of OSPF each address must belong to an OSPF area
LUX50
DCN Interconnection
64Kb/s Radio
9400 LUX50
V11 64Kbs
V11 64Kbs
64Kb/s Radio
9400 LUX50
V11 64Kbs
64Kb/s Radio
9400 LUX50
V11 64Kbs
! Multiple 9400LUX50 terminals can be chained without need for external switch
LUX50
DCN Interconnection
Example of mixed network topology

Unique
LAN subnets
NMS center
DCN
9500MPR subnet
9400AWY
9400LUX50
WAN subnet
9400AWY
WAN subnet
LUX50 & AWY

DCN Interconnection
9400 AWY
NMS_V11 signal 64Kbps

Synchronous RS-422
1320CT
(initial setup)
9400 UX LUX 50
9500 MPR & 9400 AWY & 9400LUX50 collocated

DCN Interconnection
512Kb/s Radio
64Kb/s Radio
9500 MPR
9400 AWY
V11 64Kbs
64Kb/s Radio
10/100 BT
10/100 Base T
10/100 BT
V11 64Kbs
9500 MPR-MSS1c
512Kb/s Radio
9500 MPR
9400 AWY
10/100 Base T
512Kb/s Radio
9500 MPR
9400LUX50
64Kb/s Radio
10/100 Base T
10/100 Base T
! Multiple MPR & AWY & LUX50 can be chained without need for external
switch
9500 MPR-e
www.alcatel-lucent.com
www.alcatel-lucent.com

TMN Networking PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TMN Networking PDF

Hochgeladen von

Copyright:

Verfügbare Formate

AT THE SPEED OF IDEAS

Modifications in respect to the previous version (April 2012)

4 | Presentation Title | Month Year

9500MPR (MSS 8/4/1) Capability

SNMPv2c for supervision

512 Kb/s Radio

Physical DCN Ports:

9500MPR (MSS 1c) Capability

Physical DCN Ports:

10/100 /1000 Base T

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

6 | TMN Networking | April 2012

9500MPR (MPR-e) Capability

Physical DCN Ports:

! MPR-e has routing capability. From DCN/IP point of view it is a router.

7 | TMN Networking | April 2012

In this case the Supervision

! Multiple MPR nodes can be chained without need for external

10 | Presentation Title | Month Year

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

13 | Presentation Title | Month Year

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

16 | Presentation Title | Month Year

! LSY has routing capability based on IS-IS.

192 Kb/s Radio

9600 LSY (GNE)

192 Kb/s Radio

9600 LSY (w/ ADM)

192 Kb/s Radio

192 Kb/s Radio

19 | Presentation Title | Month Year

9500 MPR & 9400 AWY collocated

9500MPR TMN Networking

21 | Presentation Title | Month Year

Serial V11 RS 422

22 | TMN Networking | April 2012

192 Kb/s min

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

NMS Ethernet RJ45

used to chain collocated equipment

23 | TMN Networking | April 2012

9500MPR product (IDU: MSS-1)

NMS Ethernet RJ45

used to chain collocated equipment

24 | TMN Networking | April 2012

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

2 OoB Ethernet RJ45 Management

1 InB Ethernet RJ45 Management on a

25 | TMN Networking | April 2012

9500 MXC, INU/INUe modules - indoor

4 ports Ethernet connector assembly for

NCC Node Controller Card (NMS ports)

MPR - AWY common management (LAN connection)

1 ports Ethernet connector assembly for NMS / RJ45

NMS Serial port v.24/RS232

9500 MPR CSM

NMS Ethernet RJ45 local interface

27 | TMN Networking | April 2012

MPR - MXC common management (LAN connection)

1 ports Ethernet connector assembly for NMS / RJ45

NMS Ethernet RJ45 local interface

Serial Interface v24 RJ 45

9500 MXC, NCC card (NMS function)