Alcatel-Lucent 5620 Troubleshooting Manual page 75

Alarm name, ID, type, and probable
cause(s)
Alarm name: EthernetPortNoFrameLock
Alarm ID: 306
Type: communicationsAlarm (4)
Probable cause: NoFrameLock (237)
Alarm name: EthernetPortRemoteFault
Alarm ID: 304
Type: communicationsAlarm (4)
Probable cause: RemoteFault (235)
Alarm name: EthernetPortSignalFailure
Alarm ID: 303
Type: communicationsAlarm (4)
Probable cause: SignalFailure (234)
Alarm name:
TmnxEqPortEtherLoopDetected
Alarm ID: 461
Type: portEtherLoopDetected (48)
Probable cause: HighBer (238)
(2 of 2)
Alarm name, ID, type, and probable
cause(s)
Alarm name: RemoteMepCCMAlarm
Alarm ID: 502
Type: oamAlarm (18)
Probable cause: missingRemoteMep (388)
Alarm name, ID, type, and probable
cause(s)
Alarm name: LogLocFailure
Alarm ID: 340
Type: storageAlarm (25)
Probable causes:
•
AdminLocFailure (244)
•
BackupLocFailure (245)
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
3HE 04244 AAAB Ed. 01
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Major
Object Type (class):
EthernetPortSpecifics
Domain: ethernetequipment
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class):
EthernetPortSpecifics
Domain: ethernetequipment
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class):
EthernetPortSpecifics
Domain: ethernetequipment
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class):
EthernetPortSpecifics
Domain: ethernetequipment
Self-clearing alarm raised: Yes
Table 3-13 Domain: ethernetoam
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Major
Object Type (class): Mep
Domain: ethernetoam
Self-clearing alarm raised: Yes
Table 3-14 Domain: file
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Variable or indeterminate
Object Type (class): Policy
Domain: file
Self-clearing alarm raised: No
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
—
—
—
—
Additional information
—
Additional information
The alarm is raised when an attempt
to create a log or billing file fails.
The probable cause is
AdminLocFailure when using the
admin location fails, in which case
the backup location, if specified, is
used instead.
The probable cause is
BackupLocFailure when using the
backup location fails.
November 2008 3-37