Get-Disk | Select number, uniqueid
This will list all the disks (including LUNs if any) and its corresponding Unique ID (UUID)
Open Disk manager (diskmgmt.msc) to identify the Lun, Disk number and use the PowerShell output to fetch the unique ID (UUID)
VM migration error from one host to another host:
When I try to migrate a VM from one host to another host which is on a different cluster, I got the above error. Per VMware, this can be ignored.
Second error can also be ignored per VMware.
Things that continue to work if vCenter is down:
- Fault Tolerance will continue to work for the configured VMs. However, in case of a failover, no new secondary VMs will be created.
- HA will continue to work
- You can take snapshot of the VM by connecting to the ESXi host using vSphere client
- VMs will continue to work
- dvSwitch will continue to work
- vSwitch will continue to work
What will not work?
- vMotion will not work since vMotion requires vCenter server
- Storage vMotion will not work
- DRS will not work since DRS requires vMotion.
- You cannot deploy VMs from templates
- You cannot clone a VM
Sometimes when you search in VMware Vcenter, you get below error.
Login to the query service failed.
The server cold not interpret the communication from the client. (The remote server returned an error: (500) Internal Server Error.)
- Close the Vpshere client
- Open it again and uncheck Use Windows session credentials.
- Manually type the login credentials
- Now do the search
Manually type the login credentials.
Today one of the user reported that he is unable to connect to a VM. When I checked (VM -> edit settings -> I found the Network card was not connected. It was unchecked). I was unable to ‘check’ it. When I tried to check, I got the below error: Invalid configuration for device ‘0’.
VM -> Edit settings -> Remove the NIC card -> ok
VM -> Edit settings -> Add a NIC card -> ok
This resolved the issue.
If you get error while trying to login Vcenter via web UI and get this error.
If you click OK, you will find the Vcenter UI without any VMs. It will be all blank. You may need to check the service status of your Vcenter Inventory as the name suggests. In our environment, the Vcenter is an appliance. Also it is a VM. If your Vcenter is a Windows machine / VM then you can check services.msc.
To resolve this issue and you have Vcenter appliance. Open a Web browser and type the Vcenter IP with port 5480 (xxx.xxx.xxx.xxx:5480) and login.
Here you can start the inventory service as shown below:
Identify your Vcenter (Appliance) IP address:
Strangely though Vpshere client functions without any issue and only Web UI faces this issue. Login to Vsphere client, and open the Vcenter appliance console.
This is a simplest way. Click the Vcenter appliance in the Vsphere client and click summary. You can see the IP address.