Two-Level MCT Configuration Example

The following figure depicts a two-level MCT configuration. The clients can be server hosts or networking devices. The associated configuration follows.
Note: The LAG IDs are locally significant only and need not be matching on the two ends of a LAG.
Figure 1. Two-Level MCT Configuration
Note: In a two-level MCT configuration using dynamic LAGs, ensure that the upper and lower clusters have different Cluster IDs because the Cluster LACP module uses the Cluster ID as part of the LACPDU system ID.

The client configuration is the same as in the single-level example (refer to Single-Level MCT Configuration Example).