Alcatel-Lucent 5620 - Page 120

3 — Troubleshooting using network alarms
3-78 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Name:
NeManagementAndTrapManagementMismat
ch
Type: communicationsAlarm (4)
Probable cause: neManagementChange
(817)
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
This user-defined alarm is raised
when the NE configuration is one of
the following:
• The Active Management IP is set
to Out Of Band, and the Primary
Route Preference is set to In
Band.
• The Active Management IP is set
to In Band, and the Primary
Route Preference is set to Out of
Band.
Name:
NodeAlreadyManagedOverAnotherProtocol
Type: discoveryControlAlarm (33)
Probable cause: nodeAlreadyDiscovered
(818)
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM tries to rediscover a
previously discovered NE using a
different IP version.
Name: NodeColdStart
Type: equipmentAlarm (3)
Probable cause: nodeColdStart (135)
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM receives a
SNMPv2-MIB.coldStart trap from an
NE.
Name: NodeRebooted
Type: equipmentAlarm (3)
Probable cause: nodeReboot (25)
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM detects an NE reboot based
on the latest NE sysUpTime value.
Name: NodeUpgraded
Type: configurationAlarm (11)
Probable cause: upgradedNodeVersion (140)
Severity: Info
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM detects an NE software
version upgrade.
Name: NodeVersionMismatch
Type: configurationAlarm (11)
Probable cause: DowngradedNodeVersion
(139)
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the
software version on an NE differs
from the version recorded for the NE
in the 5620 SAM database.
Name:
OutOfBandManagementConnectionDown
Type: communicationsAlarm (4)
Probable cause:
managementConnectionDown (111)
Severity: Critical
Object Type (class):
NodeDiscoveryControl
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM cannot reach a managed
NE using the ping function over an
out-of-band connection.
Name: PatchLevelMismatch
Type: softwareAlarm (19)
Probable cause: patchLevelMismatch (490)
Severity: Critical
Object Type (class): NmsSystem
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM primary main server
software patch level does not match
the standby main server software
patch level.
Alarm Attributes Additional information
(6 of 11)
Aug 2010
AAAD
8.0 R4