No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Log Reference

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document supports all the logs of device, including the parameters, meaning, possible causes and solution.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
OSPF/3/NBR_DOWN_REASON

OSPF/3/NBR_DOWN_REASON

Message

OSPF/3/NBR_DOWN_REASON:Neighbor state leaves full or changed to Down. (ProcessId=[USHORT], NeighborRouterId=[IPADDR], NeighborAreaId=[ULONG], NeighborInterface=[STRING],NeighborDownImmediate reason=[STRING], NeighborDownPrimeReason=[STRING], NeighborChangeTime=[STRING])

Description

The neighbor went Down.

Parameters

Parameter Name Parameter Meaning
ProcessId ID of an OSPF process
NeighborRouterId ID of a neighbor
NeighborAreaId IP address of an area
NeighborInterface Neighbor's interface
NeighborDownImmediate reason

Direct cause for the OSPF neighbor to go 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.
NeighborDownPrimeReason

Primary reason that the neighbor goes Down:

  • Hello Not Seen: indicates that no Hello packet is received.
  • Interface Parameter Mismatch: indicates that the parameters set on both ends of the link do not match.
  • Logical Interface State Change: indicates that the status of the logical interface changes.
  • Physical Interface State Change: indicates that the status of the physical interface changes.
  • OSPF Process Reset: indicates that the OSPF process restarts.
  • Area reset: indicates that the area restarts because the area type changes.
  • Area Option Mis-match: indicates that the area options of the interfaces on both ends of the link do not match.
  • Vlink Peer Not Reachable: indicates that the neighbor on the virtual link is not reachable.
  • Sham-Link Unreachable: indicates that the neighbor on the sham link is not reachable.
  • Undo Network Command: indicates that the network command is deleted.
  • Undo NBMA Peer: indicates that the neighbor configuration on the NBMA interface is deleted.
  • Passive Interface Down: indicates that the neighbor relationship goes Down because the silent-interface command is configured on the local interface.
  • Opaque Capability Enabled: indicates that Opaque capability is enabled.
  • Opaque Capability Disabled: indicates that Opaque capability is disabled.
  • Virtual Interface State Change: indicates that the status of a virtual link interface changes.
  • BFD Session Down: indicates that the BFD session goes Down.
  • Down Retransmission Limit Exceed: indicates that the number of retransmission times reaches the limit.
  • 1-Wayhello Received: indicates that the device receives 1-way hello packets.
  • Router State Change from DR or BDR to DROTHER: indicates that the interface state machine changes to DROTHER from DR or BDR.
  • Neighbor State Change from DR or BDR to DROTHER: indicates that the neighbor state machine changes to DROTHER from DR or BDR.
  • NSSA Area Configure Change: indicates that the configuration of the NSSA area changes.
  • Stub Area Configure Change: indicates that the configuration of the Stub area changes.
  • Received Invalid DD Packet: indicates that invalid DD packets are received.
  • Not Received DD during RouterDeadInterval: indicates that no DD packet is received during the time when the Dead timer starts.
  • M,I,MS bit or SequenceNum Incorrect: indicates that the M, I, and MS bits do not comply with specifications in the protocol.
  • Unable Opaque Capability,Find 9,10,11 Type Lsa: indicates that Type9, Type10, and Type11 LSAs are received and that Opaque capability is disabled.
  • Not NSSA,Find 7 Type Lsa in Summary List: indicates that this area is not an NSSA and that Type 7 LSAs are found in the summary table.
  • LSrequest Packet,Unknown Reason: indicates that LSR packets are received with an unknown reason.
  • NSSA or STUB Area,Find 5 ,11 Type Lsa: indicates that this area is an NSSA or a Stub area and that Type 5 and Type11 LSAs are found.
  • LSrequest Packet,Request Lsa is Not in the Lsdb: indicates that the neighbor sends an LSR to this process or area to request an LSA and that this LSA does not exist in the LSDB of this process.
  • LSrequest Packet, exist same lsa in the Lsdb: indicates that this process receives an LSA that is same as that in the LSDB and that the LSA is found in the request list of the neighbor.
  • LSrequest Packet, exist newer lsa in the Lsdb: indicates that this process receives a new LSA that exists in the local LSDB and that the LSA is found in the request list of the neighbor.
  • Neighbor state was not full when LSDB overflow: indicates that the LSDB overflows and that the neighbor state machine is not Full.
  • Filter LSA configuration change: indicates that the configuration of LSA filter changes.
  • ACL changed for Filter LSA: indicates that the ACL configuration of LSA filter changes.
  • Reset Ospf Peer: indicates that the OSPF neighbor is restarted.
NeighborChangeTime Time when the neighbor status changed

Possible Causes

The neighbor status changed because the neighbor received an OSPF message or an event affecting the neighbor relationship occurred.

Procedure

  1. This log message is informational only, and no action is required.
Translation
Download
Updated: 2019-05-29

Document ID: EDOC1000097209

Views: 72053

Downloads: 181

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next