show bgp summary

Default EBGP mode for receive and advertise.

Number of BGP groups.

Number of BGP peers.

Number of down BGP peers.

Name of routing table.

Total number of paths.

Number of active routes.

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.

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

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.

Routes in process by BGP import policy.

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

Peer's AS number.

Number of packets received from the peer.

Number of packets sent to the peer.

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.

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

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

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.