requesting that the neighbor advertise the route to certain communities
only
prepending private AS numbers to specific routes to help balance inbound
traffic
setting a multi-exit discriminator on specific routes to help balance
inbound traffic
When you apply a route map to inbound data, it determines which of the ISP-
advertised routes the local router accepts. You can configure the inbound
route map to perform such tasks as:
filtering external routes according to:
•
network address or prefix length
•
the AS through which packets must pass
•
community
•
metric
applying attributes to filtered routes, including:
•
local preference
•
community
deleting communities defined for the routes
As you learn how to configure these policies in the following sections, you
will be instructed to create a route map entry and to apply a route map to
inbound or outbound data. Depending on the types of policies that you
implement, you may need to configure community or AS path lists.
The next several sections describe how to configure these map entries and
lists.
Creating a Route Map Entry
To create a route map entry, enter this command from the global configuration
mode context:
Syntax: route-map <mapname> <sequence number>
You can apply one route map to each neighbor for outbound data and one for
inbound data. You can configure multiple policies in the single route map by
creating entries with the same name but a different sequence number.
IP Routing—Configuring RIP, OSPF, BGP, and PBR
Configuring BGP
13-87