Ospf Init State Problems - Avaya 8800 Troubleshooting Manual

Unicast routing troubleshooting
5. Verify that the following parameters are configured to the same values on both
6. Verify that the following parameters are configured to the same values on both
7. Verify that configured access lists are not affecting OSPF or IP traffic between the

OSPF Init state problems

A router can be stuck in Init state and not form an adjacency. There are several possible causes
for this type of problem:
• Inverse Address Resolution Protocol (ARP) misconfiguration
• Access Lists implemented on routers
• Authentication mismatch or configuration problem
Check that the path is not reachable due to access lists implemented on routers. Ensure the
multicast address of 224.0.0.5 is able to traverse the link. If multicast traffic is blocked, you
must to configure the Avaya Ethernet Routing Switch 8800/8600 for OSPF NBMA instead of
Broadcast.
Problems arise if there is a mismatch in authentication keys, or if both sides are not configured
for authentication.
1. In the CLI, to determine if there is an authentication problem, view the OSPF packets
2. In the ACLI, view the OSPF packets by using the following commands:
362 Troubleshooting
interfaces: subnet, hello interval, and dead interval. To display these parameters,
enter the following command using the CLI or ACLI:
show ip ospf int-timers
interfaces: area ID, area type (for example, stub or NSSA). To display these
parameters, enter the following command using the CLI or ACLI:
show ip ospf area
neighbors. To display the ACL configuration, enter the following command using
the CLI or ACLI:
show filter acl config
that are received by using the following commands:
trace level 6 2
trace screen on
The following example shows the error received when there is an authentication
failure:
[03/24/03 15:55:07:216] tMainTask OSPF: os_recv.c : 710 :
verify_ospf_packet: authType mismatch
trace level 6 2
trace screen enable
Comments? infodev@avaya.com
ipa= 10.1.1.18
July 2013