Active-passive mct, Configure active-passive mct, Active-passive mct configuration considerations – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual
Page 633
Multi-Service IronWare Switching Configuration Guide
603
53-1003036-02
About Multi-Chassis Trunk (MCT)
18
c. Configure the session VLAN for the cluster.
d. Configure one or more client/member VLANs for the cluster.
e. Configure the ICL port or LAG being used for the cluster.
f.
Configure the MCT peer for this cluster.
g. Deploy the cluster. All attributes except for client or member VLANs cannot be changed
after the cluster is deployed.
h. Configure the MCT cluster client instances.
Active-Passive MCT
Active-Passive MCT configuration considerations
•
To enable MCT Active-Passive mode, both the MCT nodes must be configured as
Active-Passive. If only one node is configured, then cluster CCP session will not come up.
•
Active-Passive mode is supported for the following combinations.
-
L2VPN MCT configured.
-
L2 + L2VPN MCT configured.
•
Active-Passive mode does not support L2 MCT.
•
VLL and VPLS are supported over L2VPN MCT.
•
Node where the Pseudo Wire’s are Active must be configured as the MCT Active node .
•
The CCEP ports must be part of dynamic LAG. Active-Passive mode is not supported on static
LAG CCEP ports and single port CCEP.
•
CCEP ports elected under passive node will be made LACP-BLOCKED.
•
VLL PW’s role is based on the client role, the node under which the client ports are active the
PW’s will be active from that particular node towards the upstream.
•
When using VPLS, the Pseudo Wire’s role and the client role are independent, and is based on
the client role election based on the configuration.
Configure Active-Passive MCT
After configuring the basic steps are required to build an MCT scenerio, follow the steps below to
configure the MCT cluster.
Configure the MCT cluster.
1. Create a cluster with any name but with a matching cluster ID as the MCT peer.
2. Configure a unique RBridge ID for this peer. The RBridge ID must be unique across all MCT
peers and CCEPs.
3. Configure the session VLAN for the cluster.
4. Configure one or more client/member VLANs for the cluster.
5. Configure the LAG being used for the cluster.
6. Enable the Active/Passive mode
7. Configure the client role