
•
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
Non-contiguous bitmasks for PBR allows more granular and flexible control over routing policies. Network addresses that are in the
middle of a subnet can be included or excluded. Specific 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 traffic flow. Existing entries in CAM are adjusted to accommodate the new entries. Hot Lock
PBR is enabled by default.
Configuration Task List for Policy-based Routing
To enable the PBR:
•
•
Create a Rule for a Redirect-list
Policy-based Routing (PBR)
627
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...