display bgp peer verbose

Function

The display bgp peer verbose command displays detailed information about BGP peers.

Format

display bgp peer ipv4-address verbose

display bgp peer verbose

display bgp labeled peer ipv4-address verbose

display bgp labeled peer verbose

display bgp peer ipv6-address verbose

Parameters

Parameter Description Value
ipv4-address

Specifies an IPv4 peer address.

The value is in dotted decimal notation.

labeled

Specifies the labeled unicast address family.

-

ipv6-address

Specifies an IPv6 peer address.

The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X.

Views

All views

Default Level

1: Monitoring level

Task Name and Operations

Task Name Operations
bgp read

Usage Guidelines

Usage Scenario

To check detailed information about BGP peers, excluding information about unnumbered BGP peers, run the display bgp peer verbose command. The command output helps with fault locating.

Example

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

# Display detailed information about the peer 10.2.2.9.
<HUAWEI> display bgp peer 10.2.2.9 verbose
BGP Peer is 10.2.2.9,  remote AS 100
         Type: IBGP link
         BGP version 4, Remote router ID 10.1.1.1
         Update-group ID: 1 
         BGP current state: Established, Up for 00h57m53s
         BGP current event: RecvKeepalive
         BGP last state: Established
         BGP Peer Up count: 1
         Received total routes: 0
         Received active routes total: 0
         Advertised total routes: 2
         Port: Local - 42796        Remote - 179
         Configured: Active Hold Time: 180 sec   Keepalive Time:60 sec
         Received  : Active Hold Time: 180 sec
         Negotiated: Active Hold Time: 180 sec   Keepalive Time:60 sec
         Peer optional capabilities:
         Peer supports bgp multi-protocol extension
         Peer supports bgp route refresh capability
         Peer supports bgp 4-byte-as capability
         Address family IPv4 Unicast: advertised and received
 Received: Total 60 messages
                  Update messages                1
                  Open messages                  1
                  KeepAlive messages             58
                  Notification messages          0
                  Refresh messages               0
 Sent: Total 61 messages
                  Update messages                2
                  Open messages                  1
                  KeepAlive messages             58
                  Notification messages          0
                  Refresh messages               0
 Authentication type configured: None
 Last keepalive received:2019-05-24 08:48:36
 Minimum route advertisement interval is 15 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 Listen-only has been configured
 Send best-external has been configured
 Add-path number : 3
 Peer Preferred Value: 0 
 Memory Priority: high
 Peer limit state: true
 Pipe limit percent: 10
 Pipe limit count: 3
 Pipe last limit time: 2020-11-21 08:48:36
 Routing policy configured:
 Peer's BFD has been enabled
 No routing policy is configured
 TCP-MSS configured value: 200
Table 1 Description of the display bgp peer verbose command output
Item Description
BGP version

BGP version.

BGP current state

Current BGP status:

  • Idle: BGP denies any connection request. This is the initial status of BGP.

After receiving a Start event, BGP initiates a TCP connection to the remote BGP peer, starts the ConnectRetry Timer with the initial value, listens for a TCP connection initiated by the remote BGP peer, and changes its state to Connect.

  • Connect: BGP is waiting for the TCP connection to be established before performing further actions.
  • If the TCP connection is successfully established, BGP stops the ConnectRetry Timer, sends an Open message to the peer, and changes its state to Opensent.
  • If the TCP connection fails to be established, BGP restarts the ConnectRetry Timer with the initial value, continues to listen for a TCP connection initiated by the remote peer, and changes its state to Active.
  • If the ConnectRetry timer expires, BGP restarts the ConnectRetry timer and attempts to establish a TCP connection with the peer again. At this time, BGP remains in the Connect state.
  • Active: BGP attempts to establish a TCP connection. This is the intermediate state of BGP.
  • If the TCP connection is successfully established, BGP resets the ConnectRetry timer and sends an Open message to the peer. BGP then enters the Opensent state.
  • If the ConnectRetry timer expires, BGP restarts the ConnectRetry timer and enters the Connect state.
  • If BGP attempts to establish a TCP connection with an unknown IP address, the TCP connection fails, the ConnectRetry Timer is reset, and BGP remains in the Active state.
  • OpenSent: BGP has sent an Open message to the peer and is now waiting for an Open message from the peer.
  • If BGP receives a correct Open message, BGP enters the OpenConfirm state.
  • If the Open message received by BGP is incorrect, BGP sends a Notification message to the peer and changes its state to Idle.
  • If the TCP connection fails, BGP restarts the ConnectRetry Timer with the initial value, continues to listen for a TCP connection initiated by the remote peer, and changes its state to Active.
  • OpenConfirm: BGP is waiting for a Notification or Keepalive message.
  • If BGP receives a Notification message or a TCP connection teardown message, BGP enters the Idle state.
  • If BGP receives a Keepalive message, BGP enters the Established state.
  • Established: BGP peers can exchange Update, Notification, and Keepalive messages.
  • If BGP receives an Update or Keepalive message, BGP remains in the Established state.
  • If BGP receives a Notification message, BGP enters the Idle state.
  • No neg: address family is not enabled on the BGP peer. In this state, other successfully negotiated address families can exchange Update messages normally. If the address family is enabled on the remote BGP peer, the local BGP peer receives a Notification message, disconnects from the remote BGP peer, changes to the Idle state, and re-establishes a connection with the remote BGP peer.
