Alcatel-Lucent 5620 Manual page 63

Alarm
Name: ARCInhibit (2886)
Type: configurationAlarm (11)
Probable cause: ArcInd (1098)
Name: DatabaseFileTransportFailure (2887)
Type: configurationAlarm (11)
Probable cause: DbFt (1099)
Name: DatabaseLocalCopyCreationfail
(2888)
Type: configurationAlarm (11)
Probable cause: DbFl (1100)
Name: DatabaseSyncFailed (2889)
Type: configurationAlarm (11)
Probable cause: DBMemtrf (1101)
Name: DbnotSyncd (2890)
Type: configurationAlarm (11)
Probable cause: DbUnSync (1102)
Name: FrameSizeProblem (37)
Type: configurationAlarm (11)
Probable cause: frameSizeProblem (33)
Name: Intrusion (3601)
Type: configurationAlarm (11)
Probable cause: Intrusion (1390)
Name: InvalidDatabase (2891)
Type: configurationAlarm (11)
Probable cause: DbInvalid (1103)
Name: InvalidTopology (2892)
Type: configurationAlarm (11)
Probable cause: InvalidTopo (1104)
(1 of 4)
Alcatel-Lucent 5620 Service Aware Manager, Release 9.0 R4
3HE 06513 AAAD TQZZA Edition 01
Table 2-2 Domain: netw
Attributes
Severity: Info
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
Severity: Minor
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Minor
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Minor
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Minor
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class):
StatefullConnectableInterface
Domain: netw
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
Severity: Minor
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
September 2011
Optical Alarm Reference
2 — 1830 PSS alarms
Description
The alarm is raised due to indefinite
inhibition mode of alarm report
control.
The alarm is raised when a database
file transport operation fails.
The alarm is raised when the
creation of a local database copy
fails.
The alarm is raised when database
synchronization fails.
The alarm is raised due to active and
standby main EC databases are not
sync.
The alarm is raised when a
provisioned MTU size value is greater
than the supported MTU size value.
The alarm is raised when the number
of invalid login attempts is excessive.
The alarm is raised when a database
is invalid.
The alarm is raised when topology
has misconfigured.
2-39