ONBOOT=no ineffective with multiple bonded interfaces
Issue
If there are multiple bonded interfaces on physical server, and some are set with ONBOOT=yes and others with ONBOOT=no, then all the bonded interfaces will start at boot, making the ONBOOT parameter ineffective.
Environment
Red Hat Enterprise Linux 5
Red Hat Enterprise Linux 6
A physical server with at least two bonded interfaces. Does not seem reproducible on virtual servers.
First bonded interface contains "ONBOOT=no" in its ifcfg-bond* file
Second bonded interface contains "ONBOOT=yes" in its ifcfg-bond* file
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.