2

NMS Integration overview

All Rights Reserved Alcatel-Lucent 2007

NMS Integration overview

OSPF principle
OSPF : Open Shortest Path First
OSPF is a dynamic routing protocol, in which routing tables computation is
based on interfaces status
In order to minimize convergence computation time, OSPF DCN is split into
areas
NEs inside a specific ospf area exchange their database only with the ones belonging
to the same area, except for the area 0.
An area is set stubby or not stubby: a stubby area exchange only ospf routes/status

Gateways NEs (routers)

A NE that belongs to area 0 and to another area is an Area Border Router (ABR)
A NE that belongs to area x.x.x.x which has another interface in a domain in which
routing protocol is different from ospf is an Autonous System Boundary Router
(ASBR). In order to distribute other routing tables, an ospf area has to be set as "not
stub", there is no stub area in ASBR DCN.

All Rights Reserved Alcatel-Lucent 2007

NMS Integration overview

OSPF principle Application for AWY
OSPF area declarations
OPSF areas are declared as IP ADDRESSES : w.x.y.z, with stub flag (y/n)
In AWY, an identifier is used. Note : this identifier is internally used, it has
nothing to do with ospf protocol
Identifier

Address
Stub flag

All Rights Reserved Alcatel-Lucent 2007

NMS Integration overview

OSPF - PPP interfaces
Point to point protocol (ppp) interfaces
Available ppp interfaces are
RF
V.11 (Co-dir / DCE or DTE)
G.703 (Co-dir / DCE or DTE or In frame)

Each used ppp interface should have an

associated ospf area address (whatever the
identifier)
Related alarm is based on a protocol failure
("hello" frames, with area address):
Area should be the same, including stub flag
(no alarm in case of stub flag mismatch)

All Rights Reserved Alcatel-Lucent 2007

NMS Integration overview

OSPF PPP Interfaces - "G.703 in-frame" principle
E1 #1, Framed

EC
NMS Function
E1 #1, Framed
Insertion in TS#1

Mux/demux with other E1s

Extraction of TS#1

SWP 2.1.1 : Time Slot choice

/!\ AIS has priority vs this NMS. In case of AIS, NMS-G.703 will be KO.
/!\ NMS - G.703 connector is disabled

All Rights Reserved Alcatel-Lucent 2007

NMS Integration overview

OSPF PPP Interfaces - "G.703 in-frame" application exemple
AWY Network
Input AWY Configuration : G-703 in-frame
OSPF x.x.x.x

Customer Network

AWY Network
Input AWY Configuration : G-703 in-frame
OSPF x.x.x.x

E1 continuity, or at least Time Slot Continuity (ppp fail G.703 alarm in case of
discontinuity)
The same ospf area should be used
All Rights Reserved Alcatel-Lucent 2007

NMS Integration overview

OSPF - Eth/OS interface
Eth/OS interface is generally used for Gateways NEs
Recommandation is to use AWY GNE as ASBR (avoid to use area 0 backbone).
In case of ABR DCN, if the backbone get unstable, the routing tables update may take
too much internal CPU.

Eth/OS address must be different from "Local address"

The routes that allow to reach the ospf area have to be added in the router
that supports the other types of routing protocol
The routes that allow to reach the external world from the ospf area have to
be added in the AWY GNE

All Rights Reserved Alcatel-Lucent 2007

NMS Integration overview

OSPF Eth/OS interface Example 1
How to monitor an ospf area through AWY Eth/OS interface:

172.26.64.0 / 255.255.255.0
OSPF 3.0.0.0, not stubby

(AWY)

Dest network : 0.0.0.0 / 0.0.0.0

Gateway : 172.126.64.1

Network Elements shall be monitored

via their Local addresses

172.126.64.4 / 255.255.255.0

172.126.64.1 / 255.255.255.0
Default Gateway : 172.126.64.4

In fact, default gateway should be

avoided in the AWY router.
Dest network : 172.126.64.0 / 255.255.255.0
Gateway : 172.126.64.1

All Rights Reserved Alcatel-Lucent 2007

NMS Integration overview

OSPF Eth/OS interface Example 2
How to monitor several ospf areas:
172.26.66.0 / 255.255.255.0
OSPF 3.0.0.0, not stubby

172.26.64.0 / 255.255.255.0
OSPF 2.0.0.0, not stubby
Dest network : 0.0.0.0 / 0.0.0.0
Gateway : 192.168.34.1

(Cisco)
192.168.34.34

(AWY)

192.168.34.19 / 255.255.255.0

Dest network : 139.54.216.40 / 255.255.254.0

Gateway : 192.168.34.1
192.168.34.20 / 255.255.255.0

LAN 1

192.168.34.1

Route 1 : Dest network : 172.26.64.0 / 255.255.255.0

Gateway : 192.168.34.19
Route 2 : Dest network : 172.26.66.0 / 255.255.255.0
Gateway : 192.168.34.20

139.54.216.1 / 255.255.254.0

LAN 2

139.54.216.40 / 255.255.254.0
Dest network : 0.0.0.0 / 0.0.0.0
Gateway : 139.54.216.1

Network Elements shall be monitored

via their Local addresses

All Rights Reserved Alcatel-Lucent 2007

NMS Integration overview

OSPF Eth/OS interface Example 3
In a station where the operator wishes to interconnect AWY NEs using the
Eth/OS interface and a hub: exception of the usage of ospf on Eth/OS
interface

172.26.66.6 / 255.255.255.0
OSPF 3.0.0.0, not stubby
(AWY)

(AWY)

172.126.66.6 / 255.255.255.0
OSPF 3.0.0.0, not stubby

172.126.66.4 / 255.255.255.0
OSPF 3.0.0.0, not stubby

HUB

172.126.66.1 / 255.255.255.0

Network Elements shall be monitored

via their Local addresses

All Rights Reserved Alcatel-Lucent 2007

NMS Integration overview

OSPF AWY description
The following table should be filled in when trying to understand a problem
Local Configuration
Local Address
Associated DCN Mask
172.26.66.3
255.255.255.0
OSPF Configuration
Identifier
OSPF Area Address
1
2.0.0.0
2
3
PPP interfaces Configuration
Interface
Type
RF
N/A
V.11
G.703
Eth/OS Configuration
IP Address
Mask
192.168.34.20
255.255.255.0
Static Routing
Destination Network
Destination Mask
0.0.0.0
0.0.0.0

Stub Flag
Not Stub

Ospf Id
1

Ospf Id
None
Gateway
192.168.34.1

A similar table should be filled in for routers, for NMS servers that will specify
which interfaces are used and the routing protocols that are used between
these interfaces.

All Rights Reserved Alcatel-Lucent 2007

First Configuration : Configuration Wizard

All Rights Reserved Alcatel-Lucent 2007