Hello, I just installed a second NIC on my linux system to try bonding them in active-backup mode to acheive high availability of the system. I read a mini-howto which details the steps necessary to do this, but got stumped in a problem for which I can't find a solution (or even a description) anywhere.
The default mode of operation for the bonding driver is round robin. My first attepmt, ended up with 1/2 my outgoing packets being lost, due to the kernel trying to send them out a disconnected interface. Next, I connected my main link to a hub, and the two NICs to the hub as well. Now I had every incoming packet duplicated. So far, everything is working as expected. Now, for the wierd stuff. To have the module behave in active-backup mode, you have to load it with the mode=1 parameter. In following the instructions from the howto, I also used the miimon=100 parameter. The problem is that the module does not seem to recognise these parameters (either of them). The following id the output of modprobe when trying to load the driver. [root@jgostling root]# modprobe bonding miimon=100 mode=1 /lib/modules/2.4.9-31/kernel/drivers/net/bonding.o: invalid parameter parm_miimon /lib/modules/2.4.9-31/kernel/drivers/net/bonding.o: insmod /lib/modules/2.4.9-31/kernel/drivers/net/bonding.o failed /lib/modules/2.4.9-31/kernel/drivers/net/bonding.o: insmod bonding failed To narrow down the problem further, I tried to load the driver without the miimon parameter, with the following results: [root@jgostling root]# modprobe bonding mode=1 /lib/modules/2.4.9-31/kernel/drivers/net/bonding.o: invalid parameter parm_mode /lib/modules/2.4.9-31/kernel/drivers/net/bonding.o: insmod /lib/modules/2.4.9-31/kernel/drivers/net/bonding.o failed /lib/modules/2.4.9-31/kernel/drivers/net/bonding.o: insmod bonding failed A search on the web (Google and Redhat) gave me lots of pages, but none showed this issue. The howto I read is dated October 2000, so I think there is a chance the bonding driver's interface has changed since, but I find no reference regarding this. My system is a stock Redhat 7.2 with all updates including kernel 2.4.9-31, and the driver came precompiled from Redhat. Any help would be really appreciated. Thanks, -- Javier Gostling Ingeniero de Sistemas Virtualia S.A. [EMAIL PROTECTED] Fono: +56 (2) 202-6264 x 130 Fax: +56 (2) 342-8763 Av. Kennedy 5757, of 1502 Las Condes Santiago Chile _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
