Repository navigation
ProxyVM in Shared network with management fails test #5
Description
Hi ShapeBlue team,
We are on CS 4.22.1.0 with the Veeam Integration patch applied, cloudstack veeam.integration configuration all appears to be ok.
We are attempting to test Veeam Integration.
Veeam is VSA virtual appliance version 13.1.1.18 with a Windows VBR console installed on a separate VM that talks to the VSA.
- Veeam Ovirt KVM is configured ok. Can see storage, cluster, vms.
- We have Shared network in management vlan, using DefaultSharedNetworkOffering that has these supported services
Dhcp : VirtualRouter
Dns : VirtualRouter
UserData : VirtualRouter - ProxyVM gets successfully deployed and boots ok and stays running for approx 10 mins
- We deployed a Windows vm and same Client network and observed that we can ping CS-MGMT, can ping KVM hosts but could not ping the assigned vbrproxy vm IP address.
- We tried both a DHCP assigned and a statically assigned VBR worker Proxy vm address. Same scenario.
- After 10 mins the Test of worker VM inside Veeam VBR console times out and fails with errors below - after it fails the CloudStack worker vm is destroyed along with the Volume.
cloudstack-management.log is extremely verbose and difficult to find where if any errors have occurred there.
Please assist.
Rod
Activity
nvazquez commentedon Oct 28, 2026
Hi @notdrowningworking can you please create a new Shared offering using ConfigDrive as the UserData provider? This is a known issue and we raised a documentation PR so it can be reflected in the next versions documentation: apache/cloudstack-documentation#682
notdrowningworking commentedon Oct 29, 2026
Hi @nvazquez
Thank you for that. That certainly made a difference.
However, the vbrproxy test ended in another error. It's trying to contact the VBR server on port 10006.
What could this be?
The VSA (VBR) is listening on that port, checking firewall to see if this port is being blocked
notdrowningworking commentedon Oct 29, 2026
All fixed. Tried the worker VM in the VBR network (same subnet) and then the VBR ProxyVM test worked. So we figured there was a firewall blocking the original network test above. We have 2 ProxyVMs in 2 different networks that are working. We successfully backed up and restored a vm.
nvazquez commentedon Oct 29, 2026
Great to know @notdrowningworking - thanks for letting us know