VMware vSphere

 View Only

  • 1.  Vms showing unkown and inaccissible

    Posted Aug 05, 2017 01:56 AM

    After I reboot San box and esxi hosts the data center note recognized by the hosts now the vms showing unkown and inaccessible  and could not get to vcenter. I can ping the data center but I can't brows to it via ssh or browser



  • 2.  RE: Vms showing unkown and inaccissible

    Posted Aug 06, 2017 07:14 AM

    Hi,

    This situation is when an ESXi host is rebooted or a host agent is restarted, it needs to reload the host agent configuration of each registered virtual machine (.vmx file). If the .vmx file is inaccessible, the ESXi/ESX host is unable to read the configured name of the virtual machine, and it defaults to Unknown VM.

    1. Can you access the esxi host with ping command? Can you access the VM with ping command?

    2. To re-register a virtual machine:

    1. Right-click the Unknown VM entry and click Remove From Inventory.
    2. Browse to the appropriate datastore for the virtual machine and open the folder.
    3. Right-click the *.vmx file and click Add to Inventory.
    4. Power on the virtual machine.
    5. Repeat Steps 1 to 4 for all unknown virtual machines.

    3. Reboot your ESXi, and the VM with inaccessible state should be move to another ESXi host.

    thanks



  • 3.  RE: Vms showing unkown and inaccissible

    Posted Aug 06, 2017 07:21 AM

    Thanks Greg bit the issue is I can't get to the data store o can ping it bit can't access it

    How I can connect the data store back? Note when I check the devices is says mounted but can't ssh or browse to it thru the browser.

    Any suggestions?



  • 4.  RE: Vms showing unkown and inaccissible

    Posted Aug 06, 2017 10:24 AM

    Welcome to the Community,

    please check whether vSphere handling of LUNs detected as snapshot LUNs (1011387) | VMware KB  helps.

    André



  • 5.  RE: Vms showing unkown and inaccissible

    Posted Aug 08, 2017 07:05 PM

    Andre,

    My question will be if i did add the storage back that will delete all data that i do have in the storage data center which i don't want to loose my vms.

    please check the pic that i did attached. to be able to see what I'm having



  • 6.  RE: Vms showing unkown and inaccissible

    Posted Aug 08, 2017 07:20 PM

    What do you see in vmkernel.log for those LUN's in question?

    If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points.

    Best Regards,

    Deepak Koshal

    CNE|CLA|CWMA|VCP4|VCP5|CCAH



  • 7.  RE: Vms showing unkown and inaccissible

    Posted Aug 08, 2017 07:28 PM

    Follow the "Command line" section in the KB article I mentioned. If the "esxcli storage vmfs snapshot list" returns the expected output (like the example in the article), you shouldn't have any issues with mounting the LUNs.

    If you are unsure, paste the command's output into a reply post.

    André



  • 8.  RE: Vms showing unkown and inaccissible

    Posted Aug 08, 2017 08:21 PM

    So, now im getting this error message that saying could not establish a network connection to the target.

    how I can resolve that. im just logged in as root to the esxi i can get to VC



  • 9.  RE: Vms showing unkown and inaccissible

    Posted Aug 08, 2017 08:23 PM

    Try this.

    Troubleshooting iSCSI LUN connectivity issues on ESX/ESXi hosts (1003681) | VMware KB

    If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points.

    Best Regards,

    Deepak Koshal

    CNE|CLA|CWMA|VCP4|VCP5|CCAH



  • 10.  RE: Vms showing unkown and inaccissible

    Posted Aug 06, 2017 11:56 AM

    It could be due to the underlying storage not being available or a snapshot LUN etc..

    Once the storage is recovered if the VMs are still reporting inaccessible/unknown please check the below linked KB.

    Inaccessible virtual machines are named as Unknown VM (2172) | VMware KB