Users Guide
To enable a PBR, you create a redirect list. Redirect lists are dened by rules, or routing policies. The following parameters can be dened in
the routing policies or rules:
• IP address of the forwarding router (next-hop IP address)
• Protocol as dened in the header
• Source IP address and mask
• Destination IP address and mask
• Source port
• Destination port
• TCP Flags
Once a redirect-list is applied to an interface, all trac passing through it is subjected to the rules dened in the redirect-list.
The trac is forwarded based on the following:
• Next-hop addresses are veried. If the specied next hop is reachable, then the trac is forwarded to the specied next-hop.
• If the specied next-hops are not reachable, then the normal routing table is used to forward the trac.
• 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 qualiers 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 trac to the next hop. The verication 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
Policy-based Routing (PBR)
733