Bonding 3 nics with a fourth nic on a separate network

Latest response

I have bonded three nics and that works fine however, I have configured a 4th nic for a separate network and when I bring that nic online the bond no longer responds. How do I make the Bond the first in the boot order so the 4th nic does not interfere?

Thanks,

Responses

It is possible to have a bond (3 NICs) and non-bonded interface (4th NIC) running at the same time. Is a default gateway configured on the 4th NIC?

Yes the default gateway is configured. And this is the second time I have run into this issue. I have it happening on two machines.

HWADDR=D8:9D:67:23:36:BF TYPE=Ethernet UUID=b3632c3c-9b2f-449b-a7f6-98256bab7ae2 NAME=eth3 IPADDR=10.100.51.112 NETMASK=255.255.255.0 GATEWAY=10.100.51.1 DEVICE=eth3 BOOTPROTO=none ONBOOT=no USSERCTL=no

I have onboot =no b/c of the issue. Once I turn it on the bond no longer responds.

Remove the gateway on eth3 then bring the interface up. The bond should continue working. You can also set BOOTPROTO=static and ONBOOT=yes.

You might need to configure static routes for destinations you want to traverse eth3.

Perfect that worked thank you so much!

Excellent! Glad I could help.

Great info, thanks!

When RHEL runs through the ifcfg files, if you've specified more than one file with a gateway, the default route add operation will be executed for each gateway declaration. Since the ifcfg files get processed serially, the default route will get set to whatever is declared in the last gateway-containing file.

You can typically get past this by only declaring a gateway in only one of the ifcfg files or declaring a gateway-dev in one of the higher-order network config files.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.