Pbr Configuration Guidelines; Enabling Pbr - Cisco WS-C3560-48PS-S Software Configuration Manual

Configuring Protocol-Independent Features

PBR Configuration Guidelines

Before configuring PBR, you should be aware of this information:
•
•
•
•
•
•
•
•
•

Enabling PBR

By default, PBR is disabled on the switch. 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 enable PBR
for that route map on an interface. All packets arriving on the specified interface matching the match
clauses are subject to PBR.
PBR can be fast-switched or implemented at speeds that do not slow down the switch. Fast-switched
PBR supports most match and set commands. PBR must be enabled before you enable fast-switched
PBR. Fast-switched PBR is disabled by default.
Packets that are generated by the switch, or local packets, are not normally policy-routed. When you
globally enable local PBR on the switch, all packets that originate on the switch are subject to local PBR.
Local PBR is disabled by default.
Note To enable PBR, the switch must be running the EMI.
Catalyst 3560 Switch Software Configuration Guide
30-72
To use PBR, you must have the EMI installed on the switch.
Multicast traffic is not policy-routed. PBR applies to only to unicast traffic.
You can enable PBR on a routed port or an SVI.
You can apply a policy route map to an EtherChannel port channel in Layer 3 mode, but you cannot
apply a policy route map to a physical interface that is a member of the EtherChannel. If you try to
do so, the command is rejected. When a policy route map is applied to a physical interface, that
interface cannot become a member of an EtherChannel.
You can define a maximum of 246 IP policy route maps on the switch.
You can define a maximum of 512 access control entries (ACEs) for PBR on the switch.
To use PBR, you must first enable the routing template by using the sdm prefer routing global
configuration command. PBR is not supported with the VLAN or default template. For more
information on the SDM templates, see
The number of TCAM entries used by PBR depends on the route map itself, the ACLs used, and the
order of the ACLs and route-map entries.
Policy-based routing based on packet length, IP precedence and TOS, set interface, set default next
hop, or set default interface are not supported. Policy maps with no valid set actions or with set
action set to Don't Fragment are not supported.
Chapter 30
Chapter 7, "Configuring SDM Templates."
Configuring IP Unicast Routing
78-16156-01