OSPF/3/NBR_DOWN_REASON

Message

OSPF/3/NBR_DOWN_REASON: Neighbor state left full or changed to Down. (ProcessId=[ProcessId], NeighborRouterId=[NbrRouterId], NeighborIp=[NbrIp], NeighborAreaId=[NbrAreaId], NeighborInterface=[IfName], NeighborDownImmediate reason=[NbrImmReason], NeighborDownPrimeReason=[NbrPriReason], CpuUsage=[CpuUsage]%, VpnName=[VpnName], IfMTU=[IfMTU], LocalIp=[LocalIp])

Description

Neighbor state leaves full or changed to Down.

Parameters

Parameter Name	Parameter Meaning
ProcessId	Indicates OSPF process ID.
NbrRouterId	Indicates neighbor router id.
NbrIp	Indicates neighbor ip address.
NbrAreaId	Indicates neighbor area id.
IfName	Indicates interface name.
NbrImmReason	Direct reason why the OSPF neighbor goes Down: Neighbor Down Due to Inactivity: indicates that no Hello packet is received from the OSPF neighbor within the dead time. Neighbor Down Due to LL Down LLDown: indicates that no LLD packet is received from the OSPF neighbor within the dead time. Neighbor Down Due to Kill Neighbor: indicates that the interface is Down, the BFD session is Down, or the reset ospf process command is run. To check the detailed cause, see the NeighborDownPrimeReason field. Neighbor Down Due to 1-Wayhello Received or Neighbor Down Due to SequenceNum Mismatch: indicates that the remote end sends a 1-Way Hello packet to the local end after the OSPF status is Down on the remote end, causing the OSPF status on the local end to go Down. Neighbor Down Due to AdjOK?: indicates that the AdjOK event times out. Neighbor Down Due to BadLSreq: indicates that the BadLSReq event times out in the neighbor state machine.
NbrPriReason	Primary reason that the neighbor goes Down
CpuUsage	CPU usage.
VpnName	VPN instance name.
IfMTU	Interface MTU.
LocalIp	Local interface ip address.

Possible Causes

Neighbor state change because OSPF packet impact or some action impact.

Procedure

This log message is informational only, and no action is required.