Brocade BigIron RX Series Configuration Guide - Manual (Page 609)

BigIron RX Series Configuration Guide 531
53-1002484-04
Configuring MCT
20
• Hitless upgrade. If the operation is performed with the cluster configuration, the TCP session is
re-established. The MAC entries from the cluster peers are revalidated and programmed
accordingly.
Brocade recommends shutting down all the CCEPs on the cluster node so that there is graceful
upgrade and hitless operation can be performed.
Configuring MCT
Perform the following procedures to configure a single-level MCT scenario as shown in Figure 93 .
1. Create and deploy a LAG that is used as an ICL.
2. Create and deploy the LAGs facing the clients.
3. Enable Layer 2 switching either globally or on specific interfaces.
4. Create and add ports to a client VLAN or member VLAN for communication.
a. At the CCEP or CEP, the ports can be tagged or untagged to the VLAN.
b. At the ICL, the ports can only be tagged to the VLAN. The ICL ports cannot be untagged to
any VLAN.
5. For CCP communication, create a dedicated session VLAN for the ICL interfaces and tag the
ICL ports into the session VLAN. Brocade recommends using a high VLAN number for the
session VLAN.
6. Create a virtual routing interface and associate the interface with the session VLAN to address
the link between the MCT peers.
7. Configure the MCT cluster.
a. Create a cluster with any name but with a matching cluster ID as that of the MCT peer.
b. Configure a unique RBridge ID for the MCT peer. The RBridge ID must be unique across all
the MCT peers and CCEPs.
c. Configure the session VLAN for the cluster.
d. Configure one or more client or member VLANs for the cluster.
e. Configure ICL ports or a LAG to be used for the cluster.
f. Configure the MCT peer for the cluster.
g. Deploy the cluster. All attributes except for the client or member VLANs cannot be changed
after the cluster is deployed.
8. Configure the MCT cluster client instances.
Configuration considerations
The following are the configuration considerations for MCT:
• The ICL ports must not be an untagged member of any VLAN. An ICL is preferably a LAG that
provides port level redundancy and higher bandwidth for cluster communication.
• The ICL ports can be configured only on 10 GbE ports.