Filter
Top Products
Policy-based Routing | 803
2. If the specified next-hops are not reachable, then the normal routing table is used to forward the traffic.
3. FTOS supports multiple next-hop entries in the redirect lists.
4. Redirect-Lists are applied at Ingress.
Implementing Policy-based Routing with FTOS
Non-contiguous bitmasks for PBR
Non-contiguous bitmasks for PBR allows more granular and flexible control over routing policies.
Network addresses that are in the middle of a subnet can be included or excluded.
Specific bitmasks can be entered using the dotted decimal format.
Figure 37-2. Non-contiguous bitmask example
Hot-Lock PBR
Ingress and egress Hot Lock PBR allow you to add or delete new rules into an existing policy (already
written into CAM) without disruption to traffic flow. Existing entries in CAM are adjusted to
accommodate the new entries. Hot Lock PBR is enabled by default.
FTOS#show ip redirect-list
IP redirect-list rcl0:
Defined as:
seq 5 permit ip 200.200.200.200 200.200.200.200 199.199.199.199 199.199.199.199
seq 10 redirect 1.1.1.2 tcp 234.224.234.234 255.234.234.234 222.222.222.222/24 eq 40 ack, Next-hop reachable
(via Gi 8/1), ARP resolved
Applied interfaces:
Gi 8/0
Non-Contiguous Bitmasks
Contiguous Bitmasks