Alcatel-Lucent 5620 - Page 64

2 — 1830 PSS alarms
2-40 September 2011 Alcatel-Lucent 5620 Service Aware Manager, Release 9.0 R4
Optical Alarm Reference 3HE 06513 AAAD TQZZA Edition 01
Name: LostReference (2893)
Type: configurationAlarm (11)
Probable cause: sync (1105)
Severity: Minor
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised due to lost of
redundant reference of system time.
Name: LostTimingReferences (2894)
Type: configurationAlarm (11)
Probable cause: SyncOos (1106)
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
The alarm is raised due to lost of
refererences of system time.
Name: NodeDatabaseFallbackDetected
(2923)
Type: communicationsAlarm (4)
Probable cause: nodeDatabaseFallback
(1121)
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
This alarm is raised when a
configuration fallback has been
detected on the node and comes
back up with a previous
configuration. To correct this
situation it might be necessary to
reconfigure the node, or full resync
its database with the 'fallback'
configuration returned by the node.
Name: NodeDatabaseMisalignmentDetected
(2924)
Type: communicationsAlarm (4)
Probable cause: nodeDatabaseMisalignment
(1122)
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
This alarm is raised when a
configuration misalignment has been
detected on the node and comes
back up with an unexpected
configuration (configuration change
triggered by external tool, i.e.: NEM)
To correct this situation it might be
necessary to reconfigure the node
with the SAM's old configuration or
accepting the new configuration
received from the node.
Name: NTPServerNotReachable (2896)
Type: configurationAlarm (11)
Probable cause: NTPooSync (1107)
Severity: Info
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the
network timing protocol is out of
sync.
Name: PollerProblem (31)
Type: communicationsAlarm (4)
Probable cause: resyncFailed (24)
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
The alarm is raised when the 5620
SAM is unable to poll a network
object, for example, because of
intermittent or no IP connectivity to
an NE, incorrect SNMP security
parameters, or disabled SNMP on the
NE.
Alarm Attributes Description
(2 of 4)