Configuration Guide User guide

840 FastIron Configuration Guide
53-1002494-02
Basic MCT configuration
22
To implicitly configure the session VLAN and add the ICL as a tagged member of the VLAN, enter
the following commands.
Brocade-1(config)#vlan 1000 name MCT-VLAN-example
Brocade-1(config-vlan-1000)#tagged ether 1/4 to 1/5 e 1/7 to 1/8
Step 3: Configure the cluster
Cluster local configuration uses the cluster ID and RBridgeID for the local switch or router.
Syntax: [no] cluster [<cluster-name>] <cluster-id>
Syntax: [no] rbridge-id <id>
Configuration of the peer device involves the peer's IP address, RBridgeID, and ICL specification.
The <cluster-name> variable is optional; the device auto-generates the cluster name as CLUSTER-X
when only the cluster ID is specified. The <cluster-id> variable must be the same on both cluster
devices.
Syntax: [no] peer <peer-ip> rbridge-id <peer-rbridge> icl <map-icl>
The RBridgeID must be different from the cluster RBridge and any other client in the cluster. The
MCT member VLAN is defined as any VLAN of which the ICL is a member.
To configure Brocade-1 for the cluster in the Figure 101 topology, enter the following commands.
Brocade-1(config)#cluster SX 4000
Brocade-1(config-cluster-SX)#rbridge-id 3
Brocade-1(config-cluster-SX)#session-vlan 3000
Brocade-1(config-cluster-SX)#keep-alive-vlan 3001
Brocade-1(config-cluster-SX)#icl SX-MCT ethernet 1/7
Brocade-1(config-cluster-SX)#peer 1.1.1.2 rbridge-id 2 icl SX-MCT
Brocade-1(config-cluster-SX)#deploy
To configure Brocade-2 for the cluster in the Figure 101 topology, enter the following commands.
Brocade-2(config)# cluster SX 4000
Brocade-2(config-cluster-SX)#rbridge-id 2
Brocade-2(config-cluster-SX)#session-vlan 3000
Brocade-2(config-cluster-SX)#keep-alive-vlan 3001
Brocade-2(config-cluster-SX)#icl SX-MCT ethernet 2/5
Brocade-2(config-cluster-SX)#peer 1.1.1.3 rbridge-id 3 icl SX-MCT
Brocade-2(config-cluster-SX)#deploy
Step 4: Configure clients
This section describes how to configure clients manually. For instructions on automatic client
configuration, refer to “Setting up cluster client automatic configuration” on page 841.
Client configuration requires the client name, RBridgeID, and CCEP. In the network shown in
Figure 101, Client-1 has a three-port LACP trunk (1/1-1/3), while Client-2 has a two-port static
trunk (1/1-1/2) towards the MCT cluster.
The client name can be different on the different cluster devices. To configure the client name,
enter the following command.
Syntax: [no] client <client-name>