OSN2500 Command Line Modifies Network Element ID

 Problem description

Customers in the replacement of OSN2500 equipment master board misoperation, and then did not complete synchronization on the replacement of the motherboard, the main and backup synchronization between abnormal, and then the original motherboard as a backup board insert, synchronization will lead to new and old single board network element ID changes, network element off-line, business interruption. The original network element ID is 1177, and the network element ID after exception is 10007. Customers want to use the command line to restore the network element ID to 1177, at this time the command line reported ID conflict error, error code: 39048.

Alarm information

NSERROR_CM_NEID_CONFLICT

Processing process

1. change the CXL to the single matching state, reset the veneer, then modify the ID, and still report the error.

2. it is still a problem to replace other CXL boards for the same operation.

3. Using the command line to query the ECC routing of the fault network element, we find that there is indeed a routing directed to 1177 network element, the hop number is 35, and the hop number is 36 in the neighboring network element view. If there are any network elements that conflict with the ID before confirming with the customer, or if there is a new add-on operation, the customer clearly indicates that there is No.

4. Looking at the ECC link management of the adjacent network elements on the network management, it is found that the 1177 ID points to the fault network elements, but the hops are abnormal, and there is also a route to 10007 ID.

5. As confirmed by R&D, it is suspected that the subnet is too large and the link is unstable, which causes the routing aging time to be too long and leads to the route to the original 1177 network element ID.

6. Use cm-set-maxdist command to change the ECC maximum hops of the fault network element to 10, speed up routing aging, and then set the network element ID successfully, download data to restore business.

Root cause

1. main control panel failure

2. network elements with ID conflict

Suggestion and conclusion

Reasonable planning of network subnet prevents ECC subnet from being too large.

More about Huawei OSN2500, welcome to contact us.