DCN
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
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.
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 <subnet address for Ids> netmask <mask address for Ids> gw <Eth IP of the gateway NE>
For Windows PC
route add <subnet address for Ids> mask <mask address for Ids> <Eth IP of the gateway NE>
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)
Example Employing Route addition in PCs
T
ejas box 1T
ejas box 2T
ejas box 4T
ejas box 3Ethernet IP – 192.170.20.100 Router ID – 192.180.8.100 Ethernet IP – 192.168.10.105 Router ID – 192.180.8.105 Ethernet IP – 192.172.30.110 Router ID – 192.180.8.110 Ethernet IP – 192.174.40.115 Router ID – 192.180.8.115
Switch
Ethernet IP – 192.170.20.120Windows: route add 192.180.8.0 mask 255.255.255.0 192.170.20.100 Linux: route add –net 192.180.8.0 netmask
255.255.255.0 gw 192.170.20.100 DCC-M DCC-M DCC-R DCC-R F2F3 F2F3 DCC-M DCC-M
PC
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.
T
ejas box 2 Tejas box 1 Non Tejas box 2 Non Tejas box 1 DCC-MDCC-M Create overhead tunnel here from 1 to
1-3-2 for DCC-M bytes.However the same bytes cannot be used at Tejas node 1.
1-3-2
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.
This node does not support overhead tunneling,This node contains a pass through cross connect from 1 STM port to the other.
Map management
information in a VC12 on to STM port 1-3-1.However 1 VC12 worth bandwidth now cannot be used for traffic. Non Tejas node 1 Non Tejas node 2 Tejas node 2 Tejas node 1 1-3-1 1-3-1 Map management information in a VC12 on to STM port 1-3-1.
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 Tejas box 3 Tejas box 4 Tejas box 2
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 1stE1 port.
E1
cable/twist
ed pair
cable
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
T
ejas node 4 Tejas node 2 Tejas node 3 Tejas node 1 Ethernet cableThe 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.
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.
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.
Remote Management Contd…
NE - A
NE - B
NMS PORT NMS PORT TP01 TP01 Ethernet port of an Ethernet Tributary Card, say TP01 is connected to NMS port of Network Element with a cross cable Ethernet port of an Ethernet Tributary Card, say TP01 is connected to NMS port of Network Element with a cross cable3-1
2
Make a VC-12 cross connect on STM ports 1 and 2 for the corresponding Ethernet Ports of NE-A and NE-B respectively.
Eth Port Eth