show bgp neighbor

 

List of Syntax

Syntax

Syntax (EX Series Switch, QFX Series, and OCX Series)

Syntax

Syntax (EX Series Switch, QFX Series, and OCX 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.

orf option introduced in Junos OS Release 9.2.

exact-instance option introduced in Junos OS Release 11.4.

output-queue option introduced in Junos OS Release 16.1

DontGRHelpFateSharingBfdDown is added to the options field of the command output in Junos OS Release 18.3R1.

Description

Display information about BGP peers.

Options

noneDisplay information about all BGP peers.
exact-instance instance-name(Optional) Display information for the specified instance only.
instance instance-name(Optional) Display information about BGP peers 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 neighbor instance cust1 command).
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical systems or on a particular logical system.
neighbor-address(Optional) Display information for only the BGP peer at the specified IP address.
orf (detail | neighbor-address)(Optional) Display outbound route-filtering information for all BGP peers or only for the BGP peer at the specified IP address. The default is to display brief output. Use the detail option to display detailed output.
output-queue(Optional) Display information regarding the number of routes currently queued in the 17 prioritized BGP output queues.

Additional Information

For information about the local-address, nlri, hold-time, and preference statements, see the Junos OS Routing Protocols Library.

Required Privilege Level

view

Related Documentation

List of Sample Output

show bgp neighbor

show bgp neighbor (dont-help-shared-fate-bfd-down is configured)

show bgp neighbor (CLNS)

show bgp neighbor (Layer 2 VPN)

show bgp neighbor (Layer 3 VPN) (Not supported on the OCX Series.)

show bgp neighbor neighbor-address

show bgp neighbor neighbor-address

show bgp neighbor neighbor-address (BGP Graceful Restart Enabled)

show bgp neighbor neighbor-address (BGP Long-Lived Graceful Restart)

show bgp neighbor orf neighbor-address detail

show bgp neighbor logical-system

show bgp neighbor output-queue

show bgp neighbor (Segment Routing Traffic Engineering)

Output Fields

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

Table 1: show bgp neighbor Output Fields

Field Name

Field Description

Peer

Address of the BGP neighbor. The address is followed by the neighbor port number.

AS

AS number of the peer.

Local

Address of the local routing device. The address is followed by the peer port number.

Type

Type of peer: Internal or External.

State

Current state of the BGP session:

  • Active—BGP is initiating a transport protocol connection in an attempt to connect to a peer. If the connection is successful, BGP sends an Open message.

  • Connect—BGP is waiting for the transport protocol connection to be completed.

  • Established—The BGP session has been established, and the peers are exchanging update messages.

  • Idle—This is the first stage of a connection. BGP is waiting for a Start event.

  • OpenConfirm—BGP has acknowledged receipt of an open message from the peer and is waiting to receive a keepalive or notification message.

  • OpenSent—BGP has sent an open message and is waiting to receive an open message from the peer.

  • route reflector client—The BGP session is established with a route reflector client.

Flags

Internal BGP flags:

  • Aggregate Label—BGP has aggregated a set of incoming labels (labels received from the peer) into a single forwarding label.

  • CleanUp—The peer session is being shut down.

  • Delete—This peer has been deleted.

  • Idled—This peer has been permanently idled.

  • ImportEval—At the last commit operation, this peer was identified as needing to reevaluate all received routes.

  • Initializing—The peer session is initializing.

  • SendRtn—Messages are being sent to the peer.

  • Sync—This peer is synchronized with the rest of the peer group.

  • RSync—This peer in the backup Routing Engine is synchronized with the BGP peer in the master Routing Engine for nonstop active routing.

  • TryConnect—Another attempt is being made to connect to the peer.

  • Unconfigured—This peer is not configured.

  • WriteFailed—An attempt to write to this peer failed.

Last state

Previous state of the BGP session:

  • Active—BGP is initiating a transport protocol connection in an attempt to connect to a peer. If the connection is successful, BGP sends an Open message.

  • Connect—BGP is waiting for the transport protocol connection to be completed.

  • Established—The BGP session has been established, and the peers are exchanging update messages.

  • Idle—This is the first stage of a connection. BGP is waiting for a Start event.

  • OpenConfirm—BGP has acknowledged receipt of an open message from the peer and is waiting to receive a keepalive or notification message.

  • OpenSent—BGP has sent an open message and is waiting to receive an open message from the peer.

Last event

