Alcatel-Lucent 5620 Troubleshooting Manual page 141

Service aware manager release 8.0
Hide thumbs Also See for 5620:
Table of Contents

Advertisement

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

Advertisement

Table of Contents
loading

Table of Contents