• Destination port• TCP FlagsAfter you apply a redirect-list to an interface, all traffic passing through it is subjected to the rules defined in the redirect-list.Traffic is forwarded based on the following:• Next-hop addresses are verified. If the specified next hop is reachable, traffic is forwarded to the specified next-hop.• If the specified next-hops are not reachable, the normal routing table is used to forward the traffic.• Dell Networking OS supports multiple next-hop entries in the redirect lists.• Redirect-lists are applied at Ingress.PBR with Redirect-to-Tunnel Option:You can provide a tunnel ID for a redirect rule. In this case, the resolved next hop is the tunnel interface IP. The qualifiers of the rule pertainto the inner IP details. You must provide a tunnel ID for the next hop to be a tunnel interface. If you do not provide the tunnel destination IPas the next hop, the next hop is treated as an IPv4 next hop and not a tunnel next hop.PBR with Multiple Tracking Option:PBR with the multiple tracking option enabled extends and introduces the capabilities of object tracking to verify the next hop IP addressbefore forwarding the traffic to the next hop. The multiple tracking options feature is most suitable for routers which have multiple devicesas the next hop (primarily indirect next-hops and/or Tunnel Interfaces). These options allow you to backup Indirect next-hop with another.Choose the specific Indirect next-hop and/or Tunnel interface which is available by sending ICMP pings to verify the reach ability and/orcheck the Tunnel interface UP or DOWN status, and then route traffic out to that next-hop and/or Tunnel InterfaceImplementing PBR• Non-contiguous bitmasks for PBR• Hot-Lock PBRNon-Contiguous Bitmasks for PBRNon-contiguous bitmasks for PBR allows more granular and flexible control over routing policies. You can include or exclude networkaddresses that are in the middle of a subnet can be included or excluded. Enter specific bitmasks using the dotted decimal format.Dell#show ip redirect-listIP redirect-list rcl0:Defined as:seq 5 permit ip 200.200.200.200 200.200.200.200 199.199.199.199 199.199.199.199seq 10 redirect 1.1.1.2 tcp 234.224.234.234 255.234.234.234 222.222.222.222/24seq 40 ack, Next-hop reachable(via Te 1/4/1)Applied interfaces:Te 1/2/1Hot-Lock PBRIngress and egress Hot lock PBR allows you to add or delete new rules into an existing policy (already written into content address memory[CAM]) without disruption to traffic flow. Existing entries in content addressable memory (CAM) are adjusted to accommodate the newentries. Hot Lock PBR is enabled by default.Configuration Task List for Policy-based RoutingThis section explains how to configure PBR on the system.• Create a Redirect List• Create a Rule for a Redirect-list• Create a Track-ID list638 Policy-based Routing (PBR)
