Hello, everyone!
This post will tell you one issue for NMS Fails to Query the MSP Status Due to Version Incompatibility.
Problem description:
In an office, when maintaining the status of the protective subnet in the multiplex section ring that consists of the OptiX OSN 2500, an engineer finds that the NMS displays a command error with the code 38751 when querying the multiplex section status in the NE manager or in the protection subnet. The error indicates that the board does not support this command.
The version of the host is 5.21.17.31.
The version of the NMS is V2R5C01b01cSPC007.
Handling procedure:
1. The NMS is faulty.
2. The host is faulty.
3. The cooperation of the NMS and the host is faulty.
4. Other faults. .
Root cause:
Version Incompatibility between SXCS board and GSCC board.
Solution:
1.Run cfg-get-rmsstate to query the MSP status of the NE and find that the status can be queried. The fault is probably caused by the NMS.
2. Query other devices such as the Metro 1000 on the NMS and find that the devices can be queried. Query other OptiX OSN 3500 of the version 5.21.12.43/5.21.13.47, and the equipment can be queried. Therefore, the fault is not caused by the NMS.
3. The cooperation of the NMS and the host is faulty. Analyze the returned EMS.log and find the error: NSCMD_CFG_GET_MSSPR_SWSTA_02, and the corresponding host command is cfg-get-rmsstate-new.
4. Run the command on site. The following message is displayed:
:cfg-get-rmsstate-new:1;
failed! cmd:0x853f error:0x975f NSERR_BDRSP_BAD_CMD
The MSP protocol of the OptiX OSN 3500 runs on the cross-connect board. Therefore, the query for the MSP must be performed on the cross-connect board. The R7 host supports the command. Therefore, the cause of the fault is that the cross-connect board does not support the command.
5. Query the cross-connect board and find that the version is 2.14. The corresponding host is R2. The field engineers upgrade the host to R7 but the cross-connect board is not upgraded. Upgrade the cross-connect board to the 6.31 version. The fault is rectified.
That's all, I welcome everyone to leave a message and exchange in the comment area!
Thank you！
