594
Configuring Access Control Lists
Policy Based Routing
Overview
In contemporary inter-networks, network administrators often need to
implement packet routing according to specific organizational policies. Policy
Based Routing (PBR) exactly fits this purpose. PBR provides a flexible
mechanism to implement solutions where organizational constraints dictate
that traffic be routed through specific network paths. PBR does not affect
route redistribution that occurs via routing protocols.
PBR is a true routing solution. The packet TTL is decremented in PBR-
routed packets. The destination MAC is rewritten in PBR routed packets.
ARP lookups are sent when required for unresolved next hop addresses. PBR
routed packets are routed via routing table lookups. Routes must exist in the
routing table for PBR next-hop and default next-hop rules.
Configuring PBR consists of installing a route-map with match and set
commands, and then applying the corresponding route-map to the interface.
IP routing must be enabled on the interfaces and globally.
PBR is applied to inbound traffic on IP routing interfaces. Enabling the
feature causes the router to analyze packets entering the interface using a
route-map. A VLAN can only have one associated route-map, but the
administrator can configure multiple route-map entries in the route-map
with different sequence numbers. Packets entering the interface are filtered
by a user-selected ACL. Packets that are allowed by the ACL are evaluated in
order of increasing sequence number until a viable routing destination is
found. Other actions may also be specified. If no action is executed, packets
are routed via normal routing table lookup.
ACLs present in a route-map’s match clauses inherit the ordering of the
containing route-map sequence number. Therefore, it is recommended that
ACLs used in route-map match clauses be independent of ACLs used in
access-groups in order to preserve access-group ordering.
A route-map rule may be configured as a permit or deny rule. If the rule is
marked as deny, traditional destination-based routing is performed on the
packet meeting the ACL match criteria. If the rule is marked as permit, and if
the packet meets the ACL match criteria, then the action specified by the set
commands in the route-map statement are evaluated. If no active route is
found in the route-map, the packet is forwarded using traditional destination-
Содержание N2000 Series
Страница 50: ...50 Contents ...
Страница 54: ...54 Introduction ...
Страница 134: ...134 Using Dell OpenManage Switch Administrator ...
Страница 168: ...168 Setting Basic Network Information ...
Страница 206: ...206 Managing a Switch Stack ...
Страница 242: ...242 Configuring Authentication Authorization and Accounting ...
Страница 318: ...318 Managing General System Settings Figure 12 24 Verify MOTD ...
Страница 322: ...322 Managing General System Settings ...
Страница 344: ...344 Configuring SNMP Figure 13 18 Trap Logs Click Clear to delete all entries from the trap log ...
Страница 358: ...358 Configuring SNMP ...
Страница 388: ...388 Managing Images and Files ...
Страница 415: ...Monitoring Switch Traffic 415 Figure 16 2 sFlow Agent Summary ...
Страница 451: ...Monitoring Switch Traffic 451 5 On the Capture Options dialog click Manage Interfaces ...
Страница 458: ...458 Monitoring Switch Traffic ...
Страница 488: ...488 Configuring Port Characteristics Figure 18 3 Copy Port Settings 8 Click Apply ...
Страница 502: ...502 Configuring Port Characteristics ...
Страница 541: ...Configuring Port and System Security 541 Figure 19 12 Configure Port Security Settings 5 Click Apply ...
Страница 567: ...Configuring Port and System Security 567 Figure 19 38 Captive Portal Client Status ...
Страница 666: ...666 Configuring VLANs Figure 21 6 Add Ports to VLAN 4 Click Apply 5 Verify that the ports have been added to the VLAN ...
Страница 674: ...674 Configuring VLANs Figure 21 17 GVRP Port Parameters Table ...
Страница 680: ...680 Configuring VLANs Figure 21 24 Double VLAN Port Parameter Table ...
Страница 714: ...714 Configuring VLANs ...
Страница 737: ...Configuring the Spanning Tree Protocol 737 Figure 22 9 Spanning Tree Global Settings ...
Страница 760: ...760 Configuring the Spanning Tree Protocol ...
Страница 786: ...786 Discovering Network Devices ...
Страница 793: ...Configuring Port Based Traffic Control 793 Figure 24 3 Storm Control 5 Click Apply ...
Страница 878: ...878 Configuring Connectivity Fault Management ...
Страница 899: ...Snooping and Inspecting Traffic 899 Figure 27 17 DAI Interface Configuration Summary ...
Страница 903: ...Snooping and Inspecting Traffic 903 Figure 27 24 Dynamic ARP Inspection Statistics ...
Страница 924: ...924 Configuring Link Aggregation Figure 28 7 LAG Hash Summary ...
Страница 982: ...982 Configuring Link Aggregation ...
Страница 1062: ...1062 Configuring DHCP Server and Relay Settings ...
Страница 1096: ...1096 Configuring L2 and L3 Relay Features Figure 34 3 DHCP Relay Interface Summary ...
Страница 1200: ...1200 Configuring OSPF and OSPFv3 ...
Страница 1216: ...1216 Configuring RIP ...
Страница 1240: ...1240 Configuring VRRP ...
Страница 1284: ...1284 Configuring DHCPv6 Server and Relay Settings Relay Interface Number Vl100 Relay Remote ID Option Flags ...
Страница 1291: ...Configuring Differentiated Services 1291 Figure 40 5 DiffServ Class Criteria ...
Страница 1336: ...1336 Configuring Auto VoIP ...
Страница 1367: ...Managing IPv4 and IPv6 Multicast 1367 Figure 43 20 IGMP Cache Information ...
Страница 1422: ...1422 Managing IPv4 and IPv6 Multicast ...
Страница 1440: ...1440 System Process Definitions ...
Страница 1460: ...Index 1460 ...