Alcatel-Lucent 5620 Troubleshooting Manual page 72

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name: EquipmentDown
Alarm ID: 10
Type: equipmentAlarm (3)
Probable cause: inoperableEquipment (8)
Alarm name: EquipmentFailure
Alarm ID: 145
Type: equipmentAlarm (3)
Probable cause: fanFailure (116)
Alarm name: EquipmentInTest
Alarm ID: 11
Type: equipmentAlarm (3)
Probable cause: equipmentInTest (9)
Alarm name: EquipmentMismatch
Alarm ID: 9
Type: equipmentAlarm (3)
Probable cause: equipmentTypeMismatch
(7)
Alarm name: EquipmentRemoved
Alarm ID: 8
Type: equipmentAlarm (3)
Probable cause:
replaceableEquipmentRemoved (6)
Alarm name: FanTrayRemoved
Alarm ID: 569
Type: equipmentAlarm (3)
Probable cause: FanTrayRemoved (438)
Alarm name: FirmwareMismatchAlarm
Alarm ID: 146
Type: firmwareAlarm (26)
Probable causes:
•
bootRomVersionMismatch (119)
•
fpgaVersionMismatch (120)
Alarm name: FirmwareUpgradeAlarm
Alarm ID: 212
Type: firmwareAlarm (26)
Probable cause: firmwareUpgraded (169)
(8 of 10)
3-34
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Major
Object Type (class): Equipment
Domain: equipment
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): FanTray
Domain: equipment
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class): Equipment
Domain: equipment
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): Equipment
Domain: equipment
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): Equipment
Domain: equipment
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): FanTray
Domain: equipment
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): Card
Domain: equipment
Self-clearing alarm raised: Yes
Severity: Info
Object Type (class): Card
Domain: equipment
Self-clearing alarm raised: No
November 2008 Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
—
When the object type is
ControlProcessor, the failure cause
could be that the CPM did not boot.
When the object type is a Power
Supply Tray, the failure cause could
be that a trap is received from the
managed device when the:
•
device is discovered and the
power supply tray is out of
service
•
power supply tray of a
discovered device goes out of
service or the AC power shelf
sends a fault message
The alarm is cleared when the status
changes to OK.
The alarm is raised when the
equipment enters a diagnostic state.
—
—
—
A mismatch occurred between the
firmware version and the software
image on the router. The alarm lists
the expected version.
—
Troubleshooting Guide 3HE 04244 AAAB Ed. 01