Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) - Manual (Page 359)

Multi-Service IronWare Routing Configuration Guide 331
53-1003033-02
Configuring a PBR policy
• If an IPv4 option packet matches a permit ACL filter with the option keyword, it is
hardware-forwarded based on its PBR next-hop (if available). If no PBR next-hop is available,
the packet is either software or hardware-forwarded (depending on whether ignore-options is
configured), based on an IP forwarding decision.
• Policy Based Routing (PBR) currently does not support the IPv4 and IPv6 features for changing
the MTU.
• Where the next hop is a GRE tunnel:
• Packets that are larger than the tunnel’s MTU are subject to IP fragmentation and PBR
processing of the fragmented packets.
• For route changes of the tunnel destination, the appropriate information is automatically
propagated to the PBR feature. Depending on the configuration of the route map, a route
change can change the active next hop of the PBR if it leads to the active next hop going
down which triggers a new next hop selection process.
• PBR route-map cannot be applied on VPLS, VLL, or VLL-Local endpoints and vice-versa.
• PBR policies are not supported on Layer-3 VPNs.
• In a PBR route-map definition, if even one route-map instance contains a “set
next-hop-flood-vlan” statement, all instances of that route-map will apply to both routed and
switched traffic.
• Flooding traffic to a POS interface is not allowed. It can only be flooded to Ethernet ports on the
VLAN, including the default VLAN.
• When an incoming port is POS then the SA of the outgoing flooded packets will be 0.
• IPv6 PBR to flood VLAN is not supported for switched traffic for the Brocade NetIron CES and
Brocade NetIron CER.
Configuring a PBR policy
To configure PBR, you define the policies using IP ACLs and route maps, then enable PBR globally
or on individual interfaces. The device programs the ACLs into the Layer 4 CAM on the interfaces
and routes traffic that matches the ACLs according to the instructions in the route maps.
To configure a PBR policy:
• Configure ACLs that contain the source IP addresses for the IP traffic you want to route using
PBR.
• Configure a route map that matches on the ACLs and sets the route information.
• Apply the route map to an interface.
Configure the route map
After you configure the ACLs, you can configure a PBR route map that matches based on the ACLs
and sets routing information in the IP traffic.
NOTE
The “match” and “set” statements described in this section are the only route-map statements
supported for PBR. Other route-map statements described in the documentation apply only to the
protocols with which they are described.