An OSPF adjacency with the indicated neighboring router was terminated. The local router no longer exchanges routing information with, or directs traffic to, the neighboring router. This message is generated by the routing protocol process (rpd) which controls the routing protocols that run on the router.
The RPD_OSPF_NBRDOWN message is logged each time an OSPF adjacency with a neighbor router is terminated.
When an RPD_OSPF_NBRDOWN event occurs, a message similar to the following is reported:
rpd: RPD_OSPF_NBRDOWN: OSPF neighbor xx.xx.xx.xx (ae0.653) state changed from Full to Init due to 1WayRcvd (event reason: neighbor is in one-way mode)
rpd: RPD_OSPF_NBRDOWN: OSPF neighbor xx.xx.xx.xx (realm ospf-v2 xe-1/3/1.0 area 0.0.0.0) state changed from Full to Down due to InActiveTimer (event reason: BFD session timed out and neighbor was declared dead)
rpd: RPD_OSPF_NBRDOWN: OSPF neighbor fe80::280:42ff:fe11:e415 (so-0/0/0.10) state changed from Full to Down due to KillNbr (event reason: interface went down)
The cause of the OSPF adjacency going down is due to one or more of the following reasons:
- BFD timeout
- Interface goes down
- Class-of-service configuration interfering with OSPF protocol traffic
- PIC or FPC in a hardware state that is not allowing OSPF traffic
- Neighbor router is no longer responsive to OSPF messages
Perform these steps to determine the cause and resolve the problem (if any):
1. Collect the show command output to help determine the cause of this message.
Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.
show log chassisd
show log messages
2. Analyze the show command output. Look for any related events that occurred at or just before the RPD_OSPF_NBRDOWN message. Check class-of-service and BFD configurations, if used, to verify they will not affect OSPF traffic.
3. Check the neighbor router for OSPF functionality, as the issue may be entirely with that device.
4. During a maintenance window, as it will impact transit traffic, try the following:
- Verify that the physical connection between OSPF neighbors is good.
- Run a loopback test on the PIC on each end.
- Run a rapid ping test between the two neighbor devices.
- Reseat the PIC.
- Reseat the FPC that holds the PIC.