Skip to main content
  • EN

Hi all,

my environment is VMware vSphere with 2 clusters managed by a single vCenter Server using Distributed Virtual Switch.

Cluster 1 Production

Cluster 2 DR

All VM are replicated from Cluster 1 to Cluster 2, the problem is all VMs int the destination, have the same Port ID associated to the Port Group of the source. This is a problem, because vSphere expect different values. When I try a migrate of a replica VM, I cannot do that, I obtain the error message: “A general system error occurred: vDS host error: see faultCause Cannot create DVPort 5021 of VDS dvSwitch0 on the host xyz”

I need to create new Port ID for every VM replicated or find a solution to fix this default behavior.

Please help me!

Best regards.

 

First thing that comes to mind is change the DV portgroup to ephemeral, no port ID's ;)
the one drawback of this is that the vCenter needs to be online and reachable for a VM to connect to the DV. So if you run the vCenter on the DR side, you will be fine.

That could be a great idea, I was just thinking about it as “planB”. I have 200 Port Groups this could be quite easy to do. I don’t know if there are some side effects….could it be made hot? without outage?

 

I confirm, my vCenter Server runs on the DR site.

Hi @Michele -

I was just following up on your post. Did the provided comment help answer your question? If so, we ask you please mark it as ‘Best Answer’ so others with a similar question who come across your post may benefit. If you do still have questions, don’t hesitate to ask.

Thank you.

Hi all,

no one has provided a solution. Changing Distributed Port Group to ephimeral, is something you cannot change on-the-fly, it requires to create doubled dPG. So this is not the way.

My solution: I’ve done a PowerCLI script that obtains for each VM, the network config (MAC, dPG, network card type), it removes it and recreates a new one with the exact config. This has been run on every _replica VMs.

This task has created a new Port ID for every VM, and this has solved the problem. Unfortunately, I need to run it every time I add some new VMs...not very flexible, but it works.

Cheers.

Ah, ok. Good to hear you found a workaround @Michele . A suggestion for you is maybe offer a feature request or suggestion on the Veeam Forums for the Product Managers to comment on the potential of adding that functionality.

Go ahead and mark your comment as ‘Best Answer’ as what you did seems the best “solution” to your query.

Thank you.

Comment


Terms & Conditions