Filter
Top Products
35-93
Cisco ME 3400 Ethernet Access Switch Software Configuration Guide
OL-9639-06
Chapter 35 Configuring IP Unicast Routing
Configuring Protocol-Independent Features
within the same route map. Beginning in Cisco IOS Release 12.2(37)SE, the switch supports the
continue clause for outbound policies. For more information about using the route map continue clause,
see the BGP Route-Map Continue Support for an Outbound Policy feature guide for Cisco IOS
Release
12.4(4)T at this URL:
http://www.cisco.com/en/US/products/ps6441/products_feature_guides_list.html
Note Although each of Steps 3 through 14 in the following section is 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 as-path path-list-number Match a BGP AS path access list.
Step 4
match community-list community-list-number [exact] Match a BGP community list.
Step 5
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 6
match metric metric-value Match the specified route metric. The metric-value can be
an EIGRP metric with a specified value from 0
to
4294967295.
Step 7
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 8
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 9
match interface type number [...type number] Match the specified next hop route out one of the
specified interfaces.
Step 10
match ip route-source {access-list-number |
access-list-name} [...access-list-number |
...access-list-name]
Match the address specified by the specified advertised
access lists.