Does anyone know what the error:
"interface 'dev23977' not found"
means when you issue the command:
"/etc/rc.d/init.d/network start"? Specifically how does one determine which device is being referred to in the error message. I get this message when I channel bond two NICs and restart the network. Also does anyone know which system file supplies the list of devices that will be started when you do a network restart? I have looked at the /etc/rd.d/init.d/network and functions files to try to understand how the network is started up so that I could fix the errors I am experiencing but I could not locate the file containing the interface specifications.

I also get the error:

"Bringing up interface bond0: cannot change name of eth0 to bond0: File exists
cannot change name of lo to dev9618: Device or resource busy"

However when I issue the command ifup eth0 and ifup eth1 I get a message that eth0 and eth1 are bonded to bond0. When I check the network connection using /sbin/route I find that there is no default gateway identified. When I add the gateway then the network connection is OK. But when I again use "/etc/rc.d/init.d/network start" I get the same error message as before. I have posted the relevant ifcfg-xxx files and the modprobe.conf file I am using in a previous post on 1/23/2006 and identified it as "FC4 channel bonding" if that information would be of help in answering my current question.

Thanks for the help.

<Dave Retzloff>

hello,
Did you check http://www.linuxquestions.org/questi....php?t=277239?

Paragn:

Thanks for the reply. Yes I did check out the thread you mention and tried all of the suggestions I found there. I can bond the two NICs manually but I always have to add the default gateway to bond0 to be able to ping other computers. However when I restart the network the bonding breaks and I get the error message the interface 'devxxxx' cannot be found. I think it might be related to how the network script in /etc/rc.d/init.d brings up the interfaces but I have been unable to identify where the interfaces that the script brings are identified. So far this is purely guess work on my part and I am not sure of the root cause of the problem. So far all I have are the error messages I get when I reboot the network.

<Dave>