Combining ports of different speeds in the same LAG is supported by default and the operator does not need to use the port-weight-speed or a customized hash-weight values.
The operator can modify a LAG, in service, by adding or removing ports of different speeds. In cases where some, but not all, ports in a mixed-speed LAG have a hash-weight value configured, all LAG ports use the port-speed value.
The different combinations of physical port speeds supported in the same LAG are:
1GE and 10GE
10GE, 40GE, and 100GE
100GE and 400GE
For mixed-speed LAGs:
Both LACP and non-LACP configurations are supported. With LACP enabled, LACP is unaware of physical port differences.
QoS is distributed according to the internal-scheduler-weight-mode command. By default, the hash-weight value is taken into account.
User data traffic is hashed proportionally to the hash-weight value.
CPM-originated OAM control traffic that requires per LAG hashing is hashed per physical port.
When sub-groups are used, the following behavior should be noted for selection criteria:
highest-count
highest-count continues to operate on physical link counts. Therefore, a sub-group with lower speed links is selected even if its total bandwidth is lower. For example, a 4 * 10GE subgroup is selected over a 100GE + 10 GE sub-group).
highest-weight
highest-weight continues to operate on operator-configured priorities. Therefore, it is expected that configured weights take into account the proportional bandwidth difference between member ports to achieve the wanted behavior. For example, to favor sub-groups with higher bandwidth capacity but lower link count in a 10GE/100GE LAG, 100GE ports need to have their priority set to a value that is at least 10 times that of the 10GE ports priority value.
best-port
best-port continues to operate on operator-configured priorities. Therefore, it is expected that the configured weights take into account proportional bandwidth difference between member ports to achieve the wanted behavior.
Feature limitations in mixed-speed LAG:
PIM lag-usage-optimization is not supported and must not be configured
LAG member links must have the default configuration for config>port>ethernet>egress-rate/ingress-rate
No support for ESM
No support for LAG weight-threshold
LAN and WAN port combinations in the same LAG:
support for 100GE LAN with 10GE WAN
no support for 100GE LAN with both 10GE LAN and 10GE WAN
no support for mixed 10GE LAN and 10GE WAN
The following ports do not support a customized LAG port hash-weight value other than port-speed and are not supported in a mixed-speed LAG:
VSM ports
10/100 FE ports
ESAT ports
PXC ports