display ospf peer

Function

The display ospf peer command displays information about neighbors in each OSPF area.

Format

display ospf [ process-id ] peer [ interfaceName | interfaceType interfaceNum | { neighbor-id | hostname hostnamestr } | brief | last-nbr-down ]

display ospf [ process-id ] peer { { interfaceName | interfaceType interfaceNum } { neighbor-id [ resolve-hostname ] | hostname hostnamestr } }

display ospf [ process-id ] peer [ interfaceName | interfaceType interfaceNum | neighbor-id | brief ] resolve-hostname

Parameters

Parameter	Description	Value
process-id	Specifies the ID of an OSPF process.	The value is an integer ranging from 1 to 4294967295.
interfaceName	Specifies the interface name.	-
interfaceType	Specifies the interface type.	-
interfaceNum	Specifies the interface number.	The value is a string of 1 to 63 case-sensitive characters, spaces not supported.
neighbor-id	Specifies the neighbor router ID.	The value is in dotted decimal notation.
hostname hostnamestr	Specifies a dynamic hostname.	The value is a string of 1 to 255 characters.
brief	Displays brief information about neighbors in each OSPF area.	-
last-nbr-down	Displays brief information about the last neighbor that goes Down in the OSPF area.	-
resolve-hostname	Displays information about resolved dynamic hostnames.	-

Views

All views

Default Level

1: Monitoring level

Task Name and Operations

Task Name	Operations
ospf	read

Usage Guidelines

Usage Scenario

The command output can display information about OSPF neighbors, and help you troubleshoot OSPF faults, verify the configurations of OSPF neighbors, and check whether the neighbor performs Graceful Restart (GR).

The command output includes such information as all OSPF interfaces, interface types, status, and attributes. If an OSPF neighbor relationship fails to be established or routes are incorrectly calculated, you can run the command to check whether OSPF interfaces are normal.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display brief information about OSPF neighbors.

<HUAWEI> display ospf 1 peer brief
(M) Indicates MADJ interface
          OSPF Process 1 with Router ID 1.1.1.1
                   Peer Statistic Informations

  Total number of peer(s): 2
  Peer(s) in full state: 2

-------------------------------------------------------------------------
 Area Id         Interface      Neighbor id      State
 0.0.0.0         GE0/1/8        1.1.1.2          Full
 0.0.0.1         GE0/1/16        1.1.1.2          Full
-------------------------------------------------------------------------

# Display information about resolved dynamic hostnames.

<HUAWEI> display ospf peer brief resolve-hostname
(M) Indicates MADJ interface
          OSPF Process 1 with Router ID 1.1.1.1
                   Peer Statistic Informations

  Total number of peer(s): 2
  Peer(s) in full state: 1
-------------------------------------------------------------------------
 Area Id         Interface                 Neighbor id      State       
 0.0.0.1         GE0/1/8                   RTR_BLR          FULL
 0.0.0.1         GE0/1/16                   RTR_BJI          2-Way
-------------------------------------------------------------------------

# Display information about the OSPF neighbor that goes Down for the last time.

<HUAWEI> display ospf 1 peer last-nbr-down
OSPF Process 1 with Router ID 10.1.1.1

               Last Down OSPF Peer

 Neighbor Ip Address : 10.2.1.2
 Neighbor Area   Id  : 0.0.0.0
 Neighbor Router Id  : 10.1.1.2
 Interface           : GE0/1/16
 Immediate Reason    : Neighbor Down Due to Kill Neighbor
 Primary Reason      : Hello Not Seen
 Down Time           : [2010/02/11] 06:50:23

# Display information about the OSPF neighbor.

<HUAWEI> display ospf peer
(M) Indicates MADJ interface
          OSPF Process 1 with Router ID 1.1.1.1
                Neighbors

 Area 0.0.0.0 interface 192.168.1.1 ( GE0/1/16 )'s neighbors
 Router ID: 2.2.2.2         Address: 192.168.1.2
   State: 2-Way  Mode:Nbr is  Slave   Priority: 1
   DR: 192.168.1.4   BDR: 192.168.1.3    MTU: 0
   Dead timer due in  32  sec
   Retrans timer interval: 5
   Neighbor is up for 00:00:05
   Neighbor Up Time : 2018-06-08 01:41:57
   Authentication Sequence: [ 0 ]

