show bgp summary

 

List of Syntax

Syntax

Syntax (EX Series Switch and QFX Series)

Syntax

Syntax (EX Series Switch and QFX Series)

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.

Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

exact-instance option introduced in Junos OS Release 11.4.

group option introduced in Junos OS Release 13.3.

Description

Display BGP summary information.

Options

noneDisplay BGP summary information for all routing instances.
exact-instance instance-name(Optional) Display information for the specified instance only.
groupDisplay overview of bgp information for a particular group
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)

show bgp summary group

show bgp summary (BGP Graceful Restart or Long-Lived Graceful Restart)

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.

Note: When graceful restart or LLGR helper mode is active, the RIB information is now displayed by the show bgp summary command. 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.

Sample Output

show bgp summary (When a Peer Is Not Established)

user@host> show bgp summary

show bgp summary (When a Peer Is Established)

user@host> show bgp summary
user@host> show bgp summary logical-system R3

show bgp summary (CLNS)

user@host> show bgp summary

show bgp summary (Layer 2 VPN)

user@host> show bgp summary

show bgp summary (Layer 3 VPN)

user@host> show bgp summary

show bgp summary group

user@host> show bgp summary group Group2
user@host> show bgp summary logical-system R3 group toR4

show bgp summary (BGP Graceful Restart or Long-Lived Graceful Restart)

user@router> show route receive-protocol bgp 10.4.12.11 detail