Error: "Datastore "XXX" conflicts with an existing datastore"

  PROBLEM Recently I tried to upgrade one of my ESXi hosts from version 6.7 to 7.0 using VMware Lifecycle Manager. The upgrade gets stuck at 47%. However, when I take the remote console using iLO, I see the ESXi is already upgraded. The LCM Events and logs show that vCenter is not able to connect to the host.  I tried to connect the Host manually and got the below error: Datastore "XXX" conflicts with an existing datastore in the datacenter that has the same URL "UUID", but it is backed by different physical storage. RESOLUTION 1.     Check if the all the vmhba are visible: Run this command to see all vmhba - esxcfg-scsidevs -a or esxcli storage core adapter list 2.     Check if the vmhba drivers are compatible. In my case smartpqi driver had to be upgraded to latest version. (Microchip-smartpqi_70.4054.2.118-1OEM.700.1.0.15843807_17871815) 3.     Check if the datastore is accessible and visble from ESXi UI or ESXCLI. 4.     Remove the host from

All shared datastores failed on the host

  Sometimes post creating a new cluster or after re-configuring the existing cluster you might get an error on ESXi “All shared datastores failed on the host”  this can happen to you very often if you are running on HPE StoreVirtual VSA. Please follow the below steps to fix this error: 1.     At the very onset, Reconfigure the HA for the cluster. Disable and re-enable HA on Cluster Level or Right Click Host and select Reconfigure for vSphere HA. 2.     If the error still persists, then follow the next steps. 3.     Make sure you migrate all the VMs manually on the other host if the DRS is disabled on the cluster. 4.     If you have any VM running on ESXi local Datastore like HPE StoreVirtual Appliance (VSA) or Backup Proxy VM, ensure to gracefully shut them down. (For How to shutdown HPE VSA gracefully follow this KB ) 5.     Now, put the host in Maintenance Mode. 6.     Right Click Host and Remove from Inventory 7.     After the host is removed, Right Click on the cluster and click A

How to Downgrade a VIB/Driver in ESXi 7

  There are two methods to downgrade a VIB or a device driver in ESXi Host. 1.     Uninstall the current or upgraded driver > reboot the host > Install the downgrade driver OR 2.     You may also install the downgrade driver directly using esxcli software vib install command. This will remove the upgraded driver itself. Let's see how to perform downgrades of vib using both methods. You may decide which one you would like to choose. You may also install drivers using Baselines in Lifecycle Manager, which will be covered in later posts. Method 1 : Uninstall the current or upgraded driver > reboot the host > Install the downgrade driver Put the ESXi host in Maintenance Mode. SSH the ESXi host Run this command to uninstall the driver: " esxcli software vib remove -n <vib_name> " Reboot the host Run this command to install the driver: " esxcli software vib install -d /vmfs/volume/datastore/ "   Reboot the host Run this command to

How to Change Hostname, IP, or DNS on vRealize Operations Manager appliance 6.x\7.x\8.x

  Recently I had to perform rename of a few virtual appliances according to new naming conventions adopted by the organization. Going down the list I had my vROPS 8.0 to be renamed which is a VMware Photos OS appliance. Here, I bring you a simple way to rename or change your hostname, IP, Netmask, Gateway, or DNS of your VMware appliances using just one command: 1.     First and foremost, Login to vROPS admin console and bring the cluster offline. 2.     SSH into your appliance using root. 3.     Copy and paste the below command to open the vami config tool- /opt/vmware/share/vami/vami_config_net 4.     Choose option 0 to show current configurations or directly Choose Option 3 to change Hostname 5.     Enter new Hostname and reboot 6.     You may also choose other options such as changing DNS, Gateway or IP as per your requirement. If you rename the hostname, I recommend performing a Storage vMotion which renames the folder and files of the associated appliance accordingl

How to fix vCenter UI Alarm: Certificate Status

If you are also wondering, why does the below alarm appear on your vCenter UI? You also have no expired certificate in vCenter UI Certificate Management. Find the below steps to investigate further: 1.     SSH into you vCenter Appliance using root credentials Run any of the below commands to find out all the certificates and their expiration dates: vp="/usr/lib/vmware-vmafd/bin/vecs-cli";sp="openssl x509 -noout";for s in $($vp store list | grep -Ev "* CRLS");do echo "[ $s ]";$vp entry list --store $s | awk '/^Alias :/{alias=$(NF);printf "%s\n",alias;}' | while read ca;do print f "\t[ $ca ]\n";c=$($vp entry getcert --store $s --alias $ca);ct=$(echo "$c" | $sp -text);fp=$(echo "$c" | $sp -fingerprint);ec ho "$ct"|awk -v fp="$fp" '/Before/{gsub(/^[ \t]+/,"",$0); split($0,b,":");}/After/{gsub(/^[ \t]+/,"",$0); split($0,af,":");}/Is sue