D-Link DGS-6600-48TS Configuration Guide - Page 333

Volume 4-Layer 3 Configurations / Chapter 31-Policy Based Route Map (PBR) PBR Configuration Commands Load Sharing Network managers can now implement policies to distribute traffic among multiple paths based on the traffic characteristics. Differentiation between PBR and Static Route Configuration Filter rule Policy Base Route User Configure Static Route User Configure Base on source address Base on destination address PBR Configuration Commands The Concept of Policy base route • The traffic has to be identified "matched" according to the policy. • The "matching" of the traffic is usually done with an ACL (access-control list) that is referenced by a route-map. • In the route-map, there is a "match" for the traffic defined in that ACL then a "set" for that traffic where the network administrator defines what he or she wants to happen to that traffic (prioritize it, route it differently). If the packet matches the permit statement in the ACL, the PBR logic executes the action specified by the set command to route the packet. If the packet matches the deny statement in the ACL, the PBR logic is not applied and the packet is routed using the L3 routing table. For example: DGS-6600 > enable DGS-6600# configure terminal DGS-6600(config)# ip access-list test DGS-6600(config-ip-acl)# deny host 1.1.1.4 any priority 10 DGS-6600(config-ip-acl)# permit 1.1.1.0 255.255.255.0 any priority 20 DGS-6600(config-ip-acl)# exit DGS-6600(config)# route-map pbr permit 10 DGS-6600(config-route-map)# match ip address test DGS-6600(config-route-map)# set ip next-hop 2.2.2.2 In the above scenario, if the packet comes from 1.1.1.4 it will be routed by the routing table. Should the packet come from 1.1.1.5 it will be policy routed to 2.2.2.2. Configuration Guidelines The match and set commands to define the conditions for policy routing packets. The match commands specify the conditions under which policy routing occurs. The set commands specify the DGS-6600 Configuration Guide 333