Dcn

DCN Data Communication Networks

© Tejas Networks India Ltd., 2008, Proprietary Information Rev 2.0 Reviewed by:

Why DCN?
To Manage Local and Remote Network Elements

 Local Management includes the management of the node through the NMS interface using direct ethernet cable or through switch. The PC/Laptop and the node should be on same IP subnet  Remote Management includes  Management of the node through IBC  Overhead Tunneling  VC-12 Management  E1 / Eth Management

© Tejas Networks India Ltd., 2008, Proprietary Information Rev 2.0 Reviewed by:

Why DCN? Contd.
When two nodes are connected by Optical fiber cable, one can use IBC (In-band Communication) for remote management. Bytes used are:  DCC-R, D1 to D3 bytes in RSOH (192Kbps)  DCC-M, D4 to D12 bytes in MSOH (576Kbps)  F1 byte in RSOH (64Kbps)  F2 byte in HOPOH (64Kbps)  F3 byte in HOPOH (64Kbps)  F2 & F3 bytes in HOPOH (128Kbps) Note: 1) Both ends of the optical fiber should have same ECC byte selected. 2) Both end of the optical fiber should have same MTU size selected. 3) OSPF has to be enabled on all of the provisioned interfaces.

© Tejas Networks India Ltd., 2008, Proprietary Information Rev 2.0 Reviewed by:

Routing for Management
Adding Static Route To remotely access the non-gate way NE’s from a gate way NE, add a static route in the PC/Laptop only if it is connected to the gateway NE through the switch. For Linux PC route add –net netmask gw For Windows PC route add mask
Updating routing table on NE’s dynamically In old s/w, OSPF has to be enabled both ‘on Ethernet’ and ‘globally’ for the gateway NE and for the non-gateway NE’s involved in Eth Management. For other non-gateway NE’s, OSPF has to be enabled ONLY ‘globally’ In new s/w, OSPF has to be enabled for each individual Network Interface (including the Eth interface) for the gateway NE and for the non-gateway NE’s involved in Eth Management. For other non-gateway NE’s, OSPF has to be enabled for each individual Network Interface (excluding the Eth interface)

© Tejas Networks India Ltd., 2008, Proprietary Information Rev 2.0 Reviewed by:

Example Employing Route addition in PCs Ethernet IP – 192.168.10.105

Ethernet IP – 192.170.20.100

Router ID – 192.180.8.105

Router ID – 192.180.8.100 Ethernet IP – 192.170.20.120

Tejas box 1

DCC-M

DCC-M

DCC-R

Tejas box 2 DCC-M

Switch

PC

Windows: route add 192.180.8.0 mask 255.255.255.0 192.170.20.100

DCC-R

DCC-M

Linux: route add –net 192.180.8.0 netmask 255.255.255.0 gw 192.170.20.100

Tejas box 4

F2F3

F2F3

Tejas box 3

Ethernet IP – 192.172.30.110

Ethernet IP – 192.174.40.115

Router ID – 192.180.8.110

Router ID – 192.180.8.115

© Tejas Networks India Ltd., 2008, Proprietary Information Rev 2.0 Reviewed by:

Remote Management (…contd.)
Overhead Tunneling-Feature Supported by Tejas nodes if it comes in between two non-Tejas nodes, who are already exchanging management information using DDC-R /DCC- M /F1 /F2 /F2- F3 bytes.

Non Tejas box 1

Tejas box 2

DCC-M

1-3-1 DCC-M Non Tejas box 2

Tejas box 1 1-3-2

Create overhead tunnel here from 1-3-1 to 1-32 for DCC-M bytes.However the same bytes cannot be used at Tejas node 1.

© Tejas Networks India Ltd., 2008, Proprietary Information Rev 2.0 Reviewed by:

Remote Management (…contd.)
VC12 Management  VC12 Management is required if a non-Tejas node comes in between two Tejas nodes and the non-Tejas node does NOT support overhead tunneling.

Non Tejas node 1

Map management information in a VC12 on to STM port 1-3-1.However 1 VC12 worth bandwidth now cannot be used for traffic.

Tejas node 1 1-3-1

Map management information in a VC12 on to STM port 1-3-1.

Tejas node 2

1-3-1

Non Tejas node 2

This node does not support overhead tunneling,This node contains a pass through cross connect from 1 STM port to the other.

© Tejas Networks India Ltd., 2008, Proprietary Information Rev 2.0 Reviewed by:

Remote Management Contd…


E1 Management E1 Management is possible between two co-located Tejas nodes where normally the E1port #1in two nodes are directly connected either by E1 cable or by Twisted-pair cable. So, # of E1 ports gets reduced by 1 for add/drop purpose.

Tejas box 1

E1 cable/twist ed pair cable

Tejas box 2

Tejas box 4

Tejas box 3

© Tejas Networks India Ltd., 2008, Proprietary Information Rev 2.0 Reviewed by:

Tejas boxes 1 and 4 are co-located the E1 port of which are connected through E1 or by twisted pair cable. For MC16S any 3 E1 ports can be used for E1 management.But for all the other products use 1st E1 port.

Remote Management Contd…
Ethernet Management  Ethernet Management is possible between two co-located Tejas nodes where NMS ports of both the nodes are directly connected using a cross-cable. These two nodes a) should NOT be gate-way nodes b) should be in same IP subnet Note that no traffic port is wasted for this The NMS port of node 3 and 4 have been connected by an Ethernet cable.OSPF is enabled on Eth interface at both the nodes to achieve Ethernet management.

Tejas

Tejas node 1

node 4

A route in the PC has to be added only if it is connected to GNE through the switch (say node 1) for the 2 nodes involved in Ethernet mgmt. sharing the same subnet. Tejas node 3 Ethernet cable © Tejas Networks India Ltd., 2008, Proprietary Information Rev 2.0 Reviewed by:

Tejas node 2

Remote Management Contd…




 

Ethernet - VC12 Management Ethernet-VC12 Management can be used between 2 Tejas Nodes, which are located far apart. Connectivity at each end Connect the NMS port to any Ethernet port using a cross cable. Make a VC12 cross connect for that Ethernet port. Note 1: Ethernet-VC12 management can be configured at the cost of 1 Ethernet port. Note 2: Protection for the management information on a VC12 path is supported. Note 3: The two nodes should be non-gateway nodes. Note 4: The two nodes should be on same IP subnet.

© Tejas Networks India Ltd., 2008, Proprietary Information Rev 2.0 Reviewed by:

Remote Management Contd…

NMS PORT

NMS PORT

Make a VC-12 cross connect on STM ports 1 and 2 for the corresponding Ethernet Ports of NE-A and NE-B respectively.

NE - A

3-1

2

NE - B

TP01

TP01

Eth

Eth

Port

Port

Ethernet port of an Ethernet Tributary Card, say TP01 is connected to NMS port of Network Element with a cross cable © Tejas Networks India Ltd., 2008, Proprietary Information Rev 2.0 Reviewed by:

Ethernet port of an Ethernet Tributary Card, say TP01 is connected to NMS port of Network Element with a cross cable

Thank You… You…

© Tejas Networks India Ltd., 2008, Proprietary Information Rev 2.0 Reviewed by: