An OSN 3500 had 1+1 board level protection for cross-connect boards (UXCSB).
A COMMUN_FAIL fail was reported on slot 09 for UXCSB board in an OSN 3500. During switching events caused by fiber cut, the services of the MSP ring became
affected. The status of the 1+1 board protection was not showed on NM due to time out. Through Navigator by using the command: cfg-get-dpstate to verify the board protection status, the error reported was "error: 0x9763 NSERR_BDRSP_CMD_OVERTIME".The MSP protocol in OSN 3500 was "unknown
1. Check the causes of alarm COMMUN_FAIL
2. Perform a remote hard reset using the Navigator command :cfg-reset-board
3. If step two does not work, perform a hard reset on-site for the board reporting COMMUN_FAIL alarm.
4. To discard any problem, perform switching test to verify the switching status of the 1+1 board protection for cross-connect boards.
5. Perform switching test by turning off the laser.
The status of 1+1 board protection for cross-connect boards was not showed on NM or through Navigator due to there was a communication problem from the board. For this reason, an engineer on site
checked the indicators status, showing that during the switching events, the board that was as main/working board was the UXCSB located on slot 09
(the one reporting COMMUN_FAIL alarm). During switching events, the services were down due to the processing of the K bytes was being performed for the
UXCSB board on slot 09, the board that had the communication problem. For this reason the switching process was not successful.
Be aware of COMMUN_FAIL alarms on the network. This type of alarms can cause the MSP protocol not working properly.