Quantcast
Channel: Notes of a SysAdmin » Drew
Viewing all articles
Browse latest Browse all 10

RHEL: /sys/class/net/bond0/bonding/slaves: No such file or directory

$
0
0

The other day I came across the following error:

[user@host]# service network restart
Shutting down interface eth0:  /etc/sysconfig/network-scripts/ifdown-eth: line 91: /sys/class/net/bond0/bonding/slaves: No such file or directory
                                                           [  OK  ]
Shutting down interface eth2:  /etc/sysconfig/network-scripts/ifdown-eth: line 91: /sys/class/net/bond0/bonding/slaves: No such file or directory
                                                           [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface bond0:                               [  FAILED  ]


The fix is simple: you need to load the Kernel bonding module. You either didn’t set this up to begin with or the syntax of the command was used incorrectly. Create a file in /etc/modprobe.d/ called bonding.conf:

[user@host]# vi /etc/modprobe.d/bonding.conf

You just need to add the following the the bonding.conf file:

alias bond0 bonding

For a one-time load (not usual), you can load to bonding modules manually:

[user@host]# modprobe bonding

As a verification measure, you can check to see if the modules are loaded by issueing the following command and seeing the following output:

[user@host]# lsmod | grep bonding
bonding               127331  0
8021q                  25317  1 bonding
ipv6                  321422  107 cnic,bonding

This was something that was overlooked that I was able to catch, since the error in question doesn’t really tell me much, other than the fact that the /proc filesystem doesn’t see any of the bonding configuration (which is what made me look into the kernel module).


Viewing all articles
Browse latest Browse all 10

Trending Articles