Alcatel-Lucent 5620 Troubleshooting Manual page 94

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name: ModuleOutOfMemory
Alarm ID: 180
Type: equipmentAlarm (3)
Probable cause: outOfMemory (142)
Alarm name: NodeColdStart
Alarm ID: 172
Type: equipmentAlarm (3)
Probable cause: nodeColdStart (135)
Alarm name: NodeRebooted
Alarm ID: 32
Type: equipmentAlarm (3)
Probable cause: nodeReboot (25)
Alarm name: NodeUpgraded
Alarm ID: 178
Type: configurationAlarm (11)
Probable cause: upgradedNodeVersion (140)
Alarm name: NodeVersionMismatch
Alarm ID: 177
Type: configurationAlarm (11)
Probable cause: DowngradedNodeVersion
(139)
Alarm name:
OutOfBandManagementConnectionDown
Alarm ID: 138
Type: communicationsAlarm (4)
Probable cause:
managementConnectionDown (111)
Alarm name:
PersistentIndexParametersMisconfigured
Alarm ID: 173
Type: configurationAlarm (11)
Probable cause:
persistentIndexConfigurationMismatch
(136)
Alarm name:
PhysicalLinkPortsMisconfigured
Alarm ID: 239
Type: configurationAlarm (11)
Probable cause:
physicalLinkPortsMisconfigured (181)
Alarm name: PollDeadlineMissed
Alarm ID: 240
Type: configurationAlarm (11)
Probable cause: tooManyItemsToPoll (183)
(4 of 8)
3-56
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Info
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Critical
Object Type (class):
NodeDiscoveryControl
Domain: netw
Self-clearing alarm raised: No
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: Yes
Severity: Minor
Object Type (class): PhysicalLink
Domain: netw
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
November 2008 Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
The alarm is raised when the
available NE memory is insufficient
for allocation to a task.
—
—
—
After an NE is downgraded, you must
unmanage and remanage it to attain
full NE functionality and to ensure
that the 5620 SAM database contains
current information about the NE.
—
The alarm is raised if persistence is
set to Off in the BOF.
The alarm can be raised when there
is a mismatch in MTU size between
link endpoints and ports. When the
MTU is configured to match, the
alarm is cleared.
—
Troubleshooting Guide 3HE 04244 AAAB Ed. 01