Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

show bgp summary

Syntax

show bgp summary <exact-instance instance-name><instance instance-name><logical-system (all | logical-system-name)>

Syntax (EX Series Switch and QFX Series)

show bgp summary <exact-instance instance-name><instance instance-name>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Command introduced in Junos OS Release 11.3 for the QFX Series.

exact-instance option introduced in Junos OS Release 11.4.

Description

Display BGP summary information.

Options

none

Display BGP summary information for all routing instances.

exact-instance instance-name

(Optional) Display information for the specified instance only.

instance instance-name

(Optional) Display information for all routing instances whose name begins with this string (for example, cust1, cust11, and cust111 are all displayed when you run the show bgp summary instance cust1 command). The instance name can be master for the main instance, or any valid configured instance name or its prefix.

logical-system (all | logical-system-name)

(Optional) Perform this operation on all logical systems or on a particular logical system.

Required Privilege Level

view

List of Sample Output

show bgp summary (When a Peer Is Not Established)
show bgp summary (When a Peer Is Established)
show bgp summary (CLNS)
show bgp summary (Layer 2 VPN)
show bgp summary (Layer 3 VPN)

Output Fields

Table 1 describes the output fields for the show bgp summary command. Output fields are listed in the approximate order in which they appear.

Table 1: show bgp summary Output Fields

Field Name

Field Description

Groups

Number of BGP groups.

Peers

Number of BGP peers.

Down peers

Number of down BGP peers.

Table

Name of routing table.

Tot Paths

Total number of paths.

Act Paths

Number of active routes.

Suppressed

Number of routes currently inactive because of damping or other reasons. These routes do not appear in the forwarding table and are not exported by routing protocols.

History

Number of withdrawn routes stored locally to keep track of damping history.

Damp State

Number of routes with a figure of merit greater than zero, but still active because the value has not reached the threshold at which suppression occurs.

Pending

Routes in process by BGP import policy.

Peer

Address of each BGP peer. Each peer has one line of output.

AS

Peer's AS number.

InPkt

Number of packets received from the peer.

OutPkt

Number of packets sent to the peer.

OutQ

Number of BGP packets that are queued to be transmitted to a particular neighbor. It normally is 0 because the queue usually is emptied quickly.

Flaps

Number of times the BGP session has gone down and then come back up.

Last Up/Down

Last time since the neighbor transitioned to or from the established state.

State|#Active
/Received/Accepted
/Damped

Multipurpose field that displays information about BGP peer sessions. The field’s contents depend upon whether a session is established and whether it was established on the main routing device or in a routing instance.

  • If a peer is not established, the field shows the state of the peer session: Active, Connect, or Idle.

    In general, the Idle state is the first stage of a connection. BGP is waiting for a Start event. A session can be idle for other reasons as well. The reason that a session is idle is sometimes displayed. For example: Idle (Removal in progress) or Idle (LicenseFailure).

  • If a BGP session is established on the main routing device, the field shows the number of active, received, accepted, and damped routes that are received from a neighbor and appear in the inet.0 (main) and inet.2 (multicast) routing tables. For example, 8/10/10/2 and 2/4/4/0 indicate the following:
    • 8 active routes, 10 received routes, 10 accepted routes, and 2 damped routes from a BGP peer appear in the inet.0 routing table.
    • 2 active routes, 4 received routes, 4 accepted routes, and no damped routes from a BGP peer appear in the inet.2 routing table.
  • If a BGP session is established in a routing instance, the field indicates the established (Establ) state, identifies the specific routing table that receives BGP updates, and shows the number of active, received, and damped routes that are received from a neighbor. For example, Establ VPN-AB.inet.0: 2/4/0 indicates the following:
    • The BGP session is established.
    • Routes are received in the VPN-AB.inet.0 routing table.
    • The local routing device has two active routes, four received routes, and no damped routes from a BGP peer.

    When a BGP session is established, the peers are exchanging update messages.

Sample Output

show bgp summary (When a Peer Is Not Established)

user@host> show bgp summary
Groups: 2 Peers: 4 Down peers: 1
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
inet.0                 6          4          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn 
State|#Active/Received/Damped...
10.0.0.3        65002         86         90       0       2       42:54 0/0/0                
0/0/0
10.0.0.4        65002         90         91       0       1       42:54 0/2/0                
0/0/0
10.0.0.6        65002         87         90       0       3           3 Active
10.1.12.1       65001         89         89       0       1       42:54 4/4/0                
0/0/0

show bgp summary (When a Peer Is Established)

user@host> show bgp summary
Groups: 1 Peers: 3 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
inet.0                 6          4          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn 
State|#Active/Received/Damped...
10.0.0.2        65002      88675      88652       0       2       42:38 2/4/0                
0/0/0
10.0.0.3        65002      54528      54532       0       1     2w4d22h 0/0/0               
 0/0/0
10.0.0.4        65002      51597      51584       0       0     2w3d22h 2/2/0                
0/0/0

show bgp summary (CLNS)

user@host> show bgp summary
Groups: 1 Peers: 1 Down peers: 0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped...
10.245.245.1      200       1735       1737       0       0    14:26:12 Establ
  bgp.isovpn.0: 3/3/0
  aaaa.iso.0: 3/3/0

show bgp summary (Layer 2 VPN)

user@host> show bgp summary
Groups: 1 Peers: 5 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l2vpn.0            1          1          0          0          0          0
inet.0                 0          0          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped...
10.255.245.35   65299         72         74       0       1       19:00 Establ 
  bgp.l2vpn.0: 1/1/0 
  frame-vpn.l2vpn.0: 1/1/0
10.255.245.36   65299       2164       2423       0       4       19:50 Establ 
  bgp.l2vpn.0: 0/0/0 
  frame-vpn.l2vpn.0: 0/0/0
10.255.245.37   65299         36         37       0       4       17:07 Establ 
  inet.0: 0/0/0
10.255.245.39   65299        138        168       0       6       53:48 Establ 
  bgp.l2vpn.0: 0/0/0 
  frame-vpn.l2vpn.0: 0/0/0
10.255.245.69   65299        134        140       0       6       53:42 Establ 
  inet.0: 0/0/0

show bgp summary (Layer 3 VPN)

user@host> show bgp summary
Groups: 2 Peers: 2 Down peers: 0 
Table          Tot Paths  Act Paths Suppressed    History Damp State Pending 
bgp.l3vpn.0            2          2          0          0          0       0 
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped... 
10.39.1.5           2         21         22       0       0        6:26 Establ 
  VPN-AB.inet.0: 1/1/0 
10.255.71.15        1         19         21       0       0        6:17 Establ 
  bgp.l3vpn.0: 2/2/0 
  VPN-A.inet.0: 1/1/0 
  VPN-AB.inet.0: 2/2/0 
  VPN-B.inet.0: 1/1/0 

Published: 2013-04-03

Published: 2013-04-03