Alcatel-Lucent 5620 Troubleshooting Manual page 100

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name: InterfaceHelloAuthFailure
Alarm ID: 45
Type: authenticationAlarm (14)
Probable causes:
•
authTypeMismatch (45)
•
authFailure (46)
Alarm name: InterfaceHelloConfig
Alarm ID: 39
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)
Alarm name: InterfaceLsAckAuthFailure
Alarm ID: 49
Type: authenticationAlarm (14)
Probable causes:
•
authTypeMismatch (45)
•
authFailure (46)
Alarm name: InterfaceLsAckConfig
Alarm ID: 43
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)
(2 of 8)
3-62
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class): Interface
Domain: ospf
Self-clearing alarm raised: No
Severity: Warning
Object Type (class): Interface
Domain: ospf
Self-clearing alarm raised: No
Severity: Warning
Object Type (class): Interface
Domain: ospf
Self-clearing alarm raised: No
Severity: Warning
Object Type (class): Interface
Domain: ospf
Self-clearing alarm raised: No
November 2008 Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
A router uses the OSPF Hello protocol
to discover neighbors. Both the hello
authentication key and the hello
authentication type on a segment
must match. When the hello
authentication key is configured, it
applies to all levels that are
configured for the interface.
The hello authentication type
enables hello authentication at the
interface or level context. Ensure
that the authentication type
parameter values for the routing
interfaces are consistent.
The alarms may be raised when the
managed devices are negotiating
with OSPF neighbors after a link
failure or an OSPF configuration
change. In this case, manually clear
the alarm when the OSPF neighbor
status is Full.
—
—
Troubleshooting Guide 3HE 04244 AAAB Ed. 01