Alcatel-Lucent 5620 - Page 89

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-47
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Name: OTUBitErrorRateSignalDegradation
Type: communicationsAlarm (4)
Probable cause:
BitErrorRateSignalDegradation (533)
Severity: Major
Object Type (class): OtuInterface
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports a BER-SD on an OTU-enabled
interface.
Name: OTUBitErrorRateSignalFail
Type: communicationsAlarm (4)
Probable cause: BitErrorRateSignalFail (534)
Severity: Critical
Object Type (class): OtuInterface
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports a BER-SF on an OTU-enabled
interface.
Name: OTUFECRxTxModeMismatch
Type: communicationsAlarm (4)
Probable cause: FECRxTxModeMismatch
(535)
Severity: Critical
Object Type (class): OtuInterface
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports a FEC Rx/Tx mode mismatch
on an OTU-enabled interface.
Name: OTUFECSignalDegradation
Type: communicationsAlarm (4)
Probable cause: FECSignalDegradation (536)
Severity: Major
Object Type (class): OtuInterface
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports a FEC-SD on an OTU-enabled
interface.
Name: OTUFECSignalFailure
Type: communicationsAlarm (4)
Probable cause: FECSignalFailure (537)
Severity: Major
Object Type (class): OtuInterface
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports a FEC-SF on an OTU-enabled
interface.
Name: OTUIncomingAlignmentError
Type: communicationsAlarm (4)
Probable cause: IncomingAlignmentError
(579)
Severity: Major
Object Type (class): OtuInterface
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports an ODU open connection
indication on an OTU-enabled
interface.
Name: OTULossOfClock
Type: communicationsAlarm (4)
Probable cause: LossOfClock (538)
Severity: Critical
Object Type (class): OtuInterface
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports an LOC on an OTU-enabled
interface.
Name: OTULossOfFraming
Type: communicationsAlarm (4)
Probable cause: LossOfFraming (539)
Severity: Critical
Object Type (class): OtuInterface
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports an LOF on an OTU-enabled
interface.
Name: OTULossOfMultiFrame
Type: communicationsAlarm (4)
Probable cause: LossOfMultiFrame (540)
Severity: Major
Object Type (class): OtuInterface
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports an LOM on an OTU-enabled
interface.
Name: OTULossOfSignal
Type: communicationsAlarm (4)
Probable cause: LossOfSignal (541)
Severity: Critical
Object Type (class): OtuInterface
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports an LOS on an OTU-enabled
interface.
Name: OTUODUAlarmIndicationSignal
Type: communicationsAlarm (4)
Probable cause: ODUAlarmIndicationSignal
(542)
Severity: Major
Object Type (class): OtuInterface
Domain: ethernetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a device
reports an ODU AIS on an
OTU-enabled interface.
Alarm Attributes Additional information
(2 of 4)
Aug 2010
AAAD
8.0 R4