Alcatel-Lucent 5620 Troubleshooting Manual page 74

3 — Troubleshooting using network alarms
Alarm
Name: BWUtilizationExceededOnTunnel
Type: thresholdCrossed (6)
Probable cause: thresholdCrossed (12)
Name:
ForceQTagForwardingMisconfiguration
Type: configurationAlarm (11)
Probable cause:
forceQTagForwardingInconsistent (576)
Name: IsidMisconfiguration
Type: configurationAlarm (11)
Probable cause: isidInconsistent (446)
Alarm
Name: Ais
Type: communicationsAlarm (4)
Probable cause: ais (513)
Name: AncillaryPathLimitReached
Type: resourceAlarm (28)
Probable cause: resourceLimitReached
(131)
Name: AtcaFanFailure
Type: equipmentAlarm (3)
Probable cause: fanFailure (116)
Name: AtcaPowerSupplyFailure
Type: equipmentAlarm (3)
Probable cause: fanFailure (116)
Name: FanRPMAlarm
Type: equipmentAlarm (3)
Probable cause: fanFailure (116)
Name: LowTemperatureDetected
Type: environmentalAlarm (2)
Probable cause: equipmentOvercooled
(838)
(1 of 14)
3-32
Table 3-13 Domain: epipe
Attributes
Severity: Major
Object Type (class): Epipe
Domain: epipe
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class): Epipe
Domain: epipe
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class): Epipe
Domain: epipe
Implicitly cleared (self-clearing): Yes
Table 3-14 Domain: equipment
Attributes
Severity: Minor
Object Type (class): PhysicalPort
Domain: equipment
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class): DaughterCard
Domain: equipment
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class): Fan
Domain: equipment
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class): PowerSupply
Domain: equipment
Implicitly cleared (self-clearing): Yes
Severity: Info
Object Type (class): Fan
Domain: equipment
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class): Shelf
Domain: equipment
Implicitly cleared (self-clearing): Yes
Alcatel-Lucent 5620 Service Aware Manager, Release
Aug 2010
Troubleshooting Guide
Additional information
The alarm is raised when the per-CoS
or overall bandwidth utilization on a
tunnel exceeds the configured
threshold.
The alarm is raised when two I-sites
in a service use different Force Q Tag
Forwarding values.
The alarm is raised when Epipe
service sites that are bound to a PBB
backbone use different ISID values.
Additional information
The alarm is raised when an NE
reports an AIS condition on the Tx or
Rx circuit of a PDH tributary.
The alarm is raised when the
ancillary path bandwidth limit is
reached.
The alarm is raised when the
associated fan is not operationally
Up.
The alarm is raised when the
associated power supply is not
operationally Up.
The alarm is raised when the
associated fan alarm usage state is
not set to Normal.
The alarm is raised when the chassis
temperature exceeds the maximum
threshold value.
3HE 05723 AAAD TQZZA Edition 01
8.0 R4