-
- Service Provider
- Posts: 31
- Liked: 12 times
- Joined: Oct 27, 2011 8:42 am
- Full Name: Andreas Cederlund
- Location: Landskrona, Sweden
- Contact:
Proxmox VE workers
Hi,
Just testing out the Proxmox VE integration in 12.2, and I'm a newbie on Proxmox VE, so please bare with me.
I'm about to set up workers, and somehow only network interfaces of the "Linux Bridge" type shows up in the drop down list - my interfaces of the type "OVS Bridge" is not showing up in the drop down menu.
I checked the documentation on prerequisites and limitations, but there is no mention of different bridge types. It also is not possible to enter a VLAN in the dialogue box as well, as it is when creating regular VMs.
Has anyone else encountered these limitations, or am I just doing stuff wrong?
Just testing out the Proxmox VE integration in 12.2, and I'm a newbie on Proxmox VE, so please bare with me.
I'm about to set up workers, and somehow only network interfaces of the "Linux Bridge" type shows up in the drop down list - my interfaces of the type "OVS Bridge" is not showing up in the drop down menu.
I checked the documentation on prerequisites and limitations, but there is no mention of different bridge types. It also is not possible to enter a VLAN in the dialogue box as well, as it is when creating regular VMs.
Has anyone else encountered these limitations, or am I just doing stuff wrong?
-
- Veeam Vanguard
- Posts: 28
- Liked: 8 times
- Joined: Sep 20, 2021 5:10 pm
- Full Name: Jonah May
- Contact:
Re: Proxmox VE workers
I had some similar issues when testing the beta a few weeks ago. Maybe things have changed between that build and GA, but I found that only Linux bridges and SDN vNets would show in Veeam. For Linux bridges the guidance I received was to select the bridge and during deployment go into Proxmox and manually set a vlan tag.
I'm coming from vSphere over to a fresh 8.2 cluster, so I ended up just creating SDN vNets as they function pretty closely to the dvPortGroups I'm used to.
I'm coming from vSphere over to a fresh 8.2 cluster, so I ended up just creating SDN vNets as they function pretty closely to the dvPortGroups I'm used to.
-
- Veeam Software
- Posts: 423
- Liked: 89 times
- Joined: Jul 03, 2023 12:44 pm
- Full Name: Rovshan Pashayev
- Location: Czechia
- Contact:
Re: Proxmox VE workers
Hello Andreas,
There is no support for Open vSwitch in V1. But we are assessing it for future releases.
Thank you for feedback.
There is no support for Open vSwitch in V1. But we are assessing it for future releases.
Thank you for feedback.
Rovshan Pashayev
Analyst
Veeam Agent for Linux, Mac, AIX & Solaris
Analyst
Veeam Agent for Linux, Mac, AIX & Solaris
-
- Service Provider
- Posts: 31
- Liked: 12 times
- Joined: Oct 27, 2011 8:42 am
- Full Name: Andreas Cederlund
- Location: Landskrona, Sweden
- Contact:
Re: Proxmox VE workers
Hi Rovshan,
Thanks for the information about OVS, this was my guess as well. Is this documented anywhere? If not, could you please update the information about this.
Is this also the case for VLAN support on the network interfaces?
Thanks for the information about OVS, this was my guess as well. Is this documented anywhere? If not, could you please update the information about this.
Is this also the case for VLAN support on the network interfaces?
-
- Enthusiast
- Posts: 67
- Liked: 31 times
- Joined: Dec 23, 2019 7:26 pm
- Full Name: Lick A Brick
- Contact:
Re: Proxmox VE workers
In my LAB I use a VLAN tag on the bridge I use for the worker, this is also not possible to enter from the Veeam wizard.
While the worker was in 'Waiting for IP/connection' (can't remember exact message) I manually changed the VLAN tag on worker VM and rebooted it so it would get the correct IP from DHCP.
Afterwards Veeam happily continued. I assume you can do the same, just create a dummy bridge, select it while creating the worker and switch it over manually to the correct bridge.
While the worker was in 'Waiting for IP/connection' (can't remember exact message) I manually changed the VLAN tag on worker VM and rebooted it so it would get the correct IP from DHCP.
Afterwards Veeam happily continued. I assume you can do the same, just create a dummy bridge, select it while creating the worker and switch it over manually to the correct bridge.
-
- Service Provider
- Posts: 11
- Liked: 3 times
- Joined: Mar 21, 2011 1:41 am
- Full Name: Andrew Morison
- Contact:
Re: Proxmox VE workers
Hi all,
We are considering moving to something like ProxMox.
Are we able to back-up the Virtual machines independent to the network, like we are with VMware?
We host many customers on completely independent Vlans, so there is no network connectivity with any of our management environment whatsoever.
Andrew.
We are considering moving to something like ProxMox.
Are we able to back-up the Virtual machines independent to the network, like we are with VMware?
We host many customers on completely independent Vlans, so there is no network connectivity with any of our management environment whatsoever.
Andrew.
-
- Product Manager
- Posts: 6535
- Liked: 762 times
- Joined: May 19, 2015 1:46 pm
- Contact:
Re: Proxmox VE workers
Hi,
v1 does not require any connection to VMs (except for the Worker VM).
You only need connections between VBR, worker(s), and PVE:
VBR ----> PVE
VBR ----> Worker
Worker ----> PVE
That's it.
Thanks!
v1 does not require any connection to VMs (except for the Worker VM).
You only need connections between VBR, worker(s), and PVE:
VBR ----> PVE
VBR ----> Worker
Worker ----> PVE
That's it.
Thanks!
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Sep 18, 2024 12:19 pm
- Contact:
[MERGED] Feature Request - Proxmox worker VLAN
Hi,
We have an environment where we use different subnets/VLAN for different component roles in Veeam.
When we deploy a Proxmox Worker, we can set the IP, DNS and Network (vmbr0) - but not a VLAN tag. (https://helpcenter.veeam.com/docs/vbpro ... html?ver=1)
Because of that, we get an error when it tries to reach the Worker and confirm/test that it was successfully deployed.
Right now our workaround is to deploy the worker and as it's deploying and before the timeout is reach, we need to manually set the VLAN on the Worker VM.
It would be really nice to have the possibility to set the VLAN in the Wizard, when deploying a Proxmox Worker.
Thanks
We have an environment where we use different subnets/VLAN for different component roles in Veeam.
When we deploy a Proxmox Worker, we can set the IP, DNS and Network (vmbr0) - but not a VLAN tag. (https://helpcenter.veeam.com/docs/vbpro ... html?ver=1)
Because of that, we get an error when it tries to reach the Worker and confirm/test that it was successfully deployed.
Right now our workaround is to deploy the worker and as it's deploying and before the timeout is reach, we need to manually set the VLAN on the Worker VM.
It would be really nice to have the possibility to set the VLAN in the Wizard, when deploying a Proxmox Worker.
Thanks
-
- Veeam Software
- Posts: 423
- Liked: 89 times
- Joined: Jul 03, 2023 12:44 pm
- Full Name: Rovshan Pashayev
- Location: Czechia
- Contact:
Re: Proxmox VE workers
Hello @gregersen
I moved your post to the existing FR Topic.
I moved your post to the existing FR Topic.
Rovshan Pashayev
Analyst
Veeam Agent for Linux, Mac, AIX & Solaris
Analyst
Veeam Agent for Linux, Mac, AIX & Solaris
Who is online
Users browsing this forum: No registered users and 2 guests