No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ--How to setup inband DCN communication on Ethernet service port.

Publication Date:  2012-07-25 Views:  107 Downloads:  0
Issue Description
How to setup inband DCN communication on Ethernet service port on RTN equipment, to communicate between GNE on Internal DCN and NMS on External DCN using WebLCT.


Alarm Information
Null

Handling Process
The first thing to do is to enable the DCN management on the service interface. To do this go to “Function Tree”> “Communication”>”DCN Management”. Here are four different topics: “Bandwidth Management”, “Access Control”, “Port Settings” and “Protocol Settings”.

1.1
Under the topic “Bandwidth Management” it is possible to select what VLAN the DCN should be send out in (Default VLAN is 4094).


1.2

Next topic is “Access Control”, here is where the IP address and subnet mask should be set, and the port enabled.


1.3
Under “Port Settings” it is possible to decide what service interfaces to make available for DCN Management.


1.4
Under the last topic “Protocol Settings” the protocol used for DCN management are selected, in this case the IP protocol are used.


Now it is possible for a NMS to communicate with the GNE using IP over a service port, if the NMS are in the same subnet. In case the NMS is in a different subnet, but connected to the same routed DCN network as the GNE, then the GNE needs a default IP route or a static route to a router on the DCN network, which can forward the packets to the right place (NMS subnet). The NMS also have to have a default route or a static route to the a router on the DCN network, which can forward packets to the right place (GNE subnet).

2.1
To add a default route go to “Function Tree”>”Communication”>”Communication Parameters” here it is possible to set the “Gateway IP” to the desired IP.


2.2
After the new default route is set it is possible to view it by going to “Function Tree”>”Communication”>”IP Protocol Stack Management” and selecting the “IP Route Management” topic.


2.3
If the network of the NMS is known it is also possible to add a static route to the NMS network, this is also done under “Function Tree”>”Communication”>”IP Protocol Stack Management” by pressing “New” button, and then adding the destination network of the NMS.


Root Cause
For a GNE in the internal DCN to communicate with a NMS in the routed external DCN, through a service port, the service port needs both IP address on service interface and Gateway address in the routing table on the node.

Configuration steps for RTN equipment :

1. Setting VLAN, adding an IP address to a service port, and enabling the port.

2. Adding a default gateway or setting a static route.

Suggestions
The things to be aware of when configuring inband DCN is that the right default routes or the right static route are set. Also make sure that the gateway is able to route the IP packets to the destination network of the NMS, and vice versa.

Use “Ping” and “Traceroute” commands to verify and troubleshoot configuration.

References(Can be found on http://3ms.huawei.com):

DCN Feature for PTN Equipment-20100408-A
Huawei_RTN_microwave_DCN_Solutions V1.3 (20101115)


END