xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
345
To configure a route map named “map1” and add one sequence ID of 20 to the route map:
DGS-3627:admin# config route_map map1 add sequence 20
Command:4# config route_map map1 add sequence 20
Success.
config route_map sequence
Purpose To define the conditions for redistributing routes from one routing protocol into another, or to
enable policy routing, use the route map command in global configuration mode and the
match and set command in route map configuration modes.
Syntax
config route_map <map_name 16> sequence <value 1-65535> match [add | delete]
[as_path <list_name 16 > | community_list <list_name 16> {exact} | ip address
<list_name 16> | ip address prefix_list <list_name 16> | ip next_hop <list_name 16> | ip
next_hop prefix_list <list_name 16> | metric <value 0-4294967294>] [<portlist> | all]
max_entry [<value 1-n> | no_limit]
Description Route map can be used for redistribution or used as an inbound or outbound BGP session
filter.
A route map can have multiple rules; each rule is associated with a sequence number.
If one sequence entry is matched, then the following entries will not be checked.
A rule is formed by two parts, the match part and the set part. The match part defines the
match condition for the rule, and the set part defines the action that will be taken if the rule is
matched.
If a rule only has the set part defined but has no match part, then the rule will permit all, and
set part will take effect.
If a rule only has the match part defined but has no set part, and then if the rule is matched,
no action will be taken. If a rule has multiple match statements, then all the statements must
be matched in order for the rule to be matched.
If a rule has multiple set statements, then all the set will be applied if the rule is matched.
If the sequence number is not specified for the defined rule entry, the sequence number will
be automatically given. The automatically given sequence number will be a multiple of 10.
Therefore, if the defined rule is the first rule in the route map, the automatically given
sequence number will be 10. If the defined rule is not the first rule in the route map, the
sequence number will be the number that is a multiple of 10 and larger than the largest
sequence number of existing rules in the route map.
Parameters
<map_name 16> - The route map name.
<value 1-65535> - Specifies the sequence number for the rule. This is the number that
indicates the position a new route map will have in the list of route maps already configured
with the same name. Default: 10.
match deny - Specifies to deny the route if the rule is matched.
match permit - Specifies to permit the route if the rule is matched.
match as_path - Specifies to match the AS path of the route against the AS path list.
The AS path list specified here needs to be a sub-list of the AS path list associated with the
route.
match community_list - Specify to match the community of the route against the community
string.
exact - All of the communities and only those communities specified must be present.
match ip address - Specify to match the route according to the access list.
match ip address prefix_list - Specify to match the route according to the prefix list.
