Custom Search

To advertise on this site email advertise@goatnetworking.com

How to configure MCT on a Brocade MLX?

Site Admin
User avatar
Posts: 368
Joined: Wed Jan 04, 2012 2:36 pm

How to configure MCT on a Brocade MLX?

Postby admin » Tue Jun 05, 2012 10:56 am

How to configure MCT (Multi-chassis Trunking) on a Brocade NetIron MLX switch

Configure MCT for client access
1 Create lag on each switch
2 Apply appropriate vlan to client interface and ICL interface
3 Apply appropriate vlan to cluster configuration

Switch cross connect = 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>
deploy
client <CLIENT-NAME>
rbridge-id 5
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>
deploy
client <CLIENT-NAME>
rbridge-id 5
client-interface ethernet 2/7
deploy

-----------------
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


Return to Brocade

Twitter Facebook

Who is online

Users browsing this forum: No registered users and 1 guest