no vlan transport

Volker Lieder

Well-Known Member
Nov 6, 2017
50
3
48
44
Hi,
we have installed a fresh proxmox 8.1 Server with 4 x 10Gbit NIC and 2 x 1Gbit NIC

2 x 10Gbit as bond for storage
2 x 10Gbit as bond for VMS IP
2 x 1Gbit as bond for Proxmox-MGMT

cat /etc/network/interfaces
# 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 eno1
iface eno1 inet manual

auto eno2
iface eno2 inet manual

auto ens4f0np0
iface ens4f0np0 inet manual

auto ens4f1np1
iface ens4f1np1 inet manual

auto ens6f0np0
iface ens6f0np0 inet manual

auto ens6f1np1
iface ens6f1np1 inet manual

auto bond0
iface bond0 inet static
address 10.11.45.11/24
gateway 10.11.45.1
bond-slaves eno1 eno2
bond-miimon 100
bond-mode active-backup
bond-primary eno1

auto bond1
iface bond1 inet manual
bond-slaves ens4f0np0 ens4f1np1
bond-miimon 100
bond-mode active-backup
bond-primary ens4f0np0
#Storage

auto bond2
iface bond2 inet manual
bond-slaves ens6f0np0 ens6f1np1
bond-miimon 100
bond-mode active-backup
bond-primary ens6f0np0
#ACCESS

auto vmbr1
iface vmbr1 inet manual
bridge-ports bond2
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
#ACCESS

The switch to Access-Ports, Juniper QFX, is configured as trunk with the needed vlans.
If i configure a new VM, eg in vlan 2504 and add an ip address from this network to it, i cant ping a vlan interface from that range which is located on the switch for testing,
neither i cant ping another VM from that VLAN on another Proxmox Node.

Any ideas what i can check on proxmox where the vlan information to the switch is "broken"?

We have several other proxmox Nodes up and running, never have had this issue before.

Best regards,
Volker
 
Hi,

thank you for your reply. We already tested these options without success. We found the main reason yesterday.

The master unit of our juniper virtual chassis seems to have had an issue with some ports. We could "fixed" this with changing the routing engine to 2nd member and back again. Now we are updating the switch stack and hope this "bug" will be resolved.

This issue can be closed.

Best regards,
Volker
 

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!