Alcatel-Lucent 5620 Troubleshooting Manual page 136

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name:
ManagedRouteFailedRetryThresholdCrossed
Alarm ID: 397
Type: topologyAlarm (34)
Probable cause:
managedRouteCouldNotBeSetup (298)
Alarm name:
ManagedRouteRetryAttemptsExhausted
Alarm ID: 398
Type: topologyAlarm (34)
Probable cause:
managedRouteCouldNotBeSetup (298)
Alarm name:
OspfExternalLsaThresholdExceeded
Alarm ID: 372
Type: topologyAlarm (34)
Probable cause:
manyExternalLSAsFloodingIntoIGP (271)
Alarm name:
OspfInternalLsaRateThresholdExceededPer
Area
Alarm ID: 310
Type: topologyAlarm (34)
Probable cause: unstableIGPNetwork (241)
Alarm name:
OspfInternalLsaThresholdExceededPerArea
Alarm ID: 309
Type: topologyAlarm (34)
Probable cause: largeIgpNetwork (240)
Alarm name:
OspfLsaRateThresholdExceededPerRouter
Alarm ID: 308
Type: topologyAlarm (34)
Probable cause: unstableLinksOnRouter
(239)
(3 of 4)
3-98
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Major
Object Type (class): RouteManager
Domain: topology
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): RouteManager
Domain: topology
Self-clearing alarm raised: No
Severity: Major
Object Type (class): Cpaa
Domain: topology
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): Area
Domain: topology
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): Area
Domain: topology
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): Router
Domain: topology
Self-clearing alarm raised: Yes
November 2008 Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
The alarm is raised by the 5650 CPAM
when a managed route cannot be set
up after the number of attempts
specified by the cpamManagedRoute
problematicThresholdAlarmAfter
value in the nms-server.xml file.
The alarm is raised if the
cpamManagedRoute
problematicRetryStrategy value in
nms-server.xml is set to countdown.
The default
problematicRetryStrategy value of
reactive prevents the alarm from
being raised.
The alarm is raised by the 5650 CPAM
when it stops trying to set up a
managed route after the number of
attempts specified by the
cpamManagedRoute
problematicDeadAfter value in the
nms-server.xml file.
The alarm is raised if the
cpamManagedRoute
problematicRetryStrategy value in
nms-server.xml is set to countdown.
The default
problematicRetryStrategy value of
reactive prevents the alarm from
being raised.
—
—
—
—
Troubleshooting Guide 3HE 04244 AAAB Ed. 01