Alcatel-Lucent 5620 Troubleshooting Manual page 135

Alarm name, ID, type, and probable
cause(s)
Alarm name:
BgpRouteLowWatermarkPerRTargetReache
d
Alarm ID: 434
Type: topologyAlarm (34)
Probable cause:
tooLittleBgpRouteForGivenRouteTarget
(412)
Alarm name:
BgpRouteRateThresholdPerRTargetReached
Alarm ID: 435
Type: topologyAlarm (34)
Probable cause: unstableVpnSite (413)
Alarm name:
BgpRouteRateThresholdReached
Alarm ID: 429
Type: topologyAlarm (34)
Probable cause:
tooManyBgpRouteForNextHop (408)
Alarm name: CheckpointLimitAt75Percent
Alarm ID: 425
Type: configurationAlarm (11)
Probable cause: tooManyCheckpoints (337)
Alarm name:
CheckpointLimitReachedOrExceeded
Alarm ID: 426
Type: configurationAlarm (11)
Probable cause: tooManyCheckpoints (337)
Alarm name: IsisLspRateThresholdExceeded
Alarm ID: 376
Type: topologyAlarm (34)
Probable cause: unstableIGPNetwork (241)
Alarm name: IsisLspThresholdExceeded
Alarm ID: 375
Type: topologyAlarm (34)
Probable cause: largeIGPNetwork (276)
Alarm name:
IsisReachabilityThresholdExceeded
Alarm ID: 377
Type: topologyAlarm (34)
Probable cause:
manyExternalLSAsFloodingIntoIGP (271)
(2 of 4)
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
3HE 04244 AAAB Ed. 01
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Major
Object Type (class): Cpaa
Domain: topology
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): Cpaa
Domain: topology
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): Cpaa
Domain: topology
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class):
TopologyManager
Domain: topology
Self-clearing alarm raised: No
Severity: Major
Object Type (class):
TopologyManager
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): Cpaa
Domain: topology
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): Cpaa
Domain: topology
Self-clearing alarm raised: Yes
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
—
—
—
—
—
—
—
—
November 2008 3-97