7.11. Route Policy Command Reference

This command discards changes made to a route policy.

This command enters the mode to create or edit route policies.

This command saves changes made to a route policy.

This command creates a text description that is stored in the configuration file to help identify the content of the entity.

The no form of this command removes the string from the configuration.

This command configures a route policy AS path regular expression statement to use in route policy entries.

The no form of this command deletes the AS path regular expression statement.

This command configures a route policy community list to use in route policy entries.

The no form of this command deletes the community list or the provided community ID.

This command enables the context to configure route policies.

In the access-uplink operating mode, route policies are used for IGMP group membership report filtering.

The no form of this command deletes the route policy configuration.

This command triggers route policy reevaluation.

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 7210 SAS router, the consequences could be dramatic. It is more effective to control changes on a peer-by-peer basis.

When this command is enabled, a specific peer is established, and you want the peer to remain up, 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. When a triggered-policy is enabled, any routine policy change or policy assignment change within the protocol does not take effect until the protocol is reset or a clear command is issued to reevaluate 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.

This command enables the context to configure a route damping profile to use in route policy entries.

The no form of this command deletes the named route damping profile.

This command configures the half life value for the route damping profile.

The half life value is the time required for a route to remain stable in order for the Figure of Merit (FoM) value to be reduced by one half; for example, if the half life value is 6 (minutes) and the route remains stable for 6 minutes, the new FoM value is 3 (minutes). After another 3 minutes pass and the route remains stable, the new FoM value is 1.5 (minutes).

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 this command removes the half life value from the damping profile.

This command configures the maximum suppression value for the route damping profile.

This value indicates the maximum time that a route can remain suppressed.

The no form of this command removes the maximum suppression value from the damping profile.

This command configures the reuse value 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 this command removes the reuse parameter from the damping profile.

This command configures the suppression value for the route policy damping profile.

A route is suppressed when it has flapped frequently enough to increase the 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 this command removes the suppress value from the damping profile.

This command enables the context to configure a prefix list to use in route policy entries.

The no form of this command deletes the named prefix list.

This command creates a prefix entry in the route policy prefix list.

The no form of this command deletes the prefix entry from the prefix list.

This command enables the context to edit route policy entries within the route policy statement.

Multiple entries can be created using unique entries. The 7210 SAS exits the filter when the first match is found and executes the action specified. For this reason, entries must be sequenced correctly from most to least explicit.

An entry does not require matching criteria defined (in which case, everything matches) but must at least define an action to be considered complete. Entries without an action are considered incomplete and are rendered inactive.

The no form of this command removes the specified entry from the route policy statement.

This command enables the context to configure policy match criteria based on a route source or the protocol from which the route is received.

If no condition is specified, all route sources are considered to match.

The no form of this command deletes the source match criteria for the route policy statement entry.

This command specifies address families as matching conditions.

This command configures an OSPF area as a route policy match criterion.

This match criterion is only used in export policies.

All OSPF routes (internal and external) are matched using this criterion if the best path for the route is by the specified area.

The no form of this command removes the OSPF area match criterion.

This command configures a community list as a match criterion for the route policy entry.

If no community list is specified, any community is considered a match.

The no form of this command removes the community list match criterion.

This command specifies the external route matching criteria for the entry.

This command specifies the multicast group address prefix list containing multicast group addresses that are embedded in the join or prune packet as a filter criterion. The prefix list must be configured before entering this command. Prefix lists are configured in the config>router>policy-options>prefix-list context.

The no form of this command removes the criterion from the configuration.

This command specifies a prefix list host IP address as a match criterion for the route policy-statement entry.

This command specifies the router interface, specified either by name or address, as a filter criterion.

The no form of this command removes the criterion from the configuration.

This command specifies the IS-IS route level as a match criterion for the entry.

This command specifies the neighbor address as found in the source address of the actual join and prune message as a filter criterion. If no neighbor is specified, any neighbor is considered a match.

The no form of the of the command removes the neighbor IP match criterion from the configuration.

This command configures a BGP origin attribute as a match criterion for a route policy statement entry.

If no origin attribute is specified, any BGP origin attribute is considered a match.

The no form of this command removes the BGP origin attribute match criterion.

This command enables the context to configure a route policy statement. The policy statement is a logical grouping of match and action criteria. The processing action taken is determined by the action associated with the entries configured in the policy statement.

In the access-uplink operating mode, route policy statements enable appropriate processing of IGMP group membership reports received from hosts.

The no form of this command deletes the policy statement.

Note: The config>router>policy-options>policy-statement>entry>to context is not supported on 7210 SAS platforms configured in the access-uplink operating mode.

This command configures a prefix list as a match criterion for a route policy statement entry.

If no prefix list is specified, any network prefix is considered a match.

