LACP LAGs

Connect can create sub-interfaces using LAGs. To do this, a HostPort must have its isLag attribute set to true.

SubHostPorts (other HostPorts that are part of the LAG) must also be created for each member of the Bond on compute. This is indicated by setting a HostPort's ParentHostPortID field to the ID of the LAG HostPort.

Before associating a LAG-enabled HostPort to a HostPortLabel, make sure that the LAG exists on the Fabric Services System fabric and that its members map to the SubHostPorts in Connect.

If a LAG mapping to the ParentHostPort and its SubHostPort members are not found on the fabric, or if the SubHostPorts are scattered across multiple LAGs on the fabric, Connect will raise an alarm.

Note: This section only applies to LACP LAGs (Active/Active). Linux mode-1 bonds (Active/Standby) are not yet supported. In the future, these Active/Standby lags should not be created as LAGs on the fabric.