Replies posted by arjun_sen
Hello there,Failover clustering is supported on AHV by enabling MPIO on Guest OS Windows Server level.Leveraging MPIO enables the Guest to completely takeover the control for ability to determine which failover peer should write on the shared vDisk. Following documentation lists out the steps to leverage Volume Group from Nutanix Cluster to be presented to the VMs for configuring In-Guest clustering.https://portal.nutanix.com/#/page/docs/details?targetId=Advanced-Admin-AOS-v510:vmm-failover-cluster-create-t.html (Access to support portal required)
Hi @Neel Kotak @JESUS19 The above tests suggests to check if the dvsdata.db directory is present in Esxi host. When an ESXi host boots it will get the data required to recreate the VDS structure locally by reading /etc/vmware/dvsdata.db and from esx.conf. You can view the dvsdata.db file yourself by doing:(This location is held by the Host ramdisk which is non-persistent) net-dvs -f /etc/vmware/dvsdata.db Secondly, the VMFS volume that holds a working directory (place where CVM .vmx is stored) that is connected to a VDS will have the following folder: drwxr-xr-x 1 root root 420 Feb 8 12:33 .dvsData If you go to this folder you will see another folder. This folder appears to be some sort of unique identifier, and when comparing the string to the output of “net-dvs” it appears to be the identifier of the dvSwitch that was created. drwxr-xr-x 1 root root 1.5k Feb 8 12:47 6d 8b 2e 50 3c d3 50 4a-ad dd b5 30 2f b1 0c aa Within this folder you wil
Login to the community
Login with your account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.