Bond using mode 4 or 802.3ad may activate incorrect interface due to bug in agg_device_up() function

Solution Verified - Updated -

Issue

On some situations, bonding may use an old aggregator ID and may even try to use a slave that is actually in a down state.

Environment

  • Red Hat Enterprise Linux 5
  • Red Hat Enterprise Linux 6
  • with 802.3ad/mode 4 bonding

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content