This section provides information to configure route policies using the command line interface.
Route policies allow the configuration of IGMP group membership reports filtering rules.
Route policies are created in the config>router context. There are no default route policies. Each route policy must be explicitly created and applied.
A route policy impacts the flow of packets within and through the router.
Route policies can be created to control filter IGMP membership reports from specific hosts and/or specific multicast groups.
Before a route policy is applied, analyze the policy purpose and be aware of the results (and consequences) when packets match the specified criteria and the associated actions and default actions, if specified, are executed. Membership reports can be filtered based on a specific source address.
Each routing protocol has default behaviors for the import and export of routing information. Table 5 describes the default behavior for each routing protocol.
Protocol | Import | Export |
OSPF | Not applicable. All OSPF routes are accepted from OSPF neighbors and cannot be controlled via route policies. |
|
Routing policy statements can consist of as few as one or several entries. The entries specify the matching criteria. The packet fields are compared to the first entry in the policy statement. If it matches, the specified entry action is taken, either accepted or rejected. If the action is to accept or reject the route, that action is taken and the evaluation of the route ends.
If the route does not match the first entry, the route is compared to the next entry (if more than one is configured) in the policy statement. If there is a match with the second entry, the specified action is taken. If the action is to accept or reject the route, that action is taken and the evaluation of the route ends, and so on.
Each route policy statement can have a default-action clause defined. If a default-action is defined for one or more of the configured route policies, the default actions should be handled in the following ways.
Figure 1 shows an example of the route policy process.
Route policies can also match a specific route policy entry and continue to search for other entries within either the same route policy or the next route policy by specifying the next-entry option in the entry action command.
This section provides information to configure route policies and configuration examples of common tasks. The minimal route policy parameters that need to be configured are:
The following is a sample route policy configuration output.
This section describes the syntax needed to configure the route policy components.
Use the following syntax to begin a policy statement configuration. In order for a policy statement to be complete an entry must be specified (see Configuring an Entry).
The following error message displays when the you try to modify a policy options command without entering begin first.
The following example displays policy statement configuration command usage. These commands are configured in the config>router context.
There are no default policy statement options. All parameters must be explicitly configured.
To enter the mode to create or edit route policies, you must enter the begin keyword at the config>router>policy-options prompt. Other editing commands include the following.
The following error message displays when the you try to modify a policy options command without entering begin first.
Specifying a default action is optional. The default action controls those packets not matching any policy statement entries. If no default action is specified for the policy, then the action associated with the protocol to which the routing policy was applied is performed.
A policy statement must include at least one entry (see Configuring an Entry).
To enter the mode to create or edit route policies, you must enter the begin keyword at the config>router>policy-options prompt. Other editing commands include the following.
An entry action must be specified. The other parameters in the entry>action context are optional. Refer to the Route Policy Command Reference for the commands and syntax.
The following is a sample of entry parameters and includes the default action parameters which were displayed in the previous section.
This section describes the route policy configuration management tasks.
Route policy statements can be edited to modify, add, or delete parameters. To enter the mode to edit route policies, you must enter the begin keyword at the config>router>policy-options prompt. Other editing commands include the following.
The following is a sample changed configuration output.
Use the following syntax to delete a policy statement entry.
The following shows the command usage to delete a policy statement entry.
Use the following syntax to delete a policy statement.
The following shows the command usage to delete a policy statement.