BGP: Configuring Route Maps
Once you have made the ACL, apply it to the match clause of a route map entry by using the command:
A next hop address
You can use either a prefix list or an ACL to specify a next hop address. Once you have made the prefix list or ACL, apply it to the match clause of a route map entry by using one of the commands:
An update message matches this route map entry if the
An origin
To match an origin, use the command:
An update message matches this route map entry if the origin attribute in the update equals the origin specified in the entry.
A metric (the MED attribute)
To match the MED value, use the command:
An update message matches this route map entry if the MED attribute in the update equals the value specified in the entry.
Configuring a set clause
If a packet matches the match clause, then the action of the route map entry will be applied to that packet. The action might simply be to permit or deny the packet, or it might be to update its attributes by applying one or more set clauses.
Note: When configuring a set clause, make sure you are in route map mode for the same route map name sequence number as you used for the match clause. The prompt should look like this:
A set clause can change any of the following attributes on an update message:
AS path Multiple Autonomous System numbers (ASNs) can be added to the AS path attribute in the update packet. Use the command:
set
If adding multiple ASNs, separate them with spaces.
Page 30 Use Route Maps and Other Filters to Filter and Alter BGP and OSPF Routes