Documente Academic
Documente Profesional
Documente Cultură
TMN Networking
April 2012
Agenda
11.ANNEX 1 12.ANNEX 2
1. SNMP management 1. 9400LUX50 IOT
2. OSI layer model
3. IP addressing
4. Routing overview
5. OSPF routing
6. Planning and addressing a network
Notes
Alcatel-Lucent – Confidential
4 | Presentation Title | Month Year Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR (MSS 8 – MSS 4) Capability
IP parameters
Management Protocol:
SNMPv2c for supervision 9500 MPR
FTP for download/backup/restore
Telnet for debug 512 Kb/s Radio 512Kb/s Radio
NTP for time synchronization
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 MSS8/4 has routing capability. From DCN/IP point of view it is a
router.
Each port can activate OSPF or static routing ; for each MSS8/4 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.
Alcatel-Lucent – Confidential
5 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR (MSS 1c) Capability
IP parameters
Management Protocol:
SNMPv2c for supervision 9500 MPR
FTP for download/backup/restore/provisioning
SNTP for time synchronization 512 Kb/s Radio 512Kb/s Radio
10/100 Base T
IP addressing 10/100 Base T
10/100 /1000Base T
1x IP address and relevant net-mask for each 10/100 /1000 Base T
Eth DCN ports
1x IP address for the radio channel
that is the local IP address of the NE.
Alcatel-Lucent – Confidential
6 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR (MPR-e) Capability
IP parameters
Management Protocol:
SNMPv2c for supervision 9500 MPR
FTP for download/backup/restore/
SNTP for time synchronization 512 Kb/s Radio 512Kb/s Radio
Alcatel-Lucent – Confidential
7 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500 MPR
DCN Interconnection using Out of Band (OoB)
9500 MPR-e
9500 MPR
10/100 BT
10/100 Base T
512Kb/s Radio
9500 MPR
9500 MPR-MSS1c
10/100 BT
512Kb/s Radio
9500 MPR
10/100 Base T
Multiple MPR nodes can be chained without need for external switch
Alcatel-Lucent – Confidential
8 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500 MPR
DCN Interconnection using In Band (InB)
9500 MPR-e
9500 MPR
10/100 BT
10/100 Base T
9500MPR-MSS1c
10/100 BT
512Kb/s Radio
9500 MPR
10/100 Base T
Alcatel-Lucent – Confidential
10 | Presentation Title | Month Year Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
MXC Capability
IP parameters
Management Protocol:
SNMPv2c for supervision 9500 MXC
FTP for download/backup/restore
Telnet for debug 512 Kb/s Radio
NTP for time synchronization 512Kb/s Radio
IP addressing
1x IP address with its net-mask (at least /29)
for all the
- radio channels
- the used Eth port for supervision
Alcatel-Lucent – Confidential
11 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500 MXC
DCN Interconnection
9500 MXC
10/100 BT
10/100 Base T
512Kb/s Radio
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
Alcatel-Lucent – Confidential
12 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
TMN Networking
9400AWY
Alcatel-Lucent – Confidential
13 | Presentation Title | Month Year Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
AWY Capability
IP parameters
Management Protocol:
SNMPv2c for supervision 9400 AWY
FTP for download, backup, restore
Telnet for debug
NTP for time synchronization 64Kb/s Radio
64Kb/s Radio
9400 AWY
10/100 Base T
V11 64Kbs
64Kb/s Radio
9400 AWY
9400 AWY
10/100 Base T
Multiple AWY terminals can be chained without need for external switch
Alcatel-Lucent – Confidential
15 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
TMN Networking
9600LSY
Alcatel-Lucent – Confidential
16 | Presentation Title | Month Year Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
LSY Capability
Q3 parameters
Management Protocol:
OSI Q3 for supervision 9600 LSY
FTP for download
ANTP for time synchronization 192 Kb/s Radio
NSAP addressing:
1x NSAP for each NE
STM-1
STM-1
OSI over IP
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
Alcatel-Lucent – Confidential
18 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
TMN Networking
9500MPR & 9400AWY co-located
Alcatel-Lucent – Confidential
19 | Presentation Title | Month Year Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500 MPR & 9400 AWY collocated
DCN Interconnection
10/100 BT
10/100 Base T 10/100 Base T
V11 64Kbs
9500 MPR-MSS1c
10/100 BT
64Kb/s Radio G703 64Kbs 512Kb/s Radio
10/100 Base T
10/100 Base T
Multiple MPR & AWY can be chained without need for external switch
Alcatel-Lucent – Confidential
20 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR TMN Networking
TMN Interfaces
Alcatel-Lucent – Confidential
21 | Presentation Title | Month Year Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Technical specifications
Alcatel-Lucent – Confidential
22 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR product (IDU: MSS-8/MSS-4)
LCT
(initial setup)
NMS Ethernet RJ45
local interface
Ethernet RJ45 Traffic Port 4:
(always enabled)
configurable as NMS Ethernet channel
or as GNE interface
CSM module
Alcatel-Lucent – Confidential
23 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR product: (IDU: MSS-1c)
(initial setup)
Alcatel-Lucent – Confidential
24 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MXC product
LCT
NCC – Node Controller Card (NMS ports)
(initial setup)
Alcatel-Lucent – Confidential
25 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
MPR - AWY common management (LAN connection)
9400 AWY
LCT
(initial setup)
Alcatel-Lucent – Confidential
26 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
MPR - MXC common management (LAN connection)
9500 MPR
LCT
(initial setup)
9400 AWY
LCT
(initial setup)
Alcatel-Lucent – Confidential
28 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR TMN Networking
Physical Interfaces for MSS 8/4
Alcatel-Lucent – Confidential
30 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR TMN Networking
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.
Alcatel-Lucent – Confidential
31 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR TMN Networking
Focus on TMN In-Band: Multiple Port Configuration (Bridge mode)
Alcatel-Lucent – Confidential
32 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
MPR TMN Networking
TMN Related Services
Alcatel-Lucent – Confidential
33 | Presentation Title | Month Year Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR TMN Networking
Services – OSPF & Static
Alcatel-Lucent – Confidential
34 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR TMN Networking
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.
.
Alcatel-Lucent – Confidential
35 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
MPR TMN Networking
TMN IP Addresses
Alcatel-Lucent – Confidential
36 | Presentation Title | Month Year Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR Networking
MPR (MSS8/4) addresses
The 9500MPR can be configured with up to five addresses.
Alcatel-Lucent – Confidential
37 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR Networking
MSS8/4 addresses
Alcatel-Lucent – Confidential
38 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR Networking
MSS8/4 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.
Alcatel-Lucent – Confidential
39 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR Networking
MSS8/4 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.
Alcatel-Lucent – Confidential
40 | TMN Networking | January 2011 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR Networking
MPR (MSS 1C) addresses
The 9500MPR-1C can be configured with up to five addresses.
Local Address: 10.0.36.9
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 can’t be connected to an external network; only the local management is
allowed.
Alcatel-Lucent – Confidential
42 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR Networking
MPR (MSS 1C) addresses
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.
b) Intended for use when connecting to external networks or to chain
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 can’t 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.
Alcatel-Lucent – Confidential
43 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR Networking
MPR (MSS 1C) addresses
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.
b) Intended for use when connecting to external networks or to chain
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 can’t 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.
Alcatel-Lucent – Confidential
44 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR Networking
MPR (MSS 1C) addresses
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.
c) Static or OSPF routing can be enabled on it. In case of OSPF its IP
address can’t 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.
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
interfaces
Alcatel-Lucent – Confidential
45 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
MPR TMN Networking
The TMN Network
Alcatel-Lucent – Confidential
46 | Presentation Title | Month Year Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR Networking
The Basic TMN Network – RF PPP Links
Alcatel-Lucent – Confidential
47 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
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.
Alcatel-Lucent – Confidential
48 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
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..
Alcatel-Lucent – Confidential
49 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
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..
Alcatel-Lucent – Confidential
50 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
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.
Alcatel-Lucent – Confidential
51 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
MPR TMN Networking
MPR DCN example
Alcatel-Lucent – Confidential
52 | Presentation Title | Month Year Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
DCN structure
Autonomous Systems
ASBR ASBR
Autonomous System
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)
Alcatel-Lucent – Confidential
53 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
MSS8/4 IP addressing
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.
Alcatel-Lucent – Confidential
54 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
MSS1C IP addressing
Alcatel-Lucent – Confidential
55 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR Capability
Special notes in case of mixed OSPF and Static routing networks
Alcatel-Lucent – Confidential
56 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR Capability
Special notes in case of mixed OSPF and Static routing networks
-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.
Alcatel-Lucent – Confidential
57 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500MPR Capability
Special notes in case of mixed OSPF and Static routing networks
Alcatel-Lucent – Confidential
58 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500 MPR
DCN Interconnection : topology example
9500 MPR-MSS1c
S1
NMS2
NM
9500 MPR-e
10/100 BT
10/100 Base T
10/100 Base T
Alcatel-Lucent – Confidential
59 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500 MPR
DCN Interconnection : subnetting example
172.26.66.16/28
.19 .18
9500 MPR-MSS1c
.26 .29
S1
NMS2
NM
.22
9500 MPR-e .21 .25 .30 .17 .1
9500 MPR – MSS8
9500 MPR-MSS1c 9500 MPR-MSS1c
10/100 BT
172.26.66.0/28
.2
.6
9500 MPR – MSS8
9500 MPR – MSS8
.5 .4
10/100 Base T
Alcatel-Lucent – Confidential
60 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500 MPR
DCN Interconnection : mixed static routes and OSPF example
Local: x.x.x.18/32
NMS2: x.x.x.29/30
172.26.66.16/28 .19 NMS1: x.x.x.26/30
DG radi Static: default by x.x.x.30Æ
Local: x.x.x.19/32 o ÅStatic: x.x.x.20/30 by x.x.x.25
.18
9500 MPR-MSS1c
Static: default by Radio Æ
.26 .29
.22 Local: x.x.x.17/32
Local: x.x.x.1/32
NMS2
NMS: x.x.x.30/30
DG radi
S1
P#3 (InB) =Local /30
o
NM
Static: default by Radio Æ
CT: 10.0.1.5/30
Å Static: x.x.x.16/28 by x.x.x.29
Local: x.x.x.22/32
9500 MPR-e
.21 .25 .30
Å Static: x.x.x.16/28 by Radio
10/100 BT
Static: default by x.x.x.26Æ
172.26.66.0/28
.2 .2
.6 9500 MPR – MSS8
To
9500 MPR – MSS8
.4 10/100 Base T
wa
.5
rd
9500 MPR – MSS8
NO
C
Mixed OSPF Area x.y.z.w and Static routing NOC
Alcatel-Lucent – Confidential
61 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
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
172.26.66.16/28 .19 NMS1: x.x.x.26/30
DG radi Static: default by x.x.x.30Æ
Local: x.x.x.19/32 o ÅStatic: x.x.x.20/30 by x.x.x.25
.18
9500 MPR-MSS1c
Static: default by Radio Æ
CT1(CT):192.168.30.1/30 1
.26 .29
.22 Local: x.x.x.17/32
Local: x.x.x.1/32
NMS2
NMS: x.x.x.30/30
DG radi
S1
P#3 (InB) =Local /30
o
NM
Static: default by Radio Æ
CT: 10.0.1.5/30
Static: x.x.x.16/28 by x.x.x.29
Local: x.x.x.22/32
9500 MPR-e
.21 .25 .30 CT3(CT):192.168.30.1/30
Å Static: x.x.x.16/28 by Radio
10/100 BT
Static: default by x.x.x.26Æ
172.26.66.0/28 CT2(CT):192.168.30.1/30
.2 .2
.6 9500 MPR – MSS8
To
9500 MPR – MSS8
.4 10/100 Base T
wa
.5
rd
9500 MPR – MSS8
NO
C
Mixed OSPF Area x.y.z.w and Static routing NOC
Alcatel-Lucent – Confidential
62 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
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
172.26.66.16/28 .19 NMS1: x.x.x.26/30
DG radi Static: default by x.x.x.30Æ
Local: x.x.x.19/32 o ÅStatic: x.x.x.20/30 by x.x.x.25
ÅStatic: 192.168.101.0/30 by Radio
.18
9500 MPR-MSS1c
Static: default by Radio Æ
CT1(NMS):192.168.101.1/30 1
.26 .29
.22 Local: x.x.x.17/32
Local: x.x.x.1/32
NMS2
NMS2: x.x.x.30/30
DG radi
S1
P#3 (InB) =Local /30
o
NM
Static: default by Radio Æ
CT: 10.0.1.5/30
Static: x.x.x.16/28 by x.x.x.29
Local: x.x.x.22/32
9500 MPR-e
.21 .25 .30 CT3(NMS1): 192.168.103.1/30
Å Static: x.x.x.16/28 by Radio
ÅStatic: 192.168.103.0/30 by Radio
Static: default by Radio Æ .17 .1
9500 MPR-MSS1c 9500 MPR-MSS1c 9500 MPR – MSS8
Local: x.x.x.21/32 2 .1
NMS1: x.x.x.25/30 3
10/100 BT
Static: default by x.x.x.26Æ
172.26.66.0/28 CT2(NMS2): 192.168.102.1/30
.2 .2
.6 9500 MPR – MSS8
To
9500 MPR – MSS8
.4 10/100 Base T
wa
.5
rd
9500 MPR – MSS8
NO
C
Mixed OSPF Area x.y.z.w and Static routing NOC
Alcatel-Lucent – Confidential
63 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500 MPR
DCN Interconnection : OSPF routes example
172.26.66.16/28
.22 .18
9500 MPR-MSS1c
.26 .29
S1
NMS2
NM
.21
9500 MPR-e .19 .25 .30 .17 .1
9500 MPR – MSS8
9500 MPR-MSS1c 9500 MPR-MSS1c
.1
10/100 BT
172.26.66.0/28
.2
.6 .2
9500 MPR – MSS8
9500 MPR – MSS8
To
.5
wa
10/100 Base T
rd
NO
9500 MPR – MSS8
C
ALL OSPF: Area x.y.z.w
NOC
Alcatel-Lucent – Confidential
64 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
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
9500 MPR-MSS1c
the traps are sourced.
.26 .29
S1
NMS2
NM
.22
9500 MPR-e .21 .25 .30 .17 .1
9500 MPR – MSS8
9500 MPR-MSS1c 9500 MPR-MSS1c
.1
10/100 BT
172.26.66.0/28
.2
.6 .2
9500 MPR – MSS8
9500 MPR – MSS8
To
.5
wa
10/100 Base T
rd
NO
9500 MPR – MSS8
C
Also valid in case of the mixed routing NOC
Alcatel-Lucent – Confidential
65 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
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
9500 MPR-MSS1c
the traps are sourced.
.26 .29
S1
NMS2
NM
.22
9500 MPR-e .21 .25 .30 .17 .1
9500 MPR – MSS8
9500 MPR-MSS1c 9500 MPR-MSS1c
.1
10/100 BT
172.26.66.0/28
.2
.6 .2
9500 MPR – MSS8
9500 MPR – MSS8
To
.5
wa
10/100 Base T
rd
NO
9500 MPR – MSS8
C
Also valid in case of the mixed routing NOC
Alcatel-Lucent – Confidential
66 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500 MPR – Warning about to set up protection schemas in respect of the TMN
supervision (OSPF case)
172.26.66.16/28
.19 .18 Redundancy using a TMN chain must be
9500 MPR-MSS1c
avoided as soon as MSS-1C is involved
NMS2 NMS1
.26 .29 see .33 .34
S1
NMS2
NM
.22
9500 MPR-e .21 .25 .30 .17 .1
NMS2 NMS1
9500 MPR – MSS8
.33 .34
9500 MPR-MSS1c 9500 MPR-MSS1c
.1
10/100 BT
172.26.66.0/28
.2
.6 .2
9500 MPR – MSS8
9500 MPR – MSS8
To
.5
wa
10/100 Base T
rd
NO
9500 MPR – MSS8
C
NOC
Alcatel-Lucent – Confidential
67 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
ANNEX 1
SNMP management
OSI layer model
IP addressing
Routing overview
OSPF routing
Planning and addressing a network
Alcatel-Lucent – Confidential
68 | Presentation Title | Month Year Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
SNMP management
Alcatel-Lucent – Confidential
69 | Presentation Title | Month 2009 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
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”.
y The managing system to retrieve information from the agent (SNMP GET operation)
y The managing system to send configuration to the agent (SNMP SET operation)
y The agent to warn the managing system (SNMP trap operation)
Available variables to be exchanged are defined in a MIB.
Alcatel-Lucent – Confidential
70 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
SNMP management
MIB
Example:
Alcatel-Lucent – Confidential
71 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
SNMP management
MIB
ISO
0 1 2
Identified Organization
0 1 2 3
DoD
0 1 2 3 4 5 6
Internet
1
1 2 3 4 5 6
Management Private
1 1 enterprise
1 2 3 4 5 6 7 8 10 11 … 2 9 637 2117
SNMP Trap
Alcatel-Lucent – Confidential
73 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
OSI layer model
Alcatel-Lucent – Confidential
74 | Presentation Title | Month 2009 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
OSI layer model
Alcatel-Lucent – Confidential
75 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
IP addressing
Alcatel-Lucent – Confidential
76 | Presentation Title | Month 2009 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
IP addressing
IP address 172.26.64.132
172 . 26 . 64 . 132
10101100 . 00011010 . 01000000 . 10000100
1 byte = 8 bits
4 bytes = 32 bits
Alcatel-Lucent – Confidential
77 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
IP addressing
Subnet
In a subnet the first address is dedicated for the subnet address and the last is
dedicated for the broadcast address
Alcatel-Lucent – Confidential
78 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
IP addressing
Subnet
29 bits
Subnet 172.26.64.128 mask 255.255.255.248 is also expressed as
172.26.64.128/29.
Alcatel-Lucent – Confidential
80 | Presentation Title | Month 2009 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Routing overview
Static routing: All the routes are manually written by the network administrator.
Static routing can be used in our networks, just in case few elements are addressed. It’s
impossible to maintain manually the routing table of a network with several hundreds
or thousands of equipments.
Alcatel-Lucent – Confidential
81 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Routing overview
Static routing
R4
R2 N3
N2
R6
R3
N5 N8
N1
Router R1 N4
routing table R1 N7
R5
Network Next hop
… … N6
N8 R3
… …
If router R3 is down the route from router R1 to network N8 is lost.
Alcatel-Lucent – Confidential
82 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Routing overview
Dynamic routing
R4
R2 N3
N2
R6
R3
N5 N8
N1
Router R1 N4
routing table R1 N7
R5
Network Next hop
… … N6
N8 R5
R3
… …
If router R3 is down the route from router R1 to network N8 is available.
Alcatel-Lucent – Confidential
83 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Routing overview
Dynamic routing
Distance Vector routing (RIP, BGP, …) based on number of hops to reach the
destination.
y Convergence time to slow
y Bandwidth used by protocol to important
y Dedicated for little network
Link state routing (OSPF, IS-IS, …) based on link state between routers.
y Convergence time faster
y Can support huge network
We use OSPF (Open Short Path First) routing protocol in our network.
Alcatel-Lucent – Confidential
84 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
OSPF Routing
Alcatel-Lucent – Confidential
85 | Presentation Title | Month 2009 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
OSPF Routing
Link state routing
R4
R2 N3
N2
R6
R3
N5 N8
N1 Hello
R1
N4 Hello
Port a : N1
Port b : N4
Port c : N6 a
R1 b N7
Port d : nothing R5
Port e : nothing e
c
d
N6
Hello Hello
Hello
Alcatel-Lucent – Confidential
86 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
OSPF Routing
LSA
R4
R1 N3
Port a : N1 R2 N2
Port b : N4
Port c : N6 R6
Port d : nothing R3
Port e : nothing N5 N8
N1
LSA
R1 N4
N7
b
a R1
Port a : N1
Port b : N4 R5
Port c : N6 e
Port d : nothing
c N6
d
Port e : nothing
Alcatel-Lucent – Confidential
87 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
OSPF Routing
Database
Database
R1
Port a : N1 Database is built with all LSA.
Port b : N4
Port c : N6
Port d : nothing R4
Port e : nothing
R2 R2 N3
N2 Database
Port a : nothing
Port b : N2 R6
Port c : N1 R3
Port d : nothing Database N5 N8
Port e : nothing
N1 Database
… Database
N4
N7
b
a R1
R5
e
Database
c N6
d
Database
Alcatel-Lucent – Confidential
88 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
OSPF Routing
Routing table
Database From Database each router computes its routing table
R1 using “Short Path First” algorithm.
Port a : N1
Port b : N4
Port c : N6 Routing table
Port d : nothing R4
Port e : nothing
Routing table N3
R2 R2 N2 Database
Port a : nothing Routing table
Port b : N2 Routing table R6
Port c : N1 R3
Port d : nothing Database N5 N8
Port e : nothing
N1 Database
… Database
R1 routing table
Routing table N4
Network Next hop Port a R1 b Routing table N7
N1 direct
… …
a
R5
N2 R2 a e
N3 R2 a Database
c N6
d
N4 direct b Database
N5 R3
… …
b
N6 direct c
N7 R5 c Each router have got its own routing table
N8 R3 b
Alcatel-Lucent – Confidential
89 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
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).
Alcatel-Lucent – Confidential
90 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
OSPF routing
Area Type
Autonomous System
Area
Routing protocol : OSPF 0.0.0.4
Area
Area 0.0.0.2
0.0.0.1 Area
0.0.0.3
Alcatel-Lucent – Confidential
91 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
OSPF routing
Area types
Alcatel-Lucent – Confidential
92 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
OSPF routing
ASBR
Autonomous System
Alcatel-Lucent – Confidential
93 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Planning and addressing a network
Alcatel-Lucent – Confidential
94 | Presentation Title | Month 2009 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Planning and addressing a network
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.
Alcatel-Lucent – Confidential
95 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Planning and addressing a network
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.
Alcatel-Lucent – Confidential
96 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Planning and addressing a network
ASSUMPTIONS 1/3
Alcatel-Lucent – Confidential
97 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Planning and addressing a network
ASSUMPTIONS 2/3
Alcatel-Lucent – Confidential
98 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Planning and addressing a network
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.
Alcatel-Lucent – Confidential
99 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Planning and addressing a network
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.
Alcatel-Lucent – Confidential
100 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Planning and addressing a network
PARAMETERS
Alcatel-Lucent – Confidential
101 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Planning and addressing a network
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.
and the result are herebelow reporterd both in tabular and graphical formats.
Alcatel-Lucent – Confidential
102 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Planning and addressing a network
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.
used IP
unique
reused IP addresses vs
number of MPR reserved IP
addresses n.MPR ratio
addresses
(%)
Example 3 1880 1880 282 115,0
Example 2 1880 3000 240 172,3
Example 1 1880 8640 0 459,6
Alcatel-Lucent – Confidential
103 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
ANNEX 2
9500LUX50 IOT
Alcatel-Lucent – Confidential
104 | Presentation Title | Month Year Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500LUX50 IOT
Alcatel-Lucent – Confidential
105 | Presentation Title | Month 2009 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
Technical specifications
Alcatel-Lucent – Confidential
106 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
LUX50 Capability
IP parameters
Management Protocol:
SNMPv2c for supervision 9400 LUX50
FTP for download, backup, restore
Telnet for debug
NTP for time synchronization 64Kb/s Radio
V11 64Kbs
IP addressing
1x IP address for all the serial ports (/32);
that is the IP address of the NE
Alcatel-Lucent – Confidential
107 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
LUX50
DCN Interconnection
64Kb/s Radio
9400 LUX50
V11 64Kbs
V11 64Kbs
64Kb/s Radio
9400 LUX50
9400 LUX50
V11 64Kbs
Multiple 9400LUX50 terminals can be chained without need for external switch
Alcatel-Lucent – Confidential
108 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
LUX50
DCN Interconnection
DCN
9500MPR subnet
……………
9400AWY
9400AWY
9400LUX50 WAN subnet
WAN subnet
Alcatel-Lucent – Confidential
109 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
LUX50 & AWY
DCN Interconnection
9400 AWY
1320CT
(initial setup) 9400 UX – LUX 50
Alcatel-Lucent – Confidential
110 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
9500 MPR & 9400 AWY & 9400LUX50 collocated
DCN Interconnection
10/100 BT
10/100 Base T 10/100 Base T
V11 64Kbs
9500 MPR-MSS1c
10/100 BT
64Kb/s Radio V11 64Kbs 512Kb/s Radio
10/100 Base T
10/100 Base T
Multiple MPR & AWY & LUX50 can be chained without need for external
switch
Alcatel-Lucent – Confidential
111 | TMN Networking | April 2012 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction
www.alcatel-lucent.com
www.alcatel-lucent.com
Alcatel-Lucent – Confidential
112 | Presentation Title | Month 2009 Solely for authorized persons having a need to know
Proprietary – Use pursuant to Company instruction