System: HP Proliant DL360 G5 running CentOS 5.4
Bonded interface is working fine for a long time. I just went to add an alias the way I always have on a regular interface, and on first check it works (pinging on the local box) but it is not accessable from outside (iptables is turned off). In addition with this setup the normal network response started to decline, hanging for around a minute before I could get a prompt on login.
Here are my config files:
[root network-scripts]# cat ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
[root network-scripts]# cat ifcfg-eth1
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
[root network-scripts]# cat ifcfg-bond0
DEVICE=bond0
BONDING_OPTS="mode=1 miimon=100"
BOOTPROTO=none
ONBOOT=yes
NETWORK=10.2.1.0
NETMASK=255.255.255.0
IPADDR=10.2.1.11
USERCTL=no
[root network-scripts]# cat ifcfg-bond0:1
DEVICE=bond0:1
BOOTPROTO=static
ONBOOT=yes
NETWORK=10.2.1.0
NETMASK=255.255.255.0
IPADDR=10.2.1.12
USERCTL=no
any thoughts?
Does the bonding kernel module loads properly or not ?
If not, it could be related to a dependency issue w/ ipv6, appeared in rhel5.4 with bonding driver 3.4.0.
the following commands should resolve this issue:
You do not have a GATEWAY line. The only thing that can reach those interfaces are other devices on the same vlan
You need a default gateway.
Best way to do this and avoid having to bounce network service is to manually add gateway with:
ip route replace default via dev bond0
You will also need to add the line:
ZONE=public
to the ifcfg-bond0 file to ensure the gw is added to the routing table following any future reboot.
bond0:1 is still driven by a bond driver. Create eth0:1 and eth1:1 and bond them.
Please add NM_CONTROLLED=no in ifcfg-bond0 abd restart once. may help you.