PBR is the process of using a route map to specify an attribute other than the destination and then define the path out of the router based on those conditions.
With PBR, a network administrator can select policies according to specific parameters, such as:
• The IP address of the source or the destination
• The port of the source or destination
• The kind of traffic
• Network protocols
• The sizes of data packets
• An access list
Once parameters like these are established, the data packets get routed accordingly. This empowers you to increase the agility of the network.
Because you can define your routing strategy using the attributes of applications, you can execute specific traffic-management policies that control how packets get forwarded.
In this way, you can optimize how bandwidth gets used by your most important applications.
PBR is considered to be an exception to the routing information base (RIB) and is looked at before examining the RIB. This allows for more routing options.
For example, within the route map used for PBR, you can match on an access control list (ACL) that then matches on source, destination, protocol type, and/or port numbers.
You can also match on:
• Quality of service (QoS) marking, such as Internet Protocol (IP) precedence or differentiated services code point (DSCP)
• The size of the packets, effectively enabling you to send data where you want it to go based on how big or small its packets are
Once you have a positive match, you can then set the next hop device’s address and/or egress interface. You can also set QoS values at the same time, which enable you to ensure an application gets the resources it needs to function as well as you need it to.