Troubleshooting A Route Map - HP 7102dl - ProCurve Secure Router Configuration Manual

Keep these tips in mind as you search a prefix list for misconfigurations:

Troubleshooting a Route Map

Enter the following enable mode command to view a route map:
Syntax: show route-map [<mapname>]
Include a name to view only that route map. If you want to see all route maps
configured on the router, do not enter a mapname.
ProCurve# show route-map
route-map ISP1, permit, sequence 10
Criteria for
selecting
routes
Number of routes
matches by
this map entry.
route-map ISP1, permit, sequence 20
Policies applied
to routes
Figure 15-42. Viewing BGP Policies in a Route Map
You can view how many routes have been matches to the route map. (See
Figure 15-42.) If the router does not seem to be filtering any routes, verify that
you have applied the route map to the correct neighbor and as the correct
policy (inbound or outbound).
If a statement does not include a range of prefixes, then a route must
match the statement exactly in order to be selected. Make sure that the
prefix length is correct.
Sequence numbers are important. The router stops processing the list
after it finds a match. In Figure 15-41, the deny statement must have a
lower sequence number than the permit statement because the route
specified in the deny statement also matches the permit statement.
The ge and le keywords match prefixes equal to length specified, as well
as those greater or lesser than the specified length. That is, the statement
permit 0.0.0.0/0 le 17 will allow /17 routes.
Match clauses:
ip address (prefix-lists): LAN1
Set clauses:
community no-export
metric 200
BGP Filtering matches: 5 routes
Policy routing matches: 0 packets, 0 bytes
Match clauses:
ip address (prefix-lists): LAN2
Set clauses:
metric 160
BGP Filtering matches: 4 routes
Policy routing matches: 0 packets, 0 bytes
IP Routing—Configuring RIP, OSPF, BGP, and PBR
Troubleshooting Routing
15-173