Filter
Top Products
C H A P T E R 17 Access Policies
339
configure route-map <route-map> <sequence number>
add match [nlri-list <access_profile> | as-path
[access_profile <access-profile> | <as num>] |
community [access-profile <access_profile> |
<as_num>:<number> | number <community>] | next-hop
<ipaddress> | med <number> | origin [igp | egp |
incomplete | tag <number>]]
configure 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 | tag
<number>]]
configure route-map <route-map> <sequence number>
add goto <route-map>
where:
• The route-map is the name of the route map.
• The
sequence number identifies the entry in the route map to
which this statement is being added.
• The
match, set, and goto keywords specify the operations to
be performed. Within an entry, the statements are sequenced in
the order of their operation. The match statements are first,
followed by set, and then goto.
• The
nlri-list, as-path, community, next-hop, med,
origin, and weight keywords specify the type of values that
must be applied using the specified operation against the
corresponding attributes as described in Table 17.4 and
Table 17.5.
Table 17.4: Match Operation Keywords
Keyword Description
nlri-list <access_profile> Matches the NLRI against the specified access profile.
as-path [<access_profile> | <as-
no>]
Matches the AS path in the path attributes against the
specified access profile or AS number.