User guide

16-32 E
XTREME
W
ARE
S
OFTWARE
U
SER
G
UIDE
A
CCESS
P
OLICIES
R
OUTE
M
AP
O
PERATION
The entries in the route map are processed in the ascending order of the sequence
number. Within the entry, the match statements are processed first. When the match
operation is successful, the set and goto statements within the entry are processed, and
the action associated with the entry is either applied, or else the next entry is processed.
If the end of the route map is reached, it is implicitly denied.
When there are multiple match statement, the primitive match-one or match-all in the
entry determines how many matches are required for success. When there are no match
statements in an entry, the entry is considered a successful match.
R
OUTE MAP EXAMPLE
Figure 16-9 shows a topology in which route maps are used to filter or modify routing
information that is exchanged between the neighbors RTA and RTB using BGP.
Table 16-5: Set Operation Keywords
Keyword
Definition
as-path <as no> Prepends the specified AS number to the AS path in the
path attribute.
community <community> Adds the specified community to the existing community
in the path attribute.
next-hop <ipaddress> Sets the next hop in the path attribute to the specified
IP address.
med <number> Sets the MED in the path attribute to the specified MED
number.
local-preference <number> Sets the local preference in the path attribute to the
specified local preference number.
weight <number> Sets the weight associated with the NLRi to the
specified number.
origin Sets the origin in the path attributes to the specified
origin.