Alcatel-Lucent 5620 - Page 128

3 — Troubleshooting using network alarms
3-86 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Name: InterfaceNullPacketAuthFailure
Type: authenticationAlarm (14)
Probable causes:
• authTypeMismatch (45)
• authFailure (46)
Severity: Warning
Object Type (class): Interface
Domain: ospf
Implicitly cleared (self-clearing): No
The alarm is raised when an NE
receives a null packet on a
non-virtual interface from an NE
whose authentication key or
authentication type conflicts with
the local NE authentication key or
authentication type.
Name: InterfaceNullPacketConfig
Type: configurationAlarm (11)
Probable causes:
• badVersion (35)
• areaMismatch (36)
• unknownNbmaNbr (37)
• unknownVirtualNbr (38)
• netMaskMismatch (39)
• helloIntervalMismatch (40)
• deadIntervalMismatch (41)
• optionMismatch (42)
• mtuMismatch (43)
• noError (44)
• duplicateRouterId (168)
• ifTypeMismatch (187)
• nullRouterId (188)
• ifAdminDown (834)
• ifPassive (835)
Severity: Warning
Object Type (class): Interface
Domain: ospf
Implicitly cleared (self-clearing): No
The alarm is raised when an NE
receives a null packet on a
non-virtual interface from an NE
whose configuration parameters
conflict with the local NE
configuration parameters.
Name: InterfaceRxBadPacket
Type: communicationsAlarm (4)
Probable causes:
• hello (47)
• dbDescript (48)
• lsReq (49)
• lsUpdate (50)
• lsAck (51)
• nullPacket (52)
Severity: Warning
Object Type (class): Interface
Domain: ospf
Implicitly cleared (self-clearing): No
The alarm is raised when an NE
cannot parse an OSPF packet that it
receives on a non-virtual interface.
Name: LsdbOverflow
Type: equipmentAlarm (3)
Probable cause: resourceFull (53)
Severity: Major
Object Type (class): Site
Domain: ospf
Implicitly cleared (self-clearing): No
The alarm is raised when the number
of received external LSAs exceeds
the configured number allowed. By
default, there is no limit. The alarm
information includes the configured
LSDB limit and one of the following
LSDB overflow states:
• 0, which means no overflow
• 1, which means nearing limit
• 2, which means limit exceeded
Name: NeighborDown
Type: NeighborDown (20)
Probable cause: NeighborDown (103)
Severity: Major
Object Type (class):
AbstractNeighbor
Domain: ospf
Implicitly cleared (self-clearing): Yes
The alarm is raised when an OSPF
interface neighbor is operationally
down.
Alarm Attributes Additional information
(4 of 12)
Aug 2010
AAAD
8.0 R4