show bgp neighbor

AS

AS number of the peer.

Type

Type of peer: Internal or External.

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.

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

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.

Export

Name of the export 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 ignored

Path attribute codes that are ignored during neighbor updates.

Peer does not support LLGR Restarter functionality

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

Authentication algorithm

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

BGP-Static Advertisement Policy

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

Remove-private options

Options associated with the remove-private statement.

Flags for NLRI inet-label-unicast

Flags related to labeled-unicast:

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

Traffic Statistics Interval

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

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.

Threads related state

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.

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.

Local ID

Router identifier of the local routing device.

Active holdtime

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

I/O Session Thread

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

BFD

Status of BFD failure detection.

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 that peer saved LLGR forwarding for

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

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 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 advertised by peer

Address families supported by the peer: unicast or multicast.

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.

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 Receiver functionality

Graceful restart helper-mode is disabled on the peer.

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 peer can save forwarding state

Neighbor supporting this address family saves all forwarding states.

NLRI that restart is negotiated for

Router supports graceful restart for this address family.

NLRI of all end-of-rib markers sent

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

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.

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.

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.

Input dropped path attributes

Information about dropped 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).

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.

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

Trace file

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

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.

Received filter entries

(orf option only) List of received filters displayed.

prefix

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

maxlength

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