Alcatel-Lucent 5620 - Page 141

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-99
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Table 3-55 Domain: rip
Table 3-56 Domain: rmon
Name: NatL2AwSubUdpPortUsageHigh
Type: equipmentAlarm (3)
Probable cause: resourceFull (53)
Severity: Major
Object Type (class):
ResidentialSubscriberInstance
Domain: ressubscr
Implicitly cleared (self-clearing): Yes
The alarm is raised when the UDP
port usage of an L2-aware NAT
subscriber reaches the high or low
watermark.
Alarm Attributes Additional information
Name: GroupDown
Type: ProtocolAlarm (1)
Probable cause: protocolDown (1)
Severity: Critical
Object Type (class): Group
Domain: rip
Implicitly cleared (self-clearing): Yes
The alarm is raised when a RIP group
has an Operational State other than
Up, and the Administrative State is
Up.
Name: RipAuthenticationFailure
Type: authenticationAlarm (14)
Probable cause: authFailure (46)
Severity: Warning
Object Type (class): Interface
Domain: rip
Implicitly cleared (self-clearing): No
The alarm is raised when a peer
authentication failure occurs. The
alarm information includes the peer
address.
Name: RipAuthenticationMismatch
Type: authenticationAlarm (14)
Probable cause: authTypeMismatch (45)
Severity: Warning
Object Type (class): Interface
Domain: rip
Implicitly cleared (self-clearing): No
The alarm is raised when a peer
authentication mismatch occurs. The
alarm indicates the peer address.
Name: RipDown
Type: ProtocolAlarm (1)
Probable cause: protocolDown (1)
Severity: Critical
Object Type (class): Site
Domain: rip
Implicitly cleared (self-clearing): Yes
The alarm is raised when a RIP site
has an Operational State other than
Up, and the Administrative State is
Up.
Name: ripRouteMaxLimitReached
Type: ProtocolAlarm (1)
Probable cause: maxRouteReached (825)
Severity: Warning
Object Type (class): Site
Domain: rip
Implicitly cleared (self-clearing): Yes
The alarm is raised when the number
of RIP routes learned by an NE
exceeds the maximum specified in
the RIP configuration of the NE.
Alarm Attributes Additional information
Name: IncompleteConfig
Type: configurationAlarm (11)
Probable cause: incompleteConfig (225)
Severity: Major
Object Type (class): Event, Alarm
Domain: rmon
Implicitly cleared (self-clearing): Yes
The alarm is raised when an object is
created with default values but not
yet made active.
Name: MissingFallingEvent
Type: configurationAlarm (11)
Probable cause: incompleteConfig (225)
Severity: Major
Object Type (class): Alarm
Domain: rmon
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM cannot find the falling
event object that is named in an
RMON policy alarm definition.
(1 of 2)
Alarm Attributes Additional information
(2 of 2)
Aug 2010
AAAD
8.0 R4