BGP current event

Current BGP event.

BGP last state

Last BGP status, which may be Idle, Connect, Active, OpenSent, OpenConfirm, Established or No neg.

BGP Peer Up count

Flapping count of a BGP peer in a specified period of time.

Peer optional capabilities

The optional capabilities supported by the peer.

Peer Preferred Value

PrefVal of the peer.

Peer limit state

Suppression status of the pipe for receiving packets from neighbors:

  • true: suppressed.
  • false: no.
Remote router ID

Router ID of the peer.

Update-group ID

ID of the update-group to which the peer belongs.

Received total routes

Number of received route prefixes.

Received active routes total

Number of received active route prefixes.

Received : Active Hold Time

Hold time on the peer.

Received

Number of packets received from neighbors:

  • Total: total number of records.
  • Update messages: number of Update messages.
  • Open messages: number of Open messages.
  • KeepAlive messages: number of Keepalive messages.
  • Number of Notification messages:Notification packets.
  • Refresh messages: number of Route-refresh messages.
Advertised total routes

Number of sent route prefixes.

Keepalive Time

Indicates the interval at which Keepalive messages are sent to the peer.

Address family IPv4 Unicast

IPv4 unicast address family.

Authentication type configured

Authentication type that is configured.

Last keepalive received

Time when a Keepalive message was last received.

No routing policy is configured

There is no routing policy configured.

Minimum route advertisement interval is 15 seconds

Minimum route advertisement interval.

Optional capabilities

(Optional) Peer-supported capabilities.

Route refresh capability has been enabled

Route refreshing has been enabled.

Memory Priority

The priority for a BGP peer relationship to be disconnected if memory overload occurs.

Pipe limit percent

Rate limit (in percentage) of a channel for receiving packets sent by peers.

Pipe limit count

Number of times rate limiting was performed for the channel to receive packets sent by peers.

Pipe last limit time

Last speed limit time of a channel for receiving packets sent by peers.

Routing policy configured

Configured routing policy.

Listen-only has been configured

The device is enabled to listen to connection requests but not initiate connection requests proactively.

Send best-external has been configured

The local device has been enabled to advertise Best External routes to a specified peer or peer group.

Add-path number

Number of routes that the local device can send to the specified IBGP peer.

Peer's BFD has been enabled

BFD has been enabled on the peer.

TCP-MSS configured value

The TCP MSS value has been configured for TCP connection establishment.

Type

BGP link type: IBGP or EBGP.

Port

Port No.

  • Local: local port number. BGP uses TCP as the transport layer protocol and has a fixed port number of 179.
  • Remote: port number of the peer.
Configured

Locally configured timers:

  • Active Hold Time: If a BGP device does not receive a Keepalive message from its peer within the Hold Time, the BGP device considers the peer Down. In this case, the BGP device instructs other peers to withdraw the routes received from the peer that is Down.
  • Keep Alive Time: interval for sending KeepAlive packets to the peer. BGP peers send KeepAlive packets to each other periodically to notify each other that they are working normally.
Negotiated : Active Hold Time

Hold time agreed between the BGP peers after capability negotiation.

Sent

Number of packets sent to neighbors:

  • Total: total number of records.
  • Update messages: number of Update messages.
  • Open messages: number of Open messages.
  • KeepAlive messages: number of Keepalive messages.
  • Number of Notification messages:Notification packets.
  • Refresh messages: number of Route-refresh messages.
Negotiated

The value of negotiated timer.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >