Before implementing MCT in your network, the following table provides a list of MCT terminology and their definitions.
| MCT peer devices | A pair of SLX-OS device configured as peers. The LAG
interface is spread across two MCT peer devices and acts as the single
logical endpoint to the MCT client. Note: MCT is supported
across the same chassis type only; for example, SLX-9540 <--->
SLX-9540.
|
| MCT Cluster Client | The MCT Cluster Client is the device that connects with the MCT peer devices. It can be a switch or an endpoint server host in the single-level MCT topology, or another pair of MCT switches in a multi-tier MCT topology. |
| MCT Cluster Control Protocol | The control plane for Layer 2 MCT on the SLX-OS device. |
| MCT Cluster Client Edge Port (CCEP) | Ports connected to the dual-homed clients. CCEP Ports could be a LAG or a physical port. |
| MCT Cluster Edge Port (CEP) | Orphan or edge ports connected to one of the MCT nodes. |
| Inter-Chassis Link (ICL) | Inter-Chassis Link which connects two MCT nodes. For SLX-OS devices, the ICL is a VxLAN tunnel created between the MCT peer that forms the data path. |
| MCT VLANs | VLANs that are shared by the MCT peers. These VLANs are explicitly configured in the MCT configuration. |
| Designated Forwarder (DF) | MCT node that is elected to send BUM traffic to a tunnel client for particular VLAN or BD. |