Alcatel-Lucent 5620 - Page 172

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