Actions
Each term can include a
thenstatement, which defines the actions to take if a route matches all the conditions in thefromandtostatements:[edit]policy-options {policy-statementpolicy-name{termterm-name{from {family family-name;match-conditions;policysubroutine-policy-name;prefix-listname;route-filterdestination-prefix match-type<actions>;source-address-filterdestination-prefix match-type<actions>;}to {match-conditions;policysubroutine-policy-name;}then {actions;}}}}If a term does not have
fromandtostatements, all routes are considered to match and the actions apply to them all.The
thenstatement is optional.You can specify one or more actions. There are three types of actions:
- Flow control actions, which affect whether to accept or reject the route and whether to evaluate the next term or routing policy.
- Actions that manipulate route characteristics.
- Trace action, which logs route matches.
If you do not include a
thenstatement, one of the following occurs:
- The next term in the routing policy, if one is present, is evaluated.
- If there are no more terms in the routing policy, the next routing policy, if one is present, is evaluated.
- If there are no more terms or routing policies, the accept or reject action specified by the default policy is taken. For more information, see Default Routing Policies and Actions.
The following sections discuss the following action attributes: