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>Search


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


FAQ-Precautions for the HSC_UNAVAIL Alarm That Occurs During the CXL Upgrade

Publication Date:  2012-07-25 Views:  125 Downloads:  0

Issue Description

On an OptiX OSN 2500 NE, the standby CXL reports the HSC_UNAVAIL alarm with parameter 1 of 0x80 after receiving a cold reset. Five minutes later, the alarm persists with the parameter changing to 0x01.  

Alarm Information


Handling Process

No special handling is required. After the HSC_UNAVAIL alarm is reported with parameter 1 of 0x80, wait about five minutes for the parameter to change to 0x01. Then, proceed with the upgrade. After both the CXLs are upgraded, the HSC_UNAVAIL alarm is cleared.  

Root Cause

 With parameter 1 of 0x01, the HSC_UNAVAIL alarm indicates that the standby CXL is set bad. When the standby system control software is a different version from the active, the NE sets the standby CXL bad to prevent active/standby CXL switching. That is the cause of the HSC_UNAVAIL alarm with parameter 1 of 0x01. During the CXL upgrade, simply wait after the HSC_UNAVAIL alarm with parameter 1 of 0x80 and before the HSC_UNAVAIL alarm with parameter 1 of 0x01. 



The parameters of the HSC_UNAVAIL alarm are described as follows:
Parameter 1 indicates the type of the alarm.
-Value 0x01 indicates that the local board is bad.
-Value 0x02 indicates that a service board finds that the local board is bad.
-Value 0x04 indicates that the local board detects a type III BUS_ERR.
-Bits [3�6] are reserved.
-Value 0x80 indicates that less than five minutes elapse after the standby board is reset successfully.
Parameter 2 indicates whether the unavailable board is active or standby.
-0x00, active
-0x01, standby
Parameter 3 indicates the ID of the unavailable board, such as 0x09 or 0x0A.