This command creates the BGP protocol instance and BGP configuration context. BGP is administratively enabled upon creation.
The no form of the command deletes the BGP protocol instance and removes all configuration parameters for the BGP instance. BGP must be shut down before deleting the BGP instance. An error occurs if BGP is not shut down first.
no bgp
This command creates the add-paths configuration context and enables add-paths to be configured for one or more families on a BGP instance, BGP group, or BGP neighbor. The BGP add-paths capability allows the router to send and/or receive multiple paths per prefix to/from a peer. The add-paths command without additional parameters is equivalent to removing add-paths support for all address families, which causes sessions that previously negotiated the add-paths capability for one or more address families to go down and come back up without the add-paths capability.
The no form of the command removes add-paths from the configuration of BGP, BGP group, or BGP neighbor, causing sessions established using add-paths to go down and come back up without the add-paths capability.
no add-paths
This command is used to configure the add-paths capability for IPv4 routes (including labeled IPv4 routes on BGP route tunnels). By default, add-paths is not enabled for IPv4 routes.
The maximum number of paths to send per IPv4 prefix is the configured send limit, which is a mandatory parameter. The capability to receive multiple paths per prefix from a peer is configurable using the receive keyword, which is optional. If the receive keyword is not included in the command, the receive capability is enabled by default. Entering the command without optional parameters enables the ability to both send and receive multiple paths per IPv4 prefix with each peer, and configures the router to send the two best paths per prefix to each peer using the default Add-N, N=2 path selection algorithm.
In Release 7.0 and later, the BGP advertise-inactive, add-paths, and export policy commands can be configured such that active, non-BGP routes are advertised. For more information, see Advertise-Inactive, Add-Paths, and Export Policy Interaction.
The no form of the command removes add-path support for IPv4 routes, causing sessions established using add-paths for IPv4 to go down and come back up without the add-paths capability.
no ipv4
This command is used to configure the add-paths capability for VPN-IPv4 routes. By default, add-paths is not enabled for VPN-IPv4 routes.
The maximum number of paths to send per VPN-IPv4 prefix is the configured send limit, which is a mandatory parameter. The capability to receive multiple paths per prefix from a peer is configurable using the receive keyword, which is optional. If the receive keyword is not included in the command, the receive capability is enabled by default.
In Release 7.0 and later, the BGP advertise-inactive, add-paths, and export policy commands can be configured such that active, non-BGP routes are advertised. For more information, see Advertise-Inactive, Add-Paths, and Export Policy Interaction.
The no form of the command removes add-path support for VPN-IPv4 routes, causing sessions established using add-paths for VPN-IPv4 to go down and come back up without the add-paths capability.
no vpn-ipv4
This command is used to configure the add-paths capability for VPN-IPv6 routes. By default, add-paths is not enabled for VPN-IPv6 routes.
The maximum number of paths to send per VPN-IPv6 prefix is the configured send limit, which is a mandatory parameter. The capability to receive multiple paths per prefix from a peer is configurable using the receive keyword, which is optional. If the receive keyword is not included in the command, the receive capability is enabled by default.
In Release 7.0 and later, the BGP advertise-inactive, add-paths, and export policy commands can be configured such that active, non-BGP routes are advertised. For more information, see Advertise-Inactive, Add-Paths, and Export Policy Interaction.
The no form of the command removes add-path support for VPN-IPv6 routes, causing sessions established using add-paths for VPN-IPv6 to go down and come back up without the add-paths capability.
no vpn-ipv6
This command enables the advertising of inactive BGP routes to other BGP peers. By default, BGP only advertises BGP routes to other BGP peers if a given BGP route is chosen by the route table manager as the most preferred route within the system and is active in the forwarding plane. This command allows system administrators to advertise a BGP route even though it is not the most preferred route within the system for a given destination.
In Release 7.0 and later, the BGP advertise-inactive, add-paths, and export policy commands can be configured such that active, non-BGP routes are advertised. For more information, see Advertise-Inactive, Add-Paths, and Export Policy Interaction.
The no form of the command disables the advertising of inactive BGP routers to other BGP peers.
no advertise-inactive
This command configures the IPv4 transport peers to exchange labeled-BGP routes for the IPv4 address family.
When ipv4 is enabled, all IPv4 routes advertised to the remote BGP peer will be sent with an RFC 3107-formatted label for the destination route.
The no form of the command disables advertising of labeled routes.
no advertise-label
This command is used to set the router ID in the BGP aggregator path attribute to 0 when BGP aggregates routes. This prevents different routers within an AS from creating aggregate routes that contain different AS paths.
When BGP is aggregating routes, it adds the aggregator path attribute to the BGP Update messages. By default, BGP adds the AS number and router ID to the aggregator path attribute.
When this command is enabled, BGP adds only the router ID (set to 0) to the aggregator path attribute. This command is used at the group level to revert to the value defined under the global level, and this command is used at the neighbor level to revert to the value defined under the group level.
The no form of the command used at the global level reverts to the default, where BGP adds the AS number and router ID to the aggregator path attribute.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
no aggregator-id-zero
This command configures the BGP authentication key.
Authentication is performed between neighboring routers before setting up the BGP session by verifying the password. Authentication is performed using the MD5 message-based digest.
The authentication key can be any combination of ASCII characters up to 255 characters long.
The TCP MD5 key information used to securely communicate with a BGP peer is retained even after the connection has closed, allowing connectionless RST packets to be sent with the proper authentication data.
The no form of the command reverts to the default value.
MD5 authentication is disabled by default
This command enables BGP Fast Reroute (FRR) with Prefix-Independent Convergence (PIC), allowing for the creation of a backup path for IPv4 learned prefixes belonging to the router. Multiple paths must be received for a prefix in order to take advantage of this feature.
When a prefix has a backup path, and its primary paths fail, the affected traffic is rapidly diverted to the backup path without waiting for control plane reconvergence to occur. The time to reroute the traffic is independent of the number of prefixes sharing the primary or backup paths.
no backup-path
This command enables path selection configuration.
This command specifies whether the AS path is used to determine the best BGP route.
If this command is enabled, the AS paths of incoming routes are not used in the route selection process.
When as-path-ignore is used without specifying any keywords, all keywords are configured.
The no form of the command means that the AS paths of incoming routes are used to determine the best BGP route.
no as-path-ignore
This command enables the use of bidirectional forwarding (BFD) to control the state of the associated protocol interface. By enabling BFD on a given protocol interface, the state of the protocol interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for BFD are set via the BFD command under the IP interface.
The no form of this command removes BFD from the associated IGP/BGP protocol adjacency.
no bfd-enable
This command configures the cluster ID for a route reflector server.
Route reflectors are used to reduce the number of IBGP sessions required within an AS. Normally, all BGP speakers within an AS must have a BGP peering with every other BGP speaker in the AS. A route reflector and its clients form a cluster. Peers that are not part of the cluster are considered to be non-clients.
When a route reflector receives a route, it must first select the best path from all the paths received. If the route was received from a non-client peer, then the route reflector sends the route to all clients in the cluster. If the route came from a client peer, the route reflector sends the route to all non-client peers and to all client peers except the originator.
For redundancy, a cluster can have multiple route reflectors.
The no form of the command deletes the cluster ID and effectively disables route reflection for the given group.
no cluster
This command configures the BGP connect retry timer value in seconds. When this timer expires, BGP tries to reconnect to the configured peer. This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used.
The no form of the command used at the global level reverts to the default value.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
120 s
This command enables BGP route damping for learned routes that are defined within the route policy. Use damping to reduce the number of update messages sent between BGP peers and reduce the load on peers without affecting the route convergence time for stable routes. Damping parameters are set at the route policy level. See 7705 SAR OS Router Configuration Guide, ‘Route Policy Command Reference”.
The no form of the command disables learned route damping.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
no damping
This command advertises the default RTC route towards the selected peers.
The default RTC route is a special route that has a prefix length of zero. Sending the default RTC route to a peer conveys a request to receive all VPN routes from that peer, whether or not they match the route target extended community. Advertising the default RTC route to a peer does not suppress other more specific RTC routes from being sent to that peer.
The no form of the command blocks the router from advertising the default RTC route.
no default-route-target
This command creates a text description stored in the configuration file for a configuration context.
The no form of the command removes the description string from the context.
No description is associated with the configuration context
This command disables the reflection of routes by the route reflector to the clients in a specific group or neighbor.
This command only disables the reflection of routes from other client peers. Routes learned from non-client peers are still reflected to all clients.
The no form re-enables client reflection of routes.
no disable-client-reflect
This command configures BGP to disable sending communities.
no disable-communities
This command configures BGP fast external failover.
For EBGP neighbors, this feature controls whether the router should drop an EBGP session immediately upon an interface-down event, or whether the BGP session should be kept up until the hold-time expires.
When fast external failover is disabled, the EBGP session stays up until the hold-time expires or the interface comes back up. If the BGP routes become unreachable as a result of the down IP interface, BGP withdraws the unavailable route immediately from other peers.
no disable-communities
This command enables BGP peer tracking. BGP peer tracking allows a BGP peer to be dropped immediately if the route used to resolve the BGP peer address is removed from the IP routing table and there is no alternative available. The BGP peer will not wait for the hold timer to expire; therefore, the BGP reconvergence process is accelerated.
The no form of the command disables peer tracking.
no enable-peer-tracking
This command enables a route reflector of VPN-IP routes to be deployed in the data path between two BGP peers (a peer X and a peer Y) in a next-hop resolution.
All received VPN-IP routes are imported into a table that is used to resolve the BGP next hops. The next hop of a VPN-IP route that is imported from peer X and selected as having the best path by the table is advertised to peer Y (the next-hop-self command must be set for peer Y or a next-hop action must be used in an export policy that is applied to peer Y in order for the next-hop to be advertised to peer Y).
A new VPN service label value is then allocated for the VPN-IP route. This new label is advertised to peer Y and a label swap operation is then performed by the IOM.
The no form of the command disables the advertising of a new VPN service label from one BGP peer to another.
no enable-rr-vpn-forwarding
This command specifies the export route policy used to determine which routes are advertised to peers. Route policies are configured in the config>router>policy-options context. Refer to the section on “Route Policy” in the 7705 SAR OS Router Configuration Guide.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific level is used.
When multiple policy names are specified, the policies are evaluated in the order in which they are specified. A maximum of five (5) policy names can be configured. The first policy that matches is applied.
When multiple export commands are issued, the last command entered overrides the previous command.
When no export policies are specified, BGP routes are advertised and non-BGP routes are not advertised (by default).
In Release 7.0 and later, the BGP advertise-inactive, add-paths, and export policy commands can be configured such that active, non-BGP routes are advertised. For more information, see Advertise-Inactive, Add-Paths, and Export Policy Interaction.
The no form of the command removes the policy association with the BGP instance. To remove association of all policies, use the no export command without arguments.
no export
This command specifies the address family or families to be supported over BGP peerings in the base router. One or more address families can be specified in a single command. To add an address family to the currently configured families, re issue the command by including the current families in addition to any new family.
The no form of the command removes the specified address family from the associated BGP peerings. If an address family is not specified, the supported address family is reset to the default.
ipv4
The command enables procedures for BGP graceful restart (GR) helper—the receiving router role, as defined in the RFC 4724 standard—for all received IPv4 and VPN-IPv4 routes. In order for helper mode to be available for a particular address family, both peers must signal GR support for the address family during capability negotiation.
When a neighbor covered by GR helper mode restarts its control plane, the forwarding of traffic can continue uninterrupted while the session is being re-established and routes are relearned.
The no form of the command disables graceful restart and removes all graceful restart configurations in the BGP instance.
no graceful-restart
This command configures the maximum amount of time in seconds that stale routes should be maintained after a graceful restart is initiated.
The no form of the command resets the stale routes time back to the default value.
360 s
This command creates a context to configure a BGP peer group.
The no form of the command deletes the specified peer group and all configurations associated with the peer group. The group must be shut down before it can be deleted.
no group
This command configures the BGP hold time, expressed in seconds.
The BGP hold time specifies the maximum time BGP waits between successive messages (either Keepalive or Update) from its peer, before closing the connection. This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used.
The min option ensures a minimum hold time for a BGP session that is independent of the hold time advertised in a received Open message. The min option replaces the strict keyword used prior to Release 7.0. If a pre-Release 7.0 configuration database file is loaded that contains the strict keyword, the default value for min is set to the same value as the hold time (that is, seconds2 is equal to seconds).
Even though the 7705 SAR OS implementation allows setting the keepalive time separately, the configured keepalive timer is overridden by the hold-time value under the following circumstances.
The no form of the command used at the global level reverts to the default value.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
90 s
This command enables IBGP multipath load balancing when adding BGP routes to the route table if the route resolving the BGP next-hop offers multiple next-hops.
The no form of the command disables the IBGP multipath load balancing feature.
no ibgp-multipath
This command specifies the import route policy to be used to determine which routes are accepted from peers. Route policies are configured in the config>router>policy-options context. Refer to the section on “Route Policy” in the 7705 SAR OS Router Configuration Guide.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific level is used.
When multiple policy names are specified, the policies are evaluated in the order in which they are specified. A maximum of five (5) policy names can be specified. The first policy that matches is applied.
When multiple import commands are issued, the last command entered will override the previous command.
When an import policy is not specified, BGP routes are accepted by default.
The no form of the command removes the policy association with the BGP instance. To remove association of all policies, use no import without arguments.
no import
This command configures the BGP keepalive timer. A Keepalive message is sent every time this timer expires.
The keepalive parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used. The keepalive value is generally one-third of the hold-time interval. Even though the 7705 SAR OS implementation allows the keepalive value and the hold-time interval to be independently set, under the following circumstances, the configured keepalive value is overridden by the hold-time value.
The no form of the command used at the global level reverts to the default value.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
30 s
This command configures the local IP address used by the group or neighbor when communicating with BGP peers.
Outgoing connections use the local-address as the source of the TCP connection when initiating connections with a peer.
When a local address is not specified, the 7705 SAR OS uses the system IP address when communicating with IBGP peers and uses the interface address for directly connected EBGP peers. This command is used at the neighbor level to revert to the value defined under the group level.
The no form of the command removes the configured local address for BGP.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
no local-address
This command configures a BGP virtual autonomous system (AS) number.
In addition to the AS number configured for BGP in the config>router>autonomous-system context, a virtual (local) AS number is configured. The virtual AS number is added to the as-path attribute before the router’s AS number makes the virtual AS the second AS in the AS path.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). By specifying this parameter at each neighbor level, it is possible to have a separate AS number per EBGP session.
When a command is entered multiple times for the same AS, the last command entered is used in the configuration. The private attribute can be added or removed dynamically by reissuing the command.
Changing the local AS at the global level in an active BGP instance causes the BGP instance to restart with the new local AS number.
Changing the local AS at the group level in an active BGP instance causes BGP to re-establish the peer relationships with all peers in the group with the new local AS number.
Changing the local AS at the neighbor level in an active BGP instance causes BGP to re-establish the peer relationship with the new local AS number.
This is an optional command and can be used in the following situation.
Example: Provider router P is moved from AS1 to AS2. The customer router that is connected to P, however, is configured to belong to AS1. To avoid reconfiguring the customer router, the local-as value on router P can be set to AS1. Thus, router P adds AS1 to the as-path message for routes it advertises to the customer router.
The no form of the command used at the global level will remove any virtual AS number configured.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
no local-as
This command configures the default value of the BGP local preference attribute if it is not already specified in incoming routes.
This value is used if the BGP route arrives from a BGP peer without the local-preference integer set.
The specified value can be overridden by any value set via a route policy. This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used.
The no form of the command at the global level specifies that incoming routes with local preference set are not overridden and routes arriving without local preference set are interpreted as if the route had a local preference value of 100.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
no local-preference
This command configures how the BGP peer session handles loop detection in the AS path.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used.
When applied to an ongoing BGP peer session, this command does not take effect until the BGP peer session is re-established.
The no form of the command used at the global level reverts to the default (ignore- loop).
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
ignore-loop
This command is used to advertise the Multi-Exit Discriminator (MED) to BGP peers and assign the path value if the MED is not already set via a route policy (the specified value can be overridden by a MED value that is set via a route policy using the metric command. See the 7705 SAR OS Router Configuration Guide, “Route Policy Configuration Commands”).
The no form of the command used at the global level reverts to the default where the MED is not advertised.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
no med-out (the MED is not advertised)
This command configures the minimum interval, in seconds, at which a path attribute, originated by the local router, can be advertised to a peer.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used.
The no form of the command used at the global level reverts to the default.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
15 s
This command configures the minimum interval, in seconds, at which a prefix can be advertised to a peer.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used.
The no form of the command used at the global level reverts to the default.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
30 s
This command configures the time to live (TTL) value at an originating BGP peer. The TTL value is entered in the IP header of packets that are sent to a terminating BGP peer that is multiple hops away.
The no form of the command used at the global level reverts to the default value.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
1 — EBGP peers are directly connected
64 — IBGP peer
This command enables BGP multipath.
When multipath is enabled, BGP load-shares traffic across multiple links. Multipath can be configured to load-share traffic across a maximum of 16 routes. If the equal-cost routes available are more than the configured value, then routes with the lowest next-hop IP address value are chosen.
This configuration parameter is set at the global level (applies to all peers).
Multipath is disabled if the value is set to 1. When multipath is disabled and multiple equal-cost routes are available, the route with the lowest next-hop IP address will be used.
The no form of the command reverts to the default where multipath is disabled.
no multipath
This command enables the type/subtype in advertised routes to be encoded as 0x010b (extended community type: transitive IPv4-address-specific VRF route import).
The no form of the command encodes the type/subtype as 0x010a (extended community type: transitive IPv4-address-specific L2VPN identifier), in order to preserve backwards compatibility.
no mvpn-vrf-import-subtype-new
This command creates a BGP peer/neighbor instance within the context of the BGP group.
This command can be issued repeatedly to create multiple peers and their associated configurations.
The no form of the command is used to remove the specified neighbor and the entire configuration associated with the neighbor. The neighbor must be administratively shut down before it can be deleted. If the neighbor is not shut down, the command will not result in any action except a warning message on the CLI indicating that the neighbor is still administratively up.
no neighbor — no neighbors are defined
This command enables the use of split horizon. Split horizon prevents routes from being reflected back to a peer that sends the best route. It applies to routes of all address families and to any type of sending peer: EBGP and IBGP.
By default, split horizon is not enabled, meaning that no effort is taken to prevent a best route from being reflected back to the sending peer.
Note: Enabling split horizon may have a detrimental impact on peer and route scaling; therefore, operators are encouraged to use it only when absolutely needed. |
no split-horizon
This command configures the group or neighbor to always set the next-hop path attribute to its own physical interface when advertising to a peer.
This command is primarily used to avoid third-party route advertisements when connected to a multi-access network.
The no form of the command used at the group level allows third-party route advertisements in a multi-access network.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
no next-hop-self
This command opens the configuration tree for sending or accepting BGP filter lists from peers (outbound route filtering (ORF)).
no outbound-route-filtering
This command opens the configuration tree for sending or accepting extended-community-based BGP filters. In order for the no version of the command to work, all sub-commands (send-orf, accept-orf) must be removed first.
no extended-community
This command instructs the router to negotiate the receive capability in the BGP outbound route filtering (ORF) negotiation with a peer, and to accept filters that the peer wishes to send.
The no form of the command causes the router to remove the accept capability in the BGP ORF negotiation with a peer, and to clear any existing ORF filters that are currently in place.
no accept-orf
This command instructs the router to negotiate the send capability in the BGP outbound route filtering (ORF) negotiation with a peer.
This command also causes the router to send a community filter, prefix filter, or AS path filter configured as an inbound filter on the BGP session to its peer as an ORF Action ADD.
The no form of this command causes the router to remove the send capability in the BGP ORF negotiation with a peer.
The no form also causes the router to send an ORF remove action for a community filter, prefix filter, or AS path filter configured as an inbound filter on the BGP session to its peer.
If the comm-id parameters are not exclusively route target communities, the router will extract appropriate route targets and use those. If, for some reason, the comm-id parameters specified contain no route targets, the router will not send an ORF.
no send-orf
This command enables and disables passive mode for the BGP group or neighbor. When in passive mode, BGP will not attempt to actively connect to the configured BGP peers but responds only when it receives a connect open request from the peer.
The no form of the command used at the group level disables passive mode, and BGP actively attempts to connect to its peers.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
no passive
This command configures the autonomous system number for the remote peer. The peer AS number must be configured for each configured peer.
For IBGP peers, the peer AS number must be the same as the autonomous system number of this router configured under the global level.
This command may be configured under the group level for all neighbors in a particular group.
no AS numbers are defined
This command configures the route preference for routes learned from the configured peers.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used.
The lower the preference, the higher the chance of the route being the active route. The 7705 SAR OS assigns the highest default preference to BGP routes as compared to routes that are direct, static, or learned via MPLS or OSPF.
The no form of the command used at the global level reverts to the default value.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
170
This command configures the maximum number of routes that BGP can learn from a peer.
When the number of routes reaches 90% of this limit, an SNMP trap is sent. When the limit is exceeded, the BGP peering is dropped and disabled.
The no form of the command removes the prefix limit.
no prefix-limit
This command disables the delay on issuing BGP withdrawals.
By default, BGP withdrawals (messages containing the routes that are no longer valid) are delayed up to the min-route-advertisement to allow for efficient packing of BGP Update messages. However, when the rapid-withdrawal command is enabled, the delay on sending BGP withdrawals is disabled.
The no form of the command returns BGP withdrawal processing to its default behavior.
no rapid-withdrawal
This command allows all private AS numbers to be removed from the AS path before advertising them to BGP peers. The no form of the command includes private AS numbers in the AS path attribute.
If the limited keyword is included, only the leading private ASNs up to the first public ASN are removed.
When the remove-private parameter is set at the global level, it applies to all peers regardless of group or neighbor configuration. When the parameter is set at the group level, it applies to all peers in the group regardless of the neighbor configuration.
The 7705 SAR OS recognizes the set of AS numbers that are defined by IANA as private. These are AS numbers in the range 64512 through 65535, inclusive.
The no form of the command used at the global level reverts to the default value.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
no remove-private
This command specifies the route targets to be accepted from and advertised to peers. If the route-target-list is a non-null list, only routes with one or more of the given route targets are accepted from or advertised to peers.
This command is only applicable if the router is a route-reflector server.
The route-target-list is assigned at the global level and applies to all peers connected to the system.
The no form of the command with a specified route target community removes the specified community from the route-target-list.
The no form of the command entered without a route target community removes all communities from the list.
no route-target-list
where: | |
ip-addr | a.b.c.d |
comm-val | 0 to 65535 |
2-byte-asnumber | 0 to 65535 |
ext-comm-val | 0 to 4294967295 |
4-byte-asnumber | 0 to 4294967295 |
This command specifies the router ID to be used with this BGP instance. If no router ID is specified, the system interface IP address is used.
Changing the BGP router ID on an active BGP instance causes the BGP instance to restart with the new router ID. The router ID must be set to a valid host address.
no router-id
This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.
The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.
The no form of this command administratively enables an entity.
Unlike other commands and parameters where the default state is not indicated in the configuration file, the shutdown and no shutdown states are always indicated in system-generated configuration files.
Default administrative states for services and service entities are described in Special Cases.
The no form of the command places an entity in an administratively enabled state.
This command selects either RSVP-TE or LDP as the type of Label Switched Path (LSP) transport method that is used to resolve next hops between two BGP peers.
The mpls option allows both RSVP-TE and LDP to be used. The availability of RSVP-TE is checked first; if RSVP-TE is not available then, LDP is selected.
The no form of the command reverts to the default.
ldp
This command configures TTL security parameters for incoming packets. When the feature is enabled, BGP accepts incoming IP packets from a peer only if the TTL value in the packet is greater than or equal to the minimum TTL value configured for that peer.
The no form of the command disables TTL security.
no ttl-security
This command causes the base instance BGP export route policies to be applied to VPN-IPv4 routes.
The no form of the command disables the application of the base instance BGP export route policies to VPN-IPv4 routes.
no vpn-apply-export
This command causes the base instance BGP import route policies to be applied to VPN-IPv4 routes.
The no form of the command disables the application of the base instance BGP import route policies to VPN-IPv4 routes.
no vpn-apply-import
This command creates an aggregate route.
Use this command to group a number of routes with common prefixes into a single entry in the routing table. This reduces the number of routes that need to be advertised by this router and reduces the number of routes in the routing tables of downstream routers.
Both the original components and the aggregated route (source protocol aggregate) are offered to the Routing Table Manager (RTM). Subsequent policies can be configured to assign protocol-specific characteristics, such as the OSPF tag, to aggregate routes.
Multiple entries with the same prefix but a different mask can be configured; routes are aggregated to the longest mask. If one aggregate is configured as 10.0/16 and another as 10.0.0/24, then route 10.0.128/17 would be aggregated into 10.0/16 and route 10.0.0.128/25 would be aggregated into 10.0.0/24. If multiple entries are made with the same prefix and the same mask, the previous entry is overwritten.
The no form of the command removes the aggregate.
no aggregate
This command configures the autonomous system (AS) number for the router. A router can only belong to one AS. An AS number is a globally unique number within an AS. This number is used to exchange exterior routing information with neighboring ASs and as an identifier of the AS itself.
If the AS number is changed on a router with an active BGP instance, the new AS number is not used until the BGP instance is restarted either by administratively disabling/enabling (shutdown/no shutdown) the BGP instance or rebooting the system with the new configuration.
no autonomous-system
This command configures the router ID for the router instance.
The router ID is used by both OSPF and BGP routing protocols in this instance of the routing table manager. IS-IS uses the router ID value as its system ID.
When configuring a new router ID, protocols are not automatically restarted with the new router ID. The next time a protocol is initialized, the new router ID is used. This can result in an interim period of time when different protocols use different router IDs.
To force the new router ID to be used, issue the shutdown and no shutdown commands for each protocol that uses the router ID, or restart the entire router.
The no form of the command reverts to the default value.
The system uses the system interface address (which is also the loopback address). If a system interface address is not configured, use the last 32 bits of the chassis MAC address.
Note: The following command outputs are examples only; actual displays may differ depending on supported functionality and user configuration. |
The command displays router instance information.
This command enables the context to display BGP-related information.
This command displays BGP routes that have been dampened due to route flapping. This command can be entered with or without a route parameter. If no parameters are included, all dampened routes are listed.
If the keyword detail is included, more detailed information is displayed.
If a damp-type is specified, only those types of dampened routes (decayed, history, or suppressed) are displayed. Routes that have a state of decayed have gained penalties for flapping but have not yet reached the suppression limit. Routes that have a state of history have had a route flap and have been withdrawn. Routes that have a state of suppressed have reached the suppression limit and are not considered in BGP path selection.
The following output is an example of BGP damping information, and Table 57 describes the fields.
Label | Description |
BGP Router ID | The local BGP router ID |
AS | The configured autonomous system number |
Local AS | The configured or inherited local AS for the specified peer group; if not configured, it is the same value as the AS |
Network | The IP prefix and mask length for the route |
Flag/Flags | Legend: Status codes: u-used, s-suppressed, h-history, d-decayed, *-valid (if an * is not present, the status is invalid) Origin codes: i-IGP, e-EGP, ?-incomplete, >-best |
From | The originator ID path attribute value |
Reuse/Reuse time | The time when a suppressed route can be used again |
AS-Path | The BGP AS path for the route |
Peer | The router ID of the advertising router |
NextHop | The BGP next hop for the route |
Peer AS | The autonomous system number of the advertising router |
Peer Router-Id | The router ID of the advertising router |
Local Pref | The BGP local preference path attribute for the route |
Age | The time elapsed since the service was enabled |
Last update | The time that BGP was last updated |
FOM Present | The current Figure of Merit (FOM) value |
FOM Last upd. | The last updated FOM value |
Number of Flaps | The number of flaps in the neighbor connection |
Reuse time | The time when the route can be reused |
Path | The BGP AS path for the route |
Applied Policy | The applied route policy name |
This command displays group information for a BGP peer group. This command can be entered with or without parameters.
When this command is entered without a group name, information about all peer groups displays.
When the command is issued with a specific group name, information only pertaining to that specific peer group displays.
The “State” field displays the BGP group’s operational state. Valid states are:
The following output is an example of BGP group information, and Table 58 describes the fields.
Label | Description |
Group | The BGP group name |
Group Type | No Type: peer type not configured External: peer type configured as external BGP peers Internal: peer type configured as internal BGP peers |
State | Disabled: the BGP peer group has been operationally disabled Down: the BGP peer group is operationally inactive Up: the BGP peer group is operationally active |
Peer AS | The configured or inherited peer AS for the specified peer group |
Local AS | The configured or inherited local AS for the specified peer group |
Local Address | The configured or inherited local address for originating peering for the specified peer group |
Loop Detect | The configured or inherited loop detect setting for the specified peer group |
Connect Retry | The configured or inherited connect retry timer value |
Authentication | None: no authentication is configured MD5: MD5 authentication is configured |
Local Pref | The configured or inherited local preference value |
MED Out | The configured or inherited MED value that is assigned to advertised routes |
Multihop | The maximum number of router hops a BGP connection can traverse |
AS Override | The setting of the AS override |
Min Route Advt. | The minimum amount of time that must pass between route updates for the same IP prefix |
Min AS Originate | The minimum amount of time that must pass between updates for a route originated by the local router |
Prefix Limit | No Limit: no route limit assigned to the BGP peer group 1 — 4294967295: the maximum number of routes BGP can learn from a peer |
Passive | Disabled: BGP attempts to establish a BGP connection with a neighbor in the specified peer group Enabled: BGP will not actively attempt to establish a BGP connection with a neighbor in the specified peer group |
Next Hop Self | Disabled: BGP is not configured to send only its own IP address as the BGP next hop in route updates to neighbors in the peer group Enabled: BGP sends only its own IP address as the BGP next hop in route updates to neighbors in the specified peer group |
Aggregator ID 0 | Disabled: BGP is not configured to set the aggregator ID to 0.0.0.0 in all originated route aggregates sent to the neighbor in the peer group Enabled: BGP is configured to set the aggregator ID to 0.0.0.0 in all originated route aggregates sent to the neighbor in the peer group |
Remove Private | Disabled: BGP will not remove all private AS numbers from the AS path attribute in updates sent to the neighbor in the peer group Enabled: BGP removes all private AS numbers from the AS path attribute in updates sent to the neighbor in the peer group |
Damping | Disabled: the peer group is configured not to dampen route flaps Enabled: the peer group is configured to dampen route flaps |
Import Policy | The configured import policies for the peer group |
Export Policy | The configured export policies for the peer group |
Hold Time | The configured hold-time setting |
Keep Alive | The configured keepalive setting |
Min Hold Time | The configured minimum hold-time setting |
Cluster Id | The configured route reflector cluster ID None: No cluster ID has been configured |
Client Reflect | Disabled: the BGP route reflector will not reflect routes to this neighbor Enabled: the BGP route reflector is configured to reflect routes to this neighbor |
NLRI | The type of network layer reachability information that the specified peer group can accept Unicast: IPv4 unicast routing information can be carried |
Preference | The configured route preference value for the peer group |
TTL Security | Enabled: TTL security is enabled Disabled: TTL security is disabled |
Min TTL Value | The minimum TTL value configured for the peer |
Graceful Restart | The state of graceful restart |
Stale Routes Time | The length of time that stale routes are kept in the route table |
Auth key chain | The value for the authentication key chain |
Bfd Enabled | Enabled: BFD is enabled Disabled: BFD is disabled |
Creation Origin | The creation method of the peer group |
Split Horizon | The configured split-horizon setting |
List of Peers | A list of BGP peers configured under the peer group |
Total Peers | The total number of peers configured under the peer group |
Established | The total number of peers that are in an established state |
Peer Groups | The number of peer groups |
This command displays a summary of BGP inter-autonomous system (inter-AS) service label information pertaining to a next-hop resolution when enable-rr-vpn-forwarding is enabled.
The following output is an example of inter-AS service label information, and Table 59 describes the fields.
Label | Description |
NextHop | The BGP next hop ID |
Received Label | The service label ID that is received by the Multiprotocol Border Gateway Protocol (MP-BGP) |
Advertised Label | The service label ID that is advertised by the MP-BGP |
Label Origin | The origin of the received label (either external or internal) |
Total Labels allocated | The total number of service labels that are allocated as a result of the next-hop resolution |
This command displays BGP neighbor information. This command can be entered with or without any parameters.
When this command is issued without any parameters, information about all BGP peers displays.
When the command is issued with a specific IP address or ASN, information regarding only that specific peer or peers with the same AS displays.
Note: This information is not available when using SNMP. |
Note: When either received-routes or advertised-routes is specified, the routes that are received from or sent to the specified peer are listed. When either history or suppressed is specified, the routes that are learned from those peers that either have a history or are suppressed are listed. |
The following outputs are examples of BGP neighbor information:
Label | Description |
Peer | The IP address of the configured BGP peer |
Group | The BGP peer group to which this peer is assigned |
Peer AS | The configured or inherited peer AS for the peer group |
Peer Address | The configured address for the BGP peer |
Peer Port | The TCP port number used on the far-end system |
Local AS | The configured or inherited local AS for the peer group |
Local Address | The configured or inherited local address for originating peering for the peer group |
Local Port | The TCP port number used on the local system |
Peer Type | External: peer type configured as external BGP peers |
Internal: peer type configured as internal BGP peers | |
State | Idle: The BGP peer is not accepting connections |
Active: BGP is listening for and accepting TCP connections from this peer | |
Connect: BGP is attempting to establish a TCP connection with this peer | |
Open Sent: BGP has sent an OPEN message to the peer and is waiting for an OPEN message from the peer | |
Open Confirm: BGP has received a valid OPEN message from the peer and is awaiting a KEEPALIVE or NOTIFICATION | |
Established: BGP has successfully established a peering session and is exchanging routing information | |
Last State | Idle: The BGP peer is not accepting connections |
Active: BGP is listening for and accepting TCP connections from this peer | |
Connect: BGP is attempting to establish a TCP connections with this peer | |
Open Sent: BGP has sent an OPEN message to the peer and is waiting for an OPEN message from the peer | |
Open Confirm: BGP has received a valid OPEN message from the peer and is awaiting a KEEPALIVE or NOTIFICATION | |
Last Event | start: BGP has initialized the BGP neighbor |
stop: BGP has disabled the BGP neighbor | |
open: BGP transport connection is opened | |
close: BGP transport connection is closed | |
openFail: BGP transport connection failed to open | |
error: BGP transport connection error | |
connectRetry: the connect retry timer expired | |
holdTime: the hold time timer expired | |
keepAlive: the keepalive timer expired | |
recvOpen: BGP has received an OPEN message | |
revKeepalive: BGP has received a KEEPALIVE message | |
recvUpdate: BGP has received an UPDATE message | |
recvNotify: BGP has received a NOTIFICATION message | |
None: no events have occurred | |
Last Error | The last BGP error and subcode to occur on the BGP neighbor |
Local Family | The configured local family value |
Remote Family | The configured remote family value |
Connect Retry | The configured or inherited connect retry timer value |
Local Pref. | The configured or inherited local preference value |
Min Route Advt. | The minimum amount of time that must pass between route updates for the same IP prefix |
Min AS Originate | The minimum amount of time that must pass between updates for a route originated by the local router |
Multihop | The maximum number of router hops a BGP connection can traverse |
Damping | Disabled: the BGP neighbor is configured not to dampen route flaps |
Enabled: the BGP neighbor is configured to dampen route flaps | |
Loop Detect | Ignore: The BGP neighbor is configured to ignore routes with an AS loop |
Drop: The BGP neighbor is configured to drop the BGP peering if an AS loop is detected | |
Off: AS loop detection is disabled for the neighbor | |
MED Out | The configured or inherited MED value that is assigned to advertised routes |
Authentication | None: no authentication is configured |
MD5: MD5 authentication is configured | |
Next Hop Self | Disabled: BGP is not configured to send only its own IP address as the BGP next hop in route updates to the specified neighbor |
Enabled: BGP will send only its own IP address as the BGP next hop in route updates to the neighbor | |
AggregatorID Zero | Disabled: the BGP neighbor is not configured to set the aggregator ID to 0.0.0.0 in all originated route aggregates |
Enabled: the BGP neighbor is configured to set the aggregator ID to 0.0.0.0 in all originated route aggregates | |
Remove Private | Disabled: BGP will not remove all private AS numbers from the AS path attribute in updates sent to the specified neighbor |
Enabled: BGP will remove all private AS numbers from the AS path attribute in updates sent to the specified neighbor | |
Passive | Disabled: BGP will actively attempt to establish a BGP connection with the specified neighbor |
Enabled: BGP will not actively attempt to establish a BGP connection with the specified neighbor | |
Peer Identifier | The IP identifier for the peer router |
Prefix Limit | No Limit: no route limit assigned to the BGP peer group |
1 — 4294967295: the maximum number of routes BGP can learn from a peer | |
Pref Limit Idle Time* | The length of time that the session is held in the idle state after it is taken down as a result of reaching the prefix limit |
Hold Time | The configured hold-time setting |
Keep Alive | The configured keepalive setting |
Min Hold Time | The configured minimum hold-time setting |
Active Hold Time | The negotiated hold time, if the BGP neighbor is in an established state |
Active Keep Alive | The negotiated keepalive time, if the BGP neighbor is in an established state |
Cluster Id | The configured route reflector cluster ID |
None: no cluster ID has been configured | |
Client Reflect | Disabled: The BGP route reflector is configured not to reflect routes to this neighbor |
Enabled: The BGP route reflector is configured to reflect routes to this neighbor | |
Preference | The configured route preference value for the peer group |
Num of Flaps | The number of route flaps in the neighbor connection |
Recd. Prefixes | The number of routes received from the BGP neighbor |
Recd. Paths | The number of unique sets of path attributes received from the BGP neighbor |
IPv4 Recd. Prefixes | The number of unique sets of IPv4 path attributes received from the BGP neighbor |
IPv4 Active Prefixes | The number of IPv4 routes received from the BGP neighbor and active in the forwarding table |
IPv4 Suppressed Pfxs | The number of unique sets of IPv4 path attributes received from the BGP neighbor and suppressed due to route damping |
VPN-IPv4 Suppr. Pfxs | The number of unique sets of VPN-IPv4 path attributes received from the BGP neighbor and suppressed due to route damping |
VPN-IPv4 Recd. Pfxs | The number of unique sets of VPN-IPv4 path attributes received from the BGP neighbor |
VPN-IPv4 Active Pfxs | The number of VPN-IPv4 routes received from the BGP neighbor and active in the forwarding table |
IPv6 Recd. Prefixes | The number of unique sets of IPv6 path attributes received from the BGP neighbor |
IPv6 Active Prefixes | The number of IPv6 routes received from the BGP neighbor and active in the forwarding table |
VPN-IPv6 Recd. Pfxs | The number of unique sets of VPN-IPv6 path attributes received from the BGP neighbor |
VPN-IPv6 Active Pfxs | The number of VPN-IPv6 routes received from the BGP neighbor and active in the forwarding table |
VPN-IPv6 Suppr. Pfxs | The number of unique sets of VPN-IPv6 path attributes received from the BGP neighbor and suppressed due to route damping |
Backup IPv4 Pfxs | The number of BGP Fast Reroute backup path IPv4 prefixes |
Backup IPv6 Pfxs | The number of BGP Fast Reroute backup path IPv6 prefixes |
Backup Vpn IPv4 Pfxs | The number of BGP Fast Reroute backup path VPN IPv4 prefixes |
Backup Vpn IPv6 Pfxs | The number of BGP Fast Reroute backup path VPN IPv6 prefixes |
Input Queue | The number of BGP messages to be processed |
Output Queue | The number of BGP messages to be transmitted |
i/p Messages | The total number of packets received from the BGP neighbor |
o/p Messages | The total number of packets sent to the BGP neighbor |
i/p Octets | The total number of octets received from the BGP neighbor |
o/p Octets | The total number of octets sent to the BGP neighbor |
i/p Updates | The total number of updates received from the BGP neighbor |
o/p Updates | The total number of updates sent to the BGP neighbor |
TTL Security | Enabled: TTL security is enabled Disabled: TTL security is disabled |
Min TTL Value | The minimum TTL value configured for the peer |
Graceful Restart | The state of graceful restart |
Stale Routes Time | The length of time that stale routes are kept in the route table |
Advertise Inactive | The state of advertising inactive BGP routes to other BGP peers (enabled or disabled) |
Peer Tracking | The state of tracking a neighbor IP address in the routing table for a BGP session |
Advertise Label | Indicates the enabled address family for supporting RFC 3107 BGP label capability |
Auth key chain | The value for the authentication key chain |
Bfd Enabled | Enabled: BFD is enabled Disabled: BFD is disabled |
Local Capability | The capability of the local BGP speaker; for example, route refresh, MP-BGP, ORF |
Remote Capability | The capability of the remote BGP peer; for example, route refresh, MP-BGP, ORF |
Local AddPath Capabi* | The state of the local BGP add-paths capabilities. The add-paths capability allows the router to send and receive multiple paths per prefix to or from a peer. |
Remote AddPath Capab* | The state of the remote BGP add-paths capabilities |
Import Policy | The configured import policies for the peer group |
Export Policy | The configured export policies for the peer group |
Label | Description |
BGP Router ID | The local BGP router ID |
AS | The configured autonomous system number |
Local AS | The configured local AS setting. If not configured, then it is the same value as the AS. |
Flag/Flags | Legend: Status codes: u - used s - suppressed h - history d - decayed * - valid If an * is not present, then the status is invalid Origin codes: i - IGP e - EGP ? - incomplete > - best |
Network | The route IP prefix and mask length for the route |
Next Hop | The BGP next hop for the route |
LocalPref | The BGP local preference path attribute for the route |
MED | The BGP Multi-Exit Discriminator (MED) path attribute for the route |
Path-Id | The path ID that is received as part of the add-path capability |
Label | The BGP label associated with the route |
AS-Path | The BGP AS path for the route |
Label | Description |
BGP Neighbor | The IP address of the BGP neighbor |
Graceful Restart locally configured for peer | The configured state of graceful restart for the local router |
Peer's Graceful Restart feature | The configured state of graceful restart for the peer router |
NLRI(s) that peer supports restart for | The families supported by the peer router for graceful restart |
NLRI(s) that peer saved forwarding for | The families for which the peer router continued to forward packets after graceful restart |
NLRI(s) that restart is negotiated for | The families that negotiate restart during graceful restart |
NLRI(s) of received end-of-rib markers | The families for which end-of-RIB markers have been received |
NLRI(s) of all end-of-rib markers sent | The families for which end-of-RIB markers have been sent |
Restart time locally configured for peer | The length of time configured on the local router for the peer router’s graceful restart |
Restart time requested by the peer | The length of time requested by the peer router for graceful restart |
Time stale routes from peer are kept for | The length of time that the local router continues to support stale routes |
Graceful restart status on the peer | The status of graceful restart on the peer router |
Number of Restarts | The number of restarts since graceful restart is enabled between peers |
Last Restart at | The local time of the last graceful restart |
This command displays BGP next-hop information.
The following output is an example of BGP next-hop information, and Table 63 describes the fields.
Label | Description |
BGP Router ID | The local BGP router ID |
AS | The configured autonomous system number |
Local AS | The configured local AS setting. If not configured, then the value is the same as the AS. |
Next Hop | The next-hop address |
Resolving Prefix | The prefix of the best next hop |
Pref: Preference | The BGP preference attribute for the routes |
Metric | The metric derived from the IGP for a particular next hop |
Reference Count | The number of routes using the resolving prefix |
Owner | The routing protocol used to derive the best next hop |
Resolved Next Hop | The IP address of the next hop |
Egress Label | The VPN label used for VPN-IPv4 data |
Next Hops | The number of next hops |
This command displays a summary of BGP path attributes.
The following output is an example of BGP path information, and Table 64 describes the fields.
Label | Description |
BGP Router ID | The local BGP router ID |
AS | The configured autonomous system number |
Local AS | The configured local AS setting. If not configured, then the value is the same as the AS. |
Path | The AS path attribute |
Next Hop | The advertised BGP next hop |
Origin | EGP: the NLRI is learned by an EGP protocol |
IGP: the NLRI is interior to the originating AS | |
Incomplete: NLRI was learned another way | |
Segments | The number of segments in the AS path attribute |
MED | The Multi-Exit Discriminator value |
Local Preference | The local preference value. This value is used if the BGP route arrives from a BGP peer without the Local Pref attribute set. It is overridden by any value set via a route policy. |
Refs | The number of routes using a specified set of path attributes |
ASes | The number of autonomous system numbers in the AS path attribute |
Flags | IBGP-learned: path attributes learned by an IBGP peering |
Community | The BGP community attribute list |
Cluster List | The route reflector cluster list |
Originator ID | The originator ID path attribute value |
This command displays BGP route information.
When this command is issued without any parameters, the entire BGP routing table displays.
When this command is issued with an IP prefix/mask or IP address, the best match for the parameter displays.
comm-id | as-number1:comm-val1 | ext-comm | well-known-comm | |
ext-comm | type:{ip-address:comm-val1 | as-number1:comm-val2 | as-number2:comm-val1} | |
as-number1 | 0 to 65535 | |
comm-val1 | 0 to 65535 | |
type | target, origin (keywords) | |
ip-address: | a.b.c.d | |
comm-val2 | 0 to 4294967295 | |
as-number2 | 0 to 4294967295 | |
well-known-comm | null | no-export | no-export-subconfed | no-advertise (keywords) |
The following output is an example of BGP route information, and Table 65 describes the fields.
Label | Description |
BGP Router ID | The local BGP router ID |
AS | The configured autonomous system number |
Local AS | The configured local AS setting. If not configured, then the value is the same as the AS. |
Flag/Flags | Legend: Status codes: u - used s - suppressed h - history d - decayed * - valid If an * is not present, then the status is invalid Origin codes: i - IGP e - EGP ? - incomplete > - best |
Network | The IP prefix and mask length |
Nexthop | The BGP next hop |
AS-Path | The BGP AS path attribute |
Local Pref. | The local preference value. This value is used if the BGP route arrives from a BGP peer without the Local Pref attribute set. It is overridden by any value set via a route policy. |
MED | The MED metric value |
none: MED metrics are present | |
VPN Label | The label generated by the PE’s label manager |
Original Attributes | The received BGP attributes of a route from a peer without any modification from any policy |
Modified Attributes | The final BGP attributes of a route after the policies evaluation |
Route Dist. | The route distinguisher identifier attached to routes that distinguishes the VPN it belongs to |
From | The advertising BGP neighbor’s IP address |
Res. Nexthop | The resolved next hop |
Aggregator AS | The aggregator AS value |
none: aggregator AS attributes are not present | |
Aggregator | The aggregator attribute value |
none: aggregator attributes are not present | |
Atomic Aggr. | Atomic: the atomic aggregator flag is set |
Not Atomic: the atomic aggregator flag is not set | |
Community | The BGP community attribute list |
Cluster | The route reflector cluster list |
Originator Id | The originator ID path attribute value |
none: the originator ID attribute is not present | |
Peer Router Id | The router ID of the advertising router |
TieBreakReason | The step in the BGP decision process where a BGP route lost the tie-break with the next BGP route for the same prefix LocalPref — this route is not the best because the next better route has a higher LOCAL_PREF ASPathLen — this route is not the best because the next better route has a shorter AS PATH length Origin — this route is not the best because the next better route has a lower origin value MED — this route is not the best because the next better route has a lower MED, and MED comparison of the routes was allowed IBGP — this IBGP route is not the best because the next better route is an EBGP route NHCost — this route is not the best because the next better route has a lower metric value to reach the BGP NEXT HOP BGPID — this route is not the best because the next better route has a lower originator ID or BGP identifier ClusterLen — this route is not the best because the next better route has a shorter cluster list length PeerIP — this route is not the best because the next better route has a lower neighbor IP address |
VPRN Imported | The VPRNs where a particular BGP-VPN received route has been imported and installed |
This command displays a summary of BGP neighbor information.
If confederations are not configured, that portion of the output will not display.
The “State” field displays the global BGP operational state. The valid values are:
For example, if a BGP peer is operationally disabled, then the state in the summary table shows the state ‘Disabled’.
The following output is an example of BGP summary information, and Table 66 describes the fields.
Label | Description |
BGP Router ID | The local BGP router ID |
AS | The configured autonomous system number |
Local AS | The configured local AS setting. If not configured, then the value is the same as the AS. |
BGP Admin State | Down: BGP is administratively disabled |
Up: BGP is administratively enabled | |
BGP Oper State | Down: BGP is operationally disabled |
Up: BGP is operationally enabled | |
Total Peer Groups | The total number of configured BGP peer groups |
Total Peers | The total number of configured BGP peers |
Total BGP Paths | The total number of unique sets of BGP path attributes learned from BGP peers |
Total Path Memory | The total amount of memory used to store the path attributes |
Total IPv4 Remote Rts | The total number of IPv4 routes learned from BGP peers |
Total IPv4 Remote Act. Rts | The total number of IPv4 routes used in the forwarding table |
Total Supressed Rts | The total number of suppressed routes due to route damping |
Total Hist. Rts | The total number of routes with history due to route damping |
Total Decay Rts | The total number of decayed routes due to route damping |
Total VPN Peer Groups | The total number of configured VPN peer groups |
Total VPN Peers | The total number of configured VPN peers |
Total VPN Local Rts | The total number of configured local VPN routes |
Total VPN-IPv4 Rem. Rts | The total number of configured remote VPN-IPv4 routes |
Total VPN-IPv4 Rem. Act. Rts | The total number of active remote VPN-IPv4 routes used in the forwarding table |
Total VPN Supp. Rts | The total number of suppressed VPN routes due to route damping |
Total VPN Hist. Rts | The total number of VPN routes with history due to route damping |
Total VPN Decay Rts | The total number of decayed routes due to route damping |
Neighbor | The BGP neighbor address |
AS (Neighbor) | The BGP neighbor autonomous system number |
PktRcvd | The total number of packets received from the BGP neighbor |
PktSent | The total number of packets sent to the BGP neighbor |
InQ | The number of BGP messages to be processed |
OutQ | The number of BGP messages to be transmitted |
Up/Down | The amount of time that the BGP neighbor has either been established or not established depending on its current state |
State|Recv/Actv/Sent (Addr Family) | The BGP neighbor’s current state (if not established) or the number of received routes, active routes and sent routes (if established), along with the address family |
This command clears route flap statistics.
This command resets the specified BGP peer or peers. This can cause existing BGP connections to be shut down and restarted.
This command resets the entire BGP protocol.
This command logs all events changing the state of a BGP peer.
This command enables debugging for BGP graceful restart.
The no form of the command disables the debugging.
This command decodes and logs all sent and received Keepalive messages in the debug log.
This command decodes and logs all sent and received Notification messages in the debug log.
This command decodes and logs all sent and received Open messages in the debug log.
This command enables debugging for all BGP outbound route filtering (ORF) packets. ORF is used to inform a neighbor of targets (using target-list) that it is willing to receive.
This command decodes and logs all sent and received BGP packets in the debug log.
This command enables and disables debugging for BGP route refresh.
This command logs RTM changes in the debug log.
This command logs all TCP socket events to the debug log.
This command logs all BGP timer events to the debug log.
This command decodes and logs all sent and received Update messages in the debug log.