ALML
- ALML/4/V15_CPU_VOL_FAIL
- ALML/4/V15_CPU_VOL_RESUME
- ALML/4/48V_CHECK_FAULT
- ALML/4/48V_VOLTAGE_NORMAL
- ALML/0/ALL_CHANNEL_FAULTY
- ALML/0/ALL_CHANNEL_NORMAL
- ALML/4/BOARDTYPE_DIFF
- ALML/4/BOARDNOTPOWERON
- ALML/0/BRD_PWOFF
- ALML/0/BRD_PWOFF_RESUME
- ALML/4/CANBUSFAULT
- ALML/4/CANBUSFAULT_RESUME
- ALML/4/CANBUSNODELOST
- ALML/6/CANBUSNODERESUME
- ALML/4/CANCOMFAIL
- ALML/4/CANCOMRESUME
- ALML/3/CANNODEABSENT
- ALML/4/CANNODEREG
- ALML/3/CANNODE_POWEROFF
- ALML/3/CANNODE_POWERON
- ALML/4/CAN_READY
- ALML/3/CAN_SELFTEST_ERR
- ALML/4/CAN_SELFTEST_OK
- ALML/3/CHANNEL_FAULTY
- ALML/3/CHANNEL_NORMAL
- ALML/4/CHAN_POWER_LACK
- ALML/4/SYSTEM_POWER_NORMAL
- ALML/4/CLOCKFAULT
- ALML/4/CLOCKFAULT_RESUME
- ALML/4/COMMLOSTLONG
- ALML/6/COMMLOSTLONGRESUME
- ALML/3/CPU_RESET
- ALML/3/PKTERRORRISING
- ALML/3/DISCARD_PKT
- ALML/4/ENTPOWEROFF
- ALML/4/ENTPOWERON
- ALML/4/ENTRESET
- ALML/4/ENTRESETFAIL
- ALML/4/ENTUP
- ALML/4/ENT_PLUG_IN
- ALML/4/ENT_PULL_OUT
- ALML/4/ENTPOWERINVALID
- ALML/4/FANDISMATCH
- ALML/4/FANDISMATCHRESUME
- ALML/4/FANFAULT
- ALML/4/FANFAULT_RESUME
- ALML/4/FAN_LOWER
- ALML/4/FAN_LOWER_RESUME
- ALML/4/FAN_MONITOR_FAIL
- ALML/4/FAN_MONITOR_RESUME
- ALML/4/FAN_NOELABEL
- ALML/3/HG_ISOLATE
- ALML/4/HG_RELIEVE
- ALML/4/HG_STATE
- ALML/4/HSB_SWITCH_CAUSE
- ALML/4/IOFAULT
- ALML/4/IOFAULT_RESUME
- ALML/5/LOGOUT
- ALML/4/LSW2FSU_LINK_CHANGE
- ALML/4/LSW2FSU_LINK_STATE
- ALML/4/LSWTEMP_LOWER
- ALML/4/LSWTEMP_LOWER_RESUME
- ALML/4/LSWTEMP_UPPER
- ALML/4/LSWTEMP_UPPER_RESUME
- ALML/4/MASTER_TO_SLAVE
- ALML/4/MEMSIZE_DIFF
- ALML/4/NVRAMFAILURE
- ALML/6/NVRAMFAILURERESUME
- ALML/3/OIDS_MERGE_FAIL
- ALML/4/OLD_BOOT_SYN_END
- ALML/4/OLD_BOOT_SYN_START
- ALML/3/PEER_CHANNEL_FAULT
- ALML/3/PEER_CHANNEL_NORMAL
- ALML/4/POS_MISMATCH
- ALML/4/POWERSUPPLY_ON
- ALML/4/POWERSUPPLY_OFF
- ALML/4/POWER_LACK
- ALML/4/POWER_LACK_RESUME
- ALML/4/POWERINVALID
- ALML/4/POWERINVALIDRESUME
- ALML/0/POWER_DC1600_FAULT
- ALML/0/POWER_DC1600_NORMAL
- ALML/4/PUBLISH_EVENT
- ALML/4/PWRFANABSENT
- ALML/4/PWR_NOSUPPLY
- ALML/4/PWR_NOSUPPLY_RESUME
- ALML/4/RESOURCE_MODE_DIFF
- ALML/4/RTC
- ALML/4/RTC
- ALML/4/SDFAILURE
- ALML/6/SDRESUME
- ALML/4/SELFULL
- ALML/3/SFFAILURE
- ALML/6/SFRESUME
- ALML/4/SELFULL_RESUME
- ALML/4/SERDES_STATE
- ALML/4/SLAVE_TO_MASTER
- ALML/4/SPU_VERCOMP_FAIL
- ALML/4/TEMP_MONITOR_FAIL
- ALML/4/TEMP_MONITOR_RESUME
- ALML/4/TEMP_UPPER
- ALML/4/TEMP_UPPER_RESUME
- ALML/4/UPLOAD_FILE
- ALML/4/USBFAILURE
- ALML/6/USBFAILURERESUME
- ALML/4/VLCS_NEAR_DEADLINE
- ALML/2/VLCS_EXPIRED
- ALML/4/VOLT_LOWER
- ALML/4/VOLT_LOWER_RESUME
- ALML/4/VOLT_MONITOR_FAIL
- ALML/4/VOLT_MONITOR_RESUME
- ALML/4/VOLT_UPPER
- ALML/4/VOLT_UPPER_RESUME
ALML/4/V15_CPU_VOL_FAIL
Message
ALML/4/V15_CPU_VOL_FAIL: An exception occurred on the V15_CPU voltage sensor of [STRING1]. (Value=[STRING2])
Parameters
Parameter Name | Parameter Meaning |
---|---|
STRING1 | Indicates the physical entity, for example, MPU board [7]. |
STRING2 | Indicates the current voltage of the 1.5 V CPU sensor. |
Procedure
- Run the display
voltage slot slot-id command to check whether the voltage of the V15_CPU
sensor of the card is within the normal range (± 0.15 V).
- If so, the log handling ends.
- If not, go to step 2.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/4/V15_CPU_VOL_RESUME
Message
ALML/4/V15_CPU_VOL_RESUME: The V15_CPU voltage sensor of [STRING1] has been restored to its normal state. (Value=[STRING2])
ALML/4/48V_CHECK_FAULT
Message
ALML/4/48V_CHECK_FAULT:The "[STRING1]" sensor[ULONG] of [STRING2] detects a 48V_CHECK signal warning.
Parameters
Parameter Name | Parameter Meaning |
---|---|
STRING1 | Indicates the entity name. |
STRING2 | Indicates the sensor name. |
ULONG | Indicates the sensor ID. |
Possible Causes
The power supply line for a board is faulty, which causes the board unable to be powered on.
Procedure
- Run the display
power command to check whether the power module is
installed properly.
- If so, go to step 2.
- If not, install the power module properly.
- Rectify the fault according to "A Power Module Cannot Provide Power" in the Troubleshooting Insights - Campus Switch - Hardware Fault.
ALML/4/48V_VOLTAGE_NORMAL
ALML/0/ALL_CHANNEL_FAULTY
Parameters
Parameter Name | Parameter Meaning |
---|---|
STRING1 | Indicates the entity name. |
STRING2 | Indicates the entity name. |
Procedure
- Check whether the log ALML/0/ALL_CHANNEL_NORMAL is generated.
- If so, the fault is rectified, and no action is required.
- If not, go to step 2.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/4/BOARDTYPE_DIFF
ALML/4/BOARDNOTPOWERON
Description
The board in a slot fails to be powered on, and reason of the power-on failure is recorded.
Parameters
Parameter Name | Parameter Meaning |
---|---|
ULONG | Indicates a slot ID. |
STRING | Indicates the reason why the board fails to be powered on. |
Possible Causes
- The 12 V power output of the power module is abnormal.
- The CANbus is abnormal.
- The power module does not provide sufficient power to the board.
Procedure
- Run the display power system command to check whether the rated power Power(W) of the board is higher than the system remaining power The remain power.
- If so, go to step 2.
- If not, go to step 3.
- Run the display power command to check whether the power module is installed properly.
- If so, go to step 3.
- If not, install a new power module to increase the system power and reset the board to enable the system to power on this board. If you do not know which slot the new power module should be installed or the board still fails to be powered on after the power module is installed, go to step 3.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/0/BRD_PWOFF
Message
ALML/0/BRD_PWOFF: Board will be powered off for overtemperature. (BoardName=[STRING], EntityTrapFaultID=[ULONG])
Parameters
Parameter Name | Parameter Meaning |
---|---|
BoardName |
Indicates the entity name. |
EntityTrapFaultID |
Indicates the trap ID. |
Procedure
- Run the display fan command to check whether the fan module is installed properly.
- If so, go to step 2.
- If not, install the fan module properly.
- Rectify the fault according to "A Fan Fails" in the Troubleshooting Insights - Campus Switch - Hardware Fault.
ALML/0/BRD_PWOFF_RESUME
Message
ALML/0/BRD_PWOFF_RESUME:Board resume from power off. (BoardName=[STRING], EntityTrapFaultID=[ULONG])
Parameters
Parameter Name | Parameter Meaning |
---|---|
BoardName | Indicates the entity name. |
EntityTrapFaultID | Indicates the trap ID. |
ALML/4/CANBUSFAULT
ALML/4/CANBUSFAULT_RESUME
ALML/4/CANBUSNODELOST
Possible Causes
The system scans for CANbus nodes every 30s. If the system does not detect registration of a CANbus node or fails to obtain its software version after 10 detection intervals (5 minutes), the system determines that the CANbus node is lost.
Procedure
- Check whether the log ALML/6/CANBUSNODERESUME is generated.
- If so, the fault is rectified, and no action is required.
- If not, go to step 2.
- Restart the board where a CANbus node is lost and then check whether this log persists.
- If so, go to step 3.
- If not, the alarm handling ends.
- Replace this board and check whether this log persists.
- If so, collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
- If not, the alarm handling ends.
ALML/6/CANBUSNODERESUME
ALML/4/CANCOMFAIL
Message
ALML/4/CANCOMFAIL:SMS and CANbus node of [STRING] lost communication. You are recommended to perform a switchover.
Parameters
Parameter Name | Parameter Meaning |
---|---|
STRING | Information of the board where the CANbus node is located. For example, describe the information of a board through the board name, board type, or board slot ID. |
Possible Causes
- Reason 1: The system is busy. As a result, the CPU does not respond to the CANbus request for a long time.
- Reason 2: The FE link or CANbus hardware fails.
- Reason 3: There is no available power module among power modules PWR1 and PWR2 in Area A, power modules PWR3 and PWR4 in Area B, and power modules in the PoE area.
Procedure
- Run the display power command to check whether there are available power modules in the
corresponding power supply area.
- If so, go to step 2.
- If not, install available power modules in the corresponding power supply area.
- Check whether the recovery log ALML/4/CANCOMRESUME is generated
later in the log file.
- If so, the fault is rectified, and no action is required.
- If not, collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command..
ALML/4/CANCOMRESUME
ALML/3/CANNODEABSENT
ALML/4/CANNODEREG
ALML/3/CANNODE_POWEROFF
ALML/3/CANNODE_POWERON
ALML/3/CAN_SELFTEST_ERR
ALML/4/CAN_SELFTEST_OK
ALML/3/CHANNEL_FAULTY
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING] | Entity name |
[STRING] | Entity name |
[ULONG] | Channel No. |
Procedure
- Check whether the recovery log ALML/3/CHANNEL_NORMAL is generated later in the log file.
- If so, the fault is rectified, and no action is required.
- If not, go to step 2.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/3/CHANNEL_NORMAL
ALML/4/CHAN_POWER_LACK
Message
ALML/4/CHAN_POWER_LACK: [STRING] system power is insufficient. (UsedPower=[ULONG](W), TotalPower=[ULONG](W))
Parameters
Parameter Name | Parameter Meaning |
---|---|
UsedPower |
Indicates the used power. |
TotalPower |
Indicates the total power of the power supply system. |
Possible Causes
- The CMU has not registered.
- The power of the power supply system is insufficient for the switch.
Procedure
- Run the display device command to check whether the CMU has registered.
- If so, go to step 2.
- If not, wait until the CMU registers.
- Check whether the log SYSTEM_POWER_NORMAL is generated.
- If so, collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
- If not, replace the power supply system with one with higher power or run the power off command to power off unnecessary boards.
ALML/4/SYSTEM_POWER_NORMAL
Message
ALML/4/SYSTEM_POWER_NORMAL: [STRING] system power is recovered. (UsedPower=[ULONG](W), TotalPower=[ULONG](W))
Description
The rated power of the switch is lower than the maximum power of the power supply system.
ALML/4/CLOCKFAULT_RESUME
ALML/4/COMMLOSTLONG
Message
ALML/4/COMMLOSTLONG: The component in slot [STRING] has lost communication longer than an hour.
Possible Causes
Communication between the board and the system has been interrupted for more than an hour or there is no available power module among power modules PWR1 and PWR2 in Area A, power modules PWR3 and PWR4 in Area B, and power modules in the PoE area.
Procedure
- Run the display power command to check whether there are available power modules in the corresponding power supply area.
- If so, go to step 2.
- If not, install available power modules in the corresponding power supply area.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/6/COMMLOSTLONGRESUME
ALML/3/CPU_RESET
Procedure
- Check whether the board is reset for routine maintenance.
- If so, the alarm handling ends.
- If not, go to step 2.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/3/PKTERRORRISING
Message
ALML/3/PKTERRORRISING: Input packets are discarded for an error in physical layer detection. (SlotID=[STRING1], UnitID=[INTEGER], PortID=[STRING2], PeerSlotID=[STRING3], ErrorPacketStatistics=[STRING4], MonitorInterval=[STRING5])
Parameters
Parameter Name | Parameter Meaning |
---|---|
SlotID | Indicates the slot ID. |
UnitID | Indicates the chip ID. |
PortID | Indicates the port number of the HG channel. |
PeerSlotID | Indicates the slot ID of the remote card. |
ErrorPacketStatistics | Indicates the number of CRC error packets. |
MonitorInterval | Indicates the detection interval. |
Possible Causes
- The local or remote card is not securely installed.
- The local or remote card connector is faulty.
- The local or remote card is faulty.
Procedure
- Check whether the local and remote cards
are securely installed.
- If so, go to step 2.
- If not, install these cards securely.
- Remove the local and remote cards to check
whether there are bent pins on the backplane and connector.
- If so, go to step 4.
- If not, go to step 3.
- Replace the cards and check whether this
log persists.
- If so, go to step 4.
- If not, the alarm handling ends.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/3/DISCARD_PKT
Message
ALML/3/DISCARD_PKT: Packets are discarded for congestion. (SlotID=[STRING], UnitID=[INTEGER], PortID=[STRING], PeerSlotID=[STRING], DiscardNumber=[STRING], Threshold=[INTEGER], Interval=[INTEGER](s))
Parameters
Parameter Name | Parameter Meaning |
---|---|
SlotID |
Indicates the slot ID of the card where the inbound interface resides. |
UnitID |
Indicates a chip ID. |
PortID |
Indicates the port number of the HG channel. |
PeerSlotID |
Indicates the slot ID of the card where the outbound interface resides. |
DiscardNumber |
Indicates the number of discarded packets. |
Threshold |
Indicates the alarm threshold for the number of discarded packets. |
Interval |
Indicates the interval for collecting traffic statistics. |
Possible Causes
The number of packets received by the card where the inbound interface resides exceeds the forwarding capability of the card where the outbound interface resides. As a result, packets are discarded in the HG channel during inter-card forwarding.
- Cause 1: The inbound interface resides on an ES0D0G24SA00 or ES0D0G24CA00 card, and the card receives packets with CRC errors. As a result, packets are discarded in the HG channel during inter-card forwarding.
- Cause 2: The number of packets received by the card where the inbound interface resides exceeds the forwarding capability of the card where the outbound interface resides. As a result, packets are discarded in the HG channel during inter-card forwarding.
Procedure
- For cause 1, run the display device command to check whether the inbound interface resides on an ES0D0G24SA00 or ES0D0G24CA00 card.
- If so, go to step 2.
- If not, go to step 5.
- Run the display counters error command to check whether the card where the inbound interface resides receives packets with CRC errors based on the CRC field in the command output.
- If so, go to step 3.
- If not, go to step 5.
- If the interface receives packets with CRC errors, the optical module may be faulty. Replace the optical module and check whether the log is recorded.
- If so, go to step 4.
- If not, no further action is required.
- If the interface receives packets with CRC errors, the optical fiber may be faulty. Replace the optical fiber and check whether the log is recorded.
- If so, go to step 5.
- If not, no further action is required.
- For cause 2, check whether the packet forwarding capability of the card where the inbound interface resides exceeds that of the card where the outbound interface resides.
- If so, go to step 6.
- If not, go to step 7.
- Re-plan the network or replace one of the cards to ensure that the packet forwarding capability of the card where the outbound interface resides is not lower than that of the card where the inbound interface resides. After the card is replaced, check whether the log is recorded.
- If so, go to step 7.
- If not, no further action is required.
- Collect log information and configuration information, and then contact technical support personnel.You can collect diagnostic information using the display diagnostic-information command.
ALML/4/ENTPOWEROFF
Message
ALML/4/ENTPOWEROFF: [STRING1] is power off. The reason is: [STRING2], the barcode is: [STRING3].
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING1] | Information about the entity that is powered off. For example, describe information about a board through the board name, board type, or board slot ID. |
[STRING2] | Reason for power-off of an entity. |
Possible Causes
Reason 1:
The power off slot slot-id command is run to power off a board.
Reason 2:
After detecting that the power supply does not have enough power, the system powers off a board.
Procedure
- Check whether the board is powered off using the power off slot slot-id command for routine maintenance.
- If so, no action is required.
- If not, go to step 2.
- Check whether the board is powered off because of insufficient
power based on the log ALML/4/POWER_LACK.
- If so, the alarm handling ends.
- If not, collect log information and configuration information, and then contact technical support personnel.You can collect diagnostic information using the display diagnostic-information command.
ALML/4/ENTPOWERON
ALML/4/ENTRESET
Parameters
Parameter Name | Parameter Meaning |
---|---|
STRING1 | Information about the reset entity. For example, describe information about a board through the board name, board type, or board slot ID. |
STRING2 | Reason for reset of an entity. |
Possible Causes
- A board is reset using a reset command.
- The system runs abnormally. Cause 2 can be described in detail through the second parameter.
Procedure
- Check whether the device is manually reset using a reset
command.
- If so, no action is required. Wait until the device starts.
- If not, go to step 2.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/4/ENTRESETFAIL
Message
ALML/4/ENTRESETFAIL: [STRING1] is reset unsuccessfully. The reset reason is: [STRING2], the barcode is: [STRING3].
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING1] | Information about the entity that fails to be reset, including the board name, board type, and board slot ID. |
[STRING2] | Reason for reset failure of an entity. |
Procedure
- Manually reset the board to determine whether it can register
normally.
- If so, the alarm handling ends.
- If not, go to step 2.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/4/ENTUP
ALML/4/ENT_PLUG_IN
ALML/4/ENT_PULL_OUT
Parameters
Parameter Name | Parameter Meaning |
---|---|
STRING | Information about the removed entity. For example, describe information about a board through the board name, board type, or board slot ID. |
Possible Causes
- A board or a subcard is removed manually.
- The connection between a board or a subcard and the slot is loose.
Procedure
- Run the display device command to check whether the subcard or board is installed properly.
- If so, collect log information and configuration information, and then contact technical support personnel.You can collect diagnostic information using the display diagnostic-information command.
- If not, go to step 2.
- Check whether the subcard or board is removed manually.
- If so, no action is required.
- If not, install the subcard or board again.
ALML/4/FANDISMATCH
ALML/4/FANDISMATCHRESUME
ALML/4/FANFAULT
Procedure
- Rectify the fault according to "A Fan Fails" in the Troubleshooting Insights - Campus Switch - Hardware Fault.
ALML/4/FANFAULT_RESUME
ALML/4/FAN_LOWER
Message
ALML/4/FAN_LOWER:The "[STRING1]" sensor of [STRING2](entity) detects that the fan speed fell below the lower [STRING3] limit. (SensorNum=[ULONG], Value=[STRING4], UpperThreshold=[STRING5], LowerThreshold=[STRING6])
Parameters
Parameter Name | Parameter Meaning |
---|---|
STRING1 |
Sensor name |
STRING2 |
Entity name |
STRING3 |
Alarm severity |
SensorNum |
Sensor No. |
Value |
Fan speed |
UpperThreshold |
Fan speed upper threshold |
LowerThreshold |
Fan speed lower threshold |
Procedure
- Rectify the fault according to "A Fan Fails" in the Troubleshooting Insights - Campus Switch - Hardware Fault.
ALML/4/FAN_LOWER_RESUME
Message
ALML/4/FAN_LOWER_RESUME:The "[STRING1]" sensor of [STRING2](entity) detects that the fan speed increased above the lower [STRING3] limit. (SensorNum=[ULONG], Value=[STRING4], UpperThreshold=[STRING5], LowerThreshold=[STRING6])
ALML/4/FAN_MONITOR_FAIL
ALML/4/FAN_MONITOR_RESUME
ALML/4/FAN_NOELABEL
ALML/3/HG_ISOLATE
Message
Standalone mode:
ALML/3/HG_ISOLATE: Slot [ULONG] higig port isolation information. (SlotID=[ULONG], UnitID=[ULONG], PortID=hg[ULONG], PeerSlotID=[ULONG], PeerPortID=hg[ULONG], Description=HG link has turned into isolation state for [STRING])
ALML/3/HG_ISOLATE: Slot [STRING] higig port isolation information. (SlotID=[STRING], LogicPortID=hg[ULONG], PeerSlotID=[STRING], PeerPortID=hg[ULONG], Description=HG link has turned into isolation state for [STRING])
CSS mode:
ALML/3/HG_ISOLATE: Slot [STRING] higig port isolation information. (SlotID=[STRING], UnitID=[ULONG], PortID=hg[ULONG], PeerSlotID=[STRING], PeerPortID=hg[ULONG], Description=HG link has turned into isolation state for [STRING])
Parameters
Parameter Name | Parameter Meaning |
---|---|
Slot [ULONG] Slot [STRING] |
Indicates the slot ID where the fault occurred. |
SlotID |
Indicates the logical slot ID of the faulty Higig port. |
UnitID |
Indicates the chip ID for the logical slot ID where the faulty Higig port resides. |
LogicPortID |
Indicates the logical port ID of the faulty Higig port. |
PortID |
Indicates the faulty Higig port number. |
PeerSlotID |
Indicates the slot ID of the Higig port connected to the faulty Higig port. |
PeerPortID |
Indicates the port number of the Higig port connected to the faulty Higig port. |
[STRING] |
Indicates the fault cause. |
Possible Causes
Cause 1:
The Higig port went Down.
Cause 2:
A CRC error occurred on the Higig port.
Cause 3:
The Higig port frequently flapped between Up and Down states.
Procedure
- Check whether the recovery log ALML/4/HG_RELIEVE is generated later in the log file.
- If so, the fault is rectified, and no action is required.
- If not, go to step 2.
- Remove and then install the faulty board or reset it to check whether this log persists.
- If so, go to step 3.
- If not, the alarm handling ends.
- Run the display hg-fault information command in the diagnostic view to view detailed fault information.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/4/HG_RELIEVE
Message
Standalone mode:
ALML/4/HG_RELIEVE: Slot [ULONG] higig port relieve information. (SlotID=[ULONG], UnitID=[ULONG], PortID=hg[ULONG], PeerSlotID=[ULONG], PeerPortID=hg[ULONG], Description=HG link has turned into relievable state for [STRING])
ALML/4/HG_RELIEVE: Slot [STRING] higig port relieve information. (SlotID=[STRING], LogicPortID=hg[ULONG], PeerSlotID=[STRING], PeerPortID=hg[ULONG], Description=HG link has turned into relievable state for [STRING])
CSS mode:
ALML/4/HG_RELIEVE: Slot [STRING] higig port relieve information. (SlotID=[STRING], UnitID=[ULONG], PortID=hg[ULONG], PeerSlotID=[STRING], PeerPortID=hg[ULONG], Description=HG link has turned into relievable state for [STRING])
Parameters
Parameter Name | Parameter Meaning |
---|---|
Slot [ULONG] Slot [STRING] |
Indicates the ID of the slot that recovered from a fault. |
SlotID |
Indicates the logical slot ID of the Higig port that recovered from a fault. |
UnitID |
Indicates the chip ID for the logical slot ID of the Higig port that recovered from a fault. |
LogicPortID |
Indicates the logical port ID of the Higig port that recovered from a fault. |
PortID |
Indicates the port number of the Higig port that recovered from a fault. |
PeerSlotID |
Indicates the slot ID of the Higig port connected to the Higig port that recovered from a fault. |
PeerPortID |
Indicates the port number of the Higig port connected to the Higig port that recovered from a fault. |
[STRING] |
Indicates the fault recovery cause. |
ALML/4/HG_STATE
Message
ALML/4/HG_STATE: Higig port state has changed. (SlotID=[STRING1], UnitID=[INTEGER], PortID=[STRING2] has turned into [STRING3] state, PeerSlotID=[STRING4].)
Parameters
Parameter Name | Parameter Meaning |
---|---|
SlotID | Indicates the slot ID. |
UnitID | Indicates the chip ID. |
PortID | Indicates the port number of the HG channel. |
STRING3 | Indicates the port state of the HG channel. |
PeerSlotID | Indicates the slot ID of the remote card. |
Possible Causes
- The local or remote card is not securely installed.
- The local or remote card connector is faulty.
- The local or remote card is faulty.
Procedure
- Check whether the local and remote cards
are securely installed.
- If so, go to step 2.
- If not, install these cards securely.
- Remove the local and remote cards to check
whether there are bent pins on the backplane and connector.
- If so, go to step 4.
- If not, go to step 3.
- Replace the cards and check whether this
log persists.
- If so, go to step 4.
- If not, the alarm handling ends.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/4/HSB_SWITCH_CAUSE
Message
ALML/4/HSB_SWITCH_CAUSE:[STRING1] causes MPU board[ULONG] to reset. Switch cause code: [STRING2].
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING1] | Cause description of active/standby switchover. The specific causes are as follows:
|
[ULONG] | Slot ID of the active MPU |
[STRING2] | Cause code of active/standby switchover.
|
Possible Causes
Reason 1:
Forced reset is performed through the command line.
Reason 2:
The active MPU has insufficient memory.
Reason 3:
Task infinite loop occurs.
Reason 4:
A task is abnormal.
Reason 5:
Active/Standby switchover causes the active MPU to reset.
Reason 6:
An ECM channel fails.
Reason 7:
The communication of the CANbus is interrupted.
Reason 8:
The MPU is removed.
Procedure
- Check whether the active MPU is reset for routing maintenance.
- If so, the alarm handling ends.
- If not, go to step 2.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/4/IOFAULT_RESUME
ALML/5/LOGOUT
Message
ALML/5/LOGOUT:The user succeeded in logging out of output mode. (UserType=[STRING], Ip=[STRING], Command=[STRING])
Parameters
Parameter Name | Parameter Meaning |
---|---|
UserType |
Indicates the user type.
|
Ip |
Indicates the server IP address. |
Command |
Indicates the command used to exit from the redirection mode. |
ALML/4/LSWTEMP_LOWER
Message
ALML/4/LSWTEMP_LOWER: The temperature of fabric chip [STRING] fell below the lower minor limit. (Value=[STRING], UpperThreshold=[STRING], ResumeThreshold=[STRING])
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING] | Indicates the slot ID. |
Value | Indicates the current card temperature. |
UpperThreshold | Indicates the lower temperature threshold, which is 0°C and cannot be configured. |
ResumeThreshold | Indicates the lower temperature resume threshold, which is 3°C and cannot be configured. |
ALML/4/LSWTEMP_LOWER_RESUME
Message
ALML/4/LSWTEMP_LOWER_RESUME: The temperature of fabric chip [STRING] increased above the lower minor limit. (Value=[STRING], UpperThreshold=[STRING], ResumeThreshold=[STRING])
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING] | Indicates the slot ID. |
Value | Indicates the current card temperature. |
UpperThreshold | Indicates the lower temperature threshold, which is 0°C and cannot be configured. |
ResumeThreshold | Indicates the lower temperature resume threshold, which is 3°C and cannot be configured. |
ALML/4/LSWTEMP_UPPER
Message
ALML/4/LSWTEMP_UPPER: The temperature of fabric chip [STRING] exceeds the upper minor limit. This problem may be caused by poor ventilation, blocked air filter, fan failure, or idle slots without filler panels installed. (Value=[STRING], UpperThreshold=[STRING], ResumeThreshold=[STRING])
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING] | Indicates the slot ID. |
Value | Indicates the current card temperature. |
UpperThreshold | Indicates the upper temperature threshold, which is 110°C and cannot be configured. |
ResumeThreshold | Indicates the upper temperature resume threshold, which is 107°C and cannot be configured. |
Possible Causes
The device was not ventilated well, which caused heat unable to be dissipated.
The air filter was blocked by dust.
Vacant slots were not covered with filler panels.
The ambient temperature was high.
There were not enough fans in the switch.
One or more fans in the switch had failed.
Procedure
- Clean the air filter and remove the objects that block the air exhaust area (if any). Cover all vacant slots with filler panels to ensure efficient heat dissipation. Then check whether the alarm is cleared.
- Install an external cooling device.
- Check whether all fans are operating normally and add the number of fans.
- Run the display fan command to check whether any fan is operating abnormally. If some fans are operating abnormally, replace these fans.
- Contact technical support personnel.
ALML/4/LSWTEMP_UPPER_RESUME
Message
ALML/4/LSWTEMP_UPPER_RESUME: The temperature of fabric chip [STRING] fell below the upper minor limit. (Value=[STRING], UpperThreshold=[STRING], ResumeThreshold=[STRING])
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING] | Indicates the slot ID. |
Value | Indicates the current card temperature. |
UpperThreshold | Indicates the upper temperature threshold, which is 110°C and cannot be configured. |
ResumeThreshold | Indicates the upper temperature resume threshold, which is 107°C and cannot be configured. |
ALML/4/MASTER_TO_SLAVE
ALML/4/MEMSIZE_DIFF
Description
In the active/standby environment, the active and standby MPUs have different sizes of memory.
Parameters
Parameter Name | Parameter Meaning |
---|---|
ULONG1 | Size of memory of active MPU |
ULONG2 | Size of memory of standby MPU |
Procedure
- If the MPU that has smaller memory serves as the active MPU, the system can start normally. In this case, this log does not need to be processed.
- If the MPU that has larger memory serves as the active MPU, the standby MPU that has smaller memory cannot be started. You are advised to use the MPU that has smaller memory as the active MPU.
ALML/4/NVRAMFAILURE
ALML/6/NVRAMFAILURERESUME
ALML/3/OIDS_MERGE_FAIL
ALML/4/OLD_BOOT_SYN_END
ALML/4/OLD_BOOT_SYN_START
Message
ALML/4/OLD_BOOT_SYN_START: A board with version earlier than V2R1 is inserted into slot [STRING]. bootrom/bootload upgrade requires about 20 minutes. Do not reset, remove, or power off the board during the version upgrade.
Description
A card running a version prior to V200R001 is installed in the switch and needs to update its Bootrom/Bootload. The Bootrom/Bootload update will take about 20 minutes, during which the card cannot be reset, removed, or powered off.
Possible Causes
A card running a version prior to V200R001 is installed in the switch, whereas the switch is running V200R010 or a later version.
Procedure
- This alarm is informational and no action is required. After the Bootrom/Bootload update is complete, ALML/4/OLD_BOOT_SYN_END will be printed.
ALML/3/PEER_CHANNEL_FAULT
Parameters
Parameter Name | Parameter Meaning |
---|---|
ULONG1 | Slot ID of the peer board, for example, the peer board of the active MPU is the standby MPU. |
ULONG2 | Channel No. |
Procedure
- Check whether the recovery log ALML/3/PEER_CHANNEL_NORMAL is generated later in the log file.
- If so, the fault is rectified, and no action is required.
- If not, go to step 2.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/3/PEER_CHANNEL_NORMAL
ALML/4/POS_MISMATCH
Message
ALML/4/POS_MISMATCH: The temperature and fan noise in slot 6 are higher than other slots. Install the board into another slot. (SlotID=[STRING])
ALML/4/POWERSUPPLY_OFF
Procedure
- Check whether the power module is switched off manually.
- If so, turn on the power module.
- If not, go to step 2.
- Rectify the fault according to "A Power Module Cannot Provide Power" in the Troubleshooting Insights - Campus Switch - Hardware Fault.
ALML/4/POWER_LACK
Message
ALML/4/POWER_LACK:[STRING] cannot be powered on due to lack of power. (rating = [ULONG1](W), remain = [ULONG2](W))
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING] | Entity name |
[ULONG1] | Rated power of a board |
[ULONG2] | Remaining power of the system |
Procedure
- Check whether the tab of the power cable locking strap is incorrectly inserted into an air vent of the power module panel. If so, the power supply cannot work properly. You need to remove the tab from the air vent. If the log persists, go to the next step.
- Run the display device command in any view. If the Register field of the power supply displays Unregistered, this power supply fails to register. To ensure that the power supply registers successfully (that is, the Register field displays Registered), perform any of the following operations: remove and then install the power supply, remove and then install the monitoring unit, or replace the power supply. If the log persists, go to the next step.
- Increase the number of power supplies to improve the power. If the number of power supplies has reached the maximum value, replace the power supply with one providing higher power. If the log persists, go to the next step.
- Contact technical support personnel.
ALML/4/POWER_LACK_RESUME
ALML/4/POWERINVALID
Message
ALML/4/POWERINVALID:Power is invalid for some reason. (PhysicalName=[STRING], EntityTrapFaultID=[ULONG])
Parameters
Parameter Name | Parameter Meaning |
---|---|
PhysicalName | Indicates the entity name. |
EntityTrapFaultID | Indicates the trap ID. |
Procedure
- Rectify the fault according to "A Power Module Cannot Provide Power" in the Troubleshooting Insights - Campus Switch - Hardware Fault.
ALML/4/POWERINVALIDRESUME
ALML/0/POWER_DC1600_FAULT
ALML/0/POWER_DC1600_NORMAL
Message
ALML/0/POWER_DC1600_NORMAL:Power invalid for not supporting DC1600 resumed. (PhysicalName=[STRING])
Description
The alarm that the device has an unsupported 1600 W DC power module installed is cleared.
ALML/4/PUBLISH_EVENT
ALML/4/PWRFANABSENT
Procedure
- Check whether the fan board is installed securely.
- If so, go to step 2.
- If not, install the fan board securely.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/4/PWR_NOSUPPLY
Message
ALML/4/PWR_NOSUPPLY: The "[STRING1]" sensor[ULONG1] of [STRING2] detects power is online, but no supply.
Parameters
Parameter Name | Parameter Meaning |
---|---|
STRING1 | Indicates the sensor name. |
ULONG1 | Indicates the sensor ID. |
STRING2 | Indicates the card name. |
Procedure
- Check whether the power module is turned off manually.
- If so, turn on the power module.
- If not, go to step 2.
- Rectify the fault according to "A Power Module Cannot Provide Power" in the Troubleshooting Insights - Campus Switch - Hardware Fault.
ALML/4/PWR_NOSUPPLY_RESUME
ALML/4/RESOURCE_MODE_DIFF
Message
ALML/4/RESOURCE_MODE_DIFF:Resource modes mismatch. (Slot=[ULONG1], Tcamszie=[ULONG2], Cfgmode=[ULONG3], Curmode=[ULONG4])
Parameters
Parameter Name | Parameter Meaning |
---|---|
[ULONG1] | Slot ID of the board |
[ULONG2] | TCAM size |
[ULONG3] | Configuration mode |
[ULONG4] | Current mode |
ALML/4/RTC
ALML/4/SDFAILURE
ALML/6/SDRESUME
ALML/3/SFFAILURE
ALML/6/SFRESUME
ALML/4/SERDES_STATE
Message
ALML/4/SERDES_STATE: Serdes state has changed. (SlotID=[STRING1], UnitID=[INTEGER], PortID=[STRING2] has turned into [STRING3] state, PeerSlotID=[STRING4].)
Parameters
Parameter Name | Parameter Meaning |
---|---|
SlotID | Indicates the slot ID. |
UnitID | Indicates the chip ID. |
PortID | Indicates the Serdes port number. |
STRING3 | Indicates the Serdes port state. |
PeerSlotID | Indicates the slot ID of the remote card. |
Possible Causes
- The local or remote card is not securely installed.
- The local or remote card connector is faulty.
- The local or remote card is faulty.
Procedure
- Check whether the local and remote cards
are securely installed.
- If so, go to step 2.
- If not, install these cards securely.
- Remove the local and remote cards to check
whether there are bent pins on the backplane and connector.
- If so, go to step 4.
- If not, go to step 3.
- Replace the cards and check whether this
log persists.
- If so, go to step 4.
- If not, the alarm handling ends.
- Collect log information and configuration information, and then contact technical support personnel.You can collect diagnostic information using the display diagnostic-information command.
ALML/4/SLAVE_TO_MASTER
Possible Causes
Reason 1:
The slave switchover command is run to perform active/standby switchover.
Reason 2:
The active MPU resets after it becomes abnormal.
Procedure
- Check whether active/standby switchover is triggered using
the slave switchover command for routine maintenance
or triggered after the active MPU is removed and then installed or restarted.
- If so, no action is required.
- If not, go to step 2.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
ALML/4/SPU_VERCOMP_FAIL
ALML/4/TEMP_MONITOR_FAIL
ALML/4/TEMP_MONITOR_RESUME
ALML/4/TEMP_UPPER
Message
ALML/4/TEMP_UPPER:The "[STRING1]" temperature of sensor [STRING2](entity) exceeds the upper [STRING3] limit. This problem may be caused by poor ventilation, blocked air filter, fan failure, or idle slots without filler panels installed. (SensorNum=[ULONG], Value=[STRING4], UpperThreshold=[STRING5], LowerThreshold=[STRING6])
Description
The temperature sensor detects that the temperature exceeds the upper limit. This problem may be caused by poor ventilation, blocked air filter, fan failure, or vacant slots without filler panels installed.
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING1] | Indicates the name of temperature sensor. |
[STRING2] | Indicates the entity name. |
[STRING3] | Indicates the alarm severity. |
[ULONG] | Indicates the number of the temperature sensor. |
[STRING4] | Indicates the current temperature. |
[STRING5] | Upper limit of temperature |
[STRING6] | Indicates the lower limit of temperature. |
Possible Causes
The hot air in the equipment cannot be exhausted.
The air filter is blocked.
Vacant slots are not covered by filler panels.
The temperature of the environment where the device is located is high.
The number of fans on the device is insufficient.
A fan on the device is faulty.
The temperature of the chip is high.
Procedure
- Clean the air filter and remove the objects that block the air exhaust area (if any). Cover all vacant slots with filler panels to ensure efficient heat dissipation. Then check whether the alarm is cleared.
- If so, the alarm handling ends.
- If not, go to step 2.
- Check whether the ambient temperature is too high.
- If so, go to step 3.
- If not, go to step 4.
- Install an external cooling device. Then go to Step 4.
- Check whether all fan slots have fans installed.
- If so, go to step 6.
- If not, go to step 5.
- Install more fans on the device. Then go to Step 6.
- Run the display fan command to check whether any fan operates abnormally.
- If so, go to step 7.
- If not, go to step 8.
- Replace the abnormal fan. Then go to Step 8.
- Run the display temperature all command to check whether the card chip overheats.
- If so, collect log information and configuration information, and then contact technical support personnel.You can collect diagnostic information using the display diagnostic-information command.
- If not, the alarm handling ends.
ALML/4/TEMP_UPPER_RESUME
Message
ALML/4/TEMP_UPPER_RESUME:The "[STRING1]" temperature of sensor [STRING2](entity) fell below the upper [STRING3] limit. (SensorNum=[ULONG], Value=[STRING4], UpperThreshold=[STRING5], LowerThreshold=[STRING6])
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING1] |
Name of temperature sensor |
[STRING2] |
Entity name |
[STRING3] |
Alarm severity |
[ULONG] |
Sensor No. |
[STRING4] |
Current temperature |
[STRING5] |
Upper limit of temperature |
[STRING6] |
Lower limit of temperature |
ALML/4/UPLOAD_FILE
ALML/4/VLCS_NEAR_DEADLINE
Message
ALML/4/VLCS_NEAR_DEADLINE: Virtual license is near deadline, remain time is [INTEGER] days. (ItemName=[STRING])
Parameters
Parameter Name | Parameter Meaning |
---|---|
INTEGER | Remaining validity duration, in days. |
ItemName | Name of the control item. |
ALML/4/VOLT_LOWER
Message
ALML/4/VOLT_LOWER:The "[STRING1]" voltage of sensor [STRING2](entity) fell below the lower [STRING3] limit. (SensorNum=[ULONG], Value=[STRING4], UpperThreshold=[STRING5], LowerThreshold=[STRING6])
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING1] |
Name of voltage sensor |
[STRING2] |
Entity name |
[STRING3] |
Alarm severity |
[ULONG] |
Sensor No. |
[STRING4] |
Current voltage value |
[STRING5] |
Upper limit of voltage |
[STRING6] |
Lower limit of voltage |
Procedure
- Check whether the recovery log ALML/4/VOLT_LOWER_RESUME is generated later in the log file.
- If so, the fault is rectified, and no action is required.
- If not, go to step 2.
- Run the display voltage all command to view the voltage and lower voltage threshold on the board. Check whether the board is operating normally.
- If so, the alarm handling ends.
- If not, go to step 3.
- Check whether all boards are boards are abnormal.
- If so, restart the power module.
- If not, restart the corresponding boards.
- Check whether the voltage of the boards is within the normal range.
- If so, the alarm handling ends.
- If not, go to step 5.
- Replace the power module or board, and check whether the voltage of the board is within the normal range.
- If so, the alarm handling ends.
- If not, collect log information and configuration information, and then contact technical support personnel.You can collect diagnostic information using the display diagnostic-information command.
ALML/4/VOLT_LOWER_RESUME
Message
ALML/4/VOLT_LOWER_RESUME:The "[STRING1]" voltage of sensor [STRING2](entity) increased above the lower [STRING3] limit. (SensorNum=[ULONG], Value=[STRING4], UpperThreshold=[STRING5], LowerThreshold=[STRING6])
ALML/4/VOLT_MONITOR_FAIL
ALML/4/VOLT_MONITOR_RESUME
ALML/4/VOLT_UPPER
Message
ALML/4/VOLT_UPPER:The "[STRING1]" voltage of sensor [STRING2](entity) exceeds the upper [STRING3] limit. (SensorNum=[ULONG], Value=[STRING4], UpperThreshold=[STRING5], LowerThreshold=[STRING6])
Parameters
Parameter Name | Parameter Meaning |
---|---|
[STRING1] |
Name of voltage sensor |
[STRING2] |
Entity name |
[STRING3] |
Alarm severity |
[ULONG] |
Sensor No. |
[STRING4] |
Current voltage value |
[STRING5] |
Upper limit of voltage |
[STRING6] |
Lower limit of voltage |
Procedure
- Check whether any power module fails.
- If so, go to step 2.
- If not, go to step 3.
- Ensure that other power modules operate normally and replace the abnormal power module.
- Run the display voltage slot slot-id command to check whether the voltage of the board for which an alarm is generated is normal.
- If not, replace this board and go to step 4.
- If so, go to step 6.
- Check whether the alarm is cleared.
- If so, the alarm handling ends.
- If not, collect log information and configuration information, and then contact technical support personnel.You can collect diagnostic information using the display diagnostic-information command.
ALML/4/VOLT_UPPER_RESUME
Message
ALML/4/VOLT_UPPER_RESUME:The "[STRING1]" voltage of sensor [STRING2](entity) fell below the upper [STRING3] limit. (SensorNum=[ULONG], Value=[STRING4], UpperThreshold=[STRING5], LowerThreshold=[STRING6])
- ALML/4/V15_CPU_VOL_FAIL
- ALML/4/V15_CPU_VOL_RESUME
- ALML/4/48V_CHECK_FAULT
- ALML/4/48V_VOLTAGE_NORMAL
- ALML/0/ALL_CHANNEL_FAULTY
- ALML/0/ALL_CHANNEL_NORMAL
- ALML/4/BOARDTYPE_DIFF
- ALML/4/BOARDNOTPOWERON
- ALML/0/BRD_PWOFF
- ALML/0/BRD_PWOFF_RESUME
- ALML/4/CANBUSFAULT
- ALML/4/CANBUSFAULT_RESUME
- ALML/4/CANBUSNODELOST
- ALML/6/CANBUSNODERESUME
- ALML/4/CANCOMFAIL
- ALML/4/CANCOMRESUME
- ALML/3/CANNODEABSENT
- ALML/4/CANNODEREG
- ALML/3/CANNODE_POWEROFF
- ALML/3/CANNODE_POWERON
- ALML/4/CAN_READY
- ALML/3/CAN_SELFTEST_ERR
- ALML/4/CAN_SELFTEST_OK
- ALML/3/CHANNEL_FAULTY
- ALML/3/CHANNEL_NORMAL
- ALML/4/CHAN_POWER_LACK
- ALML/4/SYSTEM_POWER_NORMAL
- ALML/4/CLOCKFAULT
- ALML/4/CLOCKFAULT_RESUME
- ALML/4/COMMLOSTLONG
- ALML/6/COMMLOSTLONGRESUME
- ALML/3/CPU_RESET
- ALML/3/PKTERRORRISING
- ALML/3/DISCARD_PKT
- ALML/4/ENTPOWEROFF
- ALML/4/ENTPOWERON
- ALML/4/ENTRESET
- ALML/4/ENTRESETFAIL
- ALML/4/ENTUP
- ALML/4/ENT_PLUG_IN
- ALML/4/ENT_PULL_OUT
- ALML/4/ENTPOWERINVALID
- ALML/4/FANDISMATCH
- ALML/4/FANDISMATCHRESUME
- ALML/4/FANFAULT
- ALML/4/FANFAULT_RESUME
- ALML/4/FAN_LOWER
- ALML/4/FAN_LOWER_RESUME
- ALML/4/FAN_MONITOR_FAIL
- ALML/4/FAN_MONITOR_RESUME
- ALML/4/FAN_NOELABEL
- ALML/3/HG_ISOLATE
- ALML/4/HG_RELIEVE
- ALML/4/HG_STATE
- ALML/4/HSB_SWITCH_CAUSE
- ALML/4/IOFAULT
- ALML/4/IOFAULT_RESUME
- ALML/5/LOGOUT
- ALML/4/LSW2FSU_LINK_CHANGE
- ALML/4/LSW2FSU_LINK_STATE
- ALML/4/LSWTEMP_LOWER
- ALML/4/LSWTEMP_LOWER_RESUME
- ALML/4/LSWTEMP_UPPER
- ALML/4/LSWTEMP_UPPER_RESUME
- ALML/4/MASTER_TO_SLAVE
- ALML/4/MEMSIZE_DIFF
- ALML/4/NVRAMFAILURE
- ALML/6/NVRAMFAILURERESUME
- ALML/3/OIDS_MERGE_FAIL
- ALML/4/OLD_BOOT_SYN_END
- ALML/4/OLD_BOOT_SYN_START
- ALML/3/PEER_CHANNEL_FAULT
- ALML/3/PEER_CHANNEL_NORMAL
- ALML/4/POS_MISMATCH
- ALML/4/POWERSUPPLY_ON
- ALML/4/POWERSUPPLY_OFF
- ALML/4/POWER_LACK
- ALML/4/POWER_LACK_RESUME
- ALML/4/POWERINVALID
- ALML/4/POWERINVALIDRESUME
- ALML/0/POWER_DC1600_FAULT
- ALML/0/POWER_DC1600_NORMAL
- ALML/4/PUBLISH_EVENT
- ALML/4/PWRFANABSENT
- ALML/4/PWR_NOSUPPLY
- ALML/4/PWR_NOSUPPLY_RESUME
- ALML/4/RESOURCE_MODE_DIFF
- ALML/4/RTC
- ALML/4/RTC
- ALML/4/SDFAILURE
- ALML/6/SDRESUME
- ALML/4/SELFULL
- ALML/3/SFFAILURE
- ALML/6/SFRESUME
- ALML/4/SELFULL_RESUME
- ALML/4/SERDES_STATE
- ALML/4/SLAVE_TO_MASTER
- ALML/4/SPU_VERCOMP_FAIL
- ALML/4/TEMP_MONITOR_FAIL
- ALML/4/TEMP_MONITOR_RESUME
- ALML/4/TEMP_UPPER
- ALML/4/TEMP_UPPER_RESUME
- ALML/4/UPLOAD_FILE
- ALML/4/USBFAILURE
- ALML/6/USBFAILURERESUME
- ALML/4/VLCS_NEAR_DEADLINE
- ALML/2/VLCS_EXPIRED
- ALML/4/VOLT_LOWER
- ALML/4/VOLT_LOWER_RESUME
- ALML/4/VOLT_MONITOR_FAIL
- ALML/4/VOLT_MONITOR_RESUME
- ALML/4/VOLT_UPPER
- ALML/4/VOLT_UPPER_RESUME