trying to set up sdn and hitting an issue

F

ferret_ferret

New Member
Apr 3, 2024
4
0
1
hi,

i am setting up a new sdn vlan zone with 2 vnets, and i am seeing an error on only one of my two nodes, but the error just says, `error vmbr1` and i'm having trouble figuring out how to see what that error is, and how to go about troubleshooting it.
 
Does the bridge exist on that node? That errors is usually caused because there is some issue with the bridge.

Can you post the output of the following commands (in CODE tags, please)

Code: 
head -n-0 /etc/pve/sdn/*
cat /etc/network/interfaces
ip l

The task log of the failing task would be nice as well
 
yes, created the bridge right before i created the vnet,

Bash: 
pve2:~# head -n-0 /etc/pve/sdn/*
==> /etc/pve/sdn/subnets.cfg <==

==> /etc/pve/sdn/vnets.cfg <==
vnet: home
    zone HomeNet
    tag 6

vnet: ipv6
    zone HomeNet
    tag 9


==> /etc/pve/sdn/zones.cfg <==
vlan: HomeNet
    bridge vmbr1
    ipam pve

Bash: 
pve2:~# 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

iface eno2 inet manual

iface eno1 inet manual

auto enp8s0f1
iface enp8s0f1 inet manual

auto vmbr0
iface vmbr0 inet static
    address 192.168.1.99/24
    gateway 192.168.1.1
    bridge-ports eno2
    bridge-stp off
    bridge-fd 0

auto vmbr1
iface vmbr1 inet manual
    bridge-ports enp8s0f1
    bridge-stp off
    bridge-fd 0

source /etc/network/interfaces.d/*


Bash: 
pve2:~# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 90:b1:1c:47:42:92 brd ff:ff:ff:ff:ff:ff
    altname enp2s0f0
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 90:b1:1c:47:42:93 brd ff:ff:ff:ff:ff:ff
    altname enp2s0f1
5: enp8s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP mode DEFAULT group default qlen 1000
    link/ether 90:e2:ba:90:da:81 brd ff:ff:ff:ff:ff:ff
6: idrac: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 90:b1:1c:47:42:95 brd ff:ff:ff:ff:ff:ff
7: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 90:b1:1c:47:42:93 brd ff:ff:ff:ff:ff:ff
8: tap106i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr106i0 state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether ea:13:fa:37:1d:18 brd ff:ff:ff:ff:ff:ff
9: fwbr106i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether e2:2a:de:d6:04:27 brd ff:ff:ff:ff:ff:ff
10: fwpr106p0@fwln106i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 7e:ca:88:d5:de:8e brd ff:ff:ff:ff:ff:ff
11: fwln106i0@fwpr106p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr106i0 state UP mode DEFAULT group default qlen 1000
    link/ether e2:2a:de:d6:04:27 brd ff:ff:ff:ff:ff:ff
12: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 90:e2:ba:90:da:81 brd ff:ff:ff:ff:ff:ff
23: ln_home@pr_home: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master home state UP mode DEFAULT group default qlen 1000
    link/ether b6:03:ff:2d:f8:81 brd ff:ff:ff:ff:ff:ff
24: pr_home@ln_home: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1v6 state UP mode DEFAULT group default qlen 1000
    link/ether b2:a7:19:92:5c:dd brd ff:ff:ff:ff:ff:ff
25: home: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether b6:03:ff:2d:f8:81 brd ff:ff:ff:ff:ff:ff
26: ln_ipv6@pr_ipv6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master ipv6 state UP mode DEFAULT group default qlen 1000
    link/ether 72:2b:27:ea:05:c0 brd ff:ff:ff:ff:ff:ff
27: pr_ipv6@ln_ipv6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1v9 state UP mode DEFAULT group default qlen 1000
    link/ether aa:d7:95:0c:a9:67 brd ff:ff:ff:ff:ff:ff
28: ipv6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 72:2b:27:ea:05:c0 brd ff:ff:ff:ff:ff:ff
29: enp8s0f1.6@enp8s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1v6 state UP mode DEFAULT group default qlen 1000
    link/ether 90:e2:ba:90:da:81 brd ff:ff:ff:ff:ff:ff
30: vmbr1v6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 90:e2:ba:90:da:81 brd ff:ff:ff:ff:ff:ff
31: enp8s0f1.9@enp8s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1v9 state UP mode DEFAULT group default qlen 1000
    link/ether 90:e2:ba:90:da:81 brd ff:ff:ff:ff:ff:ff
32: vmbr1v9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 90:e2:ba:90:da:81 brd ff:ff:ff:ff:ff:ff

and i am not sure which task is failing, all i am seeing in the ui is error vmbr1 when i look at the network details on the specific node, and i am not sure where to look for the specific task that is failing or where to get more details than just that there is an error.
 
i appear to have solved the first issue of the network applying to my second node, i gave the bridge a cidr block and that seems to have solved it,

now my main issue is once i have this with a subnet under a vnet i appear to have no external connectivity, so trying to work through that now
 
ferret_ferret said:
i appear to have solved the first issue of the network applying to my second node, i gave the bridge a cidr block and that seems to have solved it,

now my main issue is once i have this with a subnet under a vnet i appear to have no external connectivity, so trying to work through that now
Click to expand...
Can you resend me the output of the commands, so I can get an idea of your current state?
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back