Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) - Manual (Page 493)

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 469
53-1003031-02
LSP load balancing for VPLS traffic
3
• IPv4 TCP packets: Source MAC address and destination MAC address, source IP address and
destination IP address, and TCP source port and TCP destination port.
• IPv4 UDP packets: Source MAC address and destination MAC address, source IP address and
destination IP address, and UDP source port and UDP destination port.
• IPv6 non-TCP/UDP packets: Source MAC address and destination MAC address, source IP
address and destination IP address.
• IPv6 TCP packets: Source MAC address and destination MAC address, source IP address and
destination IP address, and TCP source port and TCP destination port.
• IPv6 UDP packets: Source MAC address and destination MAC address, source IP address and
destination IP address, and UDP source port and UDP destination port.
A tunnel LSPs eligibility for load balancing depends on whether CoS values are defined for the VPLS
instance and the tunnel LSP:
• When the VPLS instance does not have a CoS value defined, then all tunnel LSPs to the peer
are eligible for load balancing.
• When a VPLS instance has a CoS value defined, and at least one tunnel LSP to the peer has a
CoS value less than or equal to the VPLS instance CoS value, then all tunnel LSPs with the
highest CoS value less than or equal to the VPLS instance CoS value are eligible for load
balancing.
• When a VPLS instance has a CoS value defined, and none of the tunnel LSPs to the peer has a
CoS value less than or equal to the VPLS instance CoS value, then all tunnel LSPs to the peer
that do not have a CoS value are eligible for load balancing.
NOTE
The LSPs picked for load-balancing must have the same COS values. For example: When COS of
LSP1 = 4, LSP2 = 4, LSP3 = 2, LSP4 =2, LSP5 = 1 and VPLS instance COS = 3. Then traffic is load
balanced with LSP3 and LSP4 which has same COS values.
LSP load balancing
The device evenly distributes VPLS traffic across tunnel LSPs.
In early software releases, VPLS traffic was unevenly balanced across tunnel LSPs when exactly
three tunnels were used for load balancing. For example, for tunnels A, B, and C, VPLS traffic might
be distributed among the tunnels as follows: A: 50%, B: 25%, and C: 25%.
Now, the tunnels are fully utilized. Using the same example above, VPLS traffic might be distributed
among tunnels A, B, and C as follows: A: 33.3%, B: 33.3%, and C: 33.3%. These percentages are
based on a fully distributed hash index generated by the incoming traffic. Actual distribution
percentages may vary and are based on the hash index.
Configuring LSP load balancing for VPLS traffic
To configure a VPLS instance to load balance known unicast traffic sent to a VPLS peer across
multiple tunnel LSPs, enter a command such as the following.
Brocade(config-mpls-vpls-v1)# vpls-peer 192.168.0.0 load-balance
Syntax: [no] vpls-peer ip-addr [load-balance]