Idea ID 1642001
In our production environments we heavily utilize VLAN trunk ports for our virtual host servers in order to serve the various virtual machines running on the physical server. In my many cases, the virtual machines reside on different networks and as a result, we set the VLAN ID for the virtual NIC using Hyper-V Manager settings for the virtual machine.
Currently, MicroFocus VMExplorer allows you to select the destination virtual network adapter name as part of the replication job settings, but the option to map the VLAN ID is NOT available.
- We use VLAN trunk ports for all of our virtual machine deployments
- Can the ability to set the destination VLAN ID be added to your software?
This feature will make the replication fail over process much easier and user error free. I am hoping to provide step by step replication fail over instructions to users with a limited techincal background and if I need to incorporate detail about manually checking & setting the VLAN ID after the replicated VM is turned on, this will make the fail over procedure much more complicated for the non-technical staff and also requires me to open up Hyper-V manager access to these users with the limited techincal background. I prefer to keep Hyper-V manager access locked down as much as possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.