User guide

E
XTREME
W
ARE
S
OFTWARE
U
SER
G
UIDE
16-31
U
SING
R
OUTE
M
APS
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>
where the following is true:
• 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
a 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 Ta b l e 1 6 - 4 and Table 16-5.
Table 16-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.
community [<access_profile> |
<community>]
Matches the communities in the path attribute against
the specified BGP community access profile or the
community number.
next-hop <ipaddress> Matches the next hop in the path attribute against the
specified IP address.
med <number> Matches the MED in the path attribute against the
specified MED number.
origin [igp | egp | incomplete] Matches the origin in the path attribute against the
specified origin.