Les Mikesell wrote:
> On Fri, Sep 9, 2011 at 11:51 AM, <m.roth@xxxxxxxxx> wrote:
>>
>>> Clonezilla (especially with the drbl server) can do this pretty
>>> quickly over the network without having to juggle disks, but you end
>>> up with the same problem with the NICs - and in fact you will have it
>>> with any method of backing up and restoring on a different machine so
>>> it is something to consider even if you aren't cloning. On 5.x,
>>> kudzu would normally run on the new machine, rename all the
>>> NIC-related files and create new default dhcp-based copies. Not sure
>>> how 6.0 works in that respect. If it doesn't do it automatically, you
>> <snip>
>> We've gone to upgrading using rsync, and NICs are a problem. UDEV
>> renames the NICs - eth0 to eth2, eth1 to eth3, and so there are no
>> ifcfg-eth? for them. Removing the MAC fixes this, including down in
>> /etc/udev/rules.d//70-persistant-net.rules
>
> So how do you know which NIC is which then? Most of my boxes have 4
> to 6 and they appear in random order (well, flipped in pairs by
> driver) on reboots without being anchored with MAC addresses? I need
> each one to keep the same IP and associated routes.
Yeah, I wasn't thinking of that. At some point, I should probably go back
into that rulefile and fix it. Hmmm, or write a simple script....
mark
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
