Configuration Guide User guide
838 FastIron Configuration Guide
53-1002494-02
Basic MCT configuration
22
• An ICL cannot be an LACP trunk (must be either a static trunk or single port).
• MAC learning is disabled on ICL ports for all VLANs.
• MDUP synchronizes all MAC entries for VLANs served by an ICL link.
• The cluster ID should be same on both cluster devices.
• The cluster RBridgeID should not conflict with any client RBridgeID or the peer RBridgeID.
• The client RBridgeID is unique and should be the same on the cluster devices.
• Brocade recommends keeping only ICL ports in the session VLAN during operation.
• MCT can support up to 12 members per trunk group.
• An ICL interface cannot be configured as the CCEP in any client.
• BPDU guard and root guard configuration should be identical on both cluster devices.
• As Egress PCL is configured on CCEPs, Egress ACL cannot be configured on them. All types of
ingress ACLs, DDOS attacks, and so on can still be configured on those ports.
• Brocade recommends that you configure a keep-alive VLAN as a separate link (not ICL). The
keep-alive VLAN provides a backup control path when CCP goes down.
Differences in configuring MCT for the switch and router image
There are some differences in the MCT configuration for the switch image versus the router image:
• On a switch image, STP is by default enabled for all the VLANs; however, for MCT, Layer 2
protocols such as STP and RSTP should not be enabled on the session VLAN. Therefore, STP
must be disabled explicitly for the session VLAN. STP is automatically disabled in the router
image.
• Virtual Ethernet (VE) cannot be configured on a session VLAN in a switch image, but an IP
address is needed for the cluster devices to communicate via CCP. Therefore, in a switch
image, the configured management IP address is used to establish communication between
the cluster devices.
• The management IP addresses should be configured in each of the cluster devices in the same
subnet. If the IP addresses are in different subnets, ARP does not resolve the addresses and
MCT may not work. The ARP for the peer cluster devices is always learned on the ICL port or
trunk, so any management traffic between the two devices will always go through the ICL ports.
Configuring MCT
This section provides basic configuration steps, which should be completed in the specified order.
Step 1: Configure trunks (if needed)
Step 2: Configure the session VLAN and recommended keep-alive VLAN
Step 3: Configure the cluster
Step 4: Configure clients
After completing these steps, you can verify the configuration by running the show cluster
command. Refer to “Displaying peer and client states” on page 860.