Alcatel-Lucent 5620 Troubleshooting Manual page 98

Service aware manager
Hide thumbs Also See for 5620:
Table of Contents

Advertisement

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name: TrapDestinationMisconfigured
Alarm ID: 33
Type: configurationAlarm (11)
Probable causes:
trapDestinationMisconfigured (26)
duplicateTrapLogId (27)
Alarm name: TrapMalformed
Alarm ID: 135
Type: communicationsAlarm (4)
Probable cause: trapSchemaMismatch (108)
Alarm name: TrapRateThresholdExceeded
Alarm ID: 412
Type: communicationsAlarm (4)
Probable cause:
trapRateGreaterThanConfigured (307)
Alarm name: UnmanageFailed
Alarm ID: 300
Type: discoveryControlAlarm (33)
Probable cause: unableToDeleteNode (231)
Alarm name: UnsupportedNode
Alarm ID: 288
Type: configurationAlarm (11)
Probable cause: unsupportedNode (219)
Alarm name:
UpgradedBuildVersionMismatch
Alarm ID: 174
Type: configurationAlarm (11)
Probable cause: upgradedImageNotBooted
(137)
Alarm name:
YellowAlarmThresholdReached
Alarm ID: 245
Type: communicationsAlarm (4)
Probable cause: tooManyAlarms (182)
(8 of 8)
3-60
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Critical
Object Type (class): NmsSystem
Domain: netw
Self-clearing alarm raised: No
Severity: Warning
Object Type (class):
NodeDiscoveryControl
Domain: netw
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class): Topology
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
November 2008
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
The SNMP trap destination
configured on the router is not
pointing to 5620 SAM.
The alarm is raised when an attempt
to unmanage an NE fails.
The alarm is raised during 5620 SAM
network discovery if the 5620 SAM
detects a network element running
an unsupported node software
version.
The alarm is raised for each
discovery rule element, based on the
combination of discovery rule ID and
the IP address of the device running
the unsupported software version.
The number of outstanding alarms
has reached the yellow threshold,
and non-critical alarms are being
discarded to keep below system
limits.
Troubleshooting Guide
3HE 04244 AAAB Ed. 01

Advertisement

Table of Contents
loading

Table of Contents