Alcatel-Lucent 5620 - Page 119

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-77
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Name: MemoryConsumption
Type: communicationsAlarm (4)
Probable cause: tooManyTrapsBuffered
(173)
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
The alarm is raised when one of the
following occurs
• The number of traps from a
particular NE that await
processing by the 5620 SAM
surpasses the NE red threshold
for trap memory management in
the 5620 SAM server
configuration.
• The global number of traps that
await processing by the
5620 SAM surpasses the yellow
threshold for trap memory
management in the 5620 SAM
server configuration.
Caution: Alcatel-Lucent strongly
recommends against modifying NE
trap management threshold values;
modifying these values can seriously
degrade 5620 SAM performance.
The alarm clears when one of the
following occurs.
• The number of traps from the NE
that await processing falls below
the NE red threshold.
• The global number of traps that
await processing falls below the
system yellow threshold. The NE
is resynchronized only if
required.
Name: MisconfiguredNode
Type: configurationAlarm (11)
Probable causes:
• persistOff (281)
• noSystemAddress (282)
• noIpv4Address (816)
Severity: Major
Object Type (class): Topology
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM tries to discover an NE that
is not properly configured for
management, for example, when
persistence is set to Off in the NE
BOF, or when the NE has no system
address.
Name: MissedStatsCollection
Type: communicationsAlarm (4)
Probable cause: noAuxiliaryServersAvailable
(256)
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when a 5620 SAM
main server cannot communicate
with any auxiliary server for NE
statistics collection during a
statistics poll.
Name: ModuleOutOfMemory
Type: equipmentAlarm (3)
Probable cause: outOfMemory (142)
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the
available NE memory is insufficient
for allocation to a task.
Alarm Attributes Additional information
(5 of 11)
Aug 2010
AAAD
8.0 R4