Routing actions

The RoutingAction statement must specify a minimum of one policy-based route table using the RouteTableRef parameter, or it must specify UseMainRouteTable YES. Specify UseMainRouteTable YES and no RouteTableRef parameters if you want traffic that matches the corresponding RoutingRule statement to be routed using only the main route table.

A maximum of eight RouteTableRef parameters can be specified on a RoutingAction statement. Each RouteTableRef parameter includes the name of a globally defined RouteTable statement. The order in which the RouteTableRef parameters are specified on the RoutingAction statement determines the order in which the TCP/IP stack uses the route tables when making routing decisions. The stack searches the first table for a route that can be used to reach the destination of the traffic. If no usable route (host, subnet, network, or default) exists in that route table, the next table is searched. This continues until a usable route to the destination is found, or all specified tables are exhausted. Specify the UseMainRouteTable parameter to indicate whether the main route table should also be searched when no usable route is located in any of the specified policy-based route tables. For a description of the algorithm used by the IP layer to search a route table for a usable route to a destination, see Route selection algorithm.

Performance guideline: There is a performance cost for each policy-based route table that is searched on a route lookup. Minimize the number of RouteTableRef parameters that you specify on a RoutingAction statement.