•
Destination port
•
TCP Flags
After you apply a redirect-list to an interface, all traffic passing through it is subjected to the rules defined in the redirect-list.
Traffic is forwarded based on the following:
•
Next-hop addresses are verified. If the specified next hop is reachable, 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:
You can provide a tunnel ID for a redirect rule. In this case, the resolved next hop is the tunnel interface IP. The qualifiers of the rule pertain
to the inner IP details. You must provide a tunnel ID for the next hop to be a tunnel interface. If you do not provide the tunnel destination IP
as the next hop, the next hop is treated as an IPv4 next hop and not a tunnel next hop.
PBR with Multiple Tracking Option:
PBR with the multiple tracking option enabled extends and introduces the capabilities of object tracking to verify the next hop IP address
before forwarding the traffic to the next hop. 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). These options allow 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 the 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 PBR
•
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. You can include or exclude network
addresses that are in the middle of a subnet can be included or excluded. Enter specific bitmasks 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 content addressable memory (CAM) are adjusted to accommodate the new
entries. Hot Lock PBR is enabled by default.
Configuration Task List for Policy-based Routing
This section explains how to configure PBR on the system.
•
•
Create a Rule for a Redirect-list
•
672
Policy-based Routing (PBR)
Содержание S4048T-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 11 2 1 ...
Страница 148: ...Figure 10 BFD Three Way Handshake State Changes 148 Bidirectional Forwarding Detection BFD ...
Страница 251: ...Dell Control Plane Policing CoPP 251 ...
Страница 363: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 363 ...
Страница 511: ...Figure 64 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 511 ...
Страница 512: ...Figure 65 Inspecting Configuration of LAG 10 on ALPHA 512 Link Aggregation Control Protocol LACP ...
Страница 515: ...Figure 67 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 515 ...
Страница 516: ...Figure 68 Inspecting LAG 10 Using the show interfaces port channel Command 516 Link Aggregation Control Protocol LACP ...
Страница 558: ...Figure 84 Configuring Interfaces for MSDP 558 Multicast Source Discovery Protocol MSDP ...
Страница 559: ...Figure 85 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 559 ...
Страница 560: ...Figure 86 Configuring PIM in Multiple Routing Domains 560 Multicast Source Discovery Protocol MSDP ...
Страница 564: ...Figure 88 MSDP Default Peer Scenario 2 564 Multicast Source Discovery Protocol MSDP ...
Страница 565: ...Figure 89 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 565 ...
Страница 729: ...protocol spanning tree pvst no disable vlan 300 bridge priority 4096 Per VLAN Spanning Tree Plus PVST 729 ...
Страница 841: ...Figure 115 Single and Double Tag TPID Match Service Provider Bridging 841 ...
Страница 842: ...Figure 116 Single and Double Tag First byte TPID Match 842 Service Provider Bridging ...