Good morning,
we have a cluster of 4 proxmox servers (different brands) which use a Huawei storage bay.
on each proxmox server, 8 interfaces:
2 10G coppers in LACP named MGMT (management, bond0)
2 10G coppers in LACP called VM (for VMs, bond2)
4 SFP+ with DAC cables named ISCSI (for ISCSI storage, bond1).
in the server's network conf, we therefore have:
3 BONDS,
and a single vmbr0 for VMs, on Bond2 (VM).
All ports go back to the Netgear 4000 series (10G) switches, along with the storage bay.
We had, on one machine, slow access to the bay.
When in doubt, we updated via apt-update/upgrade.
following this, bond1 no longer sees any traffic.
it's fine, you can ping its own IP address, but it doesn't ping anything around it.
no VLAN configured on the servers, it is the switch which assigns the correct Vlan for ISCSI.
on the server side, everything seems OK, but on the switch, we see the ports UP but the LACP down.
Does anyone have any ideas on how to fix this?
I'll put the network configuration below, if that helps:
Thanks in advance....
Network Conference:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read 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
auto ens9f0np0
iface ens9f0np0 inet manual
auto ens9f1np1
iface ens9f1np1 inet manual
auto ens9f2np2
iface ens9f2np2 inet manual
auto ens9f3np3
iface ens9f3np3 inet manual
auto ens2f0
iface ens2f0 inet manual
auto ens2f1
iface ens2f1 inet manual
auto ens3f0
iface ens3f0 inet manual
auto ens3f1
iface ens3f1 inet manual
auto bond0
iface bond0 inet static
address 172.26.12.105/24
gateway 172.26.12.253
bond-slaves ens9f0np0 ens9f1np1
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer2
#MGMT
auto bond1
iface bond1 inet static
address 172.26.13.105/24
bond-slaves ens2f0 ens2f1
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer2+3
#ISCSI
auto bond2
iface bond2 inet manual
bond-slaves ens9f2np2 ens9f3np3
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer2
#VMS
auto vmbr0
iface vmbr0 inet manual
bridge-ports bond2
bridge-stp off
bridge-fd 0
#pour VMs
we have a cluster of 4 proxmox servers (different brands) which use a Huawei storage bay.
on each proxmox server, 8 interfaces:
2 10G coppers in LACP named MGMT (management, bond0)
2 10G coppers in LACP called VM (for VMs, bond2)
4 SFP+ with DAC cables named ISCSI (for ISCSI storage, bond1).
in the server's network conf, we therefore have:
3 BONDS,
and a single vmbr0 for VMs, on Bond2 (VM).
All ports go back to the Netgear 4000 series (10G) switches, along with the storage bay.
We had, on one machine, slow access to the bay.
When in doubt, we updated via apt-update/upgrade.
following this, bond1 no longer sees any traffic.
it's fine, you can ping its own IP address, but it doesn't ping anything around it.
no VLAN configured on the servers, it is the switch which assigns the correct Vlan for ISCSI.
on the server side, everything seems OK, but on the switch, we see the ports UP but the LACP down.
Does anyone have any ideas on how to fix this?
I'll put the network configuration below, if that helps:
Thanks in advance....
Network Conference:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read 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
auto ens9f0np0
iface ens9f0np0 inet manual
auto ens9f1np1
iface ens9f1np1 inet manual
auto ens9f2np2
iface ens9f2np2 inet manual
auto ens9f3np3
iface ens9f3np3 inet manual
auto ens2f0
iface ens2f0 inet manual
auto ens2f1
iface ens2f1 inet manual
auto ens3f0
iface ens3f0 inet manual
auto ens3f1
iface ens3f1 inet manual
auto bond0
iface bond0 inet static
address 172.26.12.105/24
gateway 172.26.12.253
bond-slaves ens9f0np0 ens9f1np1
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer2
#MGMT
auto bond1
iface bond1 inet static
address 172.26.13.105/24
bond-slaves ens2f0 ens2f1
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer2+3
#ISCSI
auto bond2
iface bond2 inet manual
bond-slaves ens9f2np2 ens9f3np3
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer2
#VMS
auto vmbr0
iface vmbr0 inet manual
bridge-ports bond2
bridge-stp off
bridge-fd 0
#pour VMs