The no form of the command removes the string from the configuration.
The no form of the command deletes the AS path regular expression statement.
The no form of the command deletes the AS path regular expression statement.
The no form of the command removes the specified entry from the autonomous system path group.
The no form of the command deletes the community list or the provided community ID.
The no form of the command deletes the route policy configuration.
By default, when a change is made to a policy in the config router policy options context and then committed, the change is effective immediately. There may be circumstances when the changes should or must be delayed; for example, if a policy change is implemented that would effect every BGP peer on a router, the consequences could be dramatic. It is more effective to control changes on a peer by peer basis.
If the triggered-policy command is enabled, and a given peer is established, and you want the peer to remain up, then, in order for a change to a route policy to take effect, a
clear command with the
soft or
soft-inbound option must be used. In other words, when a
triggered-policy is enabled, any routine policy change or policy assignment change within the protocol will not take effect until the protocol is reset or a clear command is issued to re-evaluate route policies; for example,
clear router bgp neighbor x.x.x.x soft. This keeps the peer up and the change made to a route policy is applied only to that peer, or group of peers.
The no form of the command deletes the named route damping profile.
This command configures the half-life parameter for the route damping profile.
When the FoM value falls below the reuse threshold, the route is once again considered valid and can be reused or included in route advertisements.
The no form of the command removes the half life parameter from the damping profile.
The no form of the command removes the maximum suppression parameter from the damping profile.
When the Figure of Merit (FoM) value falls below the reuse threshold, the route is once again considered valid and can be reused or included in route advertisements.
The no form of the command removes the reuse parameter from the damping profile.
A route is suppressed when it has flapped frequently enough to increase the Figure of Merit (FoM) value to exceed the suppress threshold limit. When the
FoM value exceeds the
suppress threshold limit, the route is removed from the route table or inclusion in advertisements.
The no form of the command removes the suppress parameter from the damping profile.
The no form of the command deletes the named prefix list.
The no form of the command deletes the prefix entry from the prefix list.
The no form of the command removes the specified entry from the route policy statement.
The no form of the command removes the OSPF area match criterion.
The no form of the command removes the AS path regular expression statement as a match criterion.
The no form of the command deletes the AS path regular expression statement.
The no form of the command removes the community list match criterion.
The no form of the command deletes the source match criteria for the route policy statement entry.
The flow-spec-dest command has no effect when the policy is not applied as a BGP import or export policy.
The flow-spec-source command has no effect when the policy is not applied as a BGP import or export policy.
The no form of the command removes the criterion from the configuration.
The no form of the command removes the criterion from the configuration.
The no form of the command disables
mvpn-type in the policy evaluation.
The no form of the of the command removes the neighbor IP match criterion from the configuration.
The policy-statement is a logical grouping of match and action criteria. A single
policy-statement can affect routing in one or more protocols and/or one or more protocols peers/neighbors. A single
policy-statement can also affect both the import and export of routing information.
The no form of the command deletes the policy statement.
The no form of the command removes the
policy-variables statement.
The name of the policy variable, with the variable delimited by at-signs (@) at the beginning and the end of the name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
The no form of the command removes the prefix list match criterion.
The no form of the command removes the protocol match criterion.
The no form of the command removes the protocol match criterion.
The no form of the command removes the criterion from the configuration.
The no form of the command removes the tag field match criterion.
The to command context only applies to export policies. If it is used for an import policy, match criteria is ignored.
The no form of the command deletes export match criteria for the route policy statement entry.
The no form of the command removes the OSPF type match criterion.
Any route policy entry without the action command will be considered incomplete and will be inactive.
The no form of the command deletes the action context from the entry.
The no form of the command disables the AS path list editing action from the route policy entry.
If the optional number is specified, then the AS number is prepended as many times as indicated by the number.
The no form of the command disables the AS path prepend action from the route policy entry.
The no form of the command disables the action to edit the community path attribute for the route policy entry.
The no form of the command removes the damping profile associated with the route policy entry.
The no form of the command removes the QoS association of the routes matched by the route policy entry.
The no form of the command deletes the
default-action context for the policy statement.
The install-backup-path command overrides and has no dependency on commands such as the BGP instance
backup-path command or the VPRN-level
enable-bgp-vpn-backup command, which enable BGP fast reroute for an entire address family. The
install-backup-path command provides more precise control over which IP prefixes are supported with pre-programmed backup paths.
The install-backup-path command is supported only in BGP import policies and VRF import policies and has no effect on policy types other than BGP import policies and VRF import policies. The
install‑backup‑path command applies only to the following types of matched routes: IPv4, IPv6, label-IPv4, 6PE, VPN‑IPv4, and VPN-IPv6.
The no form of the command disables assigning a local preference in the route policy entry.
The no form of the command removes the MED attribute from the matched routes.
The no form of the command disables assigning a next hop address in the route policy entry.
The no form of the command disables advertising the next-hop-self option for the route policy entry.
The no form of the command disables setting the BGP origin for the route policy entry.
This command is used to mark BGP IPv4 and IPv6 routes matching the default-action or a specific entry of a route policy with one of the 3 following origin validation states:
The no form of the command disables setting an RTM preference in the route policy entry.
The no form of the command removes the tag.
The no form of the command disables assigning a type in the route policy entry.
all – the route expression evaluates as ‘true’ only if all the exact match entries in the referenced prefix-list have an active route in the route table associated with the policy.
none – the route expression evaluates as ‘true’ only if none of the exact match entries in the referenced prefix-list have an active route in the route table associated with the policy.
