VMs will be shown as inaccessible in the vCenter

-



Reason
A VM can become inaccessible due to any of the below reason:

  1. Issue with the ESXi servers
  2. Issue with the vCenter
  3. Issue with the datastore

Resolution
In all the three cases these are the below three troubleshooting steps:
First step will be to restart the management agents in the ESXi.
  • Login to the ESXi using SSH
  • Run any of the below commands to restart the management agents
/etc/init.d/hostd restart
/etc/init.d/vpxa restart

OR

services.sh restart

If this step did not resolve the issue for you, try the second step
Second step will be to remove the VM from the inventory and add using the vmx
file
  1. Right click on the affected VM
  2. Choose the option 'Remove from the Inventory' (Be cautious about this action...Do not delete the VM)
  3. After this step, go to the vmx location of the VM
  4. Right click on the VM and 'Add to the Inventory'
This step will definitely resolve your issue. But this step works fine only when we
know the vmx location of the VM. If you are not sure about the vmx location you
will end up in adding incorrect VMs.
Keep in your mind that you cannot access the vmdk location to find the vmx path
when the VM is inaccessible.
In these kind of situations, the best method is to use command line, the third
step!!!
  • Login to the ESXi hosting the inaccessible VM using SSH
  • Run the below command to know the vmid of the VMs in the host
vim-cmd vmsvc/getallvms




You will receive a message "Skipping invalid VM '144' " along with the details of
valid VMs.
The skipped VM will be the invalid one. The value '144' represents the vmid of the
VM.
  • Now run the below command to reload the invalid VM
vim-cmd vmsvc/reload vmid where vmid is the id of the invalid VM

Comments

Post a Comment

Popular posts from this blog

esxi-host-shows-disconnected-vmware

-
Symptom: The host and VMs in a vcenter server appears to be disconnected. Issue: The host and its corresponding vms could appear as disconnected due to issue with any of the following services. vpxa - a service which runs in the esxi host. This service communicates with vcenter server. hostd - core service which runs in the esxi host vpxd - a service which runs in the vcenter server which communicates with the vpxa Resolution: 1. Try to ping the ESXi host. This ensures that the host is reachable 2. Ensure you can login to the VMs remotely. This ensures that VMs in the host are working fine. 3. Try to login to the ESXi host using vsphere client. This ensures that the hostd services are running perfectly. If this step fails, restart the hostd service using putty. 4. If the above three steps worked fine for you, the issue would be with the vpxa or vpxd service. In that case, first try to restart the vpxa service in the host and if that didnot resol
Read more

ESXi : Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic0 is down

-
We had an issue suddenly getting an alert : Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic0 is down. Affected portgroups:"vMotion", "Management Network". So as a troubleshooting Select the ESXi host effected Click on Configuration, Select Networking, Click on vSwitch0 Properties,Click on Network adapters Select on vmnic0, Click on remove, Click on Close Again Select Networking, Click on vSwitch0 Properties,Click on Network adapters, Click on Add, Select the vmnic0, Click on Next, Click on Next, Click on Finish Now Click on Ports tab of vSwitch Properties, Select on vMotion, Click on Edit, Click on NIC Teaming, Select on vmnic1, Click on Moveup button  to Active Adapters, Select on vmnic0, Click on Move Down to Standby Adapters, Click on OK Now Click on Ports tab of vSwitch Properties, Select on Management Network, Click on Edit, Click on NIC Teaming, Select on vmnic1, Click on Moveup button  to Active Adapters, Select o
Read more

Virtual machines appear as invalid or orphaned in vCenter Server

-
Symptoms Virtual Machines show as invalid or orphaned in vCenter Server Virtual Machines show as invalid or orphaned after a VMware High Availability (VMware HA) host failure occurs Virtual Machines show as invalid or orphaned after an ESX host comes out of maintenance mode Virtual Machines show as invalid or orphaned after a failed DRS migration Virtual Machines show as invalid or orphaned after a storage failure Virtual Machines show as invalid or orphaned after the connection is lost between the vCenter Server and the host where the virtual machine resides You see one or more of these errors when trying to start a virtual machine: Could not power VM, no swap file, failed to power on VM. VMControl error -11: No such virtual machine. A general system error occurred. The system returned on error. Communication with the virtual machine may have been interrupted In   C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log   file, you see entries similar to: [11916 error
Read more