Administrator Guide

Configuring Match Routes
To configure match criterion for a route map, use the following commands.
• Match routes whose next hop is a specific interface.
CONFIG-ROUTE-MAP mode
match interface interface
The parameters are:
• For a Loopback interface, enter the keyword loopback then a number between zero (0) and 16383.
• For a 10-Gigabit Ethernet interface, enter the keyword tengigabitEthernet then the slot/port
information.
• For a VLAN, enter the keyword vlan then a number from 1 to 4094.
• Match destination routes specified in a prefix list (IPv4).
CONFIG-ROUTE-MAP mode
match ip address prefix-list-name
• Match next-hop routes specified in a prefix list (IPv4).
CONFIG-ROUTE-MAP mode
match ip next-hop {access-list-name | prefix-list prefix-list-name}
• Match source routes specified in a prefix list (IPv4).
CONFIG-ROUTE-MAP mode
match ip route-source {access-list-name | prefix-list prefix-list-name}
• Match routes with a specific value.
CONFIG-ROUTE-MAP mode
match metric metric-value
• Match routes specified as internal or external to OSPF, ISIS level-1, ISIS level-2, or locally generated.
CONFIG-ROUTE-MAP mode
match route-type {external [type-1 | type-2] | internal | level-1 | level-2 |
local }
• Match routes with a specific tag.
CONFIG-ROUTE-MAP mode
match tag tag-value
To create route map instances, use these commands. There is no limit to the number of match commands
per route map, but the convention is to keep the number of match filters in a route map low.
Set commands
do not require a corresponding match command.
Access Control Lists (ACLs) 151