The no form of this command administratively enables an entity.
The no form of the command places an entity in an administratively enabled state.
The no form of the command removes the description string from the context.
The no form of the command deletes the BGP protocol instance and removes all configuration parameters for the BGP instance. BGP must be
shutdown before deleting the BGP instance. An error occurs if BGP is not
shutdown first.
The maximum number of paths per IPv4 prefix to send 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 negotiates 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.
The no form of the command disables add-paths support for IPv4 routes, causing sessions established using add-paths for IPv4 to go down and come back up without the add-paths capability.
ipv6 send
send-limit receive
[none
]
The no form of the command disables add-paths support for IPv6 routes, causing sessions established using add-paths for IPv6 to go down and come back up without the add-paths capability.
The no form of the command disables add-paths 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.
The no form of the command disables add-paths 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
] advertise-external [ipv4] [ipv6]
The no form of the command disables the advertising of inactive BGP routers to other BGP peers.
This command configures the IPv4 transport peers to exchange IPv6 prefixes using 6PE, LDP FEC prefixes as RFC3107 labeled IPv4, as well as RFC 3107-labeled IPv4 routes.
If 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. If
include-ldp-fec-prefix option is also enabled, all activated /32 LDP FEC prefixes will be sent the to remote BGP peer with an RFC 3107 formatted label.
The no form of the command disables any or all configured options.
The no form of the command used at the global level reverts to 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 — BGP adds the AS number and router ID to the aggregator path attribute.
This command configures the comparison of BGP routes based on the MED attribute. The default behavior of SR-OS (equivalent to the no form of the command) is to only compare two routes on the basis of MED if they have the same neighbor AS (the first non-confed AS in the received AS_PATH attribute). Also by default, a route without a MED attribute is handled the same as though it had a MED attribute with the value 0. The
always-compare-med command without the
strict-as keyword allows MED to be compared even if the paths have a different neighbor AS; in this case, if neither
zero or
infinity is specified, the
zero option is inferred, meaning a route without a MED is handled the same as though it had a MED attribute with the value 0. When the
strict-as keyword is present, MED is only compared between paths from the same neighbor AS, and in this case,
zero or
infinity is mandatory and tells BGP how to interpret paths without a MED attribute.
as-path-ignore [ipv4
] [vpn-ipv4
] [ipv6
] [vpn-ipv6
] [mcast-ipv4
] [mvpn-ipv4
] [mvpn-ipv6
] [l2-vpn
]
The no form of the command removes the parameter from the configuration.
The new step is skipped when no compare-origin-validation-state is configured.
This command controls how the BGP decision process compares routes on the basis of MED. When deterministic-med is configured, BGP groups paths that are equal up to the MED comparison step based on neighbor AS, and then compares the best path from each group to arrive at the overall best path. This change to the BGP decision process makes best path selection completely deterministic in all cases. Without
deterministic-med, the overall best path selection is sometimes dependent on the order of the route arrival because of the rule that MED cannot be compared in routes from different neighbor AS.
The authentication key can be any combination of ASCII characters up to 255 characters long.
The no form of the command reverts to the default value.
Specifies the key is entered in a more complex encrypted form. If the
hash2 parameter is not used, the less encrypted
hash form is assumed.
[no
] backup-path
[ipv4
] [ipv6
]
The no form of this command removes BFD from the associated IGP/BGP protocol adjacency.
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 an 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, first it must select the best path from all the paths rec
eived. If the route was rec
eived 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.
The no form of the command deletes the cluster ID and effectively disables the Route Reflection for the given group.
no cluster — No cluster ID is defined.
The no form of the command deletes the specified member AS from the confederation.
When members are not specified in the no statement, the entire list is removed and confederations is disabled.
no confederation — No confederations are defined.
The AS number(s) of members that are part of the confederation expressed as a decimal integer. Configure up to 15 members per confed-as-num.
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.
This command enables BGP route damping for learned routes which are defined within the route policy. Use damping to reduc
e 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 via route policy definition.
The no form of the command used at the global level reverts 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.
Half-life: 15 minutes
Max-suppress: 60 minutes
Suppress-threshold: 3000
Reuse-threshold: 750
no damping — Learned route damping is disabled.
[no
] default-route-target
The no form of the command resets the behavior to the default which is to enable the use of 4-byte ASN.
[no
] disable-capability-negotiation
The no form of the command removes this command from the configuration and restores the normal behavior.
[no
] disable-client-reflect
The no form re-enables client reflection of routes.
no disable-client-reflect — Client routes are reflected to all client peers.
[no]
disable-fast-external-failover
[no
] disable-route-table-install
This command specifies whether to disable the installation of all (labeled and unlabeled) IPv4 and IPv6 BGP routes into RTM (Routing Table Manager) and the FIB (Forwarding Information Base) on the base router instance.
ebgp-link-bandwidth family [family ...
(up to 4 max)]
When the egp-link-bandwidth command is configured, BGP automatically adds a link-bandwidth extended community to every route (of the selected types) received from directly connected (single-hop) EBGP peers within the scope of the command.
|
Values
|
ipv4 The command applies to IPv4 and label-IPv4 routes. ipv6 The command applies to IPv6 and 6PE routes. vpn-ipv4 The command applies to VPN-IPv4 routes. vpn-ipv6 The command applies to VPN-IPv6 routes.
|
When the enable-origin-validation command is added to the configuration of a group or neighbor, it causes every inbound IPv4 and/or IPv6 route from that peer to be marked with one of the 3 following origin validation states:
The enable-origin-validation command applies to all types of BGP peers, but as a general rule, it should only be applied to EBGP peers and groups that contain only EBGP peers.
The no form of the command disallows ASBRs to advertise VPRN routes to their peers in other autonomous systems.
[no
] enable-peer-tracking
The no form of the command disables peer tracking.
[no
] enable-rr-vpn-forwarding
export policy-name [policy-name…]
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 — No export policy is specified. BGP routes are advertised and non-BGP routes are not advertised.
family [ipv4
] [vpn-ipv4
] [ipv6
] [mcast-ipv4
] [l2-vpn
] [mvpn-ipv4
] [mvpn-ipv6
] [flow-ipv4
] [flow-ipv6
] [mdt-safi
] [ms-pw
] [route-target
] [mcast-vpn-ipv4
] [evpn
]
The no form of the command removes the specified address family from the associated BGP peerings. If an address family is not specified, then reset the supported address family back to the default.
The no form of the command disables the validation procedure.
This command specifies the route target(s) to be accepted from or 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.
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.
The no form of the command prevents BGP from performing any third party next-hop processing toward any single-hop EBGP peers within the scope of the command. No third-party next-hop means the next-hop will always carry the IP address of the interface used to establish the TCP connection to the peer.
The no form of the command disables the application of the base instance BGP route policies to vpn-ipv4/6, mvpn-ipv4/6, l2-vpn, mdt-safi, mcast-vpn-ipv4, and evpn routes.
The no form of the command disables the application of the base instance BGP import route policies to vpn-ipv4/6, mvpn-ipv4/6, l2-vpn, mdt-safi, mcast-vpn-ipv4, and evpn routes.
The no form of the command disables graceful restart.
[no
] update-fault-tolerance
This command enables treat-as-withdraw and other similarly non-disruptive approaches for handling a wide range of UPDATE message errors, as long as there are no length errors that prevent all of the NLRI fields from being correctly identified and parsed.
The no form of the command resets the stale routes time back to the default of 360 seconds.
The no form of the command deletes the specified peer group and all configurations associated with the peer group. The group must be
shutdown before it can be deleted.
Even though the implementation allows setting the keepalive time separately, the configured
keepalive timer is overridden by the
hold-time value under the following circumstances:
|
2.
|
If the hold-time is set to zero, then the operational value of the keepalive time is set to zero; the configured keepalive time is not changed. This means that the connection with the peer is up permanently and no keepalive packets are sent to the peer.
|
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.
The no form of the command disables the IBGP multipath load balancing feature.
When origin-invalid-unusable is configured, all routes that have an origin validation state of ‘Invalid’ are considered unusable by the best path selection algorithm, meaning they are not used for forwarding and not advertised to BGP peers.
With the default of no origin-invalid-unusable, routes with an origin validation state of ‘Invalid’ are compared to other ‘usable’ routes for the same prefix according to the BGP decision process.
import policy-name [policy-name…]
When multiple import commands are issued, the last command entered will override the previous command.
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 — No import policy specified (BGP routes are accepted).
The keepalive parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-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 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:
|
1.
|
If the specified keepalive value is greater than the configured hold-time, then the specified value is ignored, and the keepalive is set to one third of the current hold-time value.
|
|
2.
|
If the specified hold-time interval is less than the configured keepalive value, then the keepalive value is reset to one third of the specified hold-time interval.
|
|
3.
|
If the hold-time interval is set to zero, then the configured value of the keepalive value is ignored. This means that the connection with the peer is up permanently and no keepalive packets are sent to the peer.
|
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.
Outgoing connections use the local-address as the source of the TCP connection when initiating connections with a peer.
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 - The router ID is used when communicating with IBGP peers and the interface address is used for directly connected EBGP peers.
local-as as-number [private
] [no-prepend-global-as]
When the local-as command is applied to a BGP neighbor and the local-as is different from the peer-as, the session comes up as EBGP and by default the global-AS number and then (in that order) the local-as number are prepended to the AS_PATH attribute in outbound routes sent to the peer. In received routes from the EBGP peer, the local AS is prepended to the AS path by default, but this can be disabled with the
private option.
When the local-as command is applied to a BGP neighbor and the local-as is the same as the peer-as, the session comes up as IBGP, and by default, the global-AS number is prepended to the AS_PATH attribute in outbound routes sent to the peer.
When the optional no-prepend-global-as command is configured, the global-as number is not added in outbound routes sent to an IBGP or EBGP peer.
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.
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 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 — Does not override the local-preference value set in arriving routes and analyze routes without local preference with value of 100.
loop-detect {drop-peer
| discard-route | ignore-loop
| off
}
The no form of the command used at the global level reverts to default, which is
loop-detect 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.
The no form of the command used at the global level reverts to 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.
The no form of the command used at the global level reverts to 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.
The no form of the command is used to disable this feature.
The no form of the command is used to convey to the BGP instance that the EBGP peers are directly connected.
The
no form of the command used at the global level reverts to 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.
1 — EBGP peers are directly connected.
The no form of the command used at the global level reverts to default where
multipath is disabled.
[no
] mvpn-vrf-import-subtype-new
The no form of the command (the default) encodes the type/subtype as 0x010a (to preserve backwards compatibility).
The label-route-transport-tunnel and
family nodes are simply contexts to configure the binding of IPv4 or IPv6 BGP labeled routes to tunnels.
If the resolution option is explicitly set to
disabled, the default binding to LDP tunnel resumes. If
resolution is set to
any, any supported tunnel type in BGP label route context will be selected following TTM preference.
The ldp value instructs BGP to search for an LDP LSP with a FEC prefix corresponding to the address of the BGP next-hop.
The rsvp value instructs BGP to search for the best metric RSVP LSP to the address of the BGP next-hop. This address can correspond to the system interface or to another loopback used by the BGP instance on the remote node. The LSP metric is provided by MPLS in the tunnel table. In the case of multiple RSVP LSPs with the same lowest metric, BGP selects the LSP with the lowest tunnel-id.
If one or more explicit tunnel types are specified using the resolution-filter option, then only these tunnel types will be selected again following the TTM preference.
When the sr-isis (
sr-ospf) value is enabled, a tunnel to the BGP next-hop is selected in the TTM from the lowest numbered ISIS (OSPF).
The user must set resolution to
filter to activate the list of tunnel-types configured under
resolution-filter.
The default next-hop resolution policy (when the no policy command is configured) is to use the longest matching active route in RTM that is not a BGP route (unless
use-bgp-routes is configured), an aggregate route or a subscriber management route.
The shortcut-tunnel and
family nodes are simply contexts to configure the binding of BGP unlabelled routes to tunnels.
If resolution is set to
any, any supported tunnel type in BGP shortcut context will be selected following TTM preference. If one or more explicit tunnel types are specified using the
resolution-filter option, then only these tunnel types will be selected again following the TTM preference.
The ldp value instructs BGP to search for an LDP LSP with a FEC prefix corresponding to the address of the BGP next-hop.
The bgp value instructs BGP to search for a BGP LSP with a RFC 107 label route prefix matching the address of the BGP next-hop.
The rsvp value instructs BGP to search for the best metric RSVP LSP to the address of the BGP next-hop. This address can correspond to the system interface or to another loopback used by the BGP instance on the remote node. The LSP metric is provided by MPLS in the tunnel table. In the case of multiple RSVP LSPs with the same lowest metric, BGP selects the LSP with the lowest tunnel-id.
When the sr-isis (
sr-ospf) value is enabled, a tunnel to the BGP next-hop is selected in the TTM from the lowest numbered ISIS (OSPF) instance.
The user must set resolution to
filter to activate the list of tunnel-types configured under
resolution-filter.
If disallow-igp is enabled, the BGP route will not be activated using IP next-hops in RTM if no tunnel next-hops are found in TTM.
[no
] outbound-route-filtering
In order for the no version of the command to work, all sub-commands (
send-orf,
accept-orf) must be removed first.
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.
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 parameter(s) are not exclusively route target communities then the router will extract appropriate route targets and use those. If, for some reason, the
comm-id parameter(s) specified contain no route targets, then the router will not send an ORF.
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
shutdown before attempting to delete it. If the neighbor is not shutdown, the command will not result in any action except a warning message on the console indicating that neighbor is still administratively up.
[no
] next-hop-self
{[ipv4
] [vpn-ipv4
] [ipv6
] [mcast-ipv4
] [l2-vpn
]} [multihoming
primary-anycast secondary-anycast]
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 — Third-party route advertisements are allowed.
The no form of the command used at the group level disables passive mode where 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 — BGP will actively try to connect to all the configured peers.
The no form of the command disables path MTU discovery.
[no
] preference
preference
The lower the preference the higher the chance of the route being the active route. The router assigns BGP routes highest default preference 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 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.
The no form of the command reverts to the default.
rapid-update {[l2-vpn
] [mvpn-ipv4
] [mvpn-ipv6
] [mdt-safi
] [evpn
]}
The no form of the command removes this command from the configuration and returns withdrawal processing to the normal behavior.
prefix-limit family limit [log-only
] [threshold
percentage] [idle-timeout
{minutes | forever
}] [post-import
]
The prefix-limit command allows each address family to have its own limit; a set of address family limits can be applied to one neighbor or to all neighbors in a group.
The no form of the command removes the
prefix-limit.
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 no form of the command used at the global level reverts to 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.
The configuration default is no split-horizon, meaning that no effort is taken to prevent a best route from being reflected back to the sending peer.
The no form of the command defaults to LDP as transport LSP method for model B or C connectivity.
The no form of the command disables TTL security.
[no
] type
{internal
| external
}
This command designates the BGP peer as type internal or external.
The type of internal indicates the peer is an IBGP peer while the type of external indicates that the peer is an EBGP peer.
The no form of the command used at the group level reverts to the default value.
The
no form of the command used at the neighbor level reverts to the value defined at the group level.
no type — Type of neighbor is derived on the local AS specified.
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 with 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 mh-secondary-interface
address {ip-address/mask | ip-address netmask}
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.
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 to reverts to the default value
.
