Alcatel-Lucent 5620 Troubleshooting Manual page 172

3 — Troubleshooting using network alarms
Alarm
Name:
ManagedRouteFailedRetryThresholdCrossed
Type: topologyAlarm (34)
Probable cause:
managedRouteCouldNotBeSetup (298)
Name:
ManagedRouteRetryAttemptsExhausted
Type: topologyAlarm (34)
Probable cause:
managedRouteCouldNotBeSetup (298)
Name: OspfExternalLsaThresholdExceeded
Type: topologyAlarm (34)
Probable cause:
manyExternalLSAsFloodingIntoIGP (271)
Name:
OspfInternalLsaRateThresholdExceededPer
Area
Type: topologyAlarm (34)
Probable cause: unstableIGPNetwork (241)
Name:
OspfInternalLsaThresholdExceededPerArea
Type: topologyAlarm (34)
Probable cause: largeIgpNetwork (240)
Name:
OspfLsaRateThresholdExceededPerRouter
Type: topologyAlarm (34)
Probable cause: unstableLinksOnRouter
(239)
Name:
OspfLsaThresholdExceededPerRouter
Type: topologyAlarm (34)
Probable cause: routerAdvertisingManyLSAs
(273)
Name: TooManyCpaaForIsisLevel2
Type: configurationAlarm (11)
Probable cause: tooManyCpaaForIsisLevel2
(288)
(3 of 4)
3-130
Attributes
Severity: Major
Object Type (class): RouteManager
Domain: topology
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): RouteManager
Domain: topology
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class): Cpaa
Domain: topology
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): Area
Domain: topology
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): Area
Domain: topology
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): Router
Domain: topology
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): Router
Domain: topology
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class): Cpaa
Domain: topology
Implicitly cleared (self-clearing): Yes
Alcatel-Lucent 5620 Service Aware Manager, Release
Aug 2010
Troubleshooting Guide
Additional information
The alarm is raised when the
5650 CPAM cannot set up a managed
route 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 alarm is not raised if the
problematicRetryStrategy value is
set to the default of reactive.
The alarm is raised when the
5650 CPAM 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 alarm is not raised if the
problematicRetryStrategy value is
set to the default value of reactive.
The alarm is raised when the number
of OSPF external LSAs exceeds the
maximum threshold because a large
number of external LSAs flooding
into the IGP.
The alarm is raised when the OSPF
internal LSA rate for an area exceeds
the maximum allowed value because
of an unstable IGP network.
The alarm is raised when the number
of OSPF internal LSAs for an area
exceeds the maximum allowed value
because of a large IGP network.
The alarm is raised when the OSPF
LSA rate for an NE exceeds the
maximum allowed value because of
an unstable NE link.
The alarm is raised when the number
of OSPF LSAs for an NE exceeds the
maximum allowed value because the
NE advertises too many LSAs.
The alarm is raised when there are
too many 7701 CPAAs for IS-IS level
2.
3HE 05723 AAAD TQZZA Edition 01
8.0 R4