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

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 793
53-1003031-02
Feature overview
8
BUT the following unique mac addresses /unique VLANs are working:
IXIA P1: SMAC = 00-00-00-03-01-xx where xx = 1, 2, 3, 4, 5, 6, 7, 8
VLAN = 10yy
where yy = 10, 11, 12, 13, 14, 15, 16, 17
IXIA P2: SMAC = 00-00-00-03-02-xx where xx = 1, 2, 3, 4, 5, 6, 7, 8
VLAN = 10yy
where yy = 10, 11, 12, 13, 14, 15, 16, 17
or
IXIA P1: SMAC = 00-00-00-03-12-xx where xx = 1, 2, 3, 4, 5, 6, 7, 8
VLAN = 10yy
where yy = 10, 11, 12, 13, 14, 15, 16, 17
IXIA P2: SMAC = 00-00-00-03-13-xx where xx = 1, 2, 3, 4, 5, 6, 7, 8
VLAN = 10yy
where yy = 10, 11, 12, 13, 14, 15, 16, 17
Existing features affected by this feature
Prior to NetIron Release R05.600, VPLS LSP load balancing is done with maximum 4 LSPs. This is
increased to eight LSPs after this feature.
In CES/CER, you would be able to assign up to 8 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. No preferences over a particular type of tunnels
dependencies.
VPLS LSP load balancing configuration scenarios
Load balance with dynamic LSP selection
Configuration in Ingress router
Brocade(config)# router mpls
Brocade(config-mpls)# policy
Brocade(config-mpls-policy)# cspf-interface-constraint
Brocade(config-mpls)# path ve100
Brocade(config-mpls-path-ve100)# strict 10.19.2.3