Alcatel-Lucent 5620 - Page 160

3 — Troubleshooting using network alarms
3-118 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Table 3-68 Domain: sonetequipment
Alarm Attributes Additional information
Name: BerLineSignalDegradation
Type: communicationsAlarm (4)
Probable cause: berLineSignalDegradation
(74)
Severity: Major
Object Type (class):
SonetPortMonitorSpecifics
Domain: sonetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a SONET
port reports a line signal degradation
BER error. The alarm corresponds to
the lb2er-sd alarm on an NE.
Name: BerLineSignalFailure
Type: communicationsAlarm (4)
Probable cause: berLineSignalFailure (75)
Severity: Major
Object Type (class):
SonetPortMonitorSpecifics
Domain: sonetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a SONET
port reports a line signal degradation
BER error. The alarm corresponds to
the lb2er-sf alarm on an NE.
Name: LineAlarmIndicationSignal
Type: communicationsAlarm (4)
Probable cause: lineAlarmIndicationSignal
(70)
Severity: Major
Object Type (class):
SonetPortMonitorSpecifics
Domain: sonetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a SONET
port reports an LAIS error. The alarm
corresponds to the lais alarm on an
NE.
Name: LineErrorCondition
Type: communicationsAlarm (4)
Probable cause: lineErrorCondition (80)
Severity: Major
Object Type (class):
SonetPortMonitorSpecifics
Domain: sonetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a SONET
port reports a line error condition
that a remote NE raises because of
b1 errors received from the local NE.
The alarm corresponds to the lrei
alarm on an NE.
Name: LineRemoteDefectIndication
Type: communicationsAlarm (4)
Probable cause:
lineRemoteDefectIndication (71)
Severity: Major
Object Type (class):
SonetPortMonitorSpecifics
Domain: sonetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a SONET
port reports a line remote defect
indication error caused by an LOF,
LOC, or LOS condition. The alarm
corresponds to the lrdi alarm on an
NE.
Name: LossOfClock
Type: communicationsAlarm (4)
Probable cause: lossOfClock (69)
Severity: Major
Object Type (class):
SonetPortMonitorSpecifics
Domain: sonetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a SONET
port reports an LOC condition, which
causes the NE to set the port
Operational State to Down.
Name: RxSectionSynchronizationError
Type: communicationsAlarm (4)
Probable cause:
rxSectionSynchronizationError (79)
Severity: Major
Object Type (class):
SonetPortMonitorSpecifics
Domain: sonetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a SONET
port reports a section
synchronization failure. A section
synchronization failure occurs when
the S1 byte is inconsistent for eight
consecutive frames.
Name: SectionB1Error
Type: communicationsAlarm (4)
Probable cause: sectionB1Error (73)
Severity: Major
Object Type (class):
SonetPortMonitorSpecifics
Domain: sonetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a SONET
port reports a section error condition
that a remote NE raises because of
b1 errors received from the local NE.
The alarm corresponds to the lrei
alarm on an NE.
Name: SectionLossOfFrame
Type: communicationsAlarm (4)
Probable cause: sectionLossOfFrame (76)
Severity: Major
Object Type (class):
SonetPortMonitorSpecifics
Domain: sonetequipment
Implicitly cleared (self-clearing): Yes
The alarm is raised when a SONET
port reports a SLOF error. The alarm
corresponds to the slof alarm on an
NE.
(1 of 3)
Aug 2010
AAAD
8.0 R4