No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Cross-Connect Board Unable to Run Manual Switching Commands After OptiX OSN 7500 Upgrade Due to the Unsteady State of the Multiplex Section Protocol

Publication Date:  2012-07-25 Views:  55 Downloads:  0
Issue Description
The OSN7500 in a certain office is upgraded from V1R3C01B025SP03 to V1R6C02B012. After the simulated packages are loaded, the active/standby main control units and standby cross-connect board are activated. When switching over the active and standby GXCSA cross-connect boards, the NMS cannot switch over. Run the cfg-set-dpsswitch command of the Navigator. Switching fails. The NE does not return any alarms. 
Alarm Information
Null
Handling Process
Check that no exception alarms occur before and during the NE upgrade.
Use the script to collect the data in the black box. The bb9.log file records the cause of the switching failure:
bb9.log              2007-11-02 09:15:12          Level:3, XcsXcpModule.cpp, Line:1409, xc manSw failed:now forbid xc switch for (msp) protocol unstead     
The multiplex section enters into the unsteady state and prohibits active/standby switching. The protocol of the NE multiplex section is a restructuring protocol. The defects of the restructuring protocol of the V1R3R3C01B025SP03 version prevent the manual switching of the cross-connect boards. Upgrade the type of the multiplex section protocol to a new protocol. Active/standby switching is supported. Upgrade the software to V1R3C02B028SP01 or a later version to rectify the fault. 
 
Root Cause
The NE cross-connect boards do not support switching. The possible causes are as follows:
The standby cross-connect board is damaged.
The software prohibits manual switching in certain state. 
 
Suggestions
The restructuring protocol of the multiplex section consumes the system resources. For active maintenance, it is recommended that the customer change the protocol to a new protocol. 

END