display bgp peer

Rate and give feedback:

Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).

display bgp peer

Function

The display bgp peer command displays information about BGP peers.

Format

display bgp peer [ { group-name | ipv4-address } log-info | [ ipv4-address ] verbose ]

display bgp ipv6 peer [ verbose ]

display bgp ipv6 peer ipv6-address { log-info | verbose }

Parameters

Parameter	Description	Value
ipv4-address	Specifies the IPv4 address of a peer to be displayed.	It is in dotted decimal notation.
group-name	Specifies the name of a peer group.	It is a string of 1 to 47 case-sensitive characters without any spaces.
log-info	Indicates to display log information of the specified peer.	-
verbose	Indicates to display detailed peer information.	-
ipv6-address	Specifies the IPv6 address of a peer to be displayed.	-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

The display bgp peer command displays information about a BGP peer. 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 successfully configured using the peer as-number command
To check whether a BGP peer is successfully deleted using the undo peer as-number command

Precautions

BGP has multiple address families. By default, the display bgp peer command displays information about BGP peers in IPv4 unicast address family only. If you want to view information about BGP peers in another address family, you need to specify its address family parameter.

To view detailed information about a BGP peer, such as information about BGP timers, the number of sent and received routes, capacities supported, the number of sent and received BGP messages, and enabled functions, specify verbose in the command.

If log-info is specified in the command, log information about a BGP peer is displayed, including information about BGP peer flapping.

Example

# Display peer information.

<AC6605> display bgp peer
 BGP Local router ID : 10.2.3.4
 local AS number : 10
 Total number of peers : 2                 
 Peers in established state : 1

  Peer        V    AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv

  10.1.1.1    4   100        0        0     0 00:00:07        Idle       0
  10.2.5.6    4   200       32       35     0 00:17:49 Established       0

Table 6-303 Description of the display bgp 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.
Peer	Indicates the IP address of the peer.
V	Indicates the BGP version used on the peer.
AS	Indicates the AS number.
MsgRcvd	Indicates the number of received messages.
MsgSent	Indicates the number of sent messages.
OutQ	Indicates the message to be sent to the specified peer.
Up/Down	Indicates the period of time during which a BGP session keeps the current state.
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 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 peer 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. Idle(Ovlmt): indicates that the peer relationship is interrupted because the number of routes exceeds the upper threshold. After a BGP peer relationship is interrupted due to the running of the peer route-limit command, the status of the BGP peer relationship is displayed as Idle(Ovlmt). If the reset bgp command is not run, the BGP peer 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 detailed information about the peer 10.2.2.9.

<AC6605> 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: 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
 Received: 
                  Total messages                 60
                  Update messages                1
                  Open messages                  1
                  KeepAlive messages             58
                  Notification messages          0
                  Refresh messages               0
 Sent: 
                  Total messages                 61
                  Update messages                2
                  Open messages                  1
                  KeepAlive messages             58
                  Notification messages          0
                  Refresh messages               0
 Authentication type configured: None
 Last keepalive received: 2012/03/06 19:17:37
 Last keepalive sent    : 2012/03/06 19:17:37
 Last update    received: 2012/03/06 19:17:43
 Last update    sent    : 2012/03/06 19:17:37

 Minimum route advertisement interval is 15 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 4-byte-as capability has been enabled 
 Listen-only has been configured
 Peer's BFD has been enabled
 Peer Preferred Value: 0 
 Routing policy configured:
 No routing policy is configured

Table 6-304 Description of the display bgp peer verbose command output

