Hi,
have you tried to connect the VM to the same network (and also change IP if needed) as where you have the hypervisor management interface and the CVMs?
If that is not working you can focus on troubleshooting the VM.

Then open a support case with Nutanix, they are really awesome.

thanks

//Magnus

recently in our company they got nutanix and VM.

I run ping db-server-name from my application server.

When I checked the Event viewer of my application Server. there is Communicaiton Link error. ie. while connecting to my database server.

When i check the time of the error and the ping status. Before communication comes, there was Request time out in my ping status.

The company which implemented said, they check Vm and Nutanix and found no errors…But recently they say in cisco switch it has old OS. This might be the reason.

In the same switch I have fixed one physical server. Which is not having single request timed out.

What u feel might be the case.

regards

I don’t see any problem of using datastore heartbeat in the Metro Availability scenario. The promote option will change the ownership of the container and make it possible for the site to manage read/write operations for that container. Metro Availability relies on vSphere HA to VM manage failover so the VM will be restarted on the new active site.

We will release a lot more details when the feature is GA so stay tuned.

//Magnus

Thank you for the fast response! next questions are coming 🙂
so datastore hearbeating must be disabled on the cluster, right?
promote will mount the nfs datastore on the nodes when I select promote?
When I perform a negoiated failover (during normal operation) the nfs datastore will be dismounted on the primary site, right? does nutanix rely therefore on the HA events triggered by the ESX Cluster or are they actively triggered by the cvms?

Hi, Good questions.
A manual interaction or scripted solution is required to activate the Nutanix Container (vSphere NFS Datastore) on the remote site when the primary site fails. You might end up in scenarios where a VM lives on one site and access it’s data over the wire meaning affinity rules might be necessary. Configuration recommendations will be released when the feature is GA early next year.

Thanks