display bgp evpn peer

Function

The display bgp evpn peer command displays information about BGP EVPN peers.

Format

display bgp evpn peer [ ipv4-address verbose | verbose ]

Parameters

Parameter	Description	Value
ipv4-address	Specifies the IPv4 address of a peer to be displayed.	It is in dotted decimal notation.
verbose	Indicates to display detailed peer information.	-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To query the following information about BGP EVPN peers, run the display bgp evpn peer command:

Status of BGP EVPN connections
Information about a BGP EVPN peer
Whether BGP peers are successfully configured using the peer enable command
Whether BGP peers are successfully deleted using the undo peer enable command

Precautions

By specifying verbose, you can query more BGP peer information, such as the BGP timer information, number of received and transmitted routes, capabilities supported by the peer, number of received and transmitted BGP information messages, and enabled configurations.

Example

# Display the information about BGP EVPN peers.

<HUAWEI> display bgp evpn peer

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

  Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv

  4.4.4.4         4         100        6        9     0 00:02:19 Established       2
  5.5.5.5         4         100        6        9     0 00:02:11 Established       2

**Table 1** Description of the **display bgp evpn peer** command output
Item	Description
BGP Local router ID	Indicates the ID of the BGP local router.
local AS number	Indicates the local AS number.
Total number of peers	Indicates the number of the peer.
Peers in established state	Indicates the number of the peer in established state.
Peer	Indicates the IP address of the peer.
V	Indicates the BGP version.
AS	Indicates the number of the AS where a member of a peer group resides.
MsgRcvd	Indicates the number of received messages.
MsgSent	Indicates the number of sent messages.
OutQ	Indicates the number of messages to be sent to peers.
Up/Down	Indicates the period of time during which a BGP session keeps the current state.
State	Indicates the BGP state mechanism: 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 to the remote BGP peer, starts the ConnectRetry Timer with the initial value, detects a TCP connection initiated by the remote BGP peer, and changes its state to Connect. Idle(Admin): indicates that the neighbor relationship is shut down initiatively and no attempt is made to establish the neighbor relationship. If the peer ignore command is configured or the peer is set to the Down state through the MIB, the neighbor is in the Idle (Admin) state. No neg: The negotiation of the capabilities of the BGP peer's address family is not successful. Idle(Ovlmt): indicates that the neighbor relationship is interrupted because the number of routes exceeds the upper threshold. After a BGP neighbor relationship is interrupted due to the running of the peer route-limit command, the status of the BGP neighbor relationship is displayed as Idle(Ovlmt). If the reset bgp command is not run, the BGP neighbor relationship will not be reestablished. Connect: indicates that BGP waits 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 detect a TCP connection 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 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 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 waits 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 detect a TCP connection initiated by the remote peer, and changes its state to Active. OpenConfirm: indicates that BGP waits for a Notification message or a 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 packets. 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.
PrefRcv	Indicates the number of route prefixes sent from the peer.

# Display the detailed information about a BGP EVPN peer.

<HUAWEI> display bgp evpn peer 4.4.4.4 verbose

        BGP Peer is 4.4.4.4,  remote AS 100
        Type: IBGP link
        BGP version 4, Remote router ID 4.4.4.4
        Update-group ID: 0
        BGP current state: Established, Up for 00h04m51s
        BGP current event: KATimerExpired
        BGP last state: OpenConfirm
        BGP Peer Up count: 2
        Received total routes: 2
        Received active routes total: 2
        Received mac routes: 0
        Advertised total routes: 2
        Port:  Local - 65472    Remote - 179
        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: received
        Address family L2VPN EVPN: advertised and received
 Received: Total 8 messages
                 Update messages                2
                 Open messages                  1
                 KeepAlive messages             5
                 Notification messages          0
                 Refresh messages               0
 Sent: Total 11 messages
                 Update messages                4
                 Open messages                  1
                 KeepAlive messages             6
                 Notification messages          0
                 Refresh messages               0
 Authentication type configured: None
 Last keepalive received: 2018-03-29 20:52:33+00:00
 Last keepalive sent    : 2018-03-29 20:52:33+00:00
 Last update    received: 2018-03-29 20:48:33+00:00
 Last update    sent    : 2018-03-29 20:48:41+00:00
 Minimum route advertisement interval is 0 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 4-byte-as capability has been enabled
 Connect-interface has been configured
 Peer Preferred Value: 0
 Routing policy configured:
 No routing policy is configured
 Tracking has been enabled, and the delay is 9s

