Study guide

5.3 Policy-Based Routing (PBR) Architecture, Configuration, and Route-Maps

Cisco ENCOR 350-401 CCNP Enterprise Core

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

0.1 Cisco 350-401 ENCOR Exam Logistics, Blueprint Structure, and Certification Paths 0.2 Preparation Strategy, Lab Environment Setup, and Practical Test Pacing

2 Enterprise Campus Architecture and High Availability

1.1 Enterprise Network Design: Two-Tier, Three-Tier, Fabric, and Cloud Architectures 1.2 High Availability Architecture: Device Redundancy, FHRPs, and Stateful Switchover (SSO) 1.3 Quality of Service (QoS) Architecture, Classification, Queuing, and Configuration Interpretation

3 Cisco Software-Defined Architecture: SD-WAN and SD-Access

2.1 Cisco Catalyst SD-WAN: Control, Management, and Data Planes 2.2 Cisco SD-Access Architecture: Control Plane, Data Plane, and Fabric Node Roles 2.3 SD-Access Campus Interoperability: Integrating Traditional Networks with Fabric

4 Device and Network Virtualization Technologies

3.1 Device Virtualization: Type 1/2 Hypervisors, Virtual Machines, and Virtual Switching 3.2 Data Path Virtualization: VRF-Lite, GRE Tunneling, and IPsec VPN Fundamentals 3.3 Network Virtualization Overlays: LISP and VXLAN Encapsulation Mechanics

5 Layer 2 Infrastructure: Trunking, EtherChannel, and Spanning Tree

4.1 802.1Q Trunking, Native VLAN, and Dynamic Trunking Protocol Troubleshooting 4.2 EtherChannel Bundling: Static, LACP, and PAgP Implementation and Verification 4.3 Spanning Tree Architecture: RSTP, MST, and STP Protection Mechanisms

6 Layer 3 Routing: OSPF Multi-Area and Protocol Comparison

5.1 Enterprise Routing Principles: Distance Vector vs. Link-State, EIGRP, and OSPF 5.2 OSPFv2 and OSPFv3 Multi-Area Architecture: LSAs, Area Types, and Summarization 5.3 Policy-Based Routing (PBR) Architecture, Configuration, and Route-Maps

7 Exterior Routing: BGP Peering and Path Selection

6.1 External BGP (eBGP) Peering, States, Neighbor Adjacencies, and Timers 6.2 BGP Path Attributes and the Step-by-Step Best Path Selection Algorithm

8 IP Services and First-Hop Redundancy

7.1 Time Synchronization: Network Time Protocol (NTP) and Precision Time Protocol (PTP) 7.2 Network Address Translation: Static NAT, Dynamic NAT, and PAT/Overload 7.3 First Hop Redundancy Protocols: HSRP and VRRP Implementation and Failover

9 IP Multicast Architecture and Protocols

8.1 Multicast Addressing, IGMPv2/v3 Host Membership, and the RPF Check 8.2 Protocol Independent Multicast Sparse Mode (PIM-SM) and Rendezvous Point Discovery 8.3 Anycast RP with MSDP, Source-Specific Multicast (SSM), and Bidirectional PIM

10 Network Diagnostics, Monitoring, and Telemetry

9.1 Network Diagnostic Tools: Conditional Debugging, Traceroute, SNMPv3, and Syslog Logging 9.2 Flexible NetFlow (FNF) Architecture: Flow Records, Exporters, and Monitors 9.3 Switched Port Analyzer: Local SPAN, Remote SPAN (RSPAN), and Encapsulated RSPAN (ERSPAN)

11 Performance Monitoring and Model-Driven Assurance

10.1 IP Service Level Agreements (IP SLA) Probes, Responder, and Route Tracking 10.2 Cisco Catalyst Center: Assurance Dashboards, AI Analytics, and Machine Reasoning Workflows 10.3 Model-Driven Telemetry and Programmable Interfaces: NETCONF and RESTCONF Verification

12 Device Access Control and AAA Architecture

11.1 Device Line Protection: Console, Aux, VTY, Local Authentication, and Privilege Levels 11.2 AAA Architecture: Comparing RADIUS vs. TACACS+ and Method List Configuration

13 Infrastructure Security: ACLs, CoPP, and API Security

12.1 IPv4 and IPv6 Access Control Lists (ACLs): Standard, Extended, and Named Rules 12.2 Control Plane Policing (CoPP): Protecting the Route Processor with MQC 12.3 REST API Security: Token Authentication, TLS Transport, and Rate Limiting

14 Enterprise Network Security Design: ISE, TrustSec, and MACsec

13.1 Endpoint Security Architecture: 802.1X, Cisco ISE Posture, and Profiling 13.2 Next-Generation Firewalls (FTD) and Enterprise Threat Defense Design 13.3 Cisco TrustSec (Security Group Tags) and MACsec (802.1AE) Layer 2 Encryption

15 Network Automation Fundamentals: Python, JSON, and YANG

