When using the kernel boot-line to configure a bond, why does one interface never join the bond?
Issue
-
When bringing an interface online using the kernel boot-line, and then configuring a bond after the boot process, the interface that is configured while booting will not become a slave of the bond until network services are restarted.
-
The interface created at boot time is to be used as a slave to the bond after initial boot, but will not join the bond - if the interface in question is not meant to be a slave of the bond this should not occur. This is used when booting from iSCSI or another network-based boot method when the end result of a bond is desired.
Environment
- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 5
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.