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>Search


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


FAQ-Two GNEs existing on same Sub network issue resolution

Publication Date:  2012-07-25 Views:  95 Downloads:  0
Issue Description

As per the above diagram we have two GNEs existing on the same subnetwork where we have to make all NEs visible under GNE1. Now when we try to search for NEs under GNE1, then we get conflict. Hence sometimes the NE after GNE2 becomes unmanaged.
Alarm Information
Handling Process
When we search for the normal NEs, we change the GNE of those NEs that are searched under GNE2 to GNE1 from the drop down menu of Primary GNE and create them. Now we select secondary GNE for all NEs as GNE2. In this way we can have three profits i.e
1) We will have visibility of NEs even if the primary GNE IDU is down.
2)Maitainance from site end for MS engineer will be easier as DCC flow will not be disabled between GNE2 and the NE before it.
3)Conflict between NEs will be stopped.
Root Cause
As there are two GNEs existing under the same subnetwork, NEs becomes unmanaged at times.We search for all NEs under the IP of GNE1. But we find that some non GNE NEs are searched under GNE1 and some under GNE2. When we try to create all Non GNEs, we cannot create those which are searched under GNE2. Normally we stop the DCC flow between GNE2 and the NE before it and create two different subnetwork to stop this problem.