Alcatel-Lucent 5620 Troubleshooting Manual page 92

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name: DuplicateRouterIdProblem
Alarm ID: 411
Type: configurationAlarm (11)
Probable cause: duplicateRouterId (168)
Alarm name: EventsThrottled
Alarm ID: 356
Type: communicationsAlarm (4)
Probable cause: snmpDaemonOverloaded
(141)
Alarm name:
FrequentFullResyncsDueToTrapProblems
Alarm ID: 265
Type: communicationsAlarm (4)
Probable cause:
frequentFullResyncsDueToTrapProblems
(198)
Alarm name: FtpClientFailure
Alarm ID: 357
Type: communicationsAlarm (4)
Probable cause: ftpClientFailure (257)
Alarm name:
InBandManagementConnectionDown
Alarm ID: 139
Type: communicationsAlarm (4)
Probable cause:
managementConnectionDown (111)
Alarm name: JMSServerDown
Alarm ID: 360
Type: communicationsAlarm (4)
Probable cause: systemFailed (144)
(2 of 8)
3-54
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Major
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: Warning
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: Critical
Object Type (class): NmsSystem
Domain: netw
Self-clearing alarm raised: No
November 2008 Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
—
—
The managed device has sent a
number of SNMP traps to the
5620 SAM, and some of the traps
were lost, possibly because of
congestion in the Ethernet or IP
infrastructure.
The NE is therefore resynchronized
to ensure consistency between the
5620 SAM database and the node
database.
To prevent frequent
resynchronziations, SNMP traps may
be ignored for a set interval, during
which the NE is in stand-down mode.
The interval is displayed in the alarm
details. After the interval passes, a
resynchronization is performed. The
alarm text message indicates, in
seconds, when the next
resynchronization will be performed.
The alarm is cleared when the
managed device is taken out of
stand-down mode.
The alarm is raised when the NE
sends notification that a file transfer
operation initiated by the FTP client
has failed because of file
unavailability, interruption during
the file transfer, or a lack of
available storage space.
—
—
Troubleshooting Guide 3HE 04244 AAAB Ed. 01