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 transparently transmitt NEC NEO DCN information by DCC mode of TCP IP protocol

Publication Date:  2012-07-25 Views:  37 Downloads:  0
Issue Description
Refering to attached Picture , it is supposed that interconnection between Huawei RTN-950 CSH [ETH-port ] version (V100R002) with NEC NEO [EM2-port] with straight ethernet cable is Sufficient to got the NEC-NEO device managed on the NMS [PNMSj] , while even the DCC mode of the whole path was changed to TCP/IP and the IP of all the RTN in the same path has been changed to be in the same subnet of the NEC, but the NEC Link could not be managed.


Alarm Information
None.


Handling Process
As here, the 3rd party MW doesn’t support OSPF for management, static routes should be manually added to the RTNs.

To solve the problem completely , follow below procedures :
1. Using NetConfig tool configure the NEO subrack as branch ( as shown in second attachment).
2. You need to add two manual routes in the RTN that is directly connected to the NEO IDU:
[ First route should be ( the destinaion address = NEC IP , Mask = 255.255.255.255 , next hop is the NEC IP) ]
[ Second route should be (( the destinaion address = NEC subnet behind, Mask = the same used mask in NetCfgj tool , next hop is the NEC IP) ].

3. Finally login with navigator to that RTN and run the below command:
[ :cm-set-ospf-import:static,enable ]


Root Cause
1. In order to manage the NEO MW through RTN DCC subnet, IP address should be assigned in the nearby RTN to the NEO and change the DCC protocol type to be TCP/IP for all the route to the BSC.
2.The ping and traceroute operations tests from the NMS server was successful to reach the RTN IDU , but fail to reach the NEC-NEO , thus it was mandatory to find and search the problem inside the routing table of the RTN ( Communication>IP protocol Stack managment ).
3. We found that the IP of the nearby NEC IDU has not been discovered , thus communication has been stopped.



Suggestions
Integration of DCN interconnection between huawei equipments and 3rd party using standard protocol such as TCP/IP should be checked refering to the matching cabapilities of OSPF protocol in both devices ,
in addition, the routing table discovered by OSPF need to be merged with the static routing table manually added to the RTN.


END