): 101 Set clauses: interface Serial0/0.209 Policy routing matches: 656 packets, 68624 bytes Another option you can use to determine whether a router is acting on enabled policies is the debug ip policy command. Take care when using debug, as it can impact the operation of the router. Remember that policy routing is applied to every packet that comes into an interface. Test this in a lab before you try it in a production network. Chapter 14: Route Maps Here, a workstation on Company 2's user network in Branch #9 is pinging Company 1's HQ network (10.101.0.1): 10.101.0.0 [90/2172416] via 172.16.101.1, 03:21:29, Serial0/0.109 According to the routing table, these packets should route through SO/0.109. But, when the user pings 10.101.0.1, the debug output tells a different story: 04:49:24: IP: s=10.209.0.2 (FastEthernet0/1), d=10.101.0.1, len 100, FIB policy match 04:49:24: IP: s=10.209.0.2 (FastEthernet0/1), d=10.101.0.1, g=172.16.101.1, len 100, FIB policy routed 04:49:25: IP: s=10.209.0.2 (FastEthernet0/1), d=10.101.0.1, len 100, FIB policy match 04:49:25: IP: s=10.209.0.2 (FastEthernet0/1), d=10.101.0.1, g=172.16.101.1, len 100, FIB policy routed 04:49:25: IP: s=10.209.0.2 (FastEthernet0/1), d=10.101.0.1, len 100, FIB policy match 04:49:25: IP: s=10.209.0.2 (FastEthernet0/1), d=10.101.0.1, g=172.16.101.1, len 100, FIB policy routed 04:49:25: IP: s=10.209.0.2 (FastEthernet0/1), d=10.101.0.1, len 100, FIB policy match 04:49:25: IP: s=10.209.0.2 (FastEthernet0/1), d=10.101.0.1 Branch-9#, g=172.16.101.1, len 100, FIB policy routed 04:49:25: IP: s=10.209.0.2 (FastEthernet0/1), d=10.101.0.1, len 100, FIB policy match 04:49:25: IP: s=10.209.0.2 (FastEthernet0/1), d=10.101.0.1, g=172.16.101.1, len 100, FIB policy routed Notice the entries in bold, each of which corresponds to a single ping packet. First, we see an FIB policy match entry. This indicates that one of the match statements in our route map was successful. The following line contains the phrase FIB policy routed. This indicates that the packet was policy-rout