When loading the bonding kernel module a network device is always created with the name as bond0.
Issue
- When the bonding kernel module is loaded a bond0 network device is created even if only device or devices with different names are desired.
For example there is configured only bonding device with name BigBond0 in
$cat /etc/sysconfig/network-scripts/ifcfg-BigBond0
...
DEVICE=BigBond0
...
But after module loading there are two bonding devices, BigBond0 and bond0.
$ip a
...
1: BigBond0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.XXX Mask:XXX.XXX.XXX.XXX
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:X errors:X dropped:X overruns:X frame:X
TX packets:X errors:X dropped:X overruns:X carrier:X
collisions:0 txqueuelen:0
RX bytes:X (X Mb) TX bytes:X (X Mb)
2: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether YY:YY:YY:YY:YY:YY brd ff:ff:ff:ff:ff:ff
...
Environment
- Red Hat Enterprise Linux 5, 6, 7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.