Nokia routers support mixing ports of different speeds in a single LAG using either port-weight-speed or hash-weight. See section LAG port hash-weight for details related to LAG port hash-weight.
The LAG port-weight-speed command enables mixed-speed LAG and defines the lowest port speed for a member port in that LAG as well as the type of speed ports allowed when mixed in the same LAG:
port-weight-speed 1 supports port speed of 1GE and 10GE
port-weight-speed 10 supports port speed of 10GE, 40GE, and 100GE
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 proportionally to port-speed, unless explicitly configured not to do so (see internal-scheduler-weight-mode).
User data traffic is hashed proportionally to port speed when any per-flow hash is deployed.
CPM-originated OAM control traffic that requires per LAG hashing is hashed per physical port.
Nokia recommends that operators use weight-threshold or hash-weight-threshold instead of port-threshold to control the LAG operational status as port-threshold is unaware of the port speed. When 1GE and 10GE or 10GE, 40GE, and 100GE ports are mixed in the same LAG then the weight assigned to each port is respectively 1 and 10 or 1, 4, and 10 thereby allowing the operator to control the LAG threshold based on the effective port weight.
The weight-threshold or hash-weight-threshold commands can also be used for LAGs with all ports of equal speed to allow for a common operational model. For example, each port has a weight of 1 to mimic port-threshold and its related configuration.
Nokia recommends that operators use weight-based thresholds for other system configurations that react to operational change of LAG member ports, like MCAC (see use-lag-port-weight) and VRRP (see weight-down).
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.
Migrating a LAG to higher speed ports is done following the process below:
Turn on mixed-speed LAG using port-weight-speed
Add compatible higher speed ports to the LAG
Optionally use weight-threshold or hash-weight-threshold instead of port-threshold
Remove lower speed links
Turn off mixed-speed LAG using no port-weight-speed
Feature limitations in mixed-speed LAGs:
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
Not supported for ESM
The following ports or cards are not supported:
VSM ports
10/100 FE ports
ESAT ports
PXC ports
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