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

680 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
MCT for VLL
18
• There is a VLL instance mct-spoke-pw established between MCT pair for sending data traffic
from standby to active node from the customer edge nodes(CE1, CE2).
• MCT cluster pair nodes communicate to each other using CCP communication provided by MCT
infrastructure to identify as cluster pairs based on per instance and negotiate active/standby
roles.
• For cluster pair PE1 and PE2, traffic from CE1 to CE2 flows as follows.
• The traffic received directly from CE1 to PE1 is sent over the active PW PW3 to node PE4
which forwards it to client CE2.
• The traffic received directly from CE1 to PE2 is sent over the MCT-SPOKE-PW to PE1. PE1
forwards this traffic over the active PW PW3 to node PE4 which forwards it to client CE2.
• For cluster pair PE1 and PE2, traffic from CE2 to CE1 flows as follows:
• Traffic is received on the active PW for the pair PW3 on node PE1. Node PE1 forwards the
traffic to CE1 directly over the local endpoint.
• Traffic forwarded to PE2 in special case (where PE1 is Active but local CCEP is down)
.
FIGURE 184 Sample topology with MCT end-points for VLL
Configuration synchronization between MCT peers
MCT peers will exchange VLL information and updates.
VLL information sync
VLL addition and deletion information will be sent to MCT peer in the below scenarios.
• Whenever End Point (CCEP for MCT Client) and at least one VLL peer is configured, the VLL
related information will sync to MCT peer. The MCT peer will add received VLL information to
separate data structure (different from normal VLL structure).
• Whenever End Point (CCEP for MCT Client) or last VLL Peer are deleted then we will send
message to MCT Peer to delete that VLL information.