Ospf Down State Or No State Problems - Avaya 8800 Troubleshooting Manual

OSPF down state or no state problems

If no state information appears for a neighbor when you enter the show ip ospf
neighbor command, then the router has not received valid OSPF hello packets from the
neighbor.
If a neighbor appears in the down state, that neighbor is typically a manually-configured
neighbor (using the config ip ospf neighbor command). If the router does not receive
a hello packet from the manually-configured neighbor within the dead interval, or never
receives a hello packet, the neighbor appears in the down state. All OSPF neighbors that you
manually configure must be NBMA neighbors.
To troubleshoot OSPF neighbors in the down state or with no state, perform the following
procedure.
Procedure steps
1. To verify that OSPF is enabled on the local router and on the neighbor router, enter
2. To verify that OSPF is enabled on the local router interface and the neighbor router
3. To verify the reachability of the neighbor, enter the following command using the
4. To verify the reachability of the neighbor through the allSPFRouters address, enter
Troubleshooting
the following CLI command:
show ip ospf info
OR
enter the following ACLI command:
show ip ospf
Also, from the command output, verify that the router IDs are different on the local
router and the neighbor router.
interface, enter the following command using the CLI or ACLI:
show ip ospf interface
Also, from the command output, verify that the OSPF interfaces are not configured
as passive interfaces.
CLI or ACLI:
ping <neighbor-ip>
the following CLI command (and see whether the neighbor responds):
ping 224.0.0.5
OSPF troubleshooting
July 2013 361