Filtering Inbound Routes - HP ProCurve Secure Router 7203 dl Advanced Management And Configuration Manual

IP Routing—Configuring RIP, OSPF, BGP, and PBR
Configuring BGP
13-100
ProCurve(config-route-map)# match ip address prefix MultiExit2
ProCurve(config-route-map)# set metric 200
ProCurve(config-route-map)# exit
ProCurve(config)# route-map ISP2 10
ProCurve(config-route-map)# match ip address prefix MultiExit1
ProCurve(config-route-map)# set metric 200
ProCurve(config-route-map)# route-map ISP2 20
ProCurve(config-route-map)# match ip address prefix MultiExit2
ProCurve(config-route-map)# set metric 160
ProCurve(config-route-map)# exit
ProCurve(config)# router bgp 1
ProCurve(config-bgp)# neighbor 1.1.1.1
ProCurve(config-bgp-neighbor)# route-map ISP1 out
ProCurve(config-bgp-neighbor)# neighbor 2.2.2.2
ProCurve(config-bgp-neighbor)# route-map ISP2 out

Filtering Inbound Routes

Just as you can control the routes that the local router advertises to a neighbor,
you can also control the routes that the router accepts from a neighbor. You
can filter inbound routes according to:
destination network address and prefix length
community
AS path
You can see "Creating Prefix Lists: Configuring Filters for Route Exchange"
on page 13-78 for a discussion of filtering inbound routes according to the
routes' destination addresses and prefix lengths.
You use a route map to apply such a filter in much the same way as you would
use a prefix list. First, you configure the prefix list. However, instead of
applying the list directly to the neighbor, you match a route map entry to the
list and apply the route map to the neighbor as inbound policy.
If you are only filtering routes, there is no reason to use a route map. However,
the advantage of a route map is that you can also apply attributes to the filtered
routes. (See "Applying Policies to Inbound Routes" on page 13-102.)