Policy-based routing, Policy-based routing (pbr), Configuration considerations – Brocade BigIron RX Series Configuration Guide User Manual
Page 723: Chapter 23, Policy-based, Routing
BigIron RX Series Configuration Guide
645
53-1002484-04
Chapter
23
Policy-Based Routing
In this chapter
•
•
•
•
•
Policy-Based Routing (PBR)
Policy-Based Routing (PBR) allows you to use ACLs and route maps to selectively modify and route
IP packets in hardware. The ACLs classify the traffic. Route maps that match on the ACLs set
routing attributes for the traffic.
A PBR policy specifies the next hop for traffic that matches the policy. Using standard ACLs with
PBR, you can route IP packets based on their source IP address. With extended ACLs, you can
route IP packets based on all of the clauses in the extended ACL.
You can configure the device to perform the following types of PBR based on a packet’s Layer 3 and
Layer 4 information:
•
Select the next-hop gateway.
•
Send the packet to the null interface (null0).
When a PBR policy has multiple next hops to a destination, PBR selects the first live next hop
specified in the policy that is up. If none of the policy's direct routes or next hops are available, the
packet is routed in the normal way.
Configuration considerations
•
A PBR policy on an interface takes precedence over a global PBR policy.
•
You cannot apply PBR on a port if that port already has ACLs, ACL-based rate limiting, or
TOS-based QoS.
•
The number of route maps that you can define is limited by the system memory. When a route
map is used in a PBR policy, the PBR policy uses up to 6 instances of a route map, up to 6 ACLs
in a matching policy of each route map instance, and up to 6 next hops in a set policy of each
route map instance.
•
ACLs with the log option configured should not be used for PBR purposes.