Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) User Manual
Page 788
760
Multi-Service IronWare Routing Configuration Guide
53-1003033-02
Configuration considerations
•
IPv6 PBR policies are not supported on Layer 3 VPNs.
•
IPv6 PBR is applied to routed traffic only by default, except when the flood VLAN option is
enabled.
•
IPv6 PBR can only be configured on physical ports, Link Aggregation Groups (LAG) ports, and
Virtual Ethernet (VEs).
•
If IPv6 PBR is applied on a VE, it works only when the VE is enabled. When the VE is disabled,
IPv6 PBR will not work and normal routing or switching takes place for the traffic received on
the VE.
•
The following combinations of IPv6 PBR and IPv4 PBR and IPv6 ACL and IPv4 ACL are allowed:
•
IPv6 PBR and IPv4 PBR can be applied to the same interface at the same time.
•
IPv6 PBR and IPv4 ACL can be applied to the same interface at the same time.
•
IPv4 PBR and IPv6 ACL can be applied to the same interface at the same time.
•
IPv6 ACL-based rate limiting is not supported on Brocade MLX Series and Brocade NetIron XMR
devices.
•
You cannot apply IPv6 PBR on a port if that port already has inbound IPv6 ACLs.
•
IPv6 PBR only supports IPv6 as the next hop and IPv6 PBR to VLAN flooding.
•
IPv6 PBR does not support IPv6 PBR to GRE and IPv6 PBR to MPLS.
•
The number of route maps that can be defined is limited by the system memory. When a route
map is used in an IPv6 PBR policy, the IPv6 PBR policy uses up to 64 instances of a route map,
up to 5 ACLs in a matching policy of each route map instance.
The following two conditions can cause more than 64 route map instances to be used.
1. If one or more of the first 64 instances has a deny clause.
2. If the access list used in the first 64 instances is not configured.
•
ACLs with the log option configured should not be used for IPv6 PBR purposes.
•
IPv6 PBR ignores implicit deny ip any any ACL entries to ensure that traffic is compared to all
the ACLs for route maps that use multiple ACLs. However, if an explicit deny ip any any entry is
configured, traffic matching this clause will be routed normally using Layer 3 paths and will not
be compared to any ACL clauses that follow this clause.
•
IPv6 PBR always selects the first next hop from the next hop list that is up. If an IPv6 PBR
policy's next hop goes down, the policy uses another next hop if available. If no next hops are
available, the device routes the traffic in the normal way. No IPv6 ECMP is supported.
•
Any changes to route map definitions will be effective immediately for the interfaces where the
IPv6 PBR route map is applied, without rebinding. However, rebinding is required for an ACL
definition change to take effect.
•
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.