NE status became “Inconsistency” during modifiyng a trail due to NMS bug

When complete SNCP creation, the NE status became “Inconsistency”.

1.At first, we suspect the database is abnormal, it caused this problem, but we checked it, it is normal.

2.We collect the NMS log ,checked the data and found the SNCP event was reported when modifying the trail and it caused the NE data inconsistency status.

[13:29:12.935],Error,[T13064],ErrorCode: 0×00000000, imapoptixadapter Thread:3308, QX_RECV_DATA (from thread 0×0) <<<…

6d 09 2e e3 00 09 2e e3 00 00 00 21 00 00 00 00

ff 00 4a a0 00 01 00 17 00 00 05 24 14 36 00 00

00 00 00 00 6f 97 00 00 00 06 00 1b 01 00 00 00   // NSEVT_CFG_SNCP_SW

00

3.  confirmed this is known NMS issue which has been fixed in the V1R9C00SPC301.

The SNCP event was reported when modifying the trail and it caused the NE data inconsistency status.
Need to consitency the NE data again. The final solution is to upgrade the current U2000 to V1R9C00SPC301.
When we modify the general service to the SNCP service, the NE would report the SNCP event like creating the new SNCP service. It is normal phenomenon.

 

Thunder-link.com now have many products and  various board on promotion, more than 86% off list price, please come to visit www.thunder-link.com; or just email for inquire: sales@thunder-link.com

TwitterLinkedInGoogle+FacebookPinterestTumblrStumbleUponRedditShare

Leave a Reply

Your email address will not be published. Required fields are marked *