display bgp flow vpnv6 all peer verbose

Function

The display bgp flow vpnv6 all peer verbose command displays BGP IPv6 VPN FlowSpec and BGP VPNv6 FlowSpec peer detailed information.

Format

display bgp flow vpnv6 all peer verbose

display bgp flow vpnv6 all peer ipv4-address verbose

Parameters

Parameter Description Value
ipv4-address

Specifies an IPv4 address.

The value is in dotted decimal notation.

Views

All views

Default Level

1: Monitoring level

Task Name and Operations

Task Name Operations
bgp read

Usage Guidelines

Usage Scenario

After BGP FlowSpec is enabled and a BGP FlowSpec peer relationship is established, you can run the display bgp flow vpnv6 all peer verbose command to query detailed information about the BGP FlowSpec peer.

Example

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

# The command displays BGP IPv6 VPN FlowSpec and BGP VPNv6 FlowSpec peer detailed information.
<HUAWEI> display  bgp flow vpnv6 all peer 10.21.2.1 verbose

         BGP Peer is 10.21.2.1,  remote AS 100
         Type: EBGP link
         BGP version 4, Remote router ID 1.1.1.1
         Update-group ID: 2
         BGP current state: Established, Up for 00h09m36s
         BGP current event: RecvKeepalive
         BGP last state: OpenConfirm
         BGP Peer Up count: 3
         Received total routes: 0
         Received active routes total: 0
         Advertised total routes: 0
         Port: Local - 179        Remote - 60480
         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 FLOW vpnv4: advertised and received
         Address family FLOW vpnv6: advertised and received
 Received: Total 16 messages
                  Update messages                3
                  Open messages                  1
                  KeepAlive messages             12
                  Notification messages          0
                  Refresh messages               0
 Sent: Total 19 messages
                  Update messages                5
                  Open messages                  2
                  KeepAlive messages             12
                  Notification messages          0
                  Refresh messages               0
 Authentication type configured: None
 Last keepalive received: 2019-09-15 12:33:11+00:00
 Last keepalive sent    : 2019-09-15 12:32:50+00:00
 Last update    received: 2019-09-15 12:23:37+00:00
 Last update    sent    : 2019-09-15 12:23:37+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 flow vpnv6 all 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 state of BGP.
  • Active: BGP tries to establish a TCP connection. This is the intermediate state of BGP.
  • Connect: BGP is waiting for the TCP connection establishment to complete before performing further actions.
  • OpenSent: BGP is waiting for an Open message from the peer.
  • OpenConfirm: BGP is waiting for a Notification or Keepalive message.
  • Established: BGP FlowSpec peers can exchange Update, Notification, and Keepalive messages.
  • 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

State of last BGP stage, which may be Idle, Connect, Active, OpenSent, OpenConfirm, Established or No neg.

BGP Peer Up count

Number of times the BGP FlowSpec peer alternates between Up and Down.

Peer optional capabilities

Optional capabilities supported by the BGP FlowSpec peer.

Peer supports bgp multi-protocol extension

The BGP FlowSpec peer supports MP-BGP.

Peer supports bgp route refresh capability

The BGP FlowSpec peer supports route-refresh.

Peer supports bgp 4-byte-as capability

The BGP FlowSpec peer supports 4-byte AS numbers.

Peer Preferred Value

Preferred value of the BGP FlowSpec peer.

Update-group ID

Update group ID of the BGP FlowSpec peer.

Received total routes

Number of route prefixes received.

Received active routes total

Number of active route prefixes received.

Received : Active Hold Time

Hold time of the BGP FlowSpec peer.

Received

Number of messages received from the BGP FlowSpec peer:

  • Total: indicates the total number of messages.
  • Update messages: indicates the number of Update messages.
  • Open messages: indicates the number of Open messages.
  • KeepAlive messages: indicates the number of Keepalive messages.
  • Notification messages: indicates the number of Notification messages.
  • Refresh messages: indicates the number of route-refresh messages.
Advertised total routes

Number of route prefixes sent.

Keepalive Time

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

Negotiated: Active Hold Time

Hold time negotiated with the BGP FlowSpec peer.

4-byte-as capability has been enabled

The 4-byte AS numbers are supported.

Address family IPv4 Unicast

IPv4 unicast address family.

Address family FLOW vpnv6

BGP-Flow VPN instance IPv6 address family.

Address family FLOW vpnv4

BGP-Flow VPN instance IPv4 address family.

Authentication type configured

Authentication type.

Last keepalive received

Last time when Keepalive messages were received.

Last keepalive sent

Time at which the last keepalive message is sent.

Minimum route advertisement interval is 30 seconds

Minimum route advertisement interval:

  • EBGP: 30s.
  • IBGP: 15s.
Optional capabilities

Optional capabilities supported by the BGP FlowSpec peer.

Route refresh capability has been enabled

Route-refresh is enabled.

Memory Priority

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

Routing policy configured

Routing policy configured.

Type

BGP link type, which can be either IBGP Link or EBGP Link.

Port

Port number:

  • Local: local port number, which is fixed at 179 because BGP uses TCP as the transport layer protocol.
  • Remote: port number of the BGP FlowSpec peer.
Configured

Timers that are locally configured:

  • Active Hold Time: indicates the hold time. If BGP does not receive any Keepalive messages from the BGP FlowSpec peer in the hold time, BGP considers that the peer is Down. BGP then instructs the other peers to withdraw the routes received from this peer.
  • Keep Alive Time: indicates the interval for sending Keepalive messages to the BGP FlowSpec peer. BGP FlowSpec peers exchange Keepalive messages periodically, indicating that they are normal.
Sent

Number of messages sent to the BGP FlowSpec peer:

  • Total: indicates the total number of messages.
  • Update messages: indicates the number of Update messages.
  • Open messages: indicates the number of Open messages.
  • KeepAlive messages: indicates the number of Keepalive messages.
  • Notification messages: indicates the number of Notification messages.
  • Refresh messages: indicates the number of route-refresh messages.
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >