show bgp summary
Use this command to display a summary of BGP neighbor status.
Command Syntax
show bgp summary
show bgp (ipv4|ipv6) (unicast|multicast|) summary
show ip bgp summary
show ip bgp summary (vrf (VRFNAME|all|default))
show ip bgp ipv4 (unicast|multicast) summary
Parameters
ipv4
IPv4 routes
ipv6
IPv6 routes
unicast
Unicast prefixes
multicast
Multicast prefixes
VRFNAME
VPN routing/forwarding instance name
all
All VRFs
default
Default VRF
Command Mode
Privileged Exec mode and Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show bgp summary
 
BGP router identifier 6.6.6.6, local AS number 64601
 
BGP table version is 1
 
1 BGP AS-PATH entries
 
0 BGP community entries
 
Neighbor V   AS   MsgRcv    MsgSen TblVer   InQ   OutQ    Up/Down   State/PfxRcd
 
*12.1.1.24 64902    7          7       1      0      0   00:02:54       0
 
* Dynamically created based on a listen range command
 
BGP dynamic peer-group: group1
 
listen range:  12.1.0.0/16
Total number of dynamically created neighbors/limit: 1/(200)
Total number of dynamically created neighbors: 1
Total number of activated dynamic peer-groups for IPv4 Unicast address-family: 
Total number of neighbors 1
Total number of Established sessions 1
 
BGP dynamic peer-group: group2
listen range:  12.2.0.0/16
Total number of dynamically created neighbors/limit: 0/(200)
Total number of dynamically created neighbors: 0
Total number of activated dynamic peer-groups for IPv4 Unicast address-family: 1
Header
BGP router identifier 10.10.15.50, local AS number 65000
1 BGP AS-PATH entries
0 BGP community entries
•	The BGP router identifier is 10.10.15.50 and the local router AS number is 65000.
•	The BGP table version tracks the local BGP table version. Any time the BGP best path algorithm executes, the table version increments.
•	There is one BGP AS-PATH entry and no community entries. 
Neighbor Entry Fields
Table 7-23 explains the fields for each neighbor entry.
  
Table 7-23: neighbor entry fields 
| Field | Description | 
|---|
| Neighbor | IP address of peer. | 
| V | BGP version of peer. | 
| AS | Autonomous system number of peer. | 
| MsgRcvd | Messages received since the BGP connection was established. | 
| MsgSent | Messages sent since the BGP connection was established. | 
| TblVer | Last version of the local router’s BGP database advertised to the peer. | 
| InQ | Received messages waiting in the input queue for further processing. | 
| OutQ | Messages waiting in the output queue to be sent. | 
| Up/Down | Connection up time and down time. | 
| State/PfxRcd | If the TCP session is up and the BGP peers have formed an adjacency, this field shows how many prefixes have been received from the remote neighbor.   Other states:   Idle: The local router has not allocated resources for the peer connection, so incoming connection requests are refused   Idle (Admin): The peer has shut down   Idle (PfxCt): Prefix overflow   Idle (G-shut): Graceful shutdown   Connect: BGP is waiting for the TCP connection to complete   Active: the local router is trying to establish a TCP connection to the remote peer. You might see this if the local peer has been configured, but the remote peer is unreachable or has not been configured.    OpenSent: BGP is waiting for an open message from its peer   OpenConfirm: BGP received an open message from the peer and is now waiting for a keepalive or notification message. If BGP receives a keepalive message from the peer, the state changes to established. If the message is a notification, the state changes to idle.   Established: BGP is ready to exchange update, notification, and keepalive messages with its peer   Invalid: The session state is invalid | 
Neighbor Entry Example
10.10.14.51   4   100  93       120     0      0    0     00:42:16        0
•	The neighbor has the IP address 10.10.14.51 and AS number 100.
•	The neighbor uses BGP version 4.
•	93 messages have been received.
•	120 messages have been sent.
•	The BGP routing table version is 0.
•	There are no received messages waiting in the input queue for further processing.
•	There are no messages waiting in the output queue to be sent. 
•	The connection has been up for 0 hours, 42 minutes and 53 seconds.
•	The local router has received no prefixes from this neighbor. 
 
Last modified date: 08/28/2023