Last activity that occurred in the BGP session:

  • Closed—The BGP session closed.

  • ConnectRetry—The transport protocol connection failed, and BGP is trying again to connect.

  • HoldTime—The session ended because the hold timer expired.

  • KeepAlive—The local routing device sent a BGP keepalive message to the peer.

  • Open—The local routing device sent a BGP open message to the peer.

  • OpenFail—The local routing device did not receive an acknowledgment of a BGP open message from the peer.

  • RecvKeepAlive—The local routing device received a BGP keepalive message from the peer.

  • RecvNotify—The local routing device received a BGP notification message from the peer.

  • RecvOpen—The local routing device received a BGP open message from the peer.

  • RecvUpdate—The local routing device received a BGP update message from the peer.

  • Start—The peering session started.

  • Stop—The peering session stopped.

  • TransportError—A TCP error occurred.

Last error

Last error that occurred in the BGP session:

  • Cease—An error occurred, such as a version mismatch, that caused the session to close.

  • Finite State Machine Error—In setting up the session, BGP received a message that it did not understand.

  • Hold Time Expired—The session's hold time expired.

  • Message Header Error—The header of a BGP message was malformed.

  • Open Message Error—A BGP open message contained an error.

  • None—No errors occurred in the BGP session.

  • Update Message Error—A BGP update message contained an error.

Export

Name of the export policy that is configured on the peer.

Import

Name of the import policy that is configured on the peer.

Options

Configured BGP options:

  • AddressFamily—Configured address family: inet or inet-vpn.

  • AdvertiseBGPStatic—Configured BGP static routes are advertised.

  • AutheKeyChain—Authentication key change is enabled.

  • BfdEnabled—Status of BFD.

  • DontGRHelpFateSharingBfdDown—Status of the dont-help-shared-fate-bfd-down option. If this option is configured the device does not go into graceful restart helper mode.

  • DropPathAttributes—Certain path attributes are configured to be dropped from neighbor updates during inbound processing.

  • GracefulRestart—Graceful restart is configured.

  • HoldTime—Hold time configured with the hold-time statement. The hold time is three times the interval at which keepalive messages are sent.

  • IgnorePathAttributes—Certain path attributes are configured to be ignored in neighbor updates during inbound processing.

  • Local Address—Address configured with the local-address statement.

  • LLGR—BGP long-lived graceful restart capability is configured.

  • LLGRHelperDisabled—BGP long-lived graceful restart is completely disabled for a neighbor.

  • Multihop—Allow BGP connections to external peers that are not on a directly connected network.

  • NLRI—Configured MBGP state for the BGP group: multicast, unicast, or both if you have configured nlri any.

  • Peer AS—Configured peer autonomous system (AS).

  • Preference—Preference value configured with the preference statement.

  • Refresh—Configured to refresh automatically when the policy changes.

  • Rib-group—Configured routing table group.

  • RFC6514CompliantSafi129—Configured SAFI 129 according to RFC 6514 (BGP VPN multicast used to use SAFI 128).

Path-attributes dropped

Path attribute codes that are dropped from neighbor updates.

Path-attributes ignored

Path attribute codes that are ignored during neighbor updates.

Peer does not support LLGR Restarter or Receiver functionality

BGP neighbor does not support long-lived graceful restart (LLGR) restarter mode completely.

Peer does not support LLGR Restarter functionality

BGP neighbor does not support long-lived graceful restart (LLGR) restarter mode for any family.

Authentication key change

(Appears only if the authentication-keychain statement has been configured) Name of the authentication keychain enabled.

Authentication algorithm

(Appears only if the authentication-algorithm statement has been configured) Type of authentication algorithm enabled: hmac or md5.

Address families configured

Names of configured address families for the VPN.

BGP-Static Advertisement Policy

Name of the BGP static policy that is configured on the peer.

Local Address

Address of the local routing device.

Remove-private options

Options associated with the remove-private statement.

Holdtime

Hold time configured with the hold-time statement. The hold time is three times the interval at which keepalive messages are sent.

Flags for NLRI inet-label-unicast

Flags related to labeled-unicast:

  • TrafficStatistics—Collection of statistics for labeled-unicast traffic is enabled.

Traffic statistics

Information about labeled-unicast traffic statistics:

  • Options—Options configured for collecting statistics about labeled-unicast traffic.

  • File—Name and location of statistics log files.

  • size—Size of all the log files, in bytes.

  • files—Number of log files.

Traffic Statistics Interval

Time between sample periods for labeled-unicast traffic statistics, in seconds.

Preference

Preference value configured with the preference statement.

Outbound Timer

