Limitations for Load Balance
Limitations for Load Balance on NE20E-S2E
Restrictions |
Guidelines |
Impact |
|---|---|---|
Fragmented and non-fragmented packets of the same flow are transmitted through different paths. The first fragment and subsequent fragments are transmitted through the same path. |
None |
The specification is restricted. |
Symmetric load balancing does not support trunk localization scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing does not support port extension scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing does not support E-Trunk scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing does not support inter-virtual cluster chassis trunk scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing does not support multicast scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing supports data traffic packets instead of protocol packets between two devices. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing does not support multi-level load balancing scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing does not support CE dual-homing scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
When the hash algorithm is set to random, symmetric load balancing does not take effect. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
For symmetric load balancing: 1. If the device connects to a non-Huawei device, upstream and downstream traffic may not be hashed to the same link due to different load balancing algorithms. 2. If the device connects to a Huawei device that does not support symmetric load balancing, upstream and downstream traffic may not be hashed to the same link. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing cannot work with MAC address- or label-based load balancing. |
Properly plan services. |
Upstream and downstream traffic may not be hashed to the same link. |
Limitations for Load Balance on NE20E-S2F
Restrictions |
Guidelines |
Impact |
|---|---|---|
Fragmented and non-fragmented packets of the same flow are transmitted through different paths. The first fragment and subsequent fragments are transmitted through the same path. |
None |
The specification is restricted. |
Symmetric load balancing does not support trunk localization scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing does not support port extension scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing does not support E-Trunk scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing does not support inter-virtual cluster chassis trunk scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing does not support multicast scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing supports data traffic packets instead of protocol packets between two devices. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing does not support multi-level load balancing scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing does not support CE dual-homing scenarios. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
When the hash algorithm is set to random, symmetric load balancing does not take effect. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
For symmetric load balancing: 1. If the device connects to a non-Huawei device, upstream and downstream traffic may not be hashed to the same link due to different load balancing algorithms. 2. If the device connects to a Huawei device that does not support symmetric load balancing, upstream and downstream traffic may not be hashed to the same link. |
None |
Upstream and downstream traffic may not be hashed to the same link. |
Symmetric load balancing cannot work with MAC address- or label-based load balancing. |
Properly plan services. |
Upstream and downstream traffic may not be hashed to the same link. |
