Cisco Catalyst 9500 series Configuration Manual page 205

Cisco ios xe everest 16.6.x
Hide thumbs Also See for Catalyst 9500 series:
Table of Contents

Advertisement

Configuring IP Unicast Routing
• Web Cache Communication Protocol (WCCP) and PBR are mutually exclusive on a switch interface.
You cannot enable WCCP when PBR is enabled on an interface. The reverse is also true, you cannot
enable PBR when WCCP is enabled on an interface.
• The number of hardware entries used by PBR depends on the route map itself, the ACLs used, and the
order of the ACLs and route-map entries.
• PBR based on TOS, DSCP and IP Precedence are not supported.
• Set interface, set default next-hop and set default interface are not supported.
• ip next-hop recursive and ip next-hop verify availability features are not available and the next-hop
should be directly connected.
• Policy-maps with no set actions are supported. Matching packets are routed normally.
• Policy-maps with no match clauses are supported. Set actions are applied to all packets.
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. 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.
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.
Procedure
Step 1
Step 2
Step 3
Command or Action
configure terminal
Example:
Device# configure terminal
route-map map-tag [permit]
[sequence number]
Example:
Device(config)# route-map pbr-map
permit
match ip address {access-list-number
| access-list-name} [access-list-number
|...access-list-name]
Routing Configuration Guide, Cisco IOS XE Everest 16.6.x (Catalyst 9500 Switches)
Purpose
Enters global configuration mode.
Defines route maps that are used to control where packets
are output, and enters route-map configuration mode.
• map-tag — A meaningful name for the route map.
The ip policy route-map interface configuration
command uses this name to reference the route map.
Multiple route-map statements with the same map
tag define a single route map.
• (Optional) permit — If permit is specified and the
match criteria are met for this route map, the route
is policy routed as defined by the set actions.
• (Optional) sequence number — The sequence
number shows the position of the route-map
statement in the given route map.
Matches the source and destination IP addresses that are
permitted by one or more standard or extended access
lists. ACLs can match on more than one source and
destination IP address.
Policy-Based Routing
195

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents