3.11.5 Policy-Based Routing (IPv4) [SL-L3A)

<Structure of this section>

(1) Capacity limits for policy-based routing

Policy-based routing uses the filtering's flow detection to detect target flows for policy-based routing. Note that policy-based routing can be used when the receive-side flow-detection mode is layer3-6,layer3-mirror-3,layer3-mirror-4,layer3-mirror-5,layer3-suppress-2,layer3-suppress-mirror-2, or custom.

The following table describes the number of entries for policy-based routing group per switch.

Table 3-62: Number of entries in a policy-based routing group per switch
Item	IPv4 Policy-based routing group
Number of access list entries	See Table 3-26: Maximum number of entries for filters on the receiving side. #1
Number of policy-based routing lists	256^#2
Number of routes that can be set for policy-based routing list information	8
Number of routes that can be linked with the tracking functionality of policy-based routing	1024^#3

Note #1: The procedure for calculating the number of entries is the same as in 3.5 Filters, QoS, and Policy-Based Mirroring.
Note #2: Each item of policy-based routing list information is registered as one list. Therefore, if the same policy-based routing list information is set for multiple access lists, the number of lists used is counted as 1.
Note #3: Each track ID is registered as one entry. Therefore, if the same track ID is set for multiple routes, the number of entries used is counted as 1.

(2) Capacity limits for tracking function

The following table describes the capacity limits for the tracking functionality of policy-based routing.

Table 3-63: Capacity limits for the tracking facility
Item	Capacity limit
Number of tracks	1024
Number of polling monitoring tracks^#	1024

#: The number of tracks for which the type icmp configuration command is set.