ONBOOT=no ineffective with multiple bonded interfaces

Solution Verified - Updated -

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, 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