Downloads |
 Feedback
|
Table Of Contents
match ip route-source prefix-list
match ipv6 next-hop prefix-list
match ipv6 route-source prefix-list
message-digest-key (OSPF virtual link)
M Commands
This chapter describes the Cisco NX-OS unicast routing commands that begin with the letter M.
match as-number
To match to a Border Gateway Protocol (BGP ) autonomous system (AS) number , use the match as-number command. To remove an AS number list entry, use the no form of this command.
match as-number {number [,number...] | as-path-access-list name [...name]}
no match as-number {number [,number...] | as-path-access-list name [...name]}]
Syntax Description
Defaults
None
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the match as-number command to provide a list of AS numbers or an AS-path access list using a regular expression. BGP uses this match criteria to determine which BGP peers to create a BGP session with.
Use the route map to specify a range of AS numbers whose peers can establish session with the local BGP through prefix peering. Cisco NX-OS ignores any other match commands if the match as-number command is present in the route-map. .
This command does not require a license.
Examples
The following example shows how to configure a list of AS numbers:
switch(config)# route-map IGP2BGPswitch(config-route-map)# match as-number 64496, 64498-64510Related Commands
match as-path
To match a BGP autonomous system path access list, use the match as-path command in route-map configuration mode. To remove a path list entry, use the no form of this command.
match as-path name [...name]
no match as-path name [...name]
Syntax Description
Defaults
No path lists are defined.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The values set by the match as-path command overrides global values.
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.
This command does not require a license.
Examples
The following example sets the autonomous system path to match BGP autonomous system path access list 20:
switch(config)# route-map IGP2BGPswitch(config-route-map)# match as-path 20Related Commands
match community
To match a Border Gateway Protocol (BGP) community, use the match community command. To remove the match community command from the configuration file and restore the system to its default condition where the software removes the BGP community list entry, use the no form of this command.
community name [...name] [exact-match]
no community name [...name] [exact-match]
Syntax Description]
Command Default
No community list is matched by the route map.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
A route map can have several parts. Any route that does not match at least one match command 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.
Matching that is based on the community list number is one of the types of match commands applicable to BGP.
This command does not require a license.
Examples
The following example shows how to match two BGP communities:
switch(config)# route-map test2switch(config-route-map)# match community bgpLow bgpHighThe following example shows that the routes matching community list 1 will have the weight set to 200. Any route that has the standard community 109 only will have the weight set to 200.
switch(config)# ip community-list standard bgpLow permit 109switch(config)# route-map set_weightswitch(config-route-map)# match community bgpLow exact-matchswitch(config-route-map)# set weight 200The following example shows that the routes that match the community list 500. Any route that has expanded community 1 will have the weight set to 150.
switch(config)# ip community-list expanded 500 permit [0-9]*switch(config)# route-map MAP_NAME permit 10switch(config-route-map)# match community 500switch(config-route-map)# set weight 150Related Commands
match extcommunity
To match a Border Gateway Protocol (BGP) extended community in a route map, use the match extcommunity command. To remove the match from the route map, use the no form of this command.
extcommunity name [...name] [exact-match]
no extommunity name [...name] [exact-match]
Syntax Description]
Command Default
No community list is matched by the route map.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
A route map can have several parts. Any route that does not match at least one match command in the route map 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.
Matching that is based on the extended community list number is one of the types of match commands applicable to BGP.
This command does not require a license.
Examples
The following example shows how to match two BGP extended community lists:
switch(config)# route-map test2switch(config-route-map)# match community bgpLocal bgpRemoteThe following example shows that the routes that match the extended community list bgpLocal will change from nontransitive to transitive:
switch(config)# ip extcommunity-list standard bgpLocal permit generic nontransitive 1.9switch(config)# route-map deletCommunityswitch(config-route-map)# match extcommunity bgpLocal exact-matchswitch(config-route-map)# set extcommunity generic transitive 1.9Related Commands
match interface
To match an interface in a route map, use the match interface command. To remove the match, use the no form of this command.
match interface {interface-type number [, interface-type number...]}
no interface {interface-type number [, interface-type number...]}
Syntax Description
interface-type
Interface type. Use ? to see a list of supported interfaces.
number
(Optional) Interface number. Use ? to see the range.
Defaults
None
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the match interface command to provide a list of interfaces to match a route against. Route next-hop addresses that are reached by one of these interfaces result in a match for the 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.
This command does not require a license.
Examples
The following example shows how to configure a list of interfaces:
switch(config)# route-map test1switch(config-route-map)# match interface ethernet 2/1, ethernet 4/3Related Commands
route-map
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing.
match ip address
To distribute any routes that have a destination IP network number address that is permitted by a standard access list, an expanded access list, or a prefix list, or to perform policy routing on packets, use the match ip address command in route-map configuration mode. To remove the match ip address entry, use the no form of this command.
match ip address {access-list-name [access-list-name...] | prefix-list prefix-list-name [prefix-list-name...]}
no match ip address {access-list-name [access-list-name...] | prefix-list prefix-list-name [prefix-list-name...]}
Syntax Description
Defaults
No access list names or prefix lists are specified.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The access-list-name argument is supported in route-maps for PBR only.
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the access-list-name or the prefix-list-name arguments.
Like matches in the same route map subblock are filtered with "or" semantics. If any one match clause is matched in the entire route map subblock, this match is treated as a successful match. Dissimilar match clauses are filtered with "and" semantics. So dissimilar matches are filtered logically. If the first set of conditions is not met, the second match clause is filtered. This process continues until a match occurs or there are no more match clauses.
Use route maps to redistribute routes or to subject packets to policy routing. Both purposes are described in this section.
Redistribution
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.
When you are passing routes through a route map, a route map can have several sections that contain specific match clauses. 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
Another purpose of route maps is to enable policy routing. The match ip address command allows you to policy route packets based on criteria that can be matched with an expanded access list; for example, a protocol, protocol service, and source or destination IP address. To define the conditions for policy routing packets, use the ip policy route-map interface configuration command, in addition to the route-map global configuration command, and the match and set route-map configuration commands. 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 policy routing occurs. The set commands specify the set actions—the particular routing actions to perform if the criteria enforced by the match commands are met. You might want to policy route packets based on their source, for example, using an access list.
This command does not require a license.
Examples
In the following example, routes that have addresses specified by access list test will be matched:
switch(config)# feature pbrswitch(config)# interface ethernet 2/10switch(config-if)# ip policy route-map chicagoswitch(config-if)# exitswitch(config)# route-map chicagoswitch(config-route-map)# match ip address testRelated Commands
match ip multicast
To configure the IPv4 multicast features for the route-map matching, use the match ip multicast route-map configuration command. To remove the match, use the no form of this command.
match ip multicast {group address/length | source address/length | rp address/length [rp-type {asm | bidir}]}
no match ip multicast
Syntax Description
Command Default
None
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
To specify the multicast attributes to match, use the match ip multicast 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)#Once you enter route-map configuration mode, you can enter the match ip multicast command.
You can configure both group and rp options.
This command does not require a license.
Examples
This examples shows how to specify the group IPv4 prefix and the length of the IPv4 prefix for the neighbors to match:
switch(config)# route-map blueberryswitch(config-route-map)# match ip multicast group 192.0.0.0/19switch(config-route-map)#This examples shows how to specify both the group IPv4 prefix and the rendezvous point the IPv4 prefix for the neighbors to match:
switch(config)# route-map raspberryswitch(config-route-map)# match ip multicast group 192.0.0.0/19 rp 209.165.201.0/27switch(config-route-map)#Related Commands
match ip next-hop prefix-list
To redistribute any IPv4 routes that have a next hop router address passed by one of the access lists specified, use the match ip next-hop prefix-list command in route-map configuration mode. To remove the next hop entry, use the no form of this command.
match ip next-hop prefix-list prefix-list-name [ ...prefix-list-name]
no match ip next-hop prefix-list prefix-list-name [ ...prefix-list-name]
Syntax Description
prefix-list-name
Number or name of a prefix list. It can be any alphanumeric string up to 63 characters. The ellipsis indicates that multiple values can be entered, up to 32 prefix lists.
Command Default
Routes are distributed freely, without being required to match a next hop address.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the prefix-list-name argument.
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.
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.
This command does not require a license.
Examples
The following example distributes routes that have a next hop router address passed by prefix list test will be distributed:
switch(config)# route-map blueswitch(config-route-map)# match ip next-hop prefix-list testRelated Commands
match ip route-source prefix-list
To redistribute IPv4 routes that have been advertised by routers and access servers at the address specified by the access lists, use the match ip route-source prefix-list command in route-map configuration mode. To remove the route-source entry, use the no form of this command.
match ip route-source prefix-list prefix-list-name [ ...prefix-list-name]
no match ip route-source prefix-list prefix-list-name [ ...prefix-list-name]
Syntax Description
prefix-list-name
Number or name of a prefix list. It can be any alphanumeric string up to 63 characters. The ellipsis indicates that multiple values can be entered, up to 32 prefix lists.
Defaults
No filtering on route source.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the prefix-list-name argument.
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.
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 second route map section with an explicit match specified.
There are situations in which the next hop and source router address of the route are not the same.
This command does not require a license.
Examples
The following example distributes routes that have been advertised by routers and access servers at the addresses specified by access lists 5 and 80:
switch(config)# route-map blueswitch(config-route-map)# match ip route-source prefix-list 5 80Related Commands
match ipv6 address
To distribute any routes that have a destination IPv6 network number address that is permitted by a standard access list, an expanded access list, or a prefix list, or to perform policy routing on packets, use the match ipv6 address command in route-map configuration mode. To remove the match statement from the route map, use the no form of this command.
match ipv6 address {prefix-list prefix-list-name [prefix-list-name...] | access-list-name
no match ipv6 address {prefix-list prefix-list-name [prefix-list-name...] | access-list-name}
Syntax Description
Defaults
No access list names or prefix lists are specified.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The access-list-name argument is supported in route-maps for PBR only.
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the prefix-list-name argument.
Like matches in the same route map subblock are filtered with "or" semantics. If any one match clause is matched in the entire route map subblock, this match is treated as a successful match. Dissimilar match clauses are filtered with "and" semantics. So dissimilar matches are filtered logically. If the first set of conditions is not met, the second match clause is filtered. This process continues until a match occurs or there are no more match clauses.
Use route maps to redistribute routes or to subject packets to policy routing. Both purposes are described in this section.
Redistribution
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.
When you are passing routes through a route map, a route map can have several sections that contain specific match clauses. 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.
This command does not require a license.
Examples
In the following example, routes that have addresses specified by access list name red will be matched:
switch(config)# feature pbrswitch(config)# route-map blueswitch(config-route-map)# match ipv6 address redRelated Commands
match ipv6 multicast
To configure the IPv6 multicast features for the route-map matching, use the match ipv6 multicast route-map configuration command. To remove the match, use the no form of this command.
ip multicast {group address/length | source address/length | rp address/length [rp-type {asm | bidir}]}
Syntax Description
Command Default
None
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
To specify the multicast attributes to match, use the match ipv6 multicast route-map configuration command. 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)#Once you enter route-map configuration mode, you can enter the match ipv6 multicast command.
You can specify the group, source, and rp options.
This command does not require a license.
Examples
This examples shows how to specify the group IPv6 prefix and the length of the IPv6 prefix for the neighbors to match:
switch(config)# route-map blueberryswitch(config-route-map)# match ipv6 multicast group 30:0::0:0/12switch(config-route-map)#This examples shows how to specify both the group IPv6 prefix and the rendezvous point IPv6 prefix for the neighbors to match:
switch(config)# route-map redswitch(config-route-map)# match ipv6 multicast group 30:0::0:0/12 rp 2001:0DB8::/48switch(config-route-map)#Related Commands
match ipv6 next-hop prefix-list
To redistribute any IPv6 routes that have a next hop router address passed by one of the access lists specified, use the match ip next-hop prefix-list command in route-map configuration mode. To remove the next hop entry, use the no form of this command.
match ipv6 next-hop prefix-list name [...name]
no match ipv6 next-hop prefix-list name [...name]
Syntax Description
name...
Prefix list name. It can be any alphanumeric string up to 63 characters. The ellipsis indicates that multiple values can be entered, up to 32 prefix lists.
Command Default
Routes are distributed freely, without being required to match a next hop address.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the name argument.
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.
Note
A permit route map containing only set commands and no match commands permits all routes.
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.
This command does not require a license.
Examples
The following example distributes routes that have a next hop router address passed by prefix list 5 will be distributed:
switch(config)# route-map blueswitch(config-route-map)# match ipv6 next-hop prefix-list testRelated Commands
match ipv6 route-source prefix-list
To redistribute IPv6 routes that have been advertised by routers and access servers at the address specified by the access lists, use the match ipv6 route-source prefix-list command in route-map configuration mode. To remove the route-source entry, use the no form of this command.
match ipv6 route-source prefix-list name [...name]
no match ipv6 route-source prefix-list name [...name]
Syntax Description
name...
Prefix list name. It can be any alphanumeric string up to 63 characters. The ellipsis indicates that multiple values can be entered, up to 32 prefix lists.
Defaults
No filtering on route source.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the name argument.
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.
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 second route map section with an explicit match specified.
There are situations in which the next hop and source router address of the route are not the same.
This command does not require a license.
Examples
The following example distributes routes that have been advertised by routers and access servers at the addresses specified by prefix list test:
switch(config)# route-map blueswitch(config-route-map)# match ipv6 route-source prefix-list testRelated Commands
match length
To base policy routing on the Level 3 length of a packet, use the match length command in route-map configuration mode. To remove the entry, use the no form of this command.
match length minimum-length maximum-length
no match length minimum-length maximum-length
Syntax Description
Command Default
No policy routing occurs on the length of a packet.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
In IPv4, use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. Each route-map has a list of match and set commands associated with it. The match commands specify the match criteria—the conditions under which policy routing occurs. The set commands specify the set actions—the particular routing actions to perform if the criteria enforced by the match commands are met.
In IPv4, 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 packet to be routed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
In IPv4, you might want to base your policy routing on the length of packets so that your interactive traffic and bulk traffic are directed to different routers.
This command does not require a license.
Examples
This example shows how to set the packets 3 to 200 bytes long:
switch(config)# route-map blueswitch(config-route-map)# match length 3 200Related Commands
match route-type
To redistribute routes of the specified type, use the match route-type command in route-map configuration mode. To remove the route type entry, use the no form of this command.
match route-type {external | internal | level-1 | level-2 | local | nssa-external | type-1 | type-2}
no match route-type {external | internal | level-1 | level-2 | local | nssa-external | type-1 | type-2}
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
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.
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 second route map section with an explicit match specified.
You can specify more than one keyword.
This command does not require a license.
Examples
The following example redistributes internal routes:
switch(config)# route-map blueberryswitch(config-route-map)# match route-type internalThe following example redistributes internal routes and type-1 OSPF routes:
switch(config)# route-map blueberryswitch(config-route-map)# match route-type internal type-1Related Commands
match tag
To redistribute routes in the routing table that match the specified tags, use the match tag command in route-map configuration mode. To remove the tag entry, use the no form of this command.
match tag tag-value [...tag-value]
no match tag tag-value [...tag-value]
Syntax Description
tag-value
List of one or more route tag values. Each can be an integer from 0 to 4294967295. You can configure up to 32 tags.
Defaults
No match tag values are defined.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the tag-value argument.
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.
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 second route map section with an explicit match specified.
This command does not require a license.
Examples
The following example redistributes routes stored in the routing table with tag 5:
switch(config)# route-map blueberryswitch(config-route-map)# match tag 5Related Commands
max-metric router-lsa (OSPF)
To configure the Open Shortest Path First (OSPF) protocol to advertise a maximum metric so that other routers do not prefer the router as an intermediate hop in their shortest path first (SPF) calculations, use the max-metric router-lsa command. To disable the advertisement of a maximum metric, use the no form of this command.
max-metric router-lsa [on-startup [seconds | wait-for bgp tag]]
no max-metric router-lsa [on-startup [seconds | wait-for bgp tag]]
Syntax Description
Defaults
Originates router link-state advertisements (LSAs) with normal link metrics.
Command Modes
Router configuration
Router VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the max-metric router-lsa command to originate LSAs with a maximum metric (LSInfinity: 0xFFFF) through all nonstub links, which allows BGP routing tables to converge without attracting transit traffic (if there are not alternate lower cost paths to the router). The router advertises accurate (normal) metrics after the configured or default timers expire or after BGP sends a notification that routing tables have converged.
Note
You can use the max-metric router-lsa command in the following situations:
•
•
•
Note
This command requires the Enterprise Services license.
Examples
The following example shows how to configure a router that is running OSPF to advertise a maximum metric for 100 seconds:
switch(config)# router ospf 100switch(config-router)# max-metric router-lsa on-startup 100The following example shows how to configure a router to advertise a maximum metric until BGP routing tables converge or until the default timer expires (600 seconds):
switch(config)# router ospf 100switch(config-router)# max-metric router-lsa on-startup wait-for bgp bgpTagRelated Commands
max-lsp-lifetime
To set the maximum time for which link-state packets (LSPs) persist without being refreshed, use the max-lsp-lifetime configuration mode command. To restore the default time, use the no form of this command.
max-lsp-lifetime value
no max-lsp-lifetime
Syntax Description
Command Default
The default is 1200 seconds.
Command Modes
Router configuration
VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The maximum LSP lifetime must be greater than the LSP refresh interval.
This command requires the Enterprise Services license.
Command Default
The following example sets the maximum time that the LSP persists to 11,000 seconds (more than 3 hours):
switch(config)# router isisswitch(config-router)# max-lsp-lifetime 11000
Related Commands
exit
Exits the current configuration mode.
feature isis
Enables IS-IS on the router.
no
Negates a command or sets its defaults.
router isis
Enables IS-IS.
maxas-limit
To configure the external Border Gateway Protocol (eBGP) to discard routes that have a high number of autonomous system (AS) numbers in the AS-path attribute, use the maxas-limit command. To revert to the default, use the no form of this command.
maxas-limit [number]
no maxas-limit
Syntax Description
number
(Optional) Maximum number of AS numbers allowed in the AS-path attribute. The range is from 1 to 2000.
Command Default
No limit
Command Modes
Router configuration
VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command requires the Enterprise Services license.
Command Default
The following example shows how to set the maximum number of AS numbers to 50:
switch(config)# router bgp 64496switch(config-router)# maxas-limit 50
Related Commands
maximum-paths (BGP)
To control the maximum number of parallel routes that the Border Gateway Protocol (BGP) can support, use the maximum-paths configuration mode command. To restore the default number of parallel routes, use the no form of this command.
maximum-paths [ibgp] number-paths
no maximum-paths [ibgp] number-paths
Syntax Description
ibgp
Configures the maximum interior BGP (iBGP) paths.
number-paths
Maximum number of parallel routes that an IP routing protocol installs in a routing table. The range is from 1 to 16.
Command Default
8 paths
Command Modes
Router address family configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
There are no usage guidelines for this command.
Examples
The following example shows how to allow a maximum of 16 paths to a destination for a BGP routing process:
switch(config)# router bgp 64496switch(config-router)# maximum-paths 16Related Commands
maximum-paths (EIGRP)
To control the maximum number of parallel routes that the Enhanced Interior Gateway Routing Protocol (EIGRP) can support, use the maximum-paths command. To remove the maximum-paths command from the configuration file and restore the default, use the no form of this command.
maximum-paths maximum
no maximum- paths
Syntax Description
maximum
Maximum number of parallel routes that EIGRP can install in a routing table. The range is from 1 to 16 routes.
Defaults
8 paths
Command Modes
Address-family configuration
Router configuration
Router VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
4.0(1)
This command was introduced.
4.0(2)
The default maximum paths was changed to 8 from 16.
Usage Guidelines
Use the maximum-paths command to allow EIGRP to install multiple paths into the routing table for each prefix. Multiple paths are installed for both internal and external routes that are learned in the same autonomous system and that are equal cost (according to the EIGRP best path algorithm).
This command requires the Enterprise Services license.
Examples
The following example shows how to allow a maximum of 10 paths to a destination:
switch(config)# router eigrp 1switch(config-router)# maximum-paths 10maximum-paths (IS-IS)
To control the maximum number of parallel routes that an IP routing protocol can support, use the maximum-paths configuration mode command. To restore the default number of parallel routes, use the no form of this command.
maximum-paths number-paths
no maximum-paths
Syntax Description
number-paths
Maximum number of parallel routes that an IP routing protocol installs in a routing table. The range is from 1 to 16.
Command Default
8 paths
Command Modes
Router configuration
VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
There are no usage guidelines for this command.
Examples
The following example shows how to allow a maximum of 16 paths to a destination for an IS-IS routing process:
switch(config)# router isis 3switch(config-router)# maximum-paths 16Related Commands
exit
Exits the current configuration mode.
feature isis
Enables IS-IS on the router.
no
Negates a command or sets its defaults.
router isis
Enables IS-IS.
maximum-paths (RIP)
To configure the maximum number of equal cost parallel routes that the the Routing Information Protocol (RIP) will install into the routing table, use the maximum-paths command in the router address-family configuration mode. To remove the maximum-paths command and restore the system to its default condition with respect to RIP, use the no form of this command.
maximum-paths maximum
no maximum-paths
Syntax Description
maximum
Maximum number of parallel routes that RIP can install in a routing table. The range is from 1 to 16.
Defaults
8 paths
Command Modes
Router address-family configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
The following example shows how to allow a maximum of 16 equal cost paths to a destination:
switch(config)# router rip Enterpriseswitch(config-router)# address-family ipv4 unicastswitch(config-router-af)# maximum-paths 16Related Commands
maximum-paths (OSPF)
To control the maximum number of parallel routes that Open Shortest Path First (OSPF) can support, use the maximum-paths command. To remove the maximum-paths command from the configuration file and restore the system to the default, use the no form of this command.
maximum-paths maximum
no maximum- paths
Syntax Description
maximum
Maximum number of parallel routes that OSPF can install in a routing table. The range is from 1 to 16 routes.
Defaults
8 paths
Command Modes
Router configuration
Router VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the maximum-paths command to allow OSPF to install multiple paths into the routing table for each prefix. Multiple paths are installed for both internal and external routes that are learned in the same autonomous system and that have an equal cost (according to the OSPF shortest path first algorithm).
This command requires the Enterprise Services license.
Examples
The following example shows how to allow a maximum of 10 paths to a destination:
switch(config)# router ospf 1switch(config-router)# maximum-paths 10maximum-paths (OSPFv3)
To control the maximum number of parallel routes that Open Shortest Path First version 3 (OSPFv3) can support, use the maximum-paths command. To remove the maximum-paths command from the configuration file and restore the system to the default, use the no form of this command.
maximum-paths maximum
no maximum- paths
Syntax Description
maximum
Maximum number of parallel routes that OSPFv3 can install in a routing table. The range is from 1 to 16 routes.
Defaults
8 paths
Command Modes
Address-family configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the maximum-paths command to allow OSPFv3 to install multiple paths into the routing table for each prefix. Multiple paths are installed for both internal and external routes that are learned in the same autonomous system and that have an equal cost (according to the OSPFv3 shortest path first algorithm).
This command requires the Enterprise Services license.
Examples
This example shows how to allow a maximum of 10 paths to a destination:
switch(config)# router ospfv3 1switch(config-router)# address-family ipv6 unicastswitch(config-router-af)# maximum-paths 10maximum-prefix
To control how many prefixes can be received from a neighbor, use the maximum-prefix command in peer template configuration mode. To disable this function, use the no form of this command.
maximum-prefix maximum [threshold] [restart restart-interval] [warning-only]
no maximum-prefix
Syntax Description
Command Default
This command is disabled by default. Peering sessions are disabled when the maximum number of prefixes is exceeded. If you do not configure the restart interval, a disabled session will stay down after the maximum-prefix limit is exceeded.
Command Modes
Peer template configuration
Router bgp configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The number of prefixes that can be configured is limited only by the available system resources on a router.
The maximum-prefix command allows you to configure a maximum number of prefixes that a Border Gateway Protocol (BGP) routing process will accept from the specified peer. This feature provides a mechanism (in addition to distribute lists, filter lists, and route maps) to control prefixes received from a peer.
When the number of received prefixes exceeds the maximum number configured, BGP disables the peering session (by default). If the restart keyword is configured, BGP will automatically reestablish the peering session at the configured time interval. If the restart keyword is not configured and a peering session is terminated because the maximum prefix limit has been exceed, the peering session will not be be reestablished until the clear ip bgp command is entered. If the warning-only keyword is configured, BGP sends only a log message and continues to peer with the sender.
There is no default limit on the number of prefixes that can be configured with this command. Limitations on the number of prefixes that can be configured are determined by the amount of available system resources.
Examples
In the following example, the maximum prefixes that will be accepted from the 192.168.1.1 neighbor is set to 1000:
switch(config)# router bgp 64496switch(config-router)# network 192.168.0.0switch(config-router)# maximum-prefix 1000In the following example, the maximum number of prefixes that will be accepted from the 192.168.2.2 neighbor is set to 5000. The router is also configured to display warning messages when 50 percent of the maximum-prefix limit (2500 prefixes) has been reached.
switch(config)# router bgp 64496switch(config-router)# network 192.168.0.0switch(config-router)# maximum-prefix 5000 50In the following example, the maximum number of prefixes that will be accepted from the 192.168.3.3 neighbor is set to 2000. The router is also configured to reestablish a disabled peering session after 30 minutes.
switch(config)# router bgp 64496switch(config-router)# network 192.168.0.0switch(config-router)# maximum-prefix 2000 restart 30In the following example, warning messages will be displayed when the maximum-prefix limit (500) for the 192.168.4.4 neighbor is exceeded:
switch(config)# router bgp 64496switch(config-router)# network 192.168.0.0switch(config-router)# maximum-prefix 500 warning-onlymessage-digest-key (OSPF virtual link)
To enable Open Shortest Path First (OSPF) Message Digest 5 (MD5) authentication on a virtual link, use the message-digest-key command. To remove an old MD5 key, use the no form of this command.
message-digest-key key-id md5 [0 | 3] key
no message-digest-key key-id
Syntax Description
Defaults
Unencrypted
Command Modes
Virtual link configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the message-digest-key command when you configure the MD5 digest authentication mode. Both interfaces on the virtual link must have the same key value.
This command requires the Enterprise Services license.
Examples
The following example shows how to set key 19 with the password 8ry4222:
switch(config-router)# area 22 virtual-link 192.0.2.2switch(config-router-vlink)# message-digest-key 19 md5 8ry4222Related Commands
authentication (virtual-link)
Configures the authentication mode on a virtual link.
metric maximum-hops
To advertise that those Enhanced Interior Gateway Routing Protocol (EIGRP) routes with a higher hop count than you specified are unreachable, use the metric maximum-hops command. To reset the value to the default, use the no form of this command.
metric maximum-hops hops-number
no metric maximum-hops
Syntax Description
Defaults
hops-number: 100
Command Modes
Address-family configuration
Router configuration
Router VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the metric maximum-hops command to provide a safety mechanism that causes EIGRP to advertise as unreachable routes with a hop count greater than the value assigned to the hops-number argument.
This command requires the Enterprise Services license.
Examples
The following example shows how to configure a hop count to 200:
switch(config)# router eigrp 1switch(config-router) address-family ipv4 unicastswitch(config-router-af)# metric maximum-hops 200Related Commands
metric weights
To tune the Enhanced Interior Gateway Routing Protocol (EIGRP) metric calculations, use the metric weights command. To reset the values to their defaults, use the no form of this command.
metric weights tos k1 k2 k3 k4 k5
no metric weights
Syntax Description
Defaults
tos: 0
k1: 1
k2: 0
k3: 1
k4: 0
k5: 0
Command Modes
Address-family configuration
Router configuration
Router VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the metric weights command to alter the default behavior of EIGRP routing and metric computation and allow the tuning of the EIGRP metric calculation for a particular ToS.
If k5 equals 0, Cisco NX-OS computes the composite EIGRP metric according to the following formula:
metric = [k1 x bandwidth + (k2 x bandwidth)/(256 - load) + k3 x delay]
If k5 does not equal zero, Cisco NX-OS performs an additional calculation:
metric = metric x [k5/(reliability + k4)]
Use the bandwidth command in interface configuration mode to set the bandwidth metric.
Use the delay command in interface configuration mode to set the delay.
255 is a reliability of 100 percent or a perfectly stable link. A load of 255 indicates a completely saturated link.
This command requires the Enterprise Services license.
Examples
The following example shows how to set the metric weights to change the default values:
switch(config)# router eigrp 1switch(config-router) address-family ipv4 unicastswitch(config-router-af)# metric weights 0 2 0 2 0 0Related Commands
bandwidth
Sets the EIGRP bandwidth metric in interface configuration mode.
delay
Sets the EIGRP delay metric in interface configuration mode.
metric-style transition
To configure the metric style that Intermediate-System-to-Intermediate System (IS-IS) uses in advertised link-state update messages (LSPs), use the metric-style transition command. To revert to the default setting, use the no form of this command.
metric-style transition
no metric-style transition
Syntax Description
This command has no keywords or arguments.
Command Default
Wide metric style
Command Modes
Router configuration
VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the metric-style transition command to configure IS-IS to generate and accept both narrow metric style and wide metric style Type Length Value (TLV) objects.
This command requires the Enterprise Services license.
Examples
The following example shows how to configure the metric style:
switch(config-router)# metric-style transitionswitch(config-router)#Related Commands
feature isis
Enables IS-IS on the router.
router isis
Creates an IS-IS instance.
