Most NEs in the WDM subnet on a U2000 NMS frequently report NE_NOT_LOGIN alarm：
1、all NEs just report NE_NOT_LOGIN,has no NE_COMMUN_BREAK,Therefore can rule out ECC storm or shock problems。
2、The initial judgment is caused by login and kick-in of NE users,but customer feedback no other U2000 manage these NEs as he know.
3、Send the command sm-get-user, to query specific information that may kick the user, the returned response contains the TEI information. (Must be multiple queries, be sure to check this user Tei value has changed so far)：
4、in step3 we can get NE9-7 all the ems terminal TEI, one is 0x6e, another is 0x6f,that means must have two EMS terminal login this NE.
5、then wen get the TEI id corresponding ems terminal ip address via lanconinfo command, one ip address is the U2000server we used, another ems terminal ip is 192.168.12.4：
We can find other NE has the same situation:
6、ask customer find the other ems terminal which ip address is 192.168.12.4, let it do not manage these NEs use the same NE user or let this ip disconnect with our U2000server DCN,after done this the problem fixed.
Two EMS terminal login in NEs use the same NE user cause login and kick-out
we can use commands :sm-get-user and :cm-get-lanconinfo to find all the EMS terminal IP address specific information and let other EMS do not manage these NEs use the same NE user or let other EMS disconnect with his U2000server DCN
all NEs just report NE_NOT_LOGIN,has no NE_COMMUN_BREAK,Therefore can rule out ECC storm or shock problems