Users Guide

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.
Non-contiguous bitmask example
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/1)
Applied interfaces:
Te 8/2/1
Hot-Lock PBR
Hot Lock PBR allow you to add or delete new rules into an existing policy (already written into 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
• Create a Track-id list. For complete tracking information, refer to Object Tracking chapter.
• Apply a Redirect-list to an Interface using a Redirect-group
Create a Redirect List
Use the following command in CONFIGURATION mode:
Table 67. Create a Redirect List
Command Syntax Command Mode Purpose
ip redirect-list redirect-list-name CONFIGURATION Create a redirect list by entering the list
name.
Format: 16 characters
Delete the redirect list with the no ip redirect-list command.
Policy-based Routing (PBR) 723