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 of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.