), 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 Policy-Routing Example 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-routed instead of being routed as it would normally. Here's an example of packets that did not match the route map, and as such were routed normally: 04:52:35: IP: s=10.209.0.2 (FastEthernet0/1), d=10.201.0.1, len 100, FIB policy rejected(no match) - normal forwarding 04:52:35: IP: s=10.209.0.2 (FastEthernet0/1), d=10.201.0.1, len 100, FIB policy rejected(no match) - normal forwarding 04:52:35: IP: s=10.209.0.2 (FastEthernet0/1), d=10.201.0.1, len 100, FIB policy rejected(n match) - normal forwarding 04:52:35: IP: s=10.209.0.2 (FastEthernet0/1), d=10.201.0.1, len 100, FIB policy rejected(no match) - normal forwarding 04:52:35: IP: s=10.209.0.2 (FastEthernet0/1), d=10.201.0.1, len 100, FIB policy rejected(no match) - normal forwarding Again, I've highlighted the entry for a single packet. This time we 