To enable a PBR, create a redirect list. Redirect lists are defined by rules, or routing policies. You can
define following parameters in routing policies or rules:
• IP address of the forwarding router (next-hop IP address)
• Protocol as defined in the header
• Source IP address and mask
• Destination IP address and mask
• Source port
• Destination port
• TCP Flags
After a redirect-list is applied to an interface, all traffic passing through it is subjected to the rules defined
in the redirect-list.
The traffic is forwarded based on the following:
• Next-hop addresses are verified. If the specified next hop is reachable, the 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:
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 qualifiers 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 traffic to the next hop. The verification
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 specific 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 traffic 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
Policy-based Routing (PBR)
729
Summary of Contents for S4820T
Page 1: ...Dell Configuration Guide for the S4820T System 9 8 0 0 ...
Page 282: ...Dell 282 Control Plane Policing CoPP ...
Page 622: ...Figure 81 Configuring Interfaces for MSDP 622 Multicast Source Discovery Protocol MSDP ...
Page 623: ...Figure 82 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 623 ...
Page 629: ...Figure 86 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 629 ...
Page 630: ...Figure 87 MSDP Default Peer Scenario 3 630 Multicast Source Discovery Protocol MSDP ...
Page 751: ...10 11 5 2 00 00 05 00 02 04 Member Ports Te 1 2 1 PIM Source Specific Mode PIM SSM 751 ...
Page 905: ...Figure 112 Single and Double Tag First byte TPID Match Service Provider Bridging 905 ...
Page 979: ...6 Member not present 7 Member not present Stacking 979 ...
Page 981: ...storm control Storm Control 981 ...
Page 1103: ...Figure 134 Setup OSPF and Static Routes Virtual Routing and Forwarding VRF 1103 ...