Creating a Route Map
To create a route map, use the following command:
create route-map <route-map>
Adding Entries to the Route Map
To add entries to the route map, use the following command:
config route-map <route-map> add <sequence number> [permit | deny]
{match-one | match-all}
Where the following is true:
• The
sequence number
the entry in the route map. Route maps are evaluated sequentially.
• The
permit
applied only if the entry is successful.
• The
match-one
least one of the matching statements is true.
• The
match-all
match statements are true. This is the default setting.
Adding Statements to the Route Map Entries
To add statements to the route map entries, use one of the following four commands:
config route-map <route-map> <sequence number> add match [nlri-list
<access_profile> | as-path <access_profile> | <as-no> | community
[access-profile <access_profile> | <as_num:number> | number <community>] |
next-hop <ipaddress> | med <number> | origin [igp | egp | incomplete]]
config route-map <route_map> <sequence number> add set [as-path <as_num> |
community [remove | {add | delete} [access-profile <access_profile> |
<as_num:number> | number <number> | next-hop <ipaddress> | med <number> |
local-preference <number> | origin [igp | egp | incomplete]]
config route-map <route-map> <sequence number> add goto <route-map>
config route-map <route-map> <sequence number> [add | delete] set
accounting-index 1 value <bin_number>
MPLS Module Installation and User Guide
uniquely identifies the entry and determines the position of
keyword permits the route; the
keyword is a logical "or". The route map is successful as long as at
keyword is a logical "and". The route map is successful when all
keyword denies the route and is
deny
Configuring Route Maps
8-11