RTN any version, at the large network which was maked with more than 2000NEs, Sometimes RTN can't visit it or add it through NMS. That means site X should
belong to GNE A, but someone add it belong GNE B. then separate subnet as A and B. Some sites should belong GNE B, but it actually at management of GNE A.
These NE can't visibility and manage.
NE_NOT_LOGIN, COM_FAIL, two alarm in one NE, it means this NE can't build communication with NMS
Terer's two solution for this issue:
1,delete NE-> search NE through GNE B IP->re-create NE-> upload it -> search fiber->finish. All these operation will take 5~8 mins
2,At NMS U2000 ot T2000, go to "DCN management" search the particular NE, at praimer GNE list select right GNE as GNE B. finish. It only need 1 minute.
The reason is this NE didn't build the ECC with his direct GNE B. because it was belong to wrong GNE A.
Separate subnet first at NTS step, thus we can confirm every NE belong to right GNE.