t interfaces, use the show ip policy command: Branch-9# sho ip policy Interface Route map FastEtherneto/o Company- FastEtherneto/1 Company- Chapter 14: Route Maps Another method for determining whether policy routing is enabled is with the show ip interface command. This command creates a lot of output, SO filtering with include Policy is useful for our purposes: Branch-9# sho ip int fo/o I include Policy Policy routing is enabled, using route map Company-1 BGP Policy Mapping is disabled The problem with these commands is that they only show that a policy is applied, not how it's working. The command show route-map will show you all the route maps configured on the router, as well as some useful statistics regarding how many times the route map has been used for policy routing. This information is accumulative, SO you can only assume the route map is working the way you want it to if the counters are incrementing: Branch-9# sho route-map route-map Company-2, permit, sequence 10 Match clauses: ip address (access-lists) 102 Set clauses: interface Serial0/0.209 Policy routing matches: 656 packets, 68624 bytes route-map Company-1, permit, sequence 10 Match clauses: ip address (access-lists) 101 Set clauses: interface Serial0/0.109 ip next-hop 172.16.101.1 Policy routing matches: 626 packets, 65304 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. This should be tested in a lab before you try it in a production network. 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