Time for which the route is available in Junos OS routing table before it is exported to BGP. This field is displayed in the output only if the out-delay parameter is configured to a non-zero value.

Number of flaps

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

Peer ID

Router identifier of the peer.

Group index

Index number for the BGP peer group. The index number differentiates between groups when a single BGP group is split because of different configuration options at the group and peer levels.

Peer index

Index that is unique within the BGP group to which the peer belongs.

Local ID

Router identifier of the local routing device.

Local Interface

Name of the interface on the local routing device.

Active holdtime

Hold time that the local routing device negotiated with the peer.

Keepalive Interval

Keepalive interval, in seconds.

BFD

Status of BFD failure detection.

Local Address

Name of directly connected interface over which direct EBGP peering is established.

NLRI and times for LLGR configured on peer

Names of address families and stale time for BGP long-lived graceful restart configured on the BGP peer or neighbor.

Times are displayed using the routing protocol daemon (rpd) %#0T format:

<weeks>w<days>d <hours>:<minutes>:<seconds>

Zero leading elements are omitted, for example, a value less than one week do not include the weeks.

NLRI and times that peer supports LLGR Restarter for

Names of address families and stale time that the BGP peer supports for restarter mode for BGP long-lived graceful restart.

Times are displayed using the routing protocol daemon (rpd) %#0T format:

<weeks>w<days>d <hours>:<minutes>:<seconds>

Zero leading elements are omitted, for example, a value less than one week do not include the weeks.

NLRI that peer saved LLGR forwarding for

Name of the address family for which the BGP peer saved BGP long-lived graceful restart forwarding.

Graceful Restart Details

Amount of time that is remaining until LLGR expires and the time remaining on the GR stale timer, along with RIB details, are displayed while LLGR receiver mode is active (a peer that negotiated LLGR has disconnected and not yet reconnected).

NLRI we are holding stale routes for

Names of address families (NLRIs) for which that stale routes are held or preserved when BGP graceful restart receiver mode is active for a neighbor.

Time until end-of-rib is assumed for stale routes

Amount of time remaining on the stale timer until which end-of-RIB (EoR) markers are assumed when BGP graceful restart receiver mode is active for a neighbor.

Time is displayed in Coordinated Universal Time (UTC) format (YYYY-MM-DD-HH:MM:SS). Note that the stale timer display (‘Time until end-of-rib is assumed’) is also present when a session is active, but the neighbor as not yet sent all of the end-of-rib indications.

Time until stale routes are deleted or become long-lived stale

Amount of time up to which stale routes are deleted or become long-lived stale routes when BGP graceful restart receiver mode is active for a neighbor.

NLRI for restart configured on peer

Names of address families configured for restart.

NLRI advertised by peer

Address families supported by the peer: unicast or multicast.

NLRI for this session

Address families being used for this session.

Peer supports Refresh capability

Remote peer’s ability to send and request full routing table readvertisement (route refresh capability). For more information, see RFC 2918, Route Refresh Capability for BGP-4.

Restart time configured on peer

Configured time allowed for restart on the neighbor.

Stale routes from peer are kept for

When graceful restart is negotiated, the maximum time allowed to hold routes from neighbors after the BGP session has gone down.

Peer does not support Restarter functionality

Graceful restart restarter-mode is disabled on the peer.

Peer does not support Receiver functionality

Graceful restart helper-mode is disabled on the peer.

Restart time requested by this peer

Restart time requested by this neighbor during capability negotiation.

Restart flag received from the peer

When this field appears, the BGP speaker has restarted (Restarting), and this peer should not wait for the end-of-rib marker from the speaker before advertising routing information to the speaker.

NLRI that peer supports restart for

Neighbor supports graceful restart for this address family.

NLRI peer can save forwarding state

Neighbor supporting this address family saves all forwarding states.

NLRI that peer saved forwarding for

Neighbor saves all forwarding states for this address family.

NLRI that restart is negotiated for

Router supports graceful restart for this address family.

NLRI of received end-of-rib markers

Address families for which end-of-routing-table markers are received from the neighbor.

NLRI of all end-of-rib markers sent

Address families for which end-of-routing-table markers are sent to the neighbor.

Peer supports 4 byte AS extension (peer-as 1)

Peer understands 4-byte AS numbers in BGP messages. The peer is running Junos OS Release 9.1 or later.

NLRIs for which peer can receive multiple paths

Appears in the command output of the local router if the downstream peer is configured to receive multiple BGP routes to a single destination, instead of only receiving the active route.

Possible value is inet-unicast.

NLRIs for which peer can send multiple paths: inet-unicast

