Vlans in xen orchestra

I created a storage vlan 10. added it to the pool. I was able to add nfs shares to the hosts with no problem. I was not able to add a Remote for backup. After much debuggging and reading logs I realized it was because the remotes are mounted in XO and not the hosts. XO did not inherit vlan10 like the hosts. I manually configured vlan 10 on XO and Boom! The Truenas nfs share mounted and backups ran great! My question is what did I miss in the GUI setup? Is it expected to have have to use the command line? I presume not because this method will not survive a reboot. How should I have done this?

With everything on a common network it has worked forever. It was when I broke everything out into vlans that, well, broke it.

You would add an extra interface to your XO deployment on the network that has the proper VLAN you need for your remote.

That has been the only workaround I’ve been able to come up with.

I added the interface via the XO gui but I had to use the command line to assign an IP address to it. Only solution? Seems odd when a “separate storage network” is recommended.

I don’t believe there is another way in the GUI to do this because it is the VM that needs access to the network. Another thing to consider is that XOA doesn’t have to live on your xcpng stack. It can live anywhere outside of that. Like on truenas as a docker container.