14.1 Python Fundamentals for Network Engineers: Data Types, Control Flow, and Libraries 14.2 JSON Data Encoding: Syntax, Formatting Rules, and Python Serialization 14.3 YANG Data Modeling: Modules, Tree Structures, and Data Representation

16 Controller REST APIs and RESTCONF Implementation

15.1 Cisco Catalyst Center Intent APIs and Authentication Workflows 15.2 Cisco Catalyst SD-WAN Manager (vManage) REST APIs and Device Interaction 15.3 RESTCONF Protocol Operations: HTTP Verbs, Datastores, and Response Codes

17 Event-Driven Automation and Infrastructure Orchestration

16.1 Cisco Embedded Event Manager (EEM) Applet Architecture and Event Detectors 16.2 Configuration Management: Comparing Ansible, Puppet, Chef, and SaltStack 16.3 Infrastructure as Code (IaC) Principles with Terraform in Enterprise Networks

5.3 Policy-Based Routing (PBR) Architecture, Configuration, and Route-Maps

Key Takeaways Explain This Topic AI

Policy-Based Routing (PBR) intercepts packets before the standard destination-based routing table lookup, directing traffic based on source IP, packet length, protocol, or application port.

Route-maps evaluate statements sequentially by sequence number; an implicit deny exists at the end of every route-map, returning unmatched traffic to normal destination routing.

The set ip next-hop directive overrides the standard routing table for reachable next-hops, whereas set ip default next-hop is evaluated only when no explicit, non-default destination route exists in the routing table.

Interface PBR ( ip policy route-map ) processes transit packets entering an interface, while Local PBR ( ip local policy route-map ) processes packets generated by the router itself.

PBR operational verification relies on show route-map to inspect match counters, show ip policy to verify interface bindings, and debug ip policy to trace real-time policy execution.

Last updated: October 2026

Policy-Based Routing (PBR) Architecture, Configuration, and Route-Maps

Traditional IP forwarding operates strictly on a destination-driven paradigm: a router evaluates incoming packets against its local routing table (RIB) and selects the best exit interface solely based on the destination IP address and Longest Prefix Match (LPM). However, enterprise networks frequently require customized traffic forwarding that overrides standard routing tables. Policy-Based Routing (PBR) provides network engineers with granular control, allowing packets to be steered based on source IP address, transport layer protocol, application port numbers, packet length, or Quality of Service (QoS) markings.

Enterprise PBR Architecture and Use Cases

PBR functions as a programmable bypass mechanism inserted directly into the router's packet forwarding path: Incoming Packet on Interface

  • |
  • v
  • [Is PBR Enabled on Interface?]
  • / \
  • YES NO
  • / \
  • [Evaluate Route-Map] v
  • | | [Standard Destination Routing Table]
  • MATCH NO MATCH |
  • | | v
  • v +-----> [Normal Forwarding / Next-Hop]
  • [Apply 'Set' Action]
  • (e.g., Force ISP 2)
  • Primary Enterprise Use Cases

Multi-Homed ISP Selection: Steering latency-sensitive voice and critical SaaS traffic through a premium primary ISP link while shunting bulk data or backup replication over an inexpensive secondary circuit.

Security Inspection Steering: Forcing specific user subnets or suspicious traffic through dedicated out-of-path security appliances (such as web proxies, firewalls, or IDS sensors) without re-architecting physical cabling.

QoS Policy Routing: Classifying traffic at the edge and assigning specific next-hop paths or IP Precedence/DSCP values to protect business-critical flows.

Equal-Cost Multi-Path Override: Bypassing standard hashing algorithms to pin specific traffic streams to deterministic transit interfaces.

Route-Map Anatomy and Processing Semantics

PBR relies on route-maps to define match criteria and forwarding actions. A route-map consists of named statement blocks ordered by sequence numbers: route-map PBR_POLICY permit 10

  • match ip address 101
  • set ip next-hop 198.51.100.1

!

  • route-map PBR_POLICY permit 20
  • match ip address 102
  • set ip next-hop 203.0.113.1
  • Route-Map Processing Rules

Sequential Evaluation: Route-maps evaluate statements in ascending sequence number order (e.g., 10, then 20, then 30). As soon as a packet matches a statement, evaluation terminates and the corresponding set action executes.

Permit vs. Deny in Route-Maps:

permit : If the packet matches the match clause, the router applies the set action.

deny : If the packet matches the match clause, the router ceases policy routing for this packet. The packet falls through to standard destination-based routing.

Implicit Deny: Every route-map terminates with an unwritten implicit deny. Packets that fail to match any sequence number exit the route-map and undergo standard destination-based routing table lookups. Packets are never dropped by an implicit deny in PBR.

The Matrix of Route-Map and ACL Logic

When an Access Control List (ACL) is called within a match ip address statement, the combination of ACL action and route-map action dictates the forwarding outcome:

Route-Map Clause ACL Condition Resulting Router Action

permit 10 permit Match Successful: Execute the set actions configured in sequence 10.

permit 10 deny No Match: Skip remaining statements in sequence 10; advance to sequence 20.

deny 10 permit Policy Exemption: Cease PBR processing immediately. Route packet via normal routing table.

