Feature Requirements |
Series |
Models |
|---|---|---|
When the hash algorithm is set to random, symmetric load balancing does not take effect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Symmetric load balancing does not support CE dual-homing scenarios. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Symmetric load balancing does not support E-Trunk scenarios. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Symmetric load balancing does not support trunk localization scenarios. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Symmetric load balancing does not support multi-level load balancing scenarios. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Symmetric load balancing does not support multicast scenarios. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Symmetric load balancing cannot work with MAC address- or label-based load balancing. You are advised to properly plan services. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Symmetric load balancing supports data traffic packets instead of protocol packets between two devices. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
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. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
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. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |