Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
(In reply to Jamie Bainbridge from comment #4)
> > Under no circumstances should Modes 0, 3, 5, or 6 be used.
>
> I assume this comes from the RHEV documentation?
>
> There is some discrepancy between what RHEV decided to allow for guest
> networks and what actually works. The knowledgebase solution I wrote
> (https://access.redhat.com/solutions/67546) lists 0 and 3 as working, a view
> which former bonding maintainer vfalico supported (Bug 1097312).
This discrepancy should be fixed on RHEV side. IICR vfalico and jpirko asked to block modes 0 5 6 when bridges are connected when discussion multiple customer tickets due their usage.
If mode 0 can actually be enabled (with caveats) by the platform, I suppose RHEV should enable it as well.
Karen, is this the current wisdom? mode 0 is good for us?
WRT to bond mode 0:
Bonding mode-0 requires manual configuration on the switch that all bond members
are connected to. The switch configuration requires all ports to be added to a single LAG (or EtherChannel) because the bond will use the same source mac on
each bond member, and without LAG on the switch, the flow will bounce between multiple ports causing unreachability.
This requirement for manual switch configuration is the reason that we do not recommend bond mode 0 being used.
-vlad