Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 703)

Multi-Service IronWare Switching Configuration Guide 673
53-1003036-02
MCT for VPLS
18
• Local-switching enable or disable
• VPLS MAC table size
For each VPLS instance which has a MCT end-point, the MCT peer node is configured as a special
VPLS peer. This is done on both MCT nodes. This is referred to as the cluster-peer and the PW
between them is called the MCT Spoke PW.
One of the nodes from MCT pair is picked as active. This can be done either globally or controlled
per VPLS instance.
Active MCT node will establish the PW session with the remote PE’s and signal this active status in
the status TLV.
MP switchover and Hitless OS upgrade is not supported but compatible.
NetIron CES and NetIron CER limitations
Consider the following limitations for the NetIron CES and NetIron CER devices
• LSP of VPLS VC cannot run over ICL port.
• Spoke VC & other normal VC cannot share same port when local switching is disabled
• As the MCT vpls uses twice the number of MACs in hardware, the system max mac shall be
reduced to half when all the vpls instances in the node are MCT enabled.
Forwarding known unicast traffic
On Active MCT PE node, traffic will be forwarded and received from all the remote PE’s.
For a host which is single homed to standby MCT PE node, the Active MCT PE node will send the
packet on the MCT Spoke PW to standby MCT PE node.
On standby MCT PE node, traffic received from local CCEP and CEP ports will be forwarded to Active
MCT PE node through the MCT Spoke PW which will then forward to the remote PE’s.
On standby, the MCT PE node traffic received from all other PE nodes except the MCT Spoke PW is
dropped.
Forwarding broadcast, unknown unicast, multicast traffic
Known unicast packets will be forwarded based on where the destination MAC is learned
(Exception to Packets received on MCT Spoke PW and destined to CCEP) but for BUM traffic it will
forwarded to all the destinations listed below.
On the active MCT PE Node
• Traffic received from CE’s is forwarded to all Remote PE’s, MCT Spoke PW and locally
connected CE’s.
• Traffic received from all Remote PE nodes (which doesn’t include the MCT Spoke PW) is sent to
all CE’s and a copy is sent to MCT Spoke PW.
• Traffic received from the MCT Spoke PW, is sent to all the Remote PE’s and locally connected
CE’s which are single-homed.