Appears in the command output of the local router if the upstream peer is configured to send multiple BGP routes to a single destination, instead of only sending the active route.

Possible value is inet-unicast.

Table inet.number

Information about the routing table:

  • RIB State—BGP is in the graceful restart process for this routing table: restart is complete or restart in progress.

  • Bit—Number that represents the entry in the routing table for this peer.

  • Send state—State of the BGP group: in sync, not in sync, or not advertising.

  • Active prefixes—Number of prefixes received from the peer that are active in the routing table.

  • Received prefixes—Total number of prefixes from the peer, both active and inactive, that are in the routing table.

  • Accepted prefixes—Total number of prefixes from the peer that have been accepted by a routing policy.

  • Suppressed due to damping—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.

Last traffic (seconds)

Last time any traffic was received from the peer or sent to the peer, and the last time the local routing device checked.

Input messages

Messages that BGP has received from the receive socket buffer, showing the total number of messages, number of update messages, number of times a policy is changed and refreshed, and the buffer size in octets. The buffer size is 16 KB.

Output messages

Messages that BGP has written to the transmit socket buffer, showing the total number of messages, number of update messages, number of times a policy is changed and refreshed, and the buffer size in octets. The buffer size is 16 KB.

Input dropped path attributes

Information about dropped path attributes:

  • Code—Path attribute code.

  • Count—Path attribute count.

Input ignored path attributes

Information about ignored path attributes:

  • Code—Path attribute code.

  • Count—Path attribute count.

Output queue

Number of BGP packets that are queued to be transmitted to a particular neighbor for a particular routing table. Output queue 0 is for unicast NLRIs, and queue 1 is for multicast NLRIs.

It also specifies the routing table name and the NLRI that the table was advertised through, in the format (routing table name, NLRI).

Note: The output queue of routing tables that are not advertised, will only show up at extensive output level.

Trace options

Configured tracing of BGP protocol packets and operations.

Trace file

Name of the file to receive the output of the tracing operation.

Filter Updates recv

(orf option only) Number of outbound-route filters received for each configured address family.

Note: The counter is cumulative. For example, the counter is increased after the remote peer either resends or clears the outbound route filtering prefix list.

Immediate

(orf option only) Number of route updates received with the immediate flag set. The immediate flag indicates that the BGP peer should readvertise the updated routes.

Note: The counter is cumulative. For example, the counter is increased after the remote peer either resends or clears the outbound route filtering prefix list.

Filter

(orf option only) Type of prefix filter received: prefix-based or extended-community.

Received filter entries

(orf option only) List of received filters displayed.

seq

(orf option only) Numerical order assigned to this prefix entry among all the received outbound route filter prefix entries.

prefix

(orf option only) Address for the prefix entry that matches the filter.

minlength

(orf option only) Minimum prefix length, in bits, required to match this prefix.

maxlength

(orf option only) Maximum prefix length, in bits, required to match this prefix.

match

(orf option only) For this prefix match, whether to permit or deny route updates.

Sample Output

show bgp neighbor

user@host > show bgp neighbor

For M Series, MX Series, and T Series routers running Junos OS Release 16.1 or later, the show bgp neighbor output includes the BGP group the peer belongs to, the routing instance (if any) that the peer is configured in, and the routing instance that the peer is using for the forwarding context (if applicable). An example follows.

show bgp neighbor (dont-help-shared-fate-bfd-down is configured)

user@host> show bgp neighbor

show bgp neighbor (CLNS)

user@host> show bgp neighbor

show bgp neighbor (Layer 2 VPN)

user@host> show bgp neighbor

show bgp neighbor (Layer 3 VPN) (Not supported on the OCX Series.)

user@host> show bgp neighbor

show bgp neighbor neighbor-address

user@host> show bgp neighbor 192.168.1.111

show bgp neighbor neighbor-address

user@host> show bgp neighbor 192.168.4.222

show bgp neighbor neighbor-address (BGP Graceful Restart Enabled)

user@router> show bgp neighbor 10.255.255.16

show bgp neighbor neighbor-address (BGP Long-Lived Graceful Restart)

user@router> show bgp neighbor 10.4.12.11

show bgp neighbor orf neighbor-address detail

user@host > show bgp neighbor orf 192.168.165.56 detail

show bgp neighbor logical-system

user@host > show bgp neighbor logical-system ITR1

show bgp neighbor output-queue

user@host > show bgp neighbor output-queue

show bgp neighbor (Segment Routing Traffic Engineering)

user@host > show bgp neighbor