**Table 1** Description of the **display ospf peer** command output
Item	Description
(M) Indicates MADJ interface	Multi-area adjacency interface.
OSPF Process 1 with Router ID 1.1.1.1	OSPF process ID and router ID.
Router ID	Router ID of the neighbor.
Total number of peer(s)	Total information of neighbors.
Peer(s) in full state	Number of entries with the neighbor state Full.
Area	Area to which the neighbor belongs.
Area Id	Area to which the neighbor belongs.
Interface	Interface that connects to the neighbor.
Neighbor Up Time	Time when the peer went Up.
Neighbor is up for	Duration in which the neighbor stays Up.
Neighbor id	Router ID of the neighbor.
Neighbor Ip Address	Address of the neighboring interface.
Neighbor Area Id	Area to which the neighbor belongs.
Neighbor Router Id	Router ID of the neighbor.
State	Neighbor status: Down: It is the initial status of the neighbor, indicating that the neighbor does not receive any information. On an NBMA network, when the neighbor is Down, Hello packets can still be transmitted at the poll interval, which is longer than the Hello interval. Attempt: It exists only on an NBMA network, indicating that two ends are attempting to establish the neighbor relationship. The interval at which Hello packets are sent is the Hello interval, which is shorter than the poll interval. Init: It indicates that the Hello packet has been received from the neighbor. 2-Way: It indicates that the Hello packet has been received from the neighbor, and the neighbor list of the Hello packet contains the local router ID. That is, the two ends can interwork. ExStart: It is the first step of establishing adjacencies. In this step, the master and slave relationship and Database Description (DD) sequence number are negotiated. Exchange: It indicates that the LSDBs start to be synchronized. In this process, DD packets, Link Status Request (LSR) packets, and Link Status Update (LSU) packets are exchanged. Loading: It indicates that the LSDBs are being synchronized. In this process, LSR packets and LSU packets are exchanged. Full: It indicates that the LSDB of the neighbor has been synchronized, and the Full adjacency is established between both ends.
Mode	Master or slave in the process of exchanging DD packets: Nbr is Master: indicates that the neighbor is the master and proactively sends DD packets. Nbr is Slave: indicates that the neighbor is the slave and cooperates with the master to send DD packets.
DR	Designated router.
BDR	Backup designated router.
MTU	Maximum Transmission Unit (MTU) value of the neighboring interface.
Dead timer due in 32 sec	The dead timer is due in x seconds.
Retrans timer interval	Interval for retransmitting LSAs, in seconds.
Authentication Sequence	Authentication sequence number.
Down Time	Time when the neighbor goes Down.
Address	Address of the neighboring interface.
Immediate Reason	Immediate reason why the neighbor goes Down: Neighbor Down Due to Inactivity: indicates that the inactivity timer times out. Neighbor Down Due to LL Down: indicates that the link is Down. For example, the interface goes Down or the IP address of the link is deleted. Neighbor Down Due to Kill Neighbor: indicates that the kill neighbor event is generated on the neighbor state machine. Neighbor Down Due to 1-Wayhello: indicates that the neighbor goes Down because it receives a 1-way packet. Received: indicates that the AdjOK? event is generated on this interface. Neighbor Down Due to SequenceNum Mismatch: indicates that the SequenceNum Mismatch event is generated on the neighbor state machine. Neighbor Down Due to BadLSreq: indicates that the BadLSreq event is generated on the neighbor state machine.
Primary Reason	Root cause of the neighbor Down event. Hello Not Seen: No Hello packet is received. Interface Parameter Mismatch: The parameters of the interfaces at both ends of the link do not match. Logical Interface State Change: The status of the logical interface changes. Link Fault or Interface Configuration Change: indicates that the link is faulty or the interface configuration is changed. OSPF Process Reset: The OSPF process restarts. Area reset: The area restarts because the area type changes. Area Option Mis-match: The area options of the interfaces on both ends of the link do not match. Vlink Peer Not Reachable: The virtual link neighbor is unreachable. The Sham-Link Unreachable:Sham-Link is unreachable. Undo Network Command: The network command is deleted. Undo NBMA Peer: The neighbor configuration on the NBMA interface is deleted. Passive Interface Down: The neighbor relationship goes Down because the silent-interface command is configured on the local interface and the interface is disabled from receiving and sending OSPF packets. Opaque Capability Enabled: The Opaque capability is enabled. Opaque Capability Disabled: indicates that the opaque capability is disabled. Virtual Interface State Change: The status of a virtual link interface changes. BFD Session Down: The BFD session is Down. Retransmission Limit Excluded: The retransmission limit is reached. 1-Wayhello Received: Only one of the two neighbors receives the Hello packet. Router State Change from DR or BDR to DROTHER: The interface state machine changes from DR or BDR to DROTHER. Neighbor State Change from DR or BDR to DROTHER: The interface state machine changes from DR or BDR to DROTHER. The NSSA Area Configure Change:NSSA area configuration changes. The Stub Area Configure Change:Stub area configuration changes. Received Invalid DD Packet: indicates that invalid DD packets are received. Not Received DD during RouterDeadInterval: No DD packet is received when the Dead timer starts. M,I,MS bit or SequenceNum Incorrect: The M, I, and MS bits in the received DD packet do not comply with the protocol. Unable Opaque Capability,Find 9,10,11 Type Lsa: indicates that LSAs of types 9, 10, and 11 are received, but the Opaque capability is not enabled. Not NSSA,Find 7 Type Lsa in Summary List: indicates that the area is not an NSSA; however, Type 7 LSAs are found in the summary table. LSrequest Packet,Unknown Reason: indicates that the packet is received due to an unknown reason. NSSA or STUB Area,Find 5 ,11 Type Lsa: indicates that the area is an NSSA/stubby area but Type 5 or Type 11 LSAs are discovered. LSrequest Packet,Request Lsa is Not in the Lsdb: indicates that the neighbor requests an LSA from the local process or area, but the LSA does not exist in the LSDB of the local process. LSrequest Packet, exist same lsa in the Lsdb: indicates that the process receives a duplicate LSA from the local LSDB; the LSA is in the request list of the neighbor. LSrequest Packet, exist newer lsa in the Lsdb: indicates that the process receives an updated LSA that exists in the local LSDB and is in the request list of the neighbor. Neighbor state was not full when LSDB overflow: If the neighbor status does not reach Full when the LSDB exceeds the threshold, the neighbor status becomes Down. The Filter LSA configuration change:LSA filter configuration is changed. The ACL configuration of the ACL changed for Filter LSA:LSA filter is changed. Reset OSPF Peer: The OSPF neighbor is reset. Interface Reset: restarts an interface. Undo OSPF Interface, Undo area, Undo network: disables an interface, area, or network. UNDO OSPF Area: The area is disabled. CPU Overload: The CPU is overloaded. Interface State Change to Standby: The interface is in the backup state. Undo Router-Id: deletes a router ID. Neighbor Router-Id changed or Ip Conflicted: The router ID of the neighbor changes or an IP address conflict occurs. Component is in Implement stat: The component status is incomplete. Sequence Number mismatched: The sequence numbers do not match. The I bit of the I Bit Incorrect in DD:DD packet does not match. The MS bit of the MS Bit Incorrect in DD:DD packet does not match. Options Incorrect in DD: The option fields of DD packets do not match. Received MTU mismatched DD Packet: indicates that the MTU of the received DD packet does not match the local MTU. OSPF Process Shutdown: The OSPF process is shut down. The number of OSPF Max Nbr In Adj:OSPF neighbors exceeds the maximum. The OSPF Dcn Intf Para MisMatch:OSPF DCN interface parameters do not match. OSPF Gr Master ForceDown:"OSPF Gr Forced Shutdown. The number of retransmitted DD retrans times upto limit:DD packets reaches the upper limit. Neighbor state was not full when LSDB overflow:OSPF Flow Control. The DD packet received in the Received DD packet without R bit in graceful-restart status:GR state does not carry the R bit. Memory Overload: The memory is overloaded. Undo OSPF Interface, Undo area: interface or area deletion.
Priority	Priority of the neighboring router.