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

GNE that supervises too many NEs cause NE lost management

Publication Date:  2012-07-25 Views:  139 Downloads:  0
Issue Description
Network gateways are overloaded by many NE’s connected to that GW and we might face a ECC loop in the network and SCC CPU usage is getting tremendously high,many NE's are connecting and disconnecting in reiterative manner and accordingly we face a management problem. In our Network the GNE is RTN 980 V1R003 and other NEs are RTN 910 V1R003 and RTN 950 V1R003.

 






Alarm Information
 1
1- GNE_ Fail
2- NE_can`t login




Handling Process
Please check the attached file for more details and here are normal steps :

1-Administration -> DCN management – SHOWS number of NEs directly supervised by GNE.
2-Communication -> NE ECC Link Management – shows all NEs that can access GNE – some are directly supervised by GNE, some are just wasting GNE resources.
3-We go to its sub network by clicking the blue arrow, and here we can find a gateway that supervises this sub network.
4-This means that the latest NEs are "supervises " by two GNEs . We have to disable DCN management (IP) and DCC management (HWECC) on IF ports which connect this two sub networks. But First we have to be sure, that all NEs in 1st sub network are supervises  only by 2nd GNE. Select all and count.
5-And check with the number of NEs in Administration->DCN Management.
6-If the number is the same, that means that all NEs in this sub network are supervised by this GNE so we can disable the management ports leading to other sub network. Always disable ports on GNE, not NE. GNE sites always have management, so if any wrong configuration occurs, the damage will be less. Disabled ports leading to 2nd GNE.

Repeat procedure for all NEs in GW sub network that have links towards other sub networks.







Root Cause
By troubleshooting, we discover that the maximum number of the ordinary NE's that can be connected to GW should not exceed 150 , and we have to put into our considerations that we have to disable the DCC across the different DCN 's and we have to configure the active and standby GW in appropriate manner.





Suggestions
Before the DCN implementation, do a proper DCN plan, and train the engineer to in case the problem happen during the implementation stage.




END