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

470 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
VPLS LSP load balancing
3
NOTE
To disable the LSP load balancing, the user must delete the VPLS peer with the no vpls-peer
command, then re-enter the vpls-peer command without the load-balance option.
In the prior example, when the load-balance option is specified, VPLS traffic originating from the
device and sent to peer 192.168.0.0 is load balanced across eligible tunnel LSPs whose
destination is the peer.
VPLS LSP load balancing
TABLE 71
Term Meaning
MAC Media Access Control
LSP Label Switched Path
VPLS Virtual Private LAN Service
VPLS LSP load balancing terms
This functional specification documents the VPLS LSP load balancing which is to be incremented
from four LSPs to eight LSPs in the NetIron R05.600 for the XMR/MLX product lines.
Limitations and prerequisites
The hashing technique to load balance is not consistent. This is an existing limitation.
Existing feature affected by this feature
Prior to Multi-Service NetIron Release 05.600, VPLS LSP load balancing is done with maximum
four LSPs. This is increased to eight LSPs after this feature.
In CES/CER, you would be able to assign up to eight LSP to a VPLS peer but at any time only one of
them is chosen for all traffic forwarding for this VPLS peer because load balancing is not supported
in CES/CER.
Assumptions and dependencies
The hashing decision has not changed for this feature support. It is based on the fields in each
packet received.
VPLS can use both LDP and RSVP tunnels for load balancing as long as they all matched the COS
criteria.
A tunnel reachable to a peer with the right COS value is all that is required to be used as a
candidate for VPLS tunnel load balancing. There are no preferences over a particular type of tunnel
dependencies.