Hello everyone!
Today, I’d like to share a case.
Problem Description
Wrong Board Created automatically, New Board Creation fails, while Inserting new Board in OSN9800 U16 new board creation fails and wrong board being created automatically.
Problem Analysis
1. We have Searched the board online event keywords: TEBoardStatusChangeEventHandler, log, and found that only one online event is received by U2000 at 14:33, and the NE_ID=xxxxx, Slot id=12.
2. We have Searched for xxxxx (NE ID) in the U2000 log file and found that the NE name is “ZZZZ”, which is a problematic network element in the live network.
3. We have searched for xxxxx(NE_ID) from the U2000 log which record the NE netconf packet(NE upload to U2000), we found that the “TNV2G220 0/12” is reported in the NE’s netconf packet, U2000 received this message and then displayed “TNV2G220” for slot 12 on U2000 client GUI.
But the actual slot type should be tnu1g404.
4.So current analysis result is as following:
In the NE netconf packet that the NE uploads to U2000, the NE provides a mismatched slot model, causes the U2000 to show a wrong slot model.
Root Cause
1. After analyzing the NE log, we found that in slot 11 U3N402 board was inserted a on October xx.
2. When customer inserts a V2G220 card into the slot 11 on October yy, the NE sent a netconf packet(including the wrong board model U3N402 which is historical online board model on October xxth) to U2000 when the slot 11 start initialization.
3. When U2000 received the netconf packet(wrong board model: U3N402) sent by the NE, it displayed the U3N402 for slot 11 on GUI, and temporarily locks the board information for sync.
4. After the board completed the initialization and run stably(about 30s to 180s later), the NE will send second netconf packet to the U2000 (including the correct board model V2G220). However, if the U2000 has not released the board information lock status, U2000 will drop the second netconf packet, causing the U2000 to display the wrong board model U3N402.
Solution Description
NE side will optimize the board report mechanism in higher version V1R19C10SPC300, the version release will be next year;
This issue only happen during the board type change, before new board boot up, old board type will send to U2000; The higher version will modify this and will not send old board type to U2000; workaround solution is to upload or synchronize NE data.
Welcome to leave a message below.
We’ll study together.
Thank you!
