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>


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


The GXCSA Keeps Reporting the APS_INDI Alarm Because the Standby GXCSA Is an Earlier Version Than the Active GXCSA

Publication Date:  2012-07-25 Views:  36 Downloads:  0
Issue Description
The engineers replace the standby GXCSA in slot 9 with a new one on an NE on an MSP ring. After the replacement, however, the GXCSA keeps reporting the APS_INDI alarm. The other NEs on the ring do not report the alarm. 
Alarm Information
Handling Process
1. Run the command :alm-get-curdata:0,ALL; to query the alarm data. It is found that the active GXCSA reports the APS_INDI alarm. Run the command :cfg-get-rmsstate:PgID; to query the MSP state. It is found that the MSP ring works properly in idle state.
2. Run the command :alm-init; to initialize the alarms reported by the NE. The APS_INDI alarm, however, persists.
3. Switch the services from the GXCSA in slot 10 to the GXCSA in slot 9. The APS_INDI alarm persists. In addition, the MSP ring becomes exceptional as follows:
#9-144:szhw [144-Yingnan ][Yingnan][2007-10-12 16:57:47]>
1 RR_S stop OFF NR 0x10 OFF
Total records:1
4. Switch the services back to the GXCSA in slot 10. The MSP ring is recovered to the idle state. The APS_INDI alarm, however, persist.
5. Query the GXCSA version. It is found that the GXCSA in slot 9 runs version 3.16 and that the GXCSA in slot 10 runs version 3.19. The engineers suspect that the problem occurs because the active and standby GXCSAs do not match each other. If the standby GXCSA is an earlier version than the active GXCSA, the standby GXCSA synchronizes its data with the active GXCSA actively after being powered on. The GXCSAs of different versions, however, maintain the file area in different formats. Therefore, the GXCSA of the earlier version obtains configuration errors and runs into data disorder. As a result, the problem occurs.
Note: The GXCSA of a later version does not synchronize its data with the GXCSA of an earlier version actively.
There are the following two ways to handle the problem:
●To solve the problem, upgrade the GXCSA in slot 9 to version 3.19.
●To avoid the problem, perform a warm reset on the GXCSA.
6. Upgrade the GXCSA in slot 9 to version 3.19. The problem is solved. 

Root Cause
1. The MSP ring is exceptional.
2. The board reports the alarm falsely.
3. The active and standby GXCSAs do not match each other. 

The OptiX NG-SDH NEs are strict in version matching. On an OptiX NG-SDH NE, ensure that the NE version and board versions are a good match.