training 2 nmsoverview

9400 AWY R2.1 | September 2007 All Rights Reserved © Alcatel-Lucent 2007

2 NMS Integration overview


NMS Integration overviewOSPF 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.


NMS Integration overviewOSPF 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


NMS Integration overviewOSPF - 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)


NMS Integration overview OSPF – PPP Interfaces - "G.703 in-frame" principle

Mux/d

em

ux w

ith o

ther E

1s

E1 #1, Framed

Extraction of TS#1

E1 #1, Framed

Insertion in TS#1

EC

NMS Function

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


NMS Integration overview OSPF – PPP Interfaces - "G.703 in-frame" application exemple

Customer Network

E1 continuity, or at least Time Slot Continuity (ppp fail G.703 alarm in case of discontinuity)

The same ospf area should be used

AWY NetworkInput AWY Configuration : G-703 in-frame

OSPF x.x.x.x

AWY NetworkInput AWY Configuration : G-703 in-frame

OSPF x.x.x.x


NMS Integration overviewOSPF - 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


NMS Integration overviewOSPF – Eth/OS interface – Example 1

172.126.64.4 / 255.255.255.0

(AWY)

172.26.64.0 / 255.255.255.0OSPF 3.0.0.0, not stubby

172.126.64.1 / 255.255.255.0Default Gateway : 172.126.64.4

Dest network : 0.0.0.0 / 0.0.0.0Gateway : 172.126.64.1

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

Network Elements shall be monitored via their Local addresses

In fact, default gateway should be avoided in the AWY router.




192.168.34.1

139.54.216.1 / 255.255.254.0

LAN 1

192.168.34.19 / 255.255.255.0 192.168.34.20 / 255.255.255.0

(AWY)

172.26.66.0 / 255.255.255.0OSPF 3.0.0.0, not stubby172.26.64.0 / 255.255.255.0

OSPF 2.0.0.0, not stubby

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

192.168.34.34

(Cisco)Dest network : 139.54.216.40 / 255.255.254.0Gateway : 192.168.34.1

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

How to monitor several ospf areas:



LAN 2



HUB

172.126.66.6 / 255.255.255.0OSPF 3.0.0.0, not stubby

172.126.66.4 / 255.255.255.0OSPF 3.0.0.0, not stubby

(AWY)

172.126.66.1 / 255.255.255.0

(AWY)

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.0OSPF 3.0.0.0, not stubby



NMS Integration overviewOSPF – 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 Stub Flag 1 2.0.0.0 Not Stub 2 3 PPP interfaces Configuration Interface Type Ospf Id RF N/ A 1 V.11 G.703 Eth/OS Configuration IP Address Mask Ospf Id 192.168.34.20 255.255.255.0 None Static Routing Destination Network Destination Mask Gateway 0.0.0.0 0.0.0.0 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.


3 First Configuration : Configuration Wizard

training 2 nmsoverview

Documents