Alcatel 5620 Troubleshooting Manual page 65

Alarm name, ID, type, and default
probable cause
Name: Default Instance Inconsistency
ID: 68
Type: Configuration Alarm
Probable cause: Multiple Default Instances
Encountered
Name: Template Inconsistency
ID: 189
Type: Configuration Alarm
Probable cause: Template Policy Mismatch
Alarm name, ID, type, and default
probable cause
Name: Bgp Down
ID: 6
Type: Protocol Alarm
Probable cause: Protocol Down
Name: Peer Connection Down
ID: 2
Type: Protocol Alarm
Probable cause: connection Down (2)
Name: Peer Down
ID: 1
Type: Protocol Alarm
Probable cause: Protocol Down
Name: Peer Group Down
ID: 5
Type: Protocol Alarm
Probable cause: Protocol Down
Name: Prefix Limit Exceeded
ID: 4
Type: Protocol Alarm
Probable cause: Prefix Limit Exceeded
Name: Prefix Limit Nearing
ID: 3
Type: Protocol Alarm
Probable cause: Prefix Limit Nearing
Alcatel 5620 Service Aware Manager, Release 2.1 R2
May 2005 95-5887-01-00-B
Table 3-15 Policy domain alarms
Default Severity, object type
Severity: warning
Object type: Manager
Domain: policy
Severity: warning
Object type: Manager
Domain: policy
Table 3-16 Routing management: BGP domain alarms
Default Severity, object type
Severity: critical
Object type: Site
Domain: bgp
Severity: critical
Object type: Peer
Domain: bgp
Severity: critical
Object type: Peer
Domain: bgp
Severity: critical
Object type: Peer Group
Domain: bgp
Severity: major
Object type: Peer
Domain: bgp
Severity: warning
Object type: Peer
Domain: bgp
3 — Troubleshooting network alarms
Additional information
—
—
Additional information
—
—
—
—
The prefix-limit is the maximum
number of routes BGP can learn
from a peer.
—
3-29