Post by Dan KenigsbergPost by BlasterBug 1094842 - Bonding modes 0, 5 and 6 should be avoided for VM networks
https://bugzilla.redhat.com/show_bug.cgi?id=1094842#c0
Dan,
What is bad about these modes that oVirt can't use them?
Do not use tlb or alb in bridge, never! It does not work, that's it. The reason
is it mangles source macs in xmit frames and arps. When it is possible, just
use mode 4 (lacp). That should be always possible because all enterprise
switches support that. Generally, for 99% of use cases, you *should* use mode
4. There is no reason to use other modes.
This switch is more of an office switch and only supports part of the
802.3ad standard:
PowerConnect* *2824
Scalable from small workgroups to dense access solutions, the 2824
offers 24-port flexibility plus two combo smallâformâfactor
pluggable (SFP) ports for connecting the switch to other networking
equipment located beyond the 100 m distance limitations of copper
cabling.
Industry-standard link aggregation adhering to IEEE 802.3ad
standards (static support only, LACP not supported)
So the only way to have some kind of bonding without buying more
expensive switches, is using balance-rr (mode=0), balance-xor (mode=2)
or broadcast (modes=3).
Post by Dan KenigsbergPost by BlasterI just tested mode 4, and the LACP with Fedora 20 appears to not be
compatible with the LAG mode on my Dell 2824.
Would there be any issues with bringing two NICS into the VM and doing
balance-alb at the guest level?
Kind regards,
Jorick Astrego
Met vriendelijke groet, With kind regards,
Jorick Astrego
Netbulae Virtualization Experts
----------------
Tel: 053 20 30 270 ***@netbulae.eu Staalsteden 4-3A KvK 08198180
Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01
----------------