Bonding - breaks management connection

[mkyb14]

Trying to understand the network layout for potentially bonding the two gig nic's on my supermicro.

Currently the h11ssl-i-o has 1 IPMI port and 2 intel onboard nic's. I'm wanting to LACP the two intel nic's and when I do so, I believe I'm killing the management interface.

Can you have the management interface on one of those nic's and have it in a bond? Attached image is just what I reversed since I lost the connection after creating the LACP and bond within proxmox. Just showing what I have there.

Assuming that the LACP is correct on the unifi switch, pfsense router has the static DHCP reservations for both intel MAC's assigned. Would be as simple as creating the linux Bond0, slaves are eno1 and eno2.

Bond0 is a slave of vmbr0?

That ultimately broke and had to use ipmi to get back in and edit the /etc/network/interfaces file to get back up and running.

 

[H4R0]

What type of switch do you have ? It must support LACP

There is really not much to it.

Set bond0 ports to "eno1 eno2" and enable autostart (do not set ip information for bond0)
Now set vmbr0 port to bond0 and check "vlan aware"
Apply the configuration
If you dont have ifupdown2 installed reboot

 

[mkyb14]

I have a capable unifi switch, and that's what I did, but lost the connection immediately. That's what got me thinking about the management IP setup during the beginning and if that port can be used in tandem with a bond.

 

[H4R0]

The IPMI nic is reserved for the uefi/bios, you cant use it with proxmox. It should not interfere with your network setup. It's a system on its own.


"pfsense router has the static DHCP reservations for both intel MAC's assigned"

If you use LACP, eno1 and eno2 should create vmbr0 with its own mac.

So you need to create a static mapping for the bridge mac not of the physical nics.

But you already assign a static ip for the bridge ?! so the dhcp mapping is not necessary.


You have to troubleshoot, check logs etc.

Does your pfsense receive a DHCP request etc.

Make sure your switch detects both ports as full duplex 1gb/10gb active