To create a route map, enter the route-map configuration mode, or
define the conditions for redistributing routes from one routing protocol into
another, use the
route-map command. To delete an entry, use
the
no
form of this command.
route-map map-tag [deny | permit] [sequence-number]
no route-map map-tag [permit | deny] [sequence-number]
Syntax Description
map-tag
|
Route map name.
|
deny
|
(Optional) Specifies that the route or packet is not
distributed as follows:
- If the match criteria are met for the route map, the
route is not redistributed.
- With policy routing, the packet is not policy routed and
route maps sharing the same map tag name are not examined. If the packet is not
policy routed, the normal forwarding algorithm is used.
|
permit
|
(Optional) Specifies that the route or packet is
distributed as follows:
- If the match criteria for this route are met, the route
is redistributed as controlled by the set actions. With policy routing, the
packet is policy routed.
- If the match criteria are not met, the next route map
with the same map tag is tested. If a route does not pass any of the match
criteria for the set of route maps sharing the same name, it is not
redistributed by that set.
|
sequence-number
|
(Optional) Number that indicates the position a new route
map will have in the list of route maps already configured with the same name.
The
no form of this command deletes the
position of the route map. Range: 0 to 65535.
|
Command Default
The
permit keyword is the default.
Command Modes
Global configuration
Command History
Release
|
Modification
|
4.0(1)
|
This command was introduced.
|
Usage Guidelines
You must enter the
feature
pbr global configuration mode command to enable
PBR before entering the
route-map command.
Use the
route-map command to enter route-map
configuration mode. Once you enter the
route-map command, the prompt changes to the
following:
switch(config-route-map)#
If you make changes to a route map that is used by a client, you must
exit the route-map configuration submode before the changes take effect in the
client. The route-map changes are not propagated to its clients until you exit
from the route-map configuration submode or 60 seconds expires since entering
the submode.
Once you enter the route-map configuration mode, the following
keywords are available:
- continue
sequence-number —Continues on a
different entry within the route-map. Range: 0 to 65535.
- description
description —Provides a description of the
route-map. The description can be any alphanumeric string up to 90 characters.
- exit —Exits from the current command mode.
- match —Matches the values from the
specified routing table. The following keywords and arguments are available:
- as-path
name [name ]
—Specifies the autonomous system (AS) path access list to match. The name can
be any alphanumeric string up to 63 characters. See the
match
as-path command for additional information.
- community
name [name |
exact-match ]— Specifies the BGP
community list name to match. See the
match
community command for additional
information.
- ip —Configures the IPv4 features. The
follow keywords and arguments are available:
address
{access-list-name
[access-list-name ] |
prefix-list
ipv4-list-name
ipv4-list-name ]}— Specifies the
address of the route or packet to match. See the
match
ip
address
command for additional information.
multicast {group
address/length |
rp
address/length }—Specifies the multicast
attributes to match. See the
match
ip
multicast command for additional
information.
next-hop —Matches the next-hop address of
route. See the
match
ip
next-hop command for additional
information.
route-source —Matches the advertising source
address of route. See the
match
ip
route-source
command for additional information.
-
- ipv6 —Configures the IPv6 features.
The follow keywords and arguments are available
address
{access-list-name
[access-list-name ] |
prefix-list
ipv6-list-name
ipv6-list-name ]}— Specifies the
address of the route or packet to match. See the
match
ipv6
address
prefix-list
command for additional information.
Note |
The IPv6 access-list name is for use in route-maps for PBR only.
|
multicast {group
address/length |
rp
address/length }—Specifies the multicast
attributes to match. See the
match
ipv6
multicast command for additional
information.
next-hop
prefix-list —Matches the next-hop address of route.
See the
match
ipv6
next-hop
prefix-list
command for additional information.
route-source —Matches the advertising source
address of route. See the
match
ipv6
route-source
prefix-list
command for additional information.
-
- length
minimum-length
maximum-length —Defines the minimum and
maximum packet length. See the
match
length
command for additional information.
- route-type —Matches the route-type of
the route. See the
match
route-type
command for additional information.
- tag —Matches the metric of route. See
the
match
tag
command for additional information.
Note |
The
default-information
originate command ignores
match statements in the optional route map.
|
- no —Negates a command or set its defaults.
- set —Sets the values in the destination
routing protocol. The
set commands specify the routing actions to
perform if the criteria enforced by the
match commands are met. You might want to
policy route packets some way other than the obvious shortest path. The
following keywords and arguments are available:
- as-path —Prepends a string for a BGP
AS-path attribute. See the
set
as-path command for additional information.
- comm-list —Sets the BGP community list
(for deletion). See the
set
comm-list command for additional
information.
- community —Sets the BGP community
attribute. See the
set
community command for additional
information.
- dampening —Sets the BGP route flap
dampening parameters. See the
set
dampening command for additional
information.
- forwarding-address —Sets the
forwarding address. See the
set
forwarding-address command for additional
information.
- ip —Configures the IP features. The
following keywords and arguments are available:
set
ip
default
next-hop —Indicates where to output packets that
pass a match clause of a route map for policy routing and for which the Cisco
NX-OS software has no explicit route to a destination. See the
set
ip
default
next-hop command for additional information.
set
ip
next-hop —Indicates where to output packets that
pass a match clause of a route map for policy routing. See the
set
ip
next-hop command for additional information.
-
- ipv6 —Configures the IPv6 features.
The following keywords and arguments are available:
set
ipv6
default
next-hop —Indicates where to output packets that
pass a match clause of a route map for policy routing and for which the Cisco
NX-OS software has no explicit route to a destination. See the
set
ipv6
default
next-hop command for additional information.
set
ipv6
next-hop —Indicates where to output packets that
pass a match clause of a route map for policy routing. See the
set
ipv6
next-hop command for additional information.
-
- level —Specifies where to import the
route. See the
set
level command for additional information.
- local-preference —Specifies the BGP
local preference path attribute. See the
set
local-preference command for additional
information.
- metric —Sets the metric for
destination routing protocol. See the
set
metric
command for additional information.
- metric-type —Sets the type of metric
for destination routing protocol. See the
set
metric-type command for additional
information.
- origin —Specifies the BGP origin code.
See the
set
origin command for additional information.
- tag —Specifies the tag value for
destination routing protocol. See the
set
tag command for additional information.
- vrf —Sets the VRF for next-hop
resolution. See the
set
vrf command for additional information.
- weight —Sets the BGP weight for the
routing table. See the
set
weight command for additional information.
Use route maps to redistribute routes or to subject packets to policy
routing. Both purposes are described in this section.
Redistribution
The
redistribute router configuration command
uses the
map-tag name to reference the route map.
Multiple route maps may share the same map tag name.
Use the
route-map global configuration command, and
the
match and
set route-map configuration commands, to
define the conditions for redistributing routes from one routing protocol into
another. Each
route-map command has a list of
match and
set commands associated with it. The
match commands specify the
match
criteria —the conditions under which redistribution
is allowed for the current
route-map
command. The
set commands specify the
set
actions —the particular redistribution actions to
perform if the criteria enforced by the
match commands are met. The
no
route-map command deletes the route
map.
The
match route-map configuration command has
multiple formats. The
match commands can be given in any order, and
all
match commands must “pass” to cause the route
to be redistributed according to the
set
actions
given with the
set commands. The
no forms of the
match commands remove the specified match
criteria.
Use route maps when you want detailed control over how routes are
redistributed between routing processes. The destination routing protocol is
the one you specify with the
router global configuration command. The
source routing protocol is the one you specify with the
redistribute router configuration command.
See the “Examples” section for an illustration of how route maps are
configured.
When you are passing routes through a route map, a route map can have
several parts. Any route that does not match at least one
match clause relating to a
route-map command will be ignored; that is,
the route will not be advertised for outbound route maps and will not be
accepted for inbound route maps. If you want to modify only some data, you must
configure a second route map section with an explicit match specified.
Policy Routing
Use the ip policy route-maor
ipv6
policy
route-map p command, in addition to the
route-map command, and the
match and
set commands to define the conditions for
policy routing packets. The
match commands specify the conditions under
which policy routing occurs. The
set commands specify the routing actions to
perform if the criteria enforced by the
match commands are met. You might want to
policy route packets some way other than the obvious shortest path.
The guidelines for the
sequence-number argument are as follows:
- If no entry is defined with the supplied tag, an entry is created
with the
sequence-number argument set to 10.
- If only one entry is defined with the supplied tag, that entry
becomes the default entry for the following
route-map command. The
sequence-number
argument
of this entry is unchanged.
- If more than one entry is defined with the supplied tag, an error
message is printed to indicate that the
sequence-number argument is required.
If the
no
route-map
map-tag command is specified (with no
sequence-number
argument), the whole route map is deleted.
Examples
This example shows how to redistribute Routing Information Protocol
(RIP) routes with a hop count equal to 1 into Open Shortest Path First (OSPF).
These routes will be redistributed into OSPF as external link-state
advertisements (LSAs) with a metric type of Type 1, and a tag equal to 1.
switch(config)# router ospf 109
switch(config-route-map)# redistribute rip route-map rip-to-ospf
switch(config-route-map)# route-map rip-to-ospf permit
switch(config-route-map)# set metric 5
switch(config-route-map)# set metric-type type1
switch(config-route-map)# set tag 1
This example for IPv6 shows how to redistribute Routing Information
Protocol (RIP) routes with a hop count equal to 1 into Open Shortest Path First
(OSPF). These routes will be redistributed into OSPF as external link-state
advertisements (LSAs) with a tag equal to 42 and a metric type equal to type1.
switch(config)# router 1
switch(config-route-map)# redistribute rip one route-map ripng-to-ospfv3
switch(config)# route-map ripng-to-ospfv3
switch(config-route-map)# match tag 42
switch(config-route-map)# set metric-type type1
This example sets the autonomous system path to match BGP autonomous
system path access list 20:
switch(config)#route-map IGP2BGP
switch(config-route-map)#match as-path 20
This example shows how to configure that the routes matching
community list 1 will have the weight set to 100. Any route that has community
109 will have the weight set to 100.
switch(config)#ip community-list 1 permit 109
switch(config)#route-map set_weight
switch(config-route-map)#match community 1
switch(config-route-map)#set weight 100
This example shows how to configure that the routes matching
community list 1 will have the weight set to 200. Any route that has community
109 alone will have the weight set to 200.
switch(config)#ip community-list 1 permit 109
switch(config)#route-map set_weight
switch(config-route-map)#match community 1 exact
switch(config-route-map)#set weight 200
This example shows how to configure that the routes match community
list LIST_NAME will have the weight set to 100. Any route that has community
101 alone will have the weight set to 100.
switch(config)#ip community-list 1 permit 101
switch(config)#route-map set_weight
switch(config-route-map)#match community LIST_NAME
switch(config-route-map)#set weight 100