Alcatel-Lucent 5620 - Page 91

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-49
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Table 3-16 Domain: ethernetoam
Table 3-17 Domain: ethernettunnel
Name: WaveTrackerEncoderFailure
Type: communicationsAlarm (4)
Probable cause: EncoderFailure (585)
Severity: Major
Object Type (class):
WaveLengthTracker
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports an encoder failure on a
wavelength tracker interface.
Name: WaveTrackerPowerControlDegrade
Type: communicationsAlarm (4)
Probable cause: PowerControlDegrade (586)
Severity: Major
Object Type (class):
WaveLengthTracker
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports a power control degradation
on a wavelength tracker interface.
Name: WaveTrackerPowerControlFailure
Type: communicationsAlarm (4)
Probable cause: PowerControlFailure (587)
Severity: Critical
Object Type (class):
WaveLengthTracker
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports a power control failure on a
wavelength tracker interface.
Name: WaveTrackerPowerControlHighlimit
Type: communicationsAlarm (4)
Probable cause: PowerControlHighlimit
(588)
Severity: Major
Object Type (class):
WaveLengthTracker
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports a power control high limit on
a wavelength tracker interface.
Name: WaveTrackerPowerControllowlimit
Type: communicationsAlarm (4)
Probable cause: PowerControllowlimit (589)
Severity: Major
Object Type (class):
WaveLengthTracker
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports a power control low limit on
a wavelength tracker interface.
Alarm Attributes Additional information
Name: RemoteMepCCMAlarm
Type: oamAlarm (18)
Probable cause: missingRemoteMep (388)
Severity: Major
Object Type (class): Mep
Domain: ethernetoam
Implicitly cleared (self-clearing): Yes
The alarm is raised when a MEP loses
connectivity with one or more
remote MEPs. The Remote MEP DB
State tab on a MEP lists the missing
remote MEPs.
Alarm Attributes Additional information
Name: apsCfgRaiseAlarm
Type: configurationAlarm (11)
Probable cause: configurationMismatch
(548)
Severity: Major
Object Type (class):
EthernetTunnelEndpoint
Domain: ethernettunnel
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
5620 SAM detects a mismatch
between the working and protection
Ethernet tunnel group
configurations.
(1 of 2)
Alarm Attributes Additional information
(4 of 4)
Aug 2010
AAAD
8.0 R4