display bgp vpnv6 all peer verbose

Function

The display bgp vpnv6 all peer verbose command displays the detailed information of all the BGP VPNv6 peers.

Format

display bgp vpnv6 all peer verbose

display bgp vpnv6 all peer ipv4-address verbose

display bgp vpnv6 all peer peerIpv6Addr verbose

Parameters

Parameter	Description	Value
ipv4-address	Specifies an IPv4 peer address.	The value is in dotted decimal notation.
peerIpv6Addr	Specifies the IPv6 address of a peer.	The value is in the X:X:X:X:X:X:X:X format.

Parameter

Description

Value

ipv4-address

Specifies an IPv4 peer address.

The value is in dotted decimal notation.

peerIpv6Addr

Specifies the IPv6 address of a peer.

The value is in the X:X:X:X:X:X:X:X format.

Views

All views

Default Level

1: Monitoring level

Task Name and Operations

Task Name	Operations
bgp	read

Usage Guidelines

Usage Scenario

The display bgp vpnv6 all peer verbose command is used to display the detailed information of all the BGP VPNv6 peers.

Example

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

# Display detailed information about the VPNv6 peer.

<HUAWEI> display bgp vpnv6 all peer verbose

         BGP Peer is 10.1.1.2,  remote AS 200
         Type: EBGP link
         BGP version 4, Remote router ID 10.1.1.2
         Update-group ID: 1
         BGP current state: Established, Up for 00h01m44s
         BGP current event: RecvKeepalive
         BGP last state: OpenConfirm
         BGP Peer Up count: 2
         Received total routes: 0
         Received active routes total: 0
         Advertised total routes: 0
         Port: Local - 179        Remote - 59043
         Configured: Connect-retry Time: 32 sec
         Configured: Min Hold Time: 0 sec
         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
         Address family VPNv6 Unicast: advertised and received
 Received: Total 6 messages
                  Update messages                2
                  Open messages                  1
                  KeepAlive messages             3
                  Notification messages          0
                  Refresh messages               0
 Sent: Total 6 messages
                  Update messages                2
                  Open messages                  2
                  KeepAlive messages             2
                  Notification messages          0
                  Refresh messages               0
 Authentication type configured: None
 Last keepalive received: 2020-01-28 11:50:08+00:00
 Last keepalive sent    : 2020-01-28 11:49:23+00:00
 Last update    received: 2020-01-28 11:48:30+00:00
 Last update    sent    : 2020-01-28 11:48:30+00:00
 No refresh received since peer has been configured
 No refresh sent since peer has been configured
 Minimum route advertisement interval is 30 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 4-byte-as capability has been enabled
 Peer Preferred Value: 0
 Memory Priority: high
 Routing policy configured:
 No routing policy is configured

# Display detailed information about the VPNv6 peer with the IPv4 address 10.1.1.2.

<HUAWEI> display bgp vpnv6 all peer 10.1.1.2 verbose

         BGP Peer is 10.1.1.2,  remote AS 200
         Type: EBGP link
         BGP version 4, Remote router ID 10.1.1.2
         Update-group ID: 1
         BGP current state: Established, Up for 00h01m06s
         BGP current event: KATimerExpired
         BGP last state: OpenConfirm
         BGP Peer Up count: 2
         Received total routes: 0
         Received active routes total: 0
         Advertised total routes: 0
         Port: Local - 179        Remote - 59043
         Configured: Connect-retry Time: 32 sec
         Configured: Min Hold Time: 0 sec
         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
         Address family VPNv6 Unicast: advertised and received
 Received: Total 5 messages
                  Update messages                2
                  Open messages                  1
                  KeepAlive messages             2
                  Notification messages          0
                  Refresh messages               0
 Sent: Total 6 messages
                  Update messages                2
                  Open messages                  2
                  KeepAlive messages             2
                  Notification messages          0
                  Refresh messages               0
 Authentication type configured: None
 Last keepalive received: 2020-01-28 11:49:17+00:00
 Last keepalive sent    : 2020-01-28 11:49:23+00:00
 Last update    received: 2020-01-28 11:48:30+00:00
 Last update    sent    : 2020-01-28 11:48:30+00:00
 No refresh received since peer has been configured
 No refresh sent since peer has been configured
 Minimum route advertisement interval is 30 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 4-byte-as capability has been enabled
 Peer Preferred Value: 0
 Memory Priority: high
 Routing policy configured:
 No routing policy is configured

**Table 1** Description of the **display bgp vpnv6 all peer verbose** command output
Item	Description
BGP version	BGP version.
BGP current state	State of BGP: 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 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.
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 Preferred Value	PrefVal of the peer.
Peer optional capabilities	Optional capabilities of the peer.
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 messages received from a peer. Total: indicates the total number of messages received from a peer. Update messages: indicates the number of Update messages received from a peer. Open messages: indicates the number of Open messages received from a peer. KeepAlive messages: indicates the number of Keepalive messages received from a peer. Notification messages: indicates the number of Notification messages received from a peer. Refresh messages: indicates the number of route-refresh messages received from a peer.
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.
Address family VPNv6 Unicast	VPNv6unicast address family.
Authentication type configured	Authentication type.
Last keepalive received	Time when a Keepalive message was last received.
Last keepalive sent	Time at which the last keepalive message is sent.
Minimum route advertisement interval is 30 seconds	Minimum route advertisement interval. The minimum interval at which EBGP routes are advertised is 30 seconds. The minimum interval at which IBGP routes are advertised is 15 seconds.
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.
Routing policy configured	Configured routing policy.
Type	BGP link type: IBGP or EBGP.
Port	Port type: Local: indicates the local port number, which is always 179. BGP uses TCP at the transport layer. Remote: indicates the port number used on the peer.
Configured	Locally configured timers. Active Hold Time: indicates the hold time. If BGP does not receive any Keepalive message from the peer in the hold time, BGP considers that the peer is Down and then instructs other peers to remove the routes that are sent from the peer. Keep Alive Time: indicates the interval at which Keepalive messages are sent to the peer. BGP peers exchange Keepalive messages periodically to maintain their relationships.
Negotiated	Hold time agreed between the BGP peers after capability negotiation.
Sent	Number of messages sent to a peer. Total: indicates the total number of messages sent to a peer. Update messages: indicates the number of Update messages sent to a peer. Open messages: indicates the number of Open messages sent to a peer. KeepAlive messages: indicates the number of Keepalive messages sent to a peer. Notification messages: indicates the number of Notification messages sent to a peer. Refresh messages: indicates the number of route-refresh messages sent to a peer.