Why are vLan Numbers NOT used in vNIC migration out of pool....
-
We have seven virtual lans and each of course has a unique vLan number.
Two XCP-ng hosts that are not in the same pool, but have the same vLans.
Each virtual machine has multiple vLans.
When migrating a VM from one pool to another pool, the network interfaces become messed up and always fails unless all of the virtual NICs are disabled in the VM.
Since each virtual NIC on each VM has a unique numeric vLan number, is there a way to tell the systems to prioritize the matching algorithm based on numeric vLan id?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login