Alcatel-Lucent 5620 Troubleshooting Manual page 93

Alarm name, ID, type, and probable
cause(s)
Alarm name:
ManagementInterfaceProtectionSwitch
Alarm ID: 34
Type: communicationsAlarm (4)
Probable causes:
•
switchToSecondary (28)
•
switchToPrimary (29)
Alarm name: MemoryConsumption
Alarm ID: 216
Type: communicationsAlarm (4)
Probable cause: tooManyTrapsBuffered
(173)
Alarm name: MisconfiguredNode
Alarm ID: 382
Type: configurationAlarm (11)
Probable causes:
•
persistOff (281)
•
noSystemAddress (282)
Alarm name: MissedStatsCollection
Alarm ID: 355
Type: communicationsAlarm (4)
Probable cause: noAuxiliaryServersAvailable
(256)
(3 of 8)
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
3HE 04244 AAAB Ed. 01
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): Topology
Domain: netw
Self-clearing alarm raised: No
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
When a network element has dual
management interfaces (in-band and
out-of-band), the alarm indicates a
switch from out-of-band
management to in-band
management or vice versa.
The alarm is raised in the following
situations.
•
The number of traps from a
particular NE that await
processing by the 5620 SAM
surpasses the NE red threshold
for trap memory management
specified in the base
configuration of the 5620 SAM
server.
•
The global number of traps that
await processing by the
5620 SAM surpasses the yellow
threshold for trap memory
management specified in the
base configuration of the
5620 SAM server.
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 conditions is met.
•
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.
—
—
November 2008 3-55