Configuring a single-level mct topology – Brocade BigIron RX Series Configuration Guide User Manual

Page 610

Advertising
background image

532

BigIron RX Series Configuration Guide

53-1002484-04

Configuring MCT

20

On the BigIron RX devices, the ICL ports can be a part of only MCT member VLANs and not
regular VLANs.

The BigIron RX devices disable MAC learning on the ICL ports for the VLANs configured in the
cluster.

MDUP synchronizes all the MAC entries for the VLANs served by the ICL link.

On the CCEP, MCT does not support multicast and routing protocols.

The Cluster ID must be the same on both the cluster switches.

The Cluster RBridge ID must not conflict with any client RBridge ID or the peer RBridge ID.

The Client RBridge ID is unique and must be the same on the cluster switches.

You can add any ports to the session VLAN, but Brocade recommends keeping only the ICL
ports during the operation.

MCT clients can support eight ports per LAG.

An ICL interface cannot be configured as the CCEP in any client.

CCEPs cannot be configured as an ICL interface.

CCEPs on an MCT node can be a single port or a LAG.

If an ICL or a client interface must be configured as a LAG interface, then only the primary port
of the LAG must be specified in the ICL or the client configuration.

After the cluster is deployed, only the cluster member VLANs and client isolation mode can be
modified. Other configurations cannot be changed.

After the client is deployed, any client configuration cannot be changed.

Clients can be added or deleted even if the cluster is deployed.

When the cluster is undeployed, all the clients in the cluster become inactive.

When a port is configured as an ICL port, the port cannot be removed from the default VLAN.

If an ICL or CCEP is a LAG interface, the LAG must be configured separately on each node.

On the BigIron RX devices, the 16x10 board which is used for an ICL interface must not be
oversubscribed to avoid risk of data packet loss when the data traffic is crossing the ICL.

In addition to the LAG for the ICL, 30 more LAGs can be supported on the BigIron RX device.

Dual MCT is not supported in the 02.9.00 release.

Configuring a single-level MCT topology

Figure 93

shows the single-level MCT topology. The topology consists of two MCT peer switches.

Top of Rack A (TOR-A) and TOR-B are connected through an ICL, which is a single-port or multi-port
10 GbE interface. The two MCT peer switches act as a single logical switch with the access
switches or servers called MCT clients (Client #1 and Client #2) connected through IEEE 802.3ad
links (LAG 2 and LAG 3) across the MCT pair.

Advertising