The Multi-Vendor Networking Forum and Resources
Brocade Configure Multi Chassis Trunking (MCT)



Multi Chassis Trunking (MCT) is a technology that allows a server (Or Switch) to connect to two switches using LACP and the two switches look like a single switch to the server. This allows the server to use both connections to transmit twice as much data. The server doesn't know it's two switches and simply thinks that it has a LACP connect to a single switch.

The two Brocade switches work independently and are managed independently. This methodology is similar to Cisco's Nexus Virtual Port Channel (VPC).

HP and Cisco Catalyst 6500's VSS are doing this a bit different. They have the two switches work as on for everything including management.

When you setup any form of MCT or VPC, etc..   You have to be careful on how you configure the switches, along with your design. When the inter cluster link between the two switches fail, one of the switches may drop all of the ports on it. This could cause a major outage if it's not configured correctly or your network design isn't setup for this to happen. It could take down single connected servers. I recommend installing another switch for the single connected servers so an inter cluster link failture will not affect those servers.

Make sure you read about the affects of link failures on the platform that you are using.

Configure MCT to a client

1  Create lag on each switch

2  Apply appropriate vlan to Client interface and ICL

3  Apply appropriate vlan to cluster configuration



For this example

Switch cross connect (Inter Cluster Link ICL) = ethernet 5/1 & 6/1
Ports used for server access = 2/7

-----------------
Switch #1
-----------------

lag "XConnect" dynamic id 1
 ports ethernet 5/1 ethernet 6/1
 primary-port 5/1
 deploy
 port-name "<PORT DESCRIPTION>" ethernet 5/1
 port-name "<PORT DESCRIPTION>" ethernet 6/1

Vlan 2 name server-access
    tagged eth 2/7
    tagged eth 5/1
   
Vlan 10 name session-vlan
    tagged eth 5/1
    router- ve 10
vlan 11 name Keep-alive-vlan
    tagged eth 5/1

interface ve 10
   ip address 192.168.1.1/30

   
lag "SERVER-NAME" dynamic id 3    ==> id needs to be unique for each server
 ports ethernet 2/7
 primary-port 2/7
 lacp-timeout long                                               
 deploy
 port-name "SERVER-NAME-PORT" ethernet 2/7
 
cluster <CLUSTER-NAME> 1
 rbridge-id 1
 session-vlan 10
 keep-alive-vlan 11
 member-vlan 2
 icl <CLUSTER-NAME> ethernet 5/1
 peer 192.168.1.2 rbridge-id 2 icl <CLUSTER-NAME>
             - This is the IP and rbridge of the other switch
 deploy
client <CLIENT-NAME>
  rbridge-id 5                                                                    - This needs to be a unique rbridge ID on this switch
  client-interface ethernet 2/7
  deploy



-----------------
  Switch #2
-----------------


lag "XConnect" dynamic id 1
 ports ethernet 5/1 ethernet 6/1
 primary-port 5/1
 deploy
 port-name "<PORT DESCRIPTION>" ethernet 5/1
 port-name "<PORT DESCRIPTION>" ethernet 6/1
 
Vlan 2 name server-access
    tagged eth 2/7
    tagged eth 5/1
   
Vlan 10 name session-vlan
    tagged eth 5/1
    router- ve 10
vlan 11 name Keep-alive-vlan
    tagged eth 5/1

interface ve 10
   ip address 192.168.1.2/30

lag "SERVER-NAME" dynamic id 3    ==> id needs to be unique for each server
 ports ethernet 2/7
 primary-port 2/7
 lacp-timeout long                                               
 deploy
 port-name "SERVER-NAME-PORT" ethernet 2/7
 
cluster <CLUSTER-NAME> 1
 rbridge-id 2
 session-vlan 10
 keep-alive-vlan 11
 member-vlan 2
 icl <CLUSTER-NAME> ethernet 5/1
 peer 192.168.1.1 rbridge-id 1 icl <CLUSTER-NAME>             - This is the IP and rbridge of the other switch
 deploy
client <CLIENT-NAME>
  rbridge-id 5
                                                                    - This needs to be a unique rbridge ID on this switch
  client-interface ethernet 2/7
  deploy
 
If you would like to add any comments or suggestions about this config please comment on Scape's Forum. I look forward to your response.

-----------------
  Notes
-----------------

It is suggested to use another port to cross connect the switches for the Keep Alive Vlan, I suggest a slow speed port instead of a 10G port
Make sure you read the configuration guide to make sure this is setup to correctly meet the needs of your network.



If you found this helpful, help me by checking out the advertisement below. Thank you!