show bgp neighbor

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

AS number of the peer.

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

Type of peer: Internal or External.

Name of the dynamic neighbor template that a peer was created in.

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.

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.

• PrefixLimitIdle—The session moves into an idle state when the number of prefixes received from the neighbor exceeds its prefix-limit value.

• PurgePending—This flag marks one or more routing table (also known as routing information base [RIB]) entries for deletion. The purge job to delete these entries begins after the peer is closed. A purge job keeps running if new routing table entries are marked for deletion.

• PurgeInProgress—The purge job has started and is not yet complete.

• PurgeImpatient—The purge begins as a low priority background job. The Adj-RIB-Out can be cleaned up and a new peering can be established in the background before all routes are deleted. After the peer goes down and the group has closed, the purge becomes a normal priority job.

• 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 primary 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.

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 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 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.

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

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

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 attribute codes that are dropped from neighbor updates.

Path attribute codes that are ignored during neighbor updates.

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

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

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

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

(Appears only if the drop-excess <percentage> or hide-excess <percentage> option in the prefix-limit statement is configured) NLRI for which the prefix-limit statement is configured.

(Appears only if the drop-excess <percentage> or hide-excess <percentage> option in the accepted-prefix-limit statement is configured) NLRI for which the accepted-prefix-limit statement is configured.

(Appears only if the drop-excess <percentage> or hide-excess <percentage> option in the prefix-limit and accepted-prefix-limit statements are configured) Performs the configured action:

• teardown <percentage>— Tears down the session when the maximum number of prefixes is reached.

• drop-excess <percentage>— Drops excess routes when the maximum number of prefixes is exceeded. If you specify a percentage, the routes are logged when the number of prefixes exceeds that percentage value of the maximum number.

• hide-excess <percentage>— Hides excess routes when the maximum number of prefixes is exceeded. If you specify a percentage, the routes are logged when the number of prefixes exceeds that percentage value of the maximum number. If the percentage is modified, the routes are re-evaluated automatically. If the active routes drop below the specified percentage, those routes are kept as hidden.

(Appears only if the drop-excess <percentage> or hide-excess <percentage> option in the prefix-limit and accepted-prefix-limit statements are configured) Number of the maximum prefixes if exceeded, the configured action in the Action field takes place.

(Appears only if the drop-excess <percentage> or hide-excess <percentage> option in the prefix-limitand accepted-prefix-limit statements are configured) Percentage of the maximum dropped or hidden routes if exceeded, displays a warning message in the logs.

(Appears only if the drop-excess <percentage> or hide-excess <percentage> option in the prefix-limit and accepted-prefix-limit statements are configured) Displays the number of routes that are dropped or hidden after exceeding the limit configured in the Limit field. The counter resets only after the peer resets.

Names of configured address families for the VPN.

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

Address of the local routing device.

Options associated with the remove-private statement.

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

Flags related to labeled-unicast:

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

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.

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

Preference value configured with the preference statement.

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 times the BGP session has gone down and then come back up.

Displays thread related state if update threading is enabled:

• Thread sync pending—Thread sync is yet to begin.

• Update thread sync—Syncing peer up with update threads.

• Shard sync—Syncincg peer up with shards. If the peer is in shard sync state, it also displays a hex value indicating which shards are yet to send peer up acknowledgement.

• Thread sync complete—Peer has been synced in update threads and shards.

• Peer UP acknowledgement received from Update Thread—Display peer up acknowledgement received from update threads.

Router identifier of the peer.

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.

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

Router identifier of the local routing device.

Name of the interface on the local routing device.

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

Keepalive interval, in seconds.

Displays the BGP I/O session thread and its state if update threading is enabled.

Displays the BGP I/O session thread and its state if update threading is enabled.

Status of BFD failure detection.

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

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.

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.

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

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).

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.

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.

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.

Names of address families configured for restart.

Address families supported by the peer: unicast or multicast.

Address families being used for this session.

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.

Configured time allowed for restart on the neighbor.

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

Graceful restart restarter-mode is disabled on the peer.

Graceful restart helper-mode is disabled on the peer.

Restart time requested by this neighbor during capability negotiation.

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.

Neighbor supports graceful restart for this address family.

Neighbor supporting this address family saves all forwarding states.

Neighbor saves all forwarding states for this address family.

Router supports graceful restart for this address family.

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

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

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

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.

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.

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 time any traffic was received from the peer or sent to the peer, and the last time the local routing device checked.

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.

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.

Information about dropped path attributes:

• Code—Path attribute code.

• Count—Path attribute count.

Information about ignored path attributes:

• Code—Path attribute code.

• Count—Path attribute count.

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).

If update threading is enabled, the Output Queue field will display the Output Queue count from update threads with an additional field that displays the Output Queue count per RIB as fetched from main or shards.

Configured tracing of BGP protocol packets and operations.

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

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

(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.

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

(orf option only) List of received filters displayed.

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

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

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

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

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

(Appears only if the validation statistics peer option is selected. Count of valid routes received per routing information base (RIB) per BGP neighbor.

(Appears only if the validation statistics peer option is selected. Count of invalid routes due to maximum-length mismatch received per BGP peer-RIB.

(Appears only if the validation statistics peer option is selected. Count of invalid routes due to origin-as mismatch received per BGP peer-RIB.

(Appears only if the validation statistics peer option is selected. Count of unknown routes received per RIB per BGP neighbor.

In the case of invalid routes, an invalid reason is displayed: [max-length | origin-as] mismatch.