Alcatel-Lucent 5620 Troubleshooting Manual page 97

Alarm name, ID, type, and probable
cause(s)
Alarm name:
StatisticsCollectionThresholdExceeded
Alarm ID: 524
Type: communicationsAlarm (4)
Probable cause:
collectionRateGreaterThanConfigured (398)
Alarm name: svcFdbMimDestTableFull
Alarm ID: 588
Type: resourceAlarm (28)
Probable cause: resourceLimitReached
(131)
Alarm name: SystemMemoryConsumption
Alarm ID: 225
Type: communicationsAlarm (4)
Probable cause: tooManyTrapsBuffered
(173)
Alarm name: SystemNameChange
Alarm ID: 228
Type: equipmentAlarm (3)
Probable cause: systemNameChange (174)
Alarm name: TraceError
Alarm ID: 289
Type: equipmentAlarm (3)
Probable cause: traceError (221)
(7 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: Major
Object Type (class): NmsSystem
Domain: netw
Self-clearing alarm raised: No
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): NmsSystem
Domain: netw
Self-clearing alarm raised: No
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
—
—
The alarm is raised when the global
number of traps that await
processing by the 5620 SAM surpasses
the system red 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 is cleared when the
number of traps that await
processing falls below the system red
threshold. The NEs are
resynchronized only if required.
Review the alarm record for
additional information, including the
old system name and the new system
name.
The alarm is raised when problems
are raised on the managed devices.
For example, when IOM unusual error
log trace messages are generated on
the managed device.
The alarm indicates the title of the
logged event and details from the
message.
Alcatel-Lucent recommends that
when 5620 SAM operators receive
the alarm, they should:
•
open a Telnet or CLI session to
the managed device
•
review the error log trace history
files
•
contact node technical support
staff with details of the event
•
clear the alarm on 5620 SAM
November 2008 3-59