EasyManua.ls Logo

Alcatel-Lucent 5620 - Page 74

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

Table of Contents