y routing takes place when a packet is received on an interface. For this reason, the policy must be placed on the Ethernet interfaces in this example. Monitoring Policy Routing Once policy routing is configured, how do you know it's working? In the preceding source-routing example, we altered the way packets routed, but the IP routing table didn't change. Normally, we would look at the routing table to determine where a router is sending packets, but with policy routing in place, the routing table is no longer the most reliable source of information. Policy Routing Example Policy routing overrides the routing table, which can be confusing when you're troubleshooting routing problems. If your packets are not rout- ing the way you expect them to, check for policy routing on your inter- faces. To see which policies are applied to which interfaces, use the show ip policy command: Branch-9#sho ip policy Interface Route map FastEtherneto/o Company-1 FastEtherneto/1 Company-2 Another method for determining whether policy routing is enabled is using 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 cumulative, 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-1, permit, sequence 10 Match clauses: ip address (access-lists) 102 Set clauses: interface Serial0/0.109 ip next-hop 172.16.101.1 Policy routing matches: 626 packets, 65304 bytes route-map Company-2, permit, sequence 10 Match clauses: ip address (access-lists