Specifying an lsp to reach a peer within a vpls, Lsp load balancing for vpls traffic – Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual
Page 492
![background image](/manuals/361646/492/background.png)
468
Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
LSP load balancing for VPLS traffic
3
Specifying an LSP to reach a peer within a VPLS
The user can specify the LSPs that can be used to reach a peer within a VPLS. The user can specify
up to four Resource ReSerVation Protocol (RSVP) LSPs per VPLS peer. VPLS subsequently selects
one of the LSPs configured to reach the specified peer. Any of the configured LSPs can be used,
and the order of configuration is not relevant to the selection of the LSP. When none of the
assigned LSPs is operational, the VPLS session with the peer is down. An LSP is considered down
when the LSPs primary, secondary, and detour paths are all down.
RSVP LSPs must be pre-configured prior to their assignment to the VPLS peer. Additionally, the
VPLS peer’s IP address must match the target IP address of any RSVP LSPs assigned to it. When
these addresses do not match, the configuration is rejected. An LSP that is assigned to any VPLS is
not allowed to be deleted from the configuration unless the VPLS LSP assignment is deleted first.
When no LSPs have been assigned to a VPLS peer, the existing mechanism is used to select an
appropriate LSP for the peer.
When LSP assignment is configured, ignore the configured COS of the LSP, and ignore the VPLS to
select an LSP for the VPLS peer. However, traffic sent on the LSP uses the CoS of the LSP. When
LSP load balancing is enabled for a VPLS peer, traffic is load-balanced on all assigned LSPs that
are operational.
To specify LSPs for a VPLS peer within a VPLS instance, enter a command such as the following.
Brocade(config-mpls-vpls-v1)# vpls-peer 192.168.0.0 lsp t1 t2 t3 t4
Syntax: vpls-peer ip-address lsp lsp1 [lsp2 / lsp3 / lsp4]
The ip-address variable specifies the IP address of the VPLS peer to which the user wants to assign
LSPs.
The lsp1 / lsp2 / lsp3 / lsp4 variables are the names of the LSPs that the user wants to assign to
the VPLS peer. The user can assign up to four LSPs to a peer using this command. When a VPLS
peer is not assigned any LSPs, the default mechanisms for selecting an LSP for the VPLS peer are
used.
LSP load balancing for VPLS traffic
In a VPLS instance, traffic from one VPLS peer to another is forwarded over an MPLS tunnel LSP.
When more than one tunnel LSP exists from the device to a VPLS peer, the device can select
multiple tunnel LSPs to forward VPLS traffic to the peer. Known unicast traffic is load-balanced
across the selected tunnel LSPs. Broadcast and unknown unicast traffic is always sent over a
single tunnel LSP, however.
For VPLS LSP load-balancing, select an LSP based on a hash-index which is calculated as follows:
NOTE
For VPLS traffic, source and destination MAC addresses come from the inner customer Ethernet
header.
•
Layer-2, non-IPv4, and IPv6 packets: Source MAC address and destination MAC address.
•
IPv4, non-TCP/UDP packets: Source MAC address and destination MAC address, source IP
address and destination IP address.