MCT Terminology
| Term | Description |
|---|---|
| Cluster Client Edge Port (CCEP) | A physical port or trunk group interface on an MCT cluster device that is connected to client devices. |
| Cluster Edge Port (CEP) | A port on an MCT cluster device that belongs to the MCT VLAN and connects to an upstream core switch or router but is neither a CCEP nor an ICL. |
| Cluster Communication Protocol (CCP) | A proprietary protocol that provides reliable, point-to-point transport to synchronize information between MCT cluster devices. It provides the default MCT control path between the two peer devices. CCP comprises two main components: CCP peer management and CCP client management. |
| Inter-Chassis Link (ICL) | A single-port or multiport 1-GbE, 10-GbE, or 40-GbE LAG between the two MCT cluster devices. It provides the control path for CCP for the cluster and also serves as the data path between the two devices. |
| MCT cluster | A pair of devices (standalone switches or stacks) that are clustered together using MCT to appear as a single logical device. The devices are connected as peers through an Inter-Chassis Link (ICL). |
| MCT cluster client | A device that connects with MCT cluster devices through static or dynamic trunks. It can be a switch or an endpoint server host in the single-level MCT topology or another pair of MCT devices in a multi-tier MCT topology. |
| MCT cluster device | One of the two devices (or stacks) in an MCT cluster. |
| MCT peer device | From the perspective of an MCT cluster device, the other device (or stack) in the MCT cluster. |
| MCT VLANs | VLANs on which MCT cluster clients are operating. Any VLAN that has an ICL port is an MCT VLAN, even if it does not have any clients. |
| MCT keep-alive VLAN | The VLAN that provides a backup control path if the ICL goes down. |
| MCT session VLANs | The VLAN used by the MCT cluster for control operations. CCP runs over this VLAN. The interface can be a single link or a LAG. In a LAG, it must be configured on the LAG virtual interface. The MCT session VLAN subnet is not distributed in routing protocols using redistribute commands. |
| RBridge ID | An RBridge ID is a value assigned to MCT cluster devices and clients that uniquely identifies them and helps associate the source MAC address with an MCT device. |
| Keep-alive timer | A keep-alive timer monitors the peer devices in a cluster. The keep-alive timer ensures that the devices in the MCT cluster are functioning correctly and can communicate with each other. |
| Hold time | Hold time is the duration for which a device maintains its current state before making any changes in response to a detected failure or change in the network. This delay can help prevent unnecessary or premature changes that could disrupt network stability. |