For feedback and comments: |
documentation.feedback@alcatel-lucent.com |
![]() |
![]() |
![]() |
![]() |
description stringThe no form of the command removes the string from the configuration.no as-path nameThe no form of the command deletes the AS path regular expression statement.as-path-group nameno as-path-group nameThe 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 entry ID expressed as a decimal integer. An entry-id uniquely identifies match criteria and the corresponding action. It is recommended that multiple entries be given entry-ids in staggered increments. This allows users to insert a new entry in an existing policy without requiring renumbering of all the existing entries.
Values The no form of the command deletes the community list or the provided community ID.no community — No community names or members are specified.
•
• reg-ex1 reg-ex2— A regular expression string. Allowed values are any string up to 63 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.
• expression expressionfrom community expression "[community list A] OR ([community list B] AND [community list C])"exclusive-lock-time seconds
Values [no] policy-optionsThe no form of the command deletes the route policy configuration.[no] triggered-policyBy 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.half-life minutesThis 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.No half life value is specified. The half life value must be explicitly configured.
Values max-suppress minutesThe no form of the command removes the maximum suppression parameter from the damping profile.
Values reuse integerWhen 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.
Values suppress integerA 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.
Values The no form of the command deletes the named prefix list.[no] prefix ip-prefix/prefix-length { [exact | longer | through length ]| [prefix-length-range length1-length2 ] }no prefix [ipv-prefix/prefix-length] [exact | longer | through length | prefix-length-range length1-length2]The no form of the command deletes the prefix entry from the prefix list.
Values ipv4-prefix: a.b.c.d (host bits must be 0)
ipv4-prefix-length: 0 — 32
ipv6-prefix: x:x:x:x:x:x:x:x (eight 16-bit pieces)
x:x:x:x:x:x:d.d.d.d
x: [0 — FFFF]H
d: [0 — 255]D
ipv6-prefix-length: 0 — 128Specifies the prefix list entry only matches the route with the specified ip-prefix and prefix mask (length) values.Specifies the prefix list entry matches any route that matches the specified ip-prefix and prefix mask length values equal to or greater than the specified mask.through lengthSpecifies the prefix list entry matches any route that matches the specified ip-prefix and has a prefix length between the specified length values inclusive.
Values
Values entry entry-idThe no form of the command removes the specified entry from the route policy statement.The entry ID expressed as a decimal integer. An entry-id uniquely identifies match criteria and the corresponding action. It is recommended that multiple entries be given entry-ids in staggered increments. This allows users to insert a new entry in an existing policy without requiring renumbering of all the existing entries.
Values area area-idThe no form of the command removes the OSPF area match criterion.as-path nameAS path regular expression statements are configured at the global route policy level (config>router>policy-options>as-path name).The no form of the command removes the AS path regular expression statement as a match criterion.no as-path — Matches any AS path.as-path-group nameno as-path-group nameThe no form of the command deletes the AS path regular expression statement.community nameThe no form of the command removes the community list match criterion.no community — Matches any community.The name specified must already be defined.[no] fromThe no form of the command deletes the source match criteria for the route policy statement entry.[no] externalfamily [ipv4] [ipv6] [mcast-ipv4] [mcast-ipv6] [vpn-ipv4] [vpn-ipv6] [l2-vpn] [mvpn-ipv4] [mvpn-ipv6] [mdt-safi] [flow-ipv4] [flow-ipv6] [route-target] [mcast-vpn-ipv4] [evpn]flow-spec-dest prefix-list-nameThe flow-spec-dest command has no effect when the policy is not applied as a BGP import or export policy.The name of a prefix-list containing IPv4 and/or IPv6 prefix entries [32 characters max].flow-spec-source prefix-list-nameThe flow-spec-source command has no effect when the policy is not applied as a BGP import or export policy.The name of a prefix-list containing IPv4 and/or IPv6 prefix entries [32 characters max].group-address prefix-list-nameThis command specifies the multicast group-address prefix list containing multicast group-addresses that are imbedded in the join or prune packet as a filter criterion. The prefix list must be configured prior to entering this command. Prefix lists are configured in the config>router>policy-options>prefix-list context.The no form of the command removes the criterion from the configuration.host-ip prefix-list-nameinterface interface-nameThe no form of the command removes the criterion from the configuration.The no form of the of the command removes the neighbor IP match criterion from the configuration.no neighbor — Matches any neighbor.
Values ipv4-address: a.b.c.d
ipv6-address: x:x:x:x:x:x:x:x[-interface]
x:x:x:x:x:x:d.d.d.d[-interface]
x: [0 — FFFF]H
d: [0 — 255]D
interface (32 chars max, mandatory for link local addresses)prefix-list nameThe name specified must already be defined.no origin — Matches any BGP origin attributeThe 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.no policy-statement — No route policy statements are defined.no policy-variables name name-string• value-string: as-path, as-path-group, community, prefix-list, damping• ip-address: next-hop• value-number: aigp-metric, as-path-prepend, local-preference, metric, origin, origin-validation, preference, tag, typeThe 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.
Values The no form of the command removes the prefix list match criterion.no prefix-list — Matches any network prefix.The no form of the command removes the protocol match criterion.protocol protocolinstance instance
Values The no form of the command removes the protocol match criterion.protocol protocolinstance instance
Values source-address ip-addresssource-address prefix-list prefix-list-nameThe no form of the command removes the criterion from the configuration.state statesrrp-non-mastertag tagThe no form of the command removes the tag field match criterion.no tag — Matches any tag value.[no] toThe 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.no action — No action is defined.add-paths-send-limit send-limit
Values aigp-metric metric
Values The no form of the command disables the AS path list editing action from the route policy entry.no as-path — The AS path attribute is not changed.The name specified must already be defined.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.no as-path-prepend — no AS number prepending configured.
Values The no form of the command disables the action to edit the community path attribute for the route policy entry.no community — The community path attribute is not changed.This command configures a damping profile used for routes matching the route policy statement entry.The no form of the command removes the damping profile associated with the route policy entry.no damping — Use the default damping profile.The name specified must already be defined.The no form of the command removes the QoS association of the routes matched by the route policy entry.
Values high — Setting the enqueuing parameter to high for a packet increases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing. Once the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.
low —Setting the enqueuing parameter to low for a packet decreases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing, once the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.
Default This command enables the context to configure actions for routes that do not match any route policy statement entries when the accept parameter is specified.no default-action — No default action is specified.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.no default-action — No default action is specified.local-preference preferenceThe no form of the command disables assigning a local preference in the route policy entry.No local-preference — BGP default preference is assigned.The no form of the command removes the MED attribute from the matched routes.no metric — Uses the configured metric (if defined) or do not advertise a metric.Specified integer is added to any existing metric. If the result of the addition results in a number greater than 4294967295, the value 4294967295 is used.Specified integer is subtracted from any existing metric. If the result of the subtraction results in a number less than 0, the value of 0 is used.Specified integer replaces any existing metric.This command enables a redirection under a filtering policy. The filtering policy in this case becomes a redirection policy and it is defined under the router>policy-option hierarchy.fwd-service service-idnext-hop ip-addressThe no form of the command disables assigning a next hop address in the route policy entry.no next-hop — The next hop attribute is not changed.
Values ipv4-prefix: a.b.c.d (host bits must be 0)
ipv4-prefix-length: 0 — 32
ipv6-prefix: x:x:x:x:x:x:x:x (eight 16-bit pieces)
x:x:x:x:x:x:d.d.d.d
x: [0 — FFFF]H
d: [0 — 255]D
name—The next-hop parameter variable 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. Policy parameters must start and end with at-signs (@); for example, “@variable@”.config>router>policy-options>policy-statement name>default-actionThe no form of the command disables advertising the next-hop-self option for the route policy entry.no next-hop-self — The next hop IP address is not changed.config>router>policy-options>policy-statement name>default-actionThe no form of the command disables setting the BGP origin for the route policy entry.origin-validation-state stateconfig>router>policy-options>policy-statement name>default-actionThis 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:preference preferenceconfig>router>policy-options>policy-statement name>default-actionThe no form of the command disables setting an RTM preference in the route policy entry.no preference — No route preference is assigned by the policy entry. The protocol default preference is used.The no form of the command removes the tag.The no form of the command disables assigning a type in the route policy entry.route-exists expressionall – 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.