35-6
Software Configuration Guide—Release 15.0(2)SG
OL-23818-01
Chapter 35 Configuring Policy-Based Routing
Policy-Based Routing Configuration Tasks
Routing based on dedicated links
Some applications or traffic can benefit from source-specific routing; for example, you can transfer stock
records to a corporate office on a higher-bandwidth, higher-cost link for a short time while sending
routine application data, such as e-mail, over a lower-bandwidth, lower-cost link.
Note PBR configuration is only allowed on interfaces belonging to the global routing table. PBR is not
supported on interfaces that belong to VRFs.
Policy-Based Routing Configuration Tasks
To configure PBR, perform the tasks described in the following sections. The task in the first section is
required; the tasks in the remaining sections are optional. For configuration examples, see the
“Policy-Based Routing Configuration Examples” section on page 35-8.
Enabling PBR, page 35-6 (Required)
Enabling Local PBR, page 35-8 (Optional)

Enabling PBR

To enable PBR, you must create a route map that specifies the match criteria and the resulting action if
all of the match clauses are met. Then you must apply that route-map on a particular interface. All
packets arriving on the specified interface matching the match clauses are subject to PBR.
To enable PBR on an interface, perform this task:
Command Purpose
Step 1 Switch(config)# route-map map-tag [permit |
deny] [sequence-number]Defines a route map to control where packets are sent. This
command puts the switch into route-map configuration mode.
Step 2 Switch(config-route-map)# match ip address
{access-list-number | name}
[...access-list-number | name]
Specifies the match criteria. The match criteria take the form
of one or more Standard or Extended IP access-lists. The
access-lists can specify the source and destination IP
addresses, protocol types, and port numbers. See Chapter 47,
“Configuring Network Security with ACLs” for more
information on Standard and Extended IP access-lists.
Step 3 Switch(config-route-map)# set ip next-hop
ip-address [... ip-address]
Or
Specifies the next-hop IP address to which matching packets
are sent. The next-hop IP address specified here must belong
to a subnet that is directly connected to this switch.
If more than one next-hop IP address is specified, the first
usable next-hop is chosen for routing matching packets. If the
next-hop is (or becomes) unavailable for some reason, the
next one in the list is chosen.