display bgp ipv6 peer

Function

The display bgp ipv6 slow-peer command displays information about slow BGP IPv6 peers.

The display bgp ipv6 peer command displays information about BGP IPv6 peers.

Format

display bgp ipv6 peer

display bgp ipv6 slow-peer

Parameters

None

Views

All views

Default Level

1: Monitoring level

Task Name and Operations

Task Name	Operations
bgp	read

Usage Guidelines

Usage Scenario

To check information about slow BGP IPv6 peers, run the display bgp ipv6 slow-peer command. The information includes the time when a peer began to be identified as a slow peer, the time when a peer last exited from the slow peer state, the number of times a peer has been identified as a slow peer, and the remaining time for a peer to exit from the slow peer state.

The

display bgp ipv6 peer command displays BGP IPv6 peer information. You can implement the following operations based on the command output:

To check the status of BGP connections
To check information about a BGP peer
To check whether a BGP peer is configured using the peer as-number command
To check whether a BGP peer is deleted using the undo peer as-number command
The display bgp peer command can be used for troubleshooting, with details as follows: If BGP peers are disconnected, specify log-info in the command to check the log information of the specified peer. In the command output, Date/Time indicates the time when the peers were disconnected, and Error Code and Error Subcode indicate the cause of the disconnection.

Example

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

# Display information about IPv6 peers.

<HUAWEI> display bgp ipv6 peer

BGP Local router ID : 10.0.0.1
local AS number : 100
Total number of peers : 1                 Peers in established state : 1

Peer              V    AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv
2001:DB8:20::21   4   200       17       19     0 00:09:59 Established       3

**Table 1** Description of the **display bgp ipv6 peer** command output
Item	Description
BGP Local router ID	Router ID of the BGP local device. If two ends have the same BGP local router ID, no BGP peer relationship can be established between them. In this situation, run the router id command in the BGP view on either end to change the BGP local router ID. Changing it to the IP address of a loopback interface is recommended.
local AS number	Local AS number.
AS	AS number.
Total number of peers	Total number of BGP peers.
Peers in established state	Number of BGP peers in Established state.
Peer	IP address of the peer.
V	BGP version used on the peer.
MsgRcvd	Number of received messages.
MsgSent	Number of sent messages.
OutQ	Message to be sent to the specified peer.
Up/Down	Period during which a BGP session keeps the current state. When the duration is shorter than 24 hours, the value is displayed as xx:xx:xx, indicating xx hours xx minutes and xx seconds. When the duration is longer than 24 hours, xxxxhxxm is displayed, indicating xxxx hours and xx minutes.
State	Status of the peer: Idle: indicates that BGP denies any request of entering. This is the initiatory status of BGP. Upon receiving a Start event, BGP initiates a TCP connection request to the remote BGP peer, starts the ConnectRetry Timer with the initial value, listens for a TCP connection request initiated by the remote BGP peer, and changes its state to Connect. Connect: indicates that BGP is waiting for the TCP connection to be set up before it determines whether to perform other operations. If the TCP connection succeeds, BGP stops the ConnectRetry Timer, sends an Open message to the remote peer, and changes its state to OpenSent. If the TCP connection fails, BGP restarts the ConnectRetry Timer with the initial value, continues to listen for a TCP connection request initiated by the remote peer, and changes its state to Active. If the ConnectRetry Timer has expired before a TCP connection is established, BGP restarts the timer with the initial value, initiates a TCP connection request to the remote BGP peer, and stays in the Connect state. Active: indicates that BGP tries to set up a TCP connection. This is the intermediate status of BGP. If the TCP connection succeeds, BGP stops the ConnectRetry Timer, sends an Open message to the remote peer, and changes its state to OpenSent. If the ConnectRetry Timer has expired before a TCP connection is established, BGP restarts the timer with the initial value and changes its state to Connect. If BGP initiates a TCP connection request with an unknown IP address, the TCP connection fails. When this occurs, BGP restarts the ConnectRetry Timer with the initial value and stays in the Active state. OpenSent: indicates that BGP has sent one Open message to its peer and is waiting for the other Open message from the peer. If there are no errors in the Open message received, BGP changes its state to OpenConfirm. If there are errors in the Open message received, BGP sends a Notification message to the remote 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 request initiated by the remote peer, and changes its state to Active. OpenConfirm: indicates that BGP is waiting for a Notification or Keepalive message. If BGP receives a Notification message, or the TCP connection fails, BGP changes its state to Idle. If BGP receives a Keepalive message, BGP changes its state to Established. Established: indicates that BGP peers can exchange Update, Notification, and Keepalive messages. If BGP receives an Update or a Keepalive message, its state stays in Established. If BGP receives a Notification message, BGP changes its state to Idle. No neg: The address family is not enabled for the BGP peer. In this state, Update messages can be exchanged in other address families whose capabilities have been successfully negotiated. If the address family is enabled for the BGP peer, the local BGP peer receives a Notification message, and the peer relationship is disconnected. Then, the BGP peer changes to the Idle state and re-establishes the peer relationship.
PrefRcv	Number of route prefixes sent from the peer.