Users Guide

• Destination port
• TCP Flags
After a redirect-list is applied to an interface, all trac passing through it is subjected to the rules dened in the redirect-list.
The trac is forwarded based on the following:
• Next-hop addresses are veried. If the specied next hop is reachable, the trac is forwarded to the specied next-hop.
• If the specied next-hops are not reachable, the normal routing table is used to forward the trac.
• Dell Networking OS supports multiple next-hop entries in the redirect lists.
• Redirect-lists are applied at Ingress.
PBR with Redirect-to-Tunnel Option:
The user can provide a tunnel id for a redirect rule. In this case, the resolved next hop would be the tunnel interface IP. The qualiers
of the rule would be pertaining to the inner IP details. For next hop to be a tunnel interface user needs to provide tunnel id
mandatory. Instead if user provides the tunnel destination IP as next hop, that would be treated as IPv4 next hop and not tunnel next
hop.
PBR with Multiple Tacking Option:
Policy based routing with multiple tracking option extends and introduces the capabilities of object tracking to verify the next hop IP
address before forwarding the trac to the next hop. The verication method is made transparent to the user. The multiple tracking
options feature is most suitable for routers which have multiple devices as the next hop (primarily indirect next-hops and/or Tunnel
Interfaces in this case). It allows you to backup Indirect Next-hop with another, choose the specic Indirect Next-hop and/or Tunnel
Interface which is available by sending ICMP pings to verify reach ability and/or check the Tunnel Interface UP or DOWN status, and
then route trac out to that next-hop and/or Tunnel Interface
Implementing Policy-based Routing with Dell Networking OS
• Non-contiguous bitmasks for PBR
• Hot-Lock PBR
Non-Contiguous Bitmasks for PBR
Non-contiguous bitmasks for PBR allows more granular and exible control over routing policies. Network addresses that are in the
middle of a subnet can be included or excluded. Specic bitmasks can be entered using the dotted decimal format.
Dell#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
seq 40 ack, Next-hop reachable(via Te 8/1)
Applied interfaces:
Te 8/2
Hot-Lock PBR
Ingress 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 trac ow. Existing entries in CAM are adjusted to accommodate the new entries. Hot Lock
PBR is enabled by default.
Conguration Task List for Policy-based Routing
To enable the PBR:
• Create a Redirect List
• Create a Rule for a Redirect-list
646
Policy-based Routing (PBR)