deny 10 deny No Match: Skip remaining statements in sequence 10; advance to sequence 20.

Next-Hop Forwarding Directives: set ip next-hop vs. set ip default next-hop

The most critical architectural distinction in PBR lies between set ip next-hop and set ip default next-hop : Incoming Packet

  • |
  • +---------------------+---------------------+
  • | |
  • [set ip next-hop] [set ip default next-hop]
  • | |
  • Is next-hop reachable? Does an explicit route exist

/ \ in RIB (excluding 0.0.0.0/0)?

  • YES NO / \
  • / \ YES NO
  • v v / \
  • Forward via PBR Fallback to standard Forward via Forward via PBR
  • next-hop routing table standard explicit default next-hop
  • RIB route

Parameter set ip next-hop set ip default next-hop

Evaluation Timing Evaluated BEFORE the standard destination routing table lookup. Evaluated AFTER checking the standard routing table for explicit routes.

Override Behavior Overrides all specific routes in the routing table (e.g., /32 , /24 ), provided the target next hop is reachable. Does NOT override explicit destination routes in the routing table.

Default Route Interaction Completely ignores any default route ( 0.0.0.0/0 ) in the routing table. Overrides the default route ( 0.0.0.0/0 ) in the routing table if no specific route matches.

Typical Use Case Dedicated policy steering (e.g., force all marketing traffic out ISP 2 regardless of destination). Backup path steering (e.g., route via primary WAN for corporate subnets, but send unknown Internet traffic to proxy).

Interface Directives: PBR also supports set interface <type/number> and set default interface <type/number> . These directives should only be used on point-to-point connections (such as serial links or GRE tunnels). Using set interface on a multiaccess Ethernet segment causes excessive ARP lookups for every destination IP, exhausting router memory and CPU resources.

Interface PBR vs. Local PBR

Routers process transit packets passing through interfaces differently from packets generated locally by the router's own control plane:

1. Interface PBR ( ip policy route-map )

Applied to an ingress physical interface, subinterface, or VLAN interface (SVI). It evaluates transit traffic entering the router from downstream devices: interface GigabitEthernet0/0/1

  • description Ingress LAN from Campus
  • ip policy route-map LAN_STEERING

Packets originated by the router itself (e.g., ping commands executed on the CLI, SNMP traps, Syslog messages, or BGP update packets) completely bypass interface PBR.

2. Local PBR ( ip local policy route-map )

Applied globally to inspect and redirect traffic originated locally by the router : ip local policy route-map ROUTER_MANAGEMENT_POLICY

This command enables network administrators to direct management or monitoring traffic out a dedicated out-of-band management interface or secondary WAN link.

Step-by-Step Cisco IOS PBR Configuration

Consider an enterprise edge router dual-homed to two ISPs:

  • ISP_1 Next-Hop: 198.51.100.1 (connected via GigabitEthernet0/0/1 )
  • ISP_2 Next-Hop: 203.0.113.1 (connected via GigabitEthernet0/0/2 )
  • Ingress LAN Interface: GigabitEthernet0/0/0

Business Objective: Route Voice over IP (VoIP) and video traffic (marked DSCP EF or CS4) out ISP_1 . Route Guest Wi-Fi subnet ( 172.16.50.0/24 ) out ISP_2 . Allow all other enterprise data to follow standard routing. ! Step 1: Define classification ACLs

  • ip access-list extended ACL_REALTIME_TRAFFIC
  • permit ip any any dscp ef
  • permit ip any any dscp cs4

!

  • ip access-list extended ACL_GUEST_WIFI
  • permit ip 172.16.50.0 0.0.0.255 any

!

  • ! Step 2: Build the route-map with sequence numbers and set clauses
  • route-map PBR_EDGE_POLICY permit 10
  • description Direct Voice and Video out ISP 1
  • match ip address ACL_REALTIME_TRAFFIC
  • set ip next-hop 198.51.100.1

!

  • route-map PBR_EDGE_POLICY permit 20
  • description Direct Guest Wi-Fi out ISP 2
  • match ip address ACL_GUEST_WIFI
  • set ip next-hop 203.0.113.1

!

  • ! Step 3: Attach the route-map to the ingress interface
  • interface GigabitEthernet0/0/0
  • description Ingress User LAN
  • ip address 10.1.1.1 255.255.255.0
  • ip policy route-map PBR_EDGE_POLICY
  • PBR Verification and Troubleshooting

Network engineers verify and troubleshoot PBR deployments using dedicated operational commands:

show route-map [map-name] : Displays route-map configuration, sequence numbers, and vital match counters indicating how many packets and bytes have matched each sequence clause.

show ip policy : Lists all interfaces where ip policy route-map is actively applied along with the bound route-map name.

show ip local policy : Displays the globally configured local policy route-map applied to self-generated router packets.

debug ip policy : Generates real-time console messages for each packet evaluated by PBR, displaying the source/destination IP, matching sequence number, and designated next-hop, or indicating if the packet fell through to the normal routing table ( routed normal ).