Link Aggregation | 167LAG Implementation RestrictionsInterface restrictions:• All of the physical links of a LAG must run in full-duplex mode at the same speed. Set the speed andmode of a port to that of the LAG before adding the port to the LAG.• LAG speed may not be changed.• Routing is not supported on links in a LAG.• An interface can belong to only one LAG.• SFTOS supports 48 LAGs, with a maximum of eight members each.SFTOS supports IEEE 802.3 Clause 43 with minor exceptions:• No optional features supported, e.g. Marker Generator/Receiver• MUX machine implemented as coupled, not independent control• Some MIB variables are not supported.Link Aggregation—MIB SupportThe IEEE 802.3 Annex 30c MIB objects that are not supported are:• dot3adAggPortDebugTable• dot3adAggPortStatsMarkerResponsePDUsRx• dot3adAggPortStatsMarkerPDUsTx• dot3adAggPortActorAdminSystemPriority• dot3adAggPortActorOperSystemPriority• dot3adAggPortPartnerAdminSystemPriority• dot3adAggPortPartnerOperSystemPriority• dot3adTablesLastChangedStatic LAG RequirementsManual aggregation is disabled by default, and when enabled, applies to all LAG interfaces. Manualaggregation uses the following default values:• If an LACP PDU (Link Aggregation Control Protocol Protocol Data Unit) is received with differentvalues, the link will drop out.• When all member links have dropped out, the group will re-aggregate with the new information.If the partner does not respond with LACP PDUs, the system will wait three seconds and aggregatemanually.The static LAG configuration should only be enabled if both parties are 802.3ad-compliant and have theprotocol enabled.LAGs should be configured and STP-enabled on both devices before connecting cables.
