VMware vSphere

 View Only
Expand all | Collapse all

Host become Not Responding

  • 1.  Host become Not Responding

    Posted Dec 14, 2012 03:37 AM

    My Host B state become Not responding. but I still able to remote access by putty. How to solve this?



  • 2.  RE: Host become Not Responding

    Posted Dec 14, 2012 07:50 AM


  • 3.  RE: Host become Not Responding

    Posted Dec 14, 2012 08:52 AM

    But I can ping and access to the host? I restrat also same..



  • 4.  RE: Host become Not Responding

    Posted Dec 14, 2012 08:10 AM

    do you have a firewall in place between that host and your vCenter?

    have you tried to restart the management agents on the Host?



  • 5.  RE: Host become Not Responding

    Posted Dec 14, 2012 08:53 AM

    Nope. I disable all my firewall. I restart also same..



  • 6.  RE: Host become Not Responding

    Posted Dec 14, 2012 09:48 AM

    Are you hosts the same,  ie both DB380's

    do you have the same NIC cards in both?



  • 7.  RE: Host become Not Responding

    Posted Dec 14, 2012 04:39 PM

    My hostname is not the same.

    I use the built in NIC card HP DL380 G5



  • 8.  RE: Host become Not Responding

    Posted Dec 14, 2012 10:09 AM

    Are you able to connect to the host using vsphere client ?

    If you are  not able to, then it clearly states that the hostd agent of the server is not responding. That is the very reason it is seen as not responding in vcenter.

    You can try browsing the datastores from ssh if it gets stuck at the prompt then that is the reason for the hang of hostd agent.

    If the host is seeing any storage related issue or any hangs in the network then the host would get into a not responding state.

    you can review the vmkernel logs then it should tell us the reason for the hostd hang.

    --Nitin     



  • 9.  RE: Host become Not Responding

    Posted Dec 14, 2012 04:41 PM

    I able to connected. But this one just show in my web client.

    I using putty to connect. I can access to ESXi host.



  • 10.  RE: Host become Not Responding

    Posted Dec 14, 2012 12:33 PM

    This is often an issue with an incorrect or not working name resolution (DNS). Please verify the host can resolve the vCenter Server's short and FQDN name and vice versa.

    André



  • 11.  RE: Host become Not Responding

    Posted Dec 14, 2012 04:43 PM

    The DNS I use on host A and host B is the same. So nothing wrong in Host A.  I don't think is a DNS problem.

    For my environment

    I use DL380 G4 as the Domain Controller and DNS Server.

    DL 380 G5 as ESXi01

    DL 380 G6 as ESXi02

    A Laptop HP Pavillion (Windows Server 2008 R2) - 8GB RAM and Intsall vCenter on it..



  • 12.  RE: Host become Not Responding

    Posted Dec 14, 2012 04:51 PM

    The DNS I use on host A and host B is the same. So nothing wrong in Host A.  I don't think is a DNS problem.

    Are you able to access the Host A using name from your vCenter server



  • 13.  RE: Host become Not Responding

    Posted Dec 14, 2012 05:13 PM
    ...  I don't think is a DNS problem.

    Well, can you confirm it's not a DNS issue? To rule this out as a  possible issue, please double check the settings and try to ping the host from your vCenter Server and vice versa using the name and FQDN.

    André