[rear-users] Bonded NICs

Jeffrey D. Fulmer JDFulmer at Armstrong.com
Tue Sep 30 21:16:05 CEST 2014

I did a recursive grep inside /usr/share/rear and found SIMPLY_BONDING. I added it to local.conf


None of the bonding came up, just eth0. I was able to config that with its new address and I was on the network.

Since I was cloning to different hardware, I was unable to boot after cloning. I solved that problem by chroot'ing /mnt/local and making a new kernel:

chroot /mnt/local
cd /boot
mkinitrd -f -v initrd-2.6.32-431.20.3.el6.x86_64kdump.img 2.6.32-431.20.3.el6.x86_64

HINT: whatever you call the kernel, make sure you have a directory by the same name in /lib/modules



From: rear-users-bounces at lists.relax-and-recover.org [rear-users-bounces at lists.relax-and-recover.org] On Behalf Of Jeffrey D. Fulmer [JDFulmer at Armstrong.com]
Sent: Tuesday, September 30, 2014 1:35 PM
To: rear-users at lists.relax-and-recover.org
Subject: [rear-users] Bonded NICs

Hello list,

I'm having trouble making a recovery disk for two servers, they are in a RedHat cluster and they have bonded NICs.  The OS is RHEL 6.5

I'm recovering to a server that has fewer NICs than the one I archived.

When the server comes up, I down all the network interfaces, i.e.,

ifconfig bond0 down
ifconfig bond1 down

then I attempt to bring up eth0

ifconfig eth0 netmask up
route add default gw

I can't ping the gateway. Everything looks fine in my routing table.

I notice these errors in the dmesg:

udev: renamed network interface eth0 to eth13
ADDRCONF(NETDEV_UP) eth0: link is not ready

The only servers that give me an issue are ones with bonded NICs.  I don't need bonded NICs on the server I'm cloning to.

Any thoughts on how I can get this rescue on the network?


rear-users mailing list
rear-users at lists.relax-and-recover.org

More information about the rear-users mailing list