Alcatel-Lucent 5620 - Page 77

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-35
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Name: CardCPUAboveThreshold
Type: configurationAlarm (11)
Probable cause:
CardCPUUtilizationCrossedAboveThreshold
(458)
Severity: Major
Object Type (class): CardSlot
Domain: equipment
Implicitly cleared (self-clearing): No
The alarm is raised when the card
CPU usage exceeds the threshold
value.
Name: CardMemoryAboveThreshold
Type: configurationAlarm (11)
Probable cause:
CardMemoryUtilizationCrossedAboveThresh
old (459)
Severity: Major
Object Type (class): CardSlot
Domain: equipment
Implicitly cleared (self-clearing): No
The alarm is raised when the card
memory usage exceeds the threshold
value.
Name: CardRxAboveThreshold
Type: configurationAlarm (11)
Probable cause:
CardRxUtilizationCrossedAboveThreshold
(460)
Severity: Major
Object Type (class): CardSlot
Domain: equipment
Implicitly cleared (self-clearing): No
The alarm is raised when the card Rx
exceeds the threshold value.
Name: CardRxTxAboveThreshold
Type: configurationAlarm (11)
Probable cause:
CardRxTxUtilizationCrossedAboveThreshold
(461)
Severity: Major
Object Type (class): CardSlot
Domain: equipment
Implicitly cleared (self-clearing): No
The alarm is raised when the card Tx
exceeds the threshold value.
Name: ConfigNotCompatible
Type: equipmentAlarm (3)
Probable cause:
DaughterCardConfigNotCompatible (301)
Severity: Critical
Object Type (class): PhysicalPort
Domain: equipment
Implicitly cleared (self-clearing): No
The alarm is raised when an MDA
configuration is incompatible with
the MDA.
Name:
ContainingEquipmentAdministrativelyDown
Type: equipmentAlarm (3)
Probable cause:
containingEquipmentAdministrativelyDown
(330)
Severity: Minor
Object Type (class): Port
Domain: equipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
compositeEquipmentState attribute
has a value of
containingEquipmentAdministrativel
yDown.
Name: ContainingEquipmentMismatch
Type: equipmentAlarm (3)
Probable cause:
containingEquipmentMismatch (328)
Severity: Major
Object Type (class): Port
Domain: equipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
compositeEquipmentState attribute
has a value of
containingEquipmentMismatch.
Name: ContainingEquipmentMissing
Type: equipmentAlarm (3)
Probable cause:
containingEquipmentMissing (327)
Severity: Major
Object Type (class): Port
Domain: equipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
compositeEquipmentState attribute
has a value of
containingEquipmentMissing.
Name:
ContainingEquipmentOperationallyDown
Type: equipmentAlarm (3)
Probable cause: containingEquipmentDown
(329)
Severity: Major
Object Type (class): Port
Domain: equipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
compositeEquipmentState attribute
has a value of
containingEquipmentOperationllyDo
wn.
Name: DataLossAlarm
Type: storageAlarm (25)
Probable cause: dataLoss (122)
Severity: Major
Object Type (class): FlashMemory
Domain: equipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
detects an error while writing to a
compact flash unit.
Alarm Attributes Additional information
(4 of 14)
Aug 2010
AAAD
8.0 R4