[HCI-VN] How to switch storage ports from single/Link Aggregation with Two Switches to standard link aggregation when upgrading from versions prior to 670 to versions 670 and later
Problem Description
After upgrading from a lower version to version 670 or later, the storage switches to standard link aggregation
Solution
- After upgrading from a lower version to 670, you need to switch to standard link aggregation. You need to shut down all virtual machines first and then Reset the storage network. Change to Link Aggregation Disabled, cut the storage port to an idle single network port, and free up the original two storage ports.
If there is no free network port available, contact VS technical support, clean up the storage port configuration in the background first and then follow the subsequent steps


- Group the original two VS ports into aggregate aggregate interface. The aggregation mode is recommended to use LACP-Layer 4 information load. If the switch does not support LACP, static aggregation-Layer 4 information load is recommended. If the switch does not support Layer 4 information load, it is not recommended to switch to standard link aggregation. It is recommended to continue using the original mode.
**Note: If you do not need to reuse the storage port with other role (business, vxlan) ports, do not check **


- After Node side creates the aggregate interface port, the switch side also creates the aggregation configuration synchronously. Note that it must be consistent with Node side. If Node side uses LACP, the switch side must also configure LACP. If Node side uses static aggregation, the switch side must also use static aggregation. The load mode must select the four-layer information load (source and destination IP + port). Otherwise, the network will be unavailable and the storage port cannot be configured successfully.
- After ensuring that Node and switch side configurations are successful, Reset the storage network to select standard link aggregation, then select the aggregate interface just created, and click Next to submit the configuration.


Scope of Operation Impact
All virtual machine changes must be shut down, no other solution
Is this a temporary solution?
Disabled
Suggestions and Summary
The reason why storage must use four-layer information load is: there will be a problem of load imbalance based on the source and destination IP or source and destination MAC. Because the IP and MAC of the storage port are fixed groups, there is a high probability that all traffic will be loaded onto one network port. This is a defect in the HASH algorithm of standard link aggregation itself, not a problem with the product itself. This problem exists on both the Node side and the switch side, so it is necessary to use four-layer information load (because the four-layer information load includes the port, and each time a TCP connection is established, the client port is random) to reduce the probability of load imbalance. If you cannot use four-layer information load and can accept the problem of load imbalance, you can also use IP or MAC load, otherwise do not switch to standard link aggregation.

Original Link
https://support.sangfor.com.cn/cases/list?product_id=33&type=1&category_id=27376&isOpen=true