Hi
Thanks for the reply.
We have the MAC addresses in the ifcfg-eth[0-5] files.
Two of the nics we have use the e1000e driver which causes the nics to come up in a random order on every reboot, so to control the order for 3 different bonds we have to tie down the mac address.
It's the mac address that causes the problem. If for any reason it changes, RHEL detects the new mac address and, changes the ifcfg-eth3 to ifgcfg-eth3.bak and instigates a dhcp request.
Just to confirm, this is RHEL 5.4 64bit
Thanks
Dan
Quote:
Originally Posted by willl_d
shouldn't your ifcfg-eth[2,3] look something like this?
DEVICE=eth2
BOOTPROTO=none <----will stop it from requesting address via DHCP
MASTER=bondname
SLAVE=yes
USERCTL=no
And your bond should be
DEVICE=bondname
BOOTPROTO=static <--will also stop the dhcp client from requesting an address.
HWADDR=some mac address...
IPADDR=whatever
NETMASK=whatever
GATEWAY=whatever
You didn't mention a distro, so I'm talking RHEL here..
|