A router's primary job is to act like a postal service for data. It looks at the destination address on a packet, consults its map—the Routing Information Base (RIB)—and forwards the packet along the best path. This destination-based logic is efficient and straightforward. But what if you need to route traffic based on who sent it, or what kind of data it is, rather than just where it's going?

This is where Policy-Based Routing (PBR) comes in. PBR is a routing exception. It allows you to create rules that inspect packets for more than just their destination. Think of it as giving special handling instructions. While the RIB provides the default public roads, PBR creates a private, unlisted route for specific traffic that needs it.

To understand PBR, you need to know when it acts. Its power comes from its position in the router's decision-making process. PBR rules are checked before the router performs a standard RIB lookup.

Here's the sequence when a packet arrives on an interface where a PBR policy is applied:

This pre-emptive check is what gives PBR its power. If a packet matches a policy, it's sent on its way without ever consulting the main routing table. If it doesn't match any policy rules, it simply falls through to the normal routing process as if PBR wasn't there.

A PBR policy is built using route-map configurations, which function like if-then statements. A route-map contains match conditions (the "if") and set actions (the "then"). You can classify traffic using a wide range of criteria.

PBR can also be applied in two ways: on an interface or locally on the router. Interface PBR affects traffic entering a specific interface from the network. Local PBR affects traffic generated by the router itself, such as management traffic or packets from routing protocol updates.

There's a critical performance trade-off to consider when implementing PBR. Modern routers don't use the main CPU for every forwarding decision. Instead, they use specialized hardware and a pre-computed forwarding table. This method, known as Cisco Express Forwarding (CEF), is extremely fast.

Standard destination-based lookups are CEF-switched. However, because PBR introduces complex, conditional logic, it can force the router to bypass the fast hardware path. The router's main CPU must then inspect the packet and make a forwarding decision, a much slower method called process switching.

Therefore, PBR should be used strategically. It is an excellent tool for special cases and policy exceptions, but it is not a replacement for a well-designed, destination-based routing architecture. Understanding its impact on the forwarding plane is key to using it effectively without unintentionally degrading network performance.