![](https://pdfstore-manualsonline.prod.a.ki/pdfasset/c/f9/cf9abe3c-cbdc-4cee-9477-3b670eb02cf4/cf9abe3c-cbdc-4cee-9477-3b670eb02cf4-bg15e.png)
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
346
config route_map sequence
match ip next_hop - Specify to match the next hop of the route according to the access list.
match ip next_hop prefix_list - Specify to match the next hop of the route according to the
prefix list.
match metric - Specify to match the metric of the route.
Restrictions Only Administrator and Operator-level users can issue this command.
Example usage:
To configure the route map match access list “ac_list1” and set the metric to 50:
DGS-3627:admin# config route_map map1 sequence 10 match add ip address ac_list1
Command:4# config route_map map1 sequence 10 match add ip address ac_list1
DGS-3627:admin# config route_map map1 sequence 10 set add metric 50
Command:4# config route_map map1 sequence 10 set add metric 50
Success.
config route_map sequence set
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 commands in route map configuration modes.
Syntax
config route_map <map_name 16> sequence <value 1-65535> set [add | delete]
[next_hop [<ipaddr> | peer_address ] | metric < uint 0-4294967294> | local_preference <
uint 0-4294967295> | weight <value 0-65535> | as_path <aspath_list> | community {<
communit_set 80 > | internet | no_export | no_advertise | local_as} {additive} |
origin[egp | igp | incomplete] | dampening <min 1-45> <value 1-20000> <value 1-
20000><min 1-255> <min 1-45>]
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 the existing rule in the route map.