34-32
Cisco Catalyst Blade Switch 3020 for HP Software Configuration Guide
OL-8915-03
Chapter 34 Configuring IP Unicast Routing
Configuring Protocol-Independent Features
the conditions defined by the match command. Although redistribution is a protocol-independent
feature, some of the match and set route-map configuration commands are specific to a particular
protocol.
One or more match commands and one or more set commands follow a route-map command. If there
are no match commands, everything matches. If there are no set commands, nothing is done, other than
the match. Therefore, you need at least one match or set command.
You can also identify route-map statements as permit or deny. If the statement is marked as a deny, the
packets meeting the match criteria are sent back through the normal forwarding channels
(destination-based routing). If the statement is marked as permit, set clauses are applied to packets
meeting the match criteria. Packets that do not meet the match criteria are forwarded through the normal
routing channel.
Note Although the steps following Step 3 are optional, you must enter at least one match route-map
configuration command and one set route-map configuration command.
Beginning in privileged EXEC mode, follow these steps to configure a route map for redistribution:
Command Purpose
Step 1
configure terminal Enter global configuration mode.
Step 2
route-map map-tag [permit | deny] [sequence number] Define any route maps used to control redistribution and
enter route-map configuration mode.
map-tag—A meaningful name for the route map. The
redistribute router configuration command uses this
name to reference this route map. Multiple route maps
might share the same map tag name.
(Optional) If permit is specified and the match criteria
are met for this route map, the route is redistributed as
controlled by the set actions. If deny is specified, the
route is not redistributed.
sequence number (Optional)— Number that indicates the
position a new route map is to have in the list of route
maps already configured with the same name.
Step 3
match ip address {access-list-number |
access-list-name} [...access-list-number |
...access-list-name]
Match a standard access list by specifying the name or
number. It can be an integer from 1 to 199.
Step 4
match metric metric-value Match the specified route metric. The metric-value can be
a specified value from 0 to 4294967295.
Step 5
match ip next-hop {access-list-number |
access-list-name} [...access-list-number |
...access-list-name]
Match a next-hop router address passed by one of the
access lists specified (numbered from 1 to 199).
Step 6
match tag tag value [...tag-value] Match the specified tag value in a list of one or more route
tag values. Each can be an integer from 0 to 4294967295.
Step 7
match interface type number [...type number] Match the specified next hop route out one of the
specified interfaces.