Alcatel-Lucent 5620 - Page 66

3 — Troubleshooting using network alarms
3-24 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Table 3-5 Domain: autoconfig
Table 3-6 Domain: bgp
Alarm Attributes Additional information
Name: DeployProfileFailed
Type: configurationAlarm (11)
Probable cause: DeployProfileFailed (453)
Severity: Major
Object Type (class):
AutoProvisioning
Domain: autoconfig
Implicitly cleared (self-clearing): No
The alarm is raised when the
deployment of a script to a 7705 SAR
fails.
Alarm Attributes Additional information
Name: BgpDown
Type: ProtocolAlarm (1)
Probable cause: protocolDown (1)
Severity: Critical
Object Type (class): Site
Domain: bgp
Implicitly cleared (self-clearing): Yes
The alarm is raised when a BGP
instance has an Operational State
other than Up, and the
Administrative State is Up.
Name: HoldTimeInconsistent
Type: ProtocolAlarm (1)
Probable cause: holdTimeInconsistent (575)
Severity: Major
Object Type (class): Peer
Domain: bgp
Implicitly cleared (self-clearing): No
The alarm is raised when a BGP site
tries to establish a peering using a
hold time that is less than the
configured strict hold time. The
peering is rejected as a result.
Name: PeerConnectionDown
Type: ProtocolAlarm (1)
Probable cause: connectionDown (2)
Severity: Critical
Object Type (class): Peer
Domain: bgp
Implicitly cleared (self-clearing): Yes
The alarm is raised when a BGP peer
has a Connection State other than
Established, and the Administrative
State of the BGP peer is Up.
Name: PeerDown
Type: ProtocolAlarm (1)
Probable cause: protocolDown (1)
Severity: Critical
Object Type (class): Peer
Domain: bgp
Implicitly cleared (self-clearing): Yes
The alarm is raised when a BGP peer
has an Operational State other than
Up, and the Administrative State is
Up.
Name: PeerGroupDown
Type: ProtocolAlarm (1)
Probable cause: protocolDown (1)
Severity: Critical
Object Type (class): PeerGroup
Domain: bgp
Implicitly cleared (self-clearing): Yes
The alarm is raised when a BGP peer
group has an Operational State other
than Up, and the Administrative
State is Up.
Name: PrefixLimitExceeded
Type: ProtocolAlarm (1)
Probable cause: prefixLimitExceeded (4)
Severity: Critical
Object Type (class): Peer
Domain: bgp
Implicitly cleared (self-clearing): No
The alarm is raised when a BGP
instance learns the maximum
number of peer routes.
Name: PrefixLimitNearing
Type: ProtocolAlarm (1)
Probable cause: prefixLimitNearing (3)
Severity: Major
Object Type (class): Peer
Domain: bgp
Implicitly cleared (self-clearing): No
The alarm is raised when a BGP
instance learns 90 percent of the
maximum number of peer routes.
Aug 2010
AAAD
8.0 R4