display ospf peer

Function

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

Format

display ospf [ process-id ] peer [ [ interface-type interface-number ] [ neighbor-id ] | brief | last-nbr-down ]

Parameters

Parameter	Description	Value
process-id	Specifies the ID of an OSPF process.	The value is an integer ranging from 1 to 65535.
interface-type interface-number	Specifies the interface type and the interface number.	-
neighbor-id	Specifies the neighbor's router ID.	It is in dotted decimal notation.
brief	Displays brief information about neighbors in each OSPF area.	-
last-nbr-down	Displays brief information about the last neighbor that went Down in the OSPF area.	-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

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).

Example

# Display information about the OSPF neighbor.

<HUAWEI> display ospf peer

         OSPF Process 1 with Router ID 10.1.1.2
                 Neighbors

 Area 0.0.0.0 interface 10.1.1.2(Vlanif100)'s neighbors
 Router ID: 10.1.1.1         Address: 10.1.1.1          GR State: Normal
   State: Full  Mode:Nbr is Slave  Priority: 1
   DR: 10.1.1.2  BDR: 10.1.1.1   MTU: 0
   Dead timer due in 35  sec
   Retrans timer interval: 5
   Neighbor is up for 00:00:05
   Authentication Sequence: [ 0 ]

**Table 1** Description of the **display ospf peer** command output
Item	Description
Area	Area to which the neighbor belongs.
interface	Interface that connects to the neighbor.
Router ID	Router ID of the neighbor.
Address	Address of the neighboring interface.
GR State	GR status after OSPF GR is enabled: Normal: indicates that a switch is in the Normal state and does not perform GR. Doing GR: indicates that a switch is performing GR. Complete GR: indicates that a switch finishes GR. Helper: indicates that the neighbor is the Helper when a switch is performing GR.
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 in the Down state, 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 for sending Hello packets 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 DD sequence number are negotiated. Exchange: It indicates that the LSDBs start to be synchronized. In this process, DD packets, LSR packets, and 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 is already 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 actively sends DD packets. Nbr is Slave: indicates that the neighbor is the slave and cooperates with the master to send DD packets.
Priority	Priority of the neighboring device.
DR	Designated router.
BDR	Backup designated router.
MTU	MTU value of the neighboring interface.
Dead timer due in 35 sec	The dead timer due in 35 seconds.
Retrans timer interval	Interval for retransmitting LSAs, in seconds.
Neighbor is up for	Time during which the neighbor remains Up.
Authentication Sequence	Authentication sequence number.

# Display brief information about OSPF neighbors.

<HUAWEI> display ospf 1 peer brief

         OSPF Process 1 with Router ID 10.10.10.1
                   Peer Statistic Information
 ----------------------------------------------------------------------------
 Area Id         Interface                  Neighbor id      State
 0.0.0.0         Vlanif10                   10.10.10.3       Full            
 ----------------------------------------------------------------------------   
 Total Peer(s):     1

**Table 2** Description of the **display ospf peer brief** command output
Item	Description
Area Id	Area to which the neighbor belongs.
Interface	Interface that connects to the neighbor.
Neighbor id	Router ID of the neighbor.
Total Peer(s)	Number of neighbors.

# Display information about the OSPF neighbor that went 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  : 2.2.2.2
         Interface           : Vlanif100
         Immediate Reason    : Neighbor Down Due to Kill Neighbor
         Primary Reason      : Logical Interface State Change
         Down Time           : 2012-09-14 17:17:7

**Table 3** Description of the **display ospf peer last-nbr-down** command output
Item	Description
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.
Interface	Interface that connects to the neighbor.
Immediate Reason	Immediate reason that the neighbor went 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 went Down from Up 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 went 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	Primary reason that the neighbor went 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 went 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 went 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 Opaque capability is disabled. Not NSSA,Find 7 Type Lsa in Summary List: indicates that this area is not an NSSA area and Type7 LSAs are found in the summary table. LSrequest Packet,Unknown Reason: indicates that LSR packets are received with the reason unknown. NSSA or STUB Area,Find 5 ,11 Type Lsa: indicates that this area is an NSSA or Stub area and Type5 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 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 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 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 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.
Down Time	Time when the neighbor went Down.