Alcatel-Lucent 5620 - Page 171

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