The prefix lists specify the network prefix (this includes the prefix and length) a specific policy entry applies.

A maximum of five prefix names can be specified.

The no form of this command removes the prefix list match criterion.

This command configures a routing protocol as a match criterion for a route policy statement entry. This command is used for both import and export policies depending how it is used.

If no protocol criterion is specified, any protocol is considered a match.

The no form of this command removes the protocol match criterion.

This command specifies the source address that is embedded in the join or prune packet as a filter criterion.

The no form of this command removes the criterion from the configuration.

This command specifies a multicast data source address as a match criterion for this entry.

This command adds an integer tag to the static route. These tags are then matched to control route redistribution.

The no form of this command removes the tag field match criterion.

This command enables the context to configure export policy match criteria based on a route destination or the protocol into which the route is being advertised.

If no condition is specified, all route destinations are considered to match.

The to command context only applies to export policies. If it is used for an import policy, match criterion is ignored.

The no form of this command deletes export match criteria for the route policy statement entry.

This command configures an OSPF type metric as a match criterion in the route policy statement entry.

If no type is specified, any OSPF type is considered a match.

The no form of this command removes the OSPF type match criterion.

This command enables the context to configure actions to take for routes matching a route policy statement entry.

This command is required and must be entered for the entry to be active.

Any route policy entry without the action command is considered incomplete and inactive.

The no form of this command deletes the action context from the entry.

The effect of this command on a route matched and accepted by a route policy entry depends on how the policy is applied (BGP import policy versus BGP export policy), the type of route, and the specific form of this command.

In a BGP import policy, this command is used to:

In a BGP export policy, this command is used to:

The no form of this command removes the AIGP attribute and any explicit AIGP metric value changes that were previously configured using this command.

This command assigns a BGP AS path list to routes matching the route policy statement entry.

If no AS path list is specified, the AS path attribute is not changed.

The no form of this command disables the AS path list editing action from the route policy entry.

The command prepends a BGP AS number once or numerous times to the AS path attribute of routes matching the route policy statement entry.

If an AS number is not configured, the AS path is not changed.

If the optional number is specified, the AS number is prepended as many times as indicated by the number.

The no form of this command disables the AS path prepend action from the route policy entry.

This command adds or removes a BGP community list to or from routes matching the route policy statement entry.

If no community list is specified, the community path attribute is not changed.

The community list changes the community path attribute according to the add and remove keywords.

The no form of this command disables the action to edit the community path attribute for the route policy entry.

This command configures a damping profile used for routes matching the route policy statement entry.

If no damping criterion is specified, the default damping profile is used.

The no form of this command removes the damping profile associated with the route policy entry.

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.

The default-action command can be set to all available action states. If the action states are accepted or rejected, the policy evaluation terminates and a result is returned.

If a default action is defined and no matches occur with the entries in the policy, the default action is used.

If a default action is defined and one or more matches occur with the entries of the policy, the default action is not used.

The no form of this command deletes the default-action context for the policy statement.

This command assigns a BGP local preference to routes matching a route policy statement entry.

If no local preference is specified, the BGP configured local preference is used.

The no form of this command disables assigning a local preference in the route policy entry.

This command assigns a metric to routes matching the policy statement entry.

If no metric is specified, the configured metric is used. If neither is defined, no metric is advertised.

The value assigned to the metric by the route policy is controlled by the required keywords.

The no form of this command disables assigning a metric in the route policy entry.

This command assigns the specified next-hop IP address to routes matching the policy statement entry.

If a next-hop IP address is not specified, the next-hop attribute is not changed.

The no form of this command disables assigning a next-hop address in the route policy entry.

This command advertises a next-hop IP address belonging to this router, even if a third-party next hop is available to routes matching the policy statement entry.

The no form of this command disables advertising the next-hop-self command for the route policy entry.

This command sets the BGP origin assigned to routes exported into BGP.

If the routes are exported into protocols other than BGP, this option is ignored.

The no form of this command disables setting the BGP origin for the route policy entry.

This command assigns a route preference to routes matching the route policy statement entry.

If no preference is specified, the default Route Table Manager (RTM) preference for the protocol is used.

The no form of this command disables setting an RTM preference in the route policy entry.

This command assigns an OSPF tag to routes matching the entry. The tag value is used to apply a tag to a route for either an OSPF or RIP route. A hexadecimal value of 4 octets can be entered.

For OSPF, all four octets can be used.

For RIP, only the two most significant octets are used when more than two octets are configured.

The no form of this command removes the tag.

This command assigns an OSPF type metric to routes matching the route policy statement entry and being exported into OSPF.

The no form of this command disables assigning an OSPF type in the route policy entry.

This command displays configured policy statement information.