HP 7102dl - ProCurve Secure Router Configuration Manual page 902

IP Routing—Configuring RIP, OSPF, BGP, and PBR
Troubleshooting Routing
Criteria for
selecting
traffic
Number of routes
matches by
this map entry
Route for
selected
traffic
15-176
Router# show route-map
route-map PBR, permit, sequence 10
Match clauses:
length 150 200
Set clauses:
ip next-hop 10.10.10.254
BGP Filtering matches:
Policy routing matches: 4 packets, 600 bytes
route-map PBR, permit, sequence 20
Match clauses:
ip address (access-lists): 101
Set clauses:
ip next-hop 10.10.10.14
BGP Filtering matches:
Policy routing matches: 144 packets, 15190 bytes
Figure 15-43. Viewing PBR Policies in a Route Map
The display lists entries in the route map by sequence number. The entries are
further divided into match clauses, which show the criteria the map uses to
select packets, and set clauses, which show the next hop address or forward-
ing interface for the PBR route. (See Figure 15-43.)
You can verify that traffic can reach its destination by applying the route map
to router traffic with this global configuration mode context command:
Syntax: ip local policy route-map <mapname>
First clear the route map statistics so that you can later verify that the router
is matching the traffic to the route map. Enter:
ProCurve# clear route-map counters
Then send a ping to the desired destination using the extended commands so
that the ping matches the criteria specified in the route map.
For example, route map entry PBR 10 (shown in Figure 15-43) selects traffic
for which the Layer 3 packet size is between 150 and 200 bytes. You could
enter this command from the enable mode context:
ProCurve# ping size 150
0 packets, 0 bytes
0 packets, 0 bytes