Apr 5, 2018
1
0
1
27
hello guys I have the following question / problem I have a cluster of three nodes and two virtual machines, of which one virtual machine should only have access to the data network and users and the other to the data network and the management network.

Data: 192.168.0.0/24
Management: 10.10.10.0/24

I have a switch divided into two vlans one for data and one for management, two of the three nodes have 4 nic that are divided into two bonds. I need one of the virtual machines to have access to the two networks so I would need two vmbr and at the same time work in equipment (bond)

How could he do it?

This is my interfaces configuration file:

# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno2 inet manual

iface eno3 inet manual

iface eno4 inet manual

auto bond0
iface bond0 inet static
address 10.10.10.10
netmask 255.255.255.0
gateway 10.10.10.1
slaves eno1 eno2
bond_miimon 100
bond_mode 802.3ad

auto bond1
iface bond1 inet static
address 192.168.0.45
netmask 255.255.255.0
slaves eno3 eno4
bond_miimon 100
bond_mode 802.3ad

auto vmbr0
iface vmbr0 inet manual
bridge_ports bond1
bridge_stp off
bridge_fd 0

auto vmbr1
iface vmbr1 inet manual
bridge_ports none
bridge_stp off
bridge_fd 0



the theory tells me that it should go like this, but I lose communication:

# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno2 inet manual

iface eno3 inet manual

iface eno4 inet manual

auto bond0
iface bond0 inet static
address 10.10.10.10
netmask 255.255.255.0
gateway 10.10.10.1
slaves eno1 eno2
bond_miimon 100
bond_mode 802.3ad

auto bond1
iface bond1 inet static
address 192.168.0.45
netmask 255.255.255.0
slaves eno3 eno4
bond_miimon 100
bond_mode 802.3ad

auto vmbr0
iface vmbr0 inet manual
bridge_ports bond1
bridge_stp off
bridge_fd 0

auto vmbr1
iface vmbr1 inet manual
bridge_ports bond0
bridge_stp off
bridge_fd 0

help me pls :(
 
Hi,

the config should work, but may be you have problems with LACP try active/backup mode to test.

It make more sense to assign the ip on the bridge and not on the bond if you use the bond on a bridge.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!