> Route-map Configuration Mode Commands
> The Route-Map Configuration sub-mode is used for the OSPFv2 and BGP-4 routing protocols. This mode includes commands that configure matching rules and set actions to perform on matched routes.
> Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
> end
> Exits the context configuration mode and returns to the Exec mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> end
> Usage
> Change the mode back to the Exec mode.
> exit
> Exits the context configuration mode and returns to the global configuration mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> exit
> Usage
> Return to the global configuration mode.
> match as-path
> Match an AS path access list
> Product
> HA
> Privilege
> Security Administrator, Administrator
> Syntax
> match as-path AS_list
> no match interface AS_list
> no
> Disables matching the specified AS path access list.
> AS_list
> Specifies the name of an AS path access list for matching. AS_list must be from 1 to 79 alphanumeric characters in length.
> Usage
> This command is used for BGP-4 routing to specify an AS path access list to be matched. Refer to the ip as-path access-list command for more information.
> Example
> To match entries in an AS path access list named ASlist1, enter the following command;
> match as-path ASlist1
> match interface
> Specifies the next-hop interface name of a route to be matched.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> match interface interface-name
> no match interface interface-name
> no
> Disables matching the specified interface name.
> interface-name
> Specifies the name of the virtual interface for matching. This variable can be from 1 to 79 alphanumeric characters in length.
> Usage
> Use this command to specify the next hop interface name for routes to be matched.
> Example
> To match routes that have the next hop interface specified as Interface123, enter the following command:
> match interface Interface123
> To disable matching routes that have the next hop interface specified as Interface123, enter the following command:
> no match interface Interface123
> match ip address
> This command matches routes with entries in a route-access-list or prefix-list.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> match ip address { prefix-list | route-access-list } list_name
> no match ip address { prefix-list | route-access-list } list_name
> no
> Disable matching from the specified prefix list or route access list.
> prefix-list
> This command matches any routes with entries in a prefix-list.
> route-access-list
> This command matches any routes with entries in a route-access-list
> list_name
> The name of the IP prefix list or IP route access-list. This variable can be a string from 1 to 63 alphanumeric characters in length.
> Usage
> Use this command to match routes specified in a route-access-list or prefix-list.
> Example
> To match routes that are specified in a prefix list named Prefix100, enter the following command:
> match ip address prefix-list Prefix100
> To disable matching routes that are specified in a prefix list named Prefix100, enter the following command:
> no match ip address prefix-list Prefix100
> match ip next-hop
> This command matches next-hop IP addresses with entries in specified standard prefix-list or route-access-list.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> match ip address next-hop { prefix-list | route-access-list } list_name
> no match ip address next-hop { prefix-list | route-access-list } list_name
> prefix-list
> This command matches any routes that have a next-hop router address that has an entry in the specified prefix list.
> route-access-list
> This command matches any routes that have a next-hop router address that has an entry in the specified route-access-list.
> list_name
> The name of the IP prefix-list or IP route-access-list. This variable is a string from 1 through 63 alphanumeric characters in length.
> Usage
> Use this command to match next-hop IP addresses that have entries in the specified prefix-list or route-access-list.
> Example
> To match next-hop addresses with entries in a prefix-list named Prefix100, enter the following command:
> match ip address next-hop prefix-list Prefix100
> To disable matching next-hop addresses with entries in a prefix-list named Prefix100, enter the following command:
> no match ip address next-hop prefix-list Prefix100
> match metric
> This command matches routes that have the specified route metric.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> match metric metric_value
> no match metric metric_value
> no
> Disables matching of the specified route metric.
> metric_value
> This is the route metric to match. This must be an integer ranging from 0 through 4294967295.
> Usage
> Use this command to match routes that have the specified route metric.
> Example
> To match routes with the route metric of 1200, enter the following command:
> match metric 1200
> To disable matching routes with a route metric of 1200, enter the following command:
> no match metric 1200
> match origin
> This command matches the origin code learned from BGP. This command is for route maps that are used with BGP routing only.
> Product
> HA
> Privilege
> Security Administrator, Administrator
> Syntax
> match origin {egp | igp | incomplete}
> no match origin {egp | igp | incomplete}
> no
> Disables matching of the origin code.
> egp
> Match origins learned from learned from the External Gateway Protocol (EGP)
> igp
> Match origins learned from learned from the local Interior Gatewway Protocol (IGP)
> incomplete
> Match origins with unknown heritage.
> Usage
> Use this command to match origin codes for BGP routing.
> Example
> To match origin codes learned from EGP, enter the following command:
> match origin egp
> match route-type external
> Match external OSPF routes of the specified type.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> match route-type external { type-1 | type-2 }
> no match route-type external { type-1 | type-2 }
> type-1
> Only match type-1 external routes.
> type-2
> Only match type-2 external routes.
> Usage
> Use this command to match external routes of a specific type.
> Example
> The following command matches all external routes that are type-2:
> match route-type external type-2
> The following command disables matching external routes that are type-2:
> no match route-type external type-2
> match tag
> This command matches routes with the specified route tag value.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> match tag tag_value
> no match tag tag_value
> no
> Disable matching routes with the specified route tag value.
> tag_value
> The route tag value to match. This must be an integer from 0 through 4294967295.
> Usage
> Use this command to match routes that have the specified route tag value.
> Example
> Use the following command match routes that have a route tag value of 1234:
> match tag 1234
> Use the following command to disable matching routes that have a route tag value of 1234:
> no match tag 1234
> set as-path
> Modify an AS path for a route by adding the specified AS numbers to the front of the path.
> Product
> HA
> Privilege
> Security Administrator, Administrator
> Syntax
> set as-path prepend ASN
> no set as-path prepend ASN
> no
> Disable prepending the AS path. Any previously set prepends are removed.
> prepend
> Prepends the autonomous system path.
> ASN
> AS number(s) to be prepended to the AS path. You can specify up to 16 different AS numbers to be prepended in the order specified. Each AS number must be separated by a space. ASN must be an integer from 1 through 65535.
> Usage
> Use this command to add up to 16 specified AS numbers to the front of the AS path.
> Example
> The following command prepends the AS numbers 100, 200, and 1000 to matching AS paths:
> set as-path prepend 100 200 1000
> set ip next-hop
> Set the IP address that is applied as the next hop for routes.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> set ip next-hop ip_address
> no set ip next-hop ip_address
> no
> Disable the specified next hop address.
> ip_address
> This is the IP address of the next hop to which packets are output.
> Usage
> Use this command to set the IP address that is used as the next hop for routes.
> Example
> To set the next hop for routes to the IP address 192.168.2.100, use the following command:
> set ip next-hop 192.168.2.100
> To disable setting the next hop for routes to the IP address 192.168.2.100, use the following command:
> no set ip next-hop 192.168.2.100
> set metric
> This command sets the route metric for matched routes to the specified value.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> set metric metric_value
> no set metric metric_value
> metric_value
> This is the metric value that is set for routes. This must be an integer from 1 through 4294967295.
> Usage
> Use this command to set the route metric for matched routes.
> Example
> To set the route metric to 12345, use the following command;
> set metric 12345
> To disable setting the route metric to 12345, enter the following command;
> no set metric 12345
> set metric-type
> This command sets the route metric type to either Type-1 or Type-2 in the AS-external-LSA.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> set metric-type { type-1 | type-2 }
> no set metric-type { type-1 | type-2 }
> type-1
> Set the route metric to external type-1.
> type-2
> Set the route metric to external type-2
> Usage
> Use this command to set the route metric to either external type-1 or external type-2.
> Example
> To set the route metric to type-1, enter the following command:
> set metric type-1
> To disable setting the metric to type, enter the following command:
> no set metric type-1
> set origin
> This command sets the BGP origin code to the specified value. This command is for route maps that are used with BGP routing only.
> Product
> HA
> Privilege
> Security Administrator, Administrator
> Syntax
> set origin {egp | igp | incomplete}
> no set origin {egp | igp | incomplete}
> no
> Disables setting the origin code.
> egp
> Set the origin code to specify that the path is from a remote External Gateway Protocol (EGP) system.
> igp
> Set the origin code to specify that the path is from a local Interior Gateway Protocol (IGP) system.
> incomplete
> Set the origin code to specify that the path is from an unknown system.
> Usage
> Use this command to set a specified origin code for BGP.
> Example
> To the origin code to EGP, enter the following command:
> set origin egp
> set tag
> This command sets the route tag value for matched routes.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> set tag tag_value
> no set tag tag_value
> no
> Disable setting the route tag to the specified value.
> tag_value
> The route tag value to set. This must be an integer from 0 through 4294967295.
> Usage
> Use this command to set the route tag value that is applied to all matched routes.
> Example
> To set the route tag value to 12345, enter the following command:
> set tag 12345
> To disable setting the route tag value to 12345, enter the following command:
> no set tag 12345
> set weight
> Set the weight in the routing table for matching routes to the specified value.
> Product
> PDSN
> Privilege
> Security Administrator, Administrator
> Syntax
> set weight value
> no set weight value
> no
> Disable setting the routing weight value.
> value
> The weight in the routing table to assign. must be an integer from 1 through 4294967295.
> Usage
> Use this command to set the routing table weight on matched routes.
> Example
> The following command sets the routing table weight for matched routes to 1000:
> set weight 1000

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883