No inter host communications with OpenVSwitch

9ui11aum3

Member
Mar 6, 2022
1
0
6
27
Hi Community ,

I'm currently facing an issue with OpenVSwitch.

3 nodes are double attached on 2 Mikrotik switches. RSTP is enable on both switches.
Our goal was to apply a similar config to exemple #4 based on the wiki example (https://pve.proxmox.com/wiki/Open_vSwitch)
Except we don't have the direct link between each host (X links on the graph)

Our network config :
Code:
auto lo
iface lo inet loopback

auto eno5
iface eno5 inet manual
        ovs_type OVSPort
        ovs_bridge vmbr0
        ovs_options tag=1 vlan_mode=native-untagged other_config:rstp-path-cost=2000 other_config:rstp-port-mcheck=true other_config:rstp-enable=true other_config:rstp-port-admin-edge=false other_config:rstp->

auto eno6
iface eno6 inet manual
        ovs_type OVSPort
        ovs_bridge vmbr0
        ovs_options tag=1 vlan_mode=native-untagged other_config:rstp-enable=true other_config:rstp-port-admin-edge=false other_config:rstp-port-auto-edge=false other_config:rstp-path-cost=2100 other_config:r>


auto vlan10
iface vlan10 inet static
        address 172.16.10.52/24
        gateway 172.16.10.254
        ovs_type OVSIntPort
        ovs_bridge vmbr0
        ovs_options tag=10

auto vmbr0
iface vmbr0 inet manual
        ovs_type OVSBridge
        ovs_ports eno5 eno6 vlan10
        up ovs-vsctl set Bridge ${IFACE} rstp_enable=true other_config:rstp-priority=32768 other_config:rstp-forward-delay=4 other_config:rstp-max-age=6
        post-up sleep 10


Our Packages version :
Code:
proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-12
pve-kernel-5.13: 7.1-7
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-3
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
openvswitch-switch: 2.15.0+ds1-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-6
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1

Code:
pve01 : 172.16.10.51
pve02 : 172.16.10.52
pve03 : 172.16.10.53
VLAN10 : our Administration VLAN

Gateway : 172.16.10.254


With the above configuration applied on each host, one host is able to reach internet, the gateway but none of the other Proxmox host.

Code:
root@pve02:~# ping 172.16.10.254
PING 172.16.10.254 (172.16.10.254) 56(84) bytes of data.
64 bytes from 172.16.10.254: icmp_seq=1 ttl=64 time=0.214 ms
64 bytes from 172.16.10.254: icmp_seq=2 ttl=64 time=0.261 ms
^C
--- 172.16.10.254 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1013ms
rtt min/avg/max/mdev = 0.214/0.237/0.261/0.023 ms
root@pve02:~# ping 172.16.10.21
PING 172.16.10.21 (172.16.10.21) 56(84) bytes of data.
64 bytes from 172.16.10.21: icmp_seq=1 ttl=64 time=0.754 ms
64 bytes from 172.16.10.21: icmp_seq=2 ttl=64 time=0.253 ms
^C
--- 172.16.10.21 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1018ms
rtt min/avg/max/mdev = 0.253/0.503/0.754/0.250 ms
root@pve02:~# ping 172.16.10.51
PING 172.16.10.51 (172.16.10.51) 56(84) bytes of data.
From 172.16.10.52 icmp_seq=1 Destination Host Unreachable
From 172.16.10.52 icmp_seq=2 Destination Host Unreachable
From 172.16.10.52 icmp_seq=3 Destination Host Unreachable
From 172.16.10.52 icmp_seq=4 Destination Host Unreachable
^C
--- 172.16.10.51 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4055ms
pipe 3
root@pve02:~#

Code:
 |-----------------------------|
 | G           G           G   | SW1
 |-|-----------|-----------|---|
 |-+-----------+-----------+---|
 | | G         | G         | G | SW2
 |-+-|---------+-|---------+-|-|
   | |         | |         | |
   | |         | |         | |
   | B         B B         B B
   | |         | |         | |
|--|-|--|      | |      |--|-|--|
|  G G  |      | |      |  G G  |
|       |      | |      |       |
|-------|      | |      |-------|
   pve01       | |         pve03
               | |     
               | |   
            |--|-|--|
            |  G G  |
            |       |
            |-------|
               pve02
 
Last edited:

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!