Alcatel-Lucent 5620 Troubleshooting Manual page 171

Alarm
Name:
BgpRouteHighWatermarkPerRTargetReache
d
Type: topologyAlarm (34)
Probable cause:
tooManyBgpRouteForGivenRouteTarget
(411)
Name:
BgpRouteLowWatermarkPerRTargetReache
d
Type: topologyAlarm (34)
Probable cause:
tooLittleBgpRouteForGivenRouteTarget
(412)
Name:
BgpRouteRateThresholdPerRTargetReached
Type: topologyAlarm (34)
Probable cause: unstableVpnSite (413)
Name: BgpRouteRateThresholdReached
Type: topologyAlarm (34)
Probable cause:
tooManyBgpRouteForNextHop (408)
Name: CheckpointLimitAt75Percent
Type: configurationAlarm (11)
Probable cause: tooManyCheckpoints (337)
Name: CheckpointLimitReachedOrExceeded
Type: configurationAlarm (11)
Probable cause: tooManyCheckpointObjects
(837)
Name: IsisLspRateThresholdExceeded
Type: topologyAlarm (34)
Probable cause: unstableIGPNetwork (241)
Name: IsisLspThresholdExceeded
Type: topologyAlarm (34)
Probable cause: largeIGPNetwork (276)
Name: IsisReachabilityThresholdExceeded
Type: topologyAlarm (34)
Probable cause:
manyExternalLSAsFloodingIntoIGP (271)
(2 of 4)
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723 AAAD TQZZA Edition 01
Attributes
Severity: Major
Object Type (class): Cpaa
Domain: topology
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): Cpaa
Domain: topology
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): Cpaa
Domain: topology
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): Cpaa
Domain: topology
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class):
TopologyManager
Domain: topology
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class):
TopologyManager
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): Cpaa
Domain: topology
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): Cpaa
Domain: topology
Implicitly cleared (self-clearing): Yes
8.0 R4 Aug 2010
Troubleshooting Guide
3 — Troubleshooting using network alarms
Additional information
The alarm is raised when there are
too many BGP routes for a route
target.
The alarm is raised when there are
too few BGP routes for a route
target.
The alarm is raised when the BGP
route rate for a target reaches the
maximum threshold value for route
targets.
The alarm is raised when the BGP
route rate for a next hop exceeds the
maximum threshold value for next
hops.
The alarm is raised when the number
of check points reaches 75 percent of
the maximum allowed value.
The alarm is raised when the number
of check points reaches or exceeds
the maximum allowed value.
The alarm is raised when the IS-IS
LSP rate exceeds the maximum
allowed value because of an unstable
IGP network.
The alarm is raised when the number
of IS-IS LSPs exceeds the maximum
allowed value because of a large IGP
network.
The alarm is raised when the IS-IS
reachability value exceeds the
maximum allowed value because too
many external LSAs are flooding the
IGP.
3-129