**Table 2** Description of the **display bgp evpn peer** command output
Item	Description
BGP Peer is 4.4.4.4	IP addresses of the BGP peer
remote AS 100	AS number of the BGP peer
Type	BGP link type, which can be IBGP Link or EBGP Link.
BGP version	BGP version (current version: BGP4)
Remote router ID	Router ID of the peer
Update-group ID	Update the peer group ID
BGP current state	Current BGP status: Idle: BGP denies any connection request. This is the initial status of BGP. After BGP receives a start event, BGP initiates a TCP connection to a peer, starts the ConnectRetry timer, and listens to the TCP messages from the peer. BGP then enters the Connect state. Idle(Admin): The neighbor relationship is shut down initiatively and no attempt is made to establish the neighbor relationship. If the peer ignore command is configured or the peer is set to the down state through the MIB, the neighbor is in this state. No neg: The negotiation of the capabilities of the BGP peer's address family is not successful. Idle(Ovlmt): The BGP neighbor relationship is interrupted because the number of routes exceeds the upper threshold (configured by running the peer route-limit command). When this happens, the neighbor is in this state. If the reset bgp command is not run, the BGP neighbor relationship is not reestablished. Connect: BGP waits for the TCP connection establishment to complete before performing further operations. If the TCP connection is successfully established, BGP stops the ConnectRetry timer and sends an Open message to the peer. BGP then enters the Opensent state. If the TCP connection fails to be established, BGP resets the ConnectRetry timer and listens to the TCP connection initiated by the peer. BGP then enters the Active state. 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 status 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 session with an unknown IP address but fails, BGP resets the ConnectRetry timer and remains in the Active state. OpenSent: BGP has sent an Open message to the peer and waits for an Open message from the peer. If BGP receives a correct Open message, BGP enters the OpenConfirm state. If BGP receives an incorrect Open message, BGP sends a Notification message to the peer and enters the Idle state. If BGP receives a TCP connection teardown message, BGP resets the ConnectRetry timer and listens to the TCP connection initiated by the peer. BGP then enters the Active state. OpenConfirm: BGP waits for a Notification or Keepalive message. If BGP receives a Notification or 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.
BGP current event	Current BGP event
BGP last state	Status of the last BGP stage, which can be Idle, Idle(Admin), Idle(Ovlmt), Connect, Active, OpenSent, OpenConfirm, or Established.
BGP Peer Up count	Number of times the BGP peer alternates between Up and Down
Received total routes	Number of route prefixes received
Received active routes total	Number of active route prefixes received
Received mac routes	Number of MAC routes received
Advertised total routes	Number of route prefixes sent
Port	Port number Local: local port number, which is fixed to 179 because BGP uses TCP as the transport layer protocol Remote: peer port number
Configured	Timers that are locally configured: Connect-retry Time: ConnectRetry interval for a peer or peer group, in the unit of seconds. When BGP initiates a TCP connection, the ConnectRetry timer is stopped if the TCP connection is established successfully. If the first attempt to establish a TCP connection fails, BGP tries again to establish the TCP connection after the ConnectRetry timer expires. Min Hold Time: minimum hold time configured on the local device, in seconds. Active Hold Time: hold time, in seconds. 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 device. Keepalive Time: interval for sending KeepAlive messages to the peer, in seconds. BGP peers send KeepAlive messages at intervals to show that they are working normally.
Received: Active Hold Time	Hold time of the peer
Negotiated	Timer negotiated by peers: Active Hold Time: hold time agreed between the BGP peers after capability negotiation Keepalive Time: Keepalive message transmission interval agreed between the BGP peers after capability negotiation
Peer optional capabilities	Capability supported by peers (optional) Peer supports bgp multi-protocol extension: Indicates the BGP peer supports BGP multi-protocol extension Peer supports bgp route refresh capability: Indicates the BGP peer supports BGP route refresh Peer supports bgp 4-byte-as capability: Indicates the BGP peer supports BGP 4-byte AS numbers
Address family IPv4 Unicast	IPv4 unicast address family
Address family L2VPN EVPN	BGP EVPN address family
Received	Number of messages received from a peer: Total: total number of messages received from the peer Update messages: number of Update messages Open messages: number of Open messages KeepAlive messages: number of Keepalive messages Notification messages: number of Notification messages Refresh messages: number of route-refresh messages
Sent	Number of messages sent to the peer: Total: total number of messages Update messages: number of Update messages Open messages: number of Open messages KeepAlive messages: number of Keepalive messages Notification messages: number of Notification messages Refresh messages: number of route-refresh messages
Authentication type configured	BGP authentication type configured. The value can be the following: Message digest 5 (MD5) Keychain (kk): kk indicates the name of the configured keychain authentication. None: No BGP authentication is configured.
Last keepalive received	Indicates the time when the Keepalive message is received last time. It can be in the following formats: YYYY/MM/DD HH:MM:SS YYYY/MM/DD HH:MM:SS UTC±HH:MM DST YYYY/MM/DD HH:MM:SS UTC±HH:MM YYYY/MM/DD HH:MM:SS DST UTC±HH:MM indicates that a time zone is configured through the clock timezone command; DST indicates that the daylight saving time is configured through the clock daylight-saving-time command.
Last keepalive sent	Time when the Keepalive message is sent last time. It can be in the following formats: YYYY/MM/DD HH:MM:SS YYYY/MM/DD HH:MM:SS UTC±HH:MM DST YYYY/MM/DD HH:MM:SS UTC±HH:MM YYYY/MM/DD HH:MM:SS DST UTC±HH:MM indicates that a time zone is configured through the clock timezone command; DST indicates that the daylight saving time is configured through the clock daylight-saving-time command.
Last update received	Time when the Update message is received last time. It can be in the following formats: YYYY/MM/DD HH:MM:SS YYYY/MM/DD HH:MM:SS UTC±HH:MM DST YYYY/MM/DD HH:MM:SS UTC±HH:MM YYYY/MM/DD HH:MM:SS DST UTC±HH:MM indicates that a time zone is configured through the clock timezone command; DST indicates that the daylight saving time is configured through the clock daylight-saving-time command.
Last update sent	Time when the Update message is sent last time. It can be in the following formats: YYYY/MM/DD HH:MM:SS YYYY/MM/DD HH:MM:SS UTC±HH:MM DST YYYY/MM/DD HH:MM:SS UTC±HH:MM YYYY/MM/DD HH:MM:SS DST UTC±HH:MM indicates that a time zone is configured through the clock timezone command; DST indicates that the daylight saving time is configured through the clock daylight-saving-time command.
Minimum route advertisement interval is 30 seconds	Minimum route advertisement intervals. The default minimum route advertisement intervals are as follows: The minimum interval for advertising EBGP routes is 30 seconds. The minimum interval for advertising IBGP routes is 15 seconds.
Optional capabilities	(Optional) Capabilities of the peer
Peer Preferred Value	Preferred value of the peer
Routing policy configured	Whether a routing policy has been configured