eshsf wrote: > Hello, > > On Thu, 17 May 2007 13:25:03 +0200 > Jan Kalcic <[EMAIL PROTECTED]> wrote: > > >> Michael Kershaw wrote: >> >>> Jan, >>> >>> In your ifcfg-bond0, instead of listing the interface as the >>> bonding_slave's, have you tried to tell it the pci info instead like >>> so: >>> >>> >>> BONDING_SLAVE0='bus-pci-0000:04:02.0' >>> BONDING_SLAVE1='bus-pci-0000:04:02.1' >>> >>> Here's my complete ifcfg-bond0: >>> >>> BOOTPROTO='static' >>> BROADCAST='192.168.148.31' >>> IPADDR='192.168.148.30' >>> MTU='1500' >>> NETMASK='255.255.255.224' >>> NETWORK='192.168.148.0' >>> REMOTE_IPADDR='' >>> STARTMODE='onboot' >>> BONDING_MASTER='yes' >>> BONDING_MODULE_OPTS='mode=active-backup miimon=100' >>> BONDING_SLAVE0='bus-pci-0000:04:02.0' >>> BONDING_SLAVE1='bus-pci-0000:04:02.1' >>> >>> Let me know if this helps! >>> >> Unfortunately not. I still have the problem both using pci info and >> adapting your config file. I guess is something wrong with the >> configuration as I have the same problem anywhere I try (openSuSE as >> well as SLES) >> > > I'm not using bonding. so, I'm not sure, but is this related to the issue? > > https://bugzilla.novell.com/show_bug.cgi?id=250620 > > > Regards, > eshsf > >
Hi eshsf, the bug you mentioned is not regarding the problem I have. When I ifdown any enslaved interface the bond0 interface goes down properly. Instead, when I simulate a link failure doing 'ifconfig eth0 down' or disconnecting the device from vmware console the problem described occurs. Jan -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
