Alcatel-Lucent 5620 Troubleshooting Manual page 89

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