Item	Description
Type	Indicates the BGP link type, which can be IBGP or EBGP.
BGP version	Indicates the BGP version.
remote router ID	Indicates the router ID of the peer.
Update-group ID	Indicates the ID of the update-group to which the peer belongs.
BGP current state	Current 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 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 peer 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. Idle(Ovlmt): indicates that the peer relationship is interrupted because the number of routes exceeds the upper threshold. After a BGP peer relationship is interrupted due to the running of the peer route-limit command, the status of the BGP peer relationship is displayed as Idle(Ovlmt). If the reset bgp command is not run, the BGP peer 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.
BGP current event	Indicates the current BGP event.
BGP last state	Indicates the last BGP status, which may be Idle, Connect, Active, OpenSent, OpenConfirm, or Established.
BGP Peer Up count	Indicates the flapping count of a BGP peer in a specified period of time.
Received total routes	Indicates the number of received route prefixes
Received active routes total	Indicates the number of received active route prefixes.
Advertised total routes	Indicates the number of sent route prefixes.
Port	Indicates the port number. 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	Indicates locally configured timers. Connect-retry Time: indicates the ConnectRetry interval for a BGP peer or peer group, in 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. 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 for sending Keepalive messages to the peer. BGP peers send Keepalive messages to each other periodically to maintain their relationships.
Received : Active Hold Time	Indicates the hold time on the peer.
Negotiated : Active Hold Time	Indicates the hold time agreed between the BGP peers after capability negotiation.
Address family IPv4 Unicast	Indicates the IPv4 unicast address family.
Received	Indicates the number of packets 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.
Sent	Indicates the 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.
Last keepalive received	Indicates the time when the Keepalive packet 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 set through the clock timezone command; DST indicates that the daylight saving time is set through the clock daylight-saving-time command.
Last keepalive sent	Indicates the time when the Keepalive packet 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 set through the clock timezone command; DST indicates that the daylight saving time is set through the clock daylight-saving-time command.
Last update received	Indicates the time when the Update packet 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 set through the clock timezone command; DST indicates that the daylight saving time is set through the clock daylight-saving-time command.
Last update sent	Indicates the time when the Update packet 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 set through the clock timezone command; DST indicates that the daylight saving time is set through the clock daylight-saving-time command.
Minimum time between advertisement runs is 15 seconds	Indicates the minimum interval between route advertisements. The minimum interval for advertising EBGP routes is 30 seconds. The minimum interval for advertising IBGP routes is 15 seconds.
Optional capabilities	(Optional) Indicates the peer-supported capabilities.
Route refresh capability has been enabled	Indicates that route refreshing has been enabled.
4-byte-as capability has been enabled	4-byte-As is enabled
Listen-only has been configured	Indicates that only connection requests are snooped and no connections will be initiated proactively.
Peer Preferred Value	Indicates the preferred value of the peer.
Routing policy configured	Indicates the configured routing policy.
Peer's BFD has been enabled	Indicates that BFP has been enabled on the peer.

# Display log information on BGP peer 10.1.1.2.

<AC6605> display bgp peer 10.1.1.2 log-info
Peer : 10.1.1.2 
 Date/Time     : 2011/13/06 11:53:21
 State         : Up
 Date/Time     : 2011/13/06 11:53:09
 State         : Down
 Error Code    : 6(CEASE)
 Error Subcode : 4(Administrative Reset)
 Notification  : Receive Notification
 Date/Time     : 2011/13/06 10:34:05
 State         : Up

Table 6-305 Description of the display bgp peer 10.1.1.2 log-info command output

Item	Description
Error Code	Error code
Error Subcode	Error subcode
Notification	Notification packet sent or received by a peer

# Display information about IPv6 peers.

<AC6605> display bgp ipv6 peer

 BGP Local router ID : 10.20.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

  20::21          4   200       17       19     0 00:09:59 Established       3

# Display detailed information about IPv6 peers.

<AC6605> display bgp ipv6 peer 9:1::1 verbose
                                                                                
        BGP Peer is 9:1::1,  remote AS 65009                                    
        Type: IBGP link                                                         
        BGP version 4, Remote router ID 10.2.2.2                                 
        Update-group ID: 1                                                      
        BGP current state: Established, Up for 00h01m13s                        
        BGP current event: KATimerExpired                                       
        BGP last state: OpenConfirm                                             
        BGP Peer Up count: 1                                                    
        Received total routes: 1                                                
        Received active routes total: 0                                         
        Advertised total routes: 1                                              
        Port:  Local - 49152    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 IPv6 Unicast: advertised and received                    
 Received: Total 4 messages

Related Topics

peer as-number