<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Host in not responsing state in ESXi-Arm Fling Members</title>
    <link>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2856907#M79</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This doesn't sound ESXi on ARM specific... but...&lt;/P&gt;&lt;P&gt;1) you could try restart hostd and vpxa services on the host.&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/1003490" target="_blank"&gt;https://kb.vmware.com/s/article/1003490&lt;/A&gt;&lt;/P&gt;&lt;P&gt;That may get the host to reconnect to VC...&lt;/P&gt;&lt;P&gt;2) If not, you can power off and unregister the VM's using cli and then register them back and power on on the remaining hosts... this will result in a controlled down time...&lt;BR /&gt;&lt;BR /&gt;3) Assuming you have HA enabled on your cluster; if you reboot the host anyway; the VMs will get failed over and powered on to a new host when that host goes down, this is less of a controlled outage, but the VM movement and power on should be automated...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope one of the 3 options helps...&lt;/P&gt;&lt;P&gt;vFouad&lt;/P&gt;</description>
    <pubDate>Mon, 12 Jul 2021 13:27:43 GMT</pubDate>
    <dc:creator>vFouad</dc:creator>
    <dc:date>2021-07-12T13:27:43Z</dc:date>
    <item>
      <title>Host in not responsing state</title>
      <link>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2856902#M78</link>
      <description>&lt;P&gt;Hello Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One of ESXi host is in not responding state in vcenter.&lt;/P&gt;&lt;P&gt;we have three host cluster.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are VM running on all the three host .&lt;/P&gt;&lt;P&gt;Now, we need to shutdown esxhost2&amp;nbsp; for h/w activity.?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How can I move VM from esxhost2 as this host will not go in maintenance state , nor vmotion will work&lt;/P&gt;&lt;P&gt;as esxhost is " disconnected from&amp;nbsp; vcenter"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;any idea to minimise downtime ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Sumit&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jul 2021 13:21:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2856902#M78</guid>
      <dc:creator>sumit_vmw</dc:creator>
      <dc:date>2021-07-12T13:21:48Z</dc:date>
    </item>
    <item>
      <title>Re: Host in not responsing state</title>
      <link>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2856907#M79</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This doesn't sound ESXi on ARM specific... but...&lt;/P&gt;&lt;P&gt;1) you could try restart hostd and vpxa services on the host.&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/1003490" target="_blank"&gt;https://kb.vmware.com/s/article/1003490&lt;/A&gt;&lt;/P&gt;&lt;P&gt;That may get the host to reconnect to VC...&lt;/P&gt;&lt;P&gt;2) If not, you can power off and unregister the VM's using cli and then register them back and power on on the remaining hosts... this will result in a controlled down time...&lt;BR /&gt;&lt;BR /&gt;3) Assuming you have HA enabled on your cluster; if you reboot the host anyway; the VMs will get failed over and powered on to a new host when that host goes down, this is less of a controlled outage, but the VM movement and power on should be automated...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope one of the 3 options helps...&lt;/P&gt;&lt;P&gt;vFouad&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jul 2021 13:27:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2856907#M79</guid>
      <dc:creator>vFouad</dc:creator>
      <dc:date>2021-07-12T13:27:43Z</dc:date>
    </item>
    <item>
      <title>Re: Host in not responsing state</title>
      <link>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2856908#M80</link>
      <description>&lt;P&gt;Hi Sumit,&lt;/P&gt;&lt;P&gt;I'm not a specialist of vCenter, but have you tried to reconnect the host to vCenter? I do that with right click on the host -&amp;gt; connection -&amp;gt; (re)connect.&lt;/P&gt;&lt;P&gt;Cyprien&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jul 2021 13:27:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2856908#M80</guid>
      <dc:creator>cyprienlaplace</dc:creator>
      <dc:date>2021-07-12T13:27:49Z</dc:date>
    </item>
    <item>
      <title>Re: Host in not responsing state</title>
      <link>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2856912#M81</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I already tried&amp;nbsp; restarting agent and it didnot&amp;nbsp; help.&lt;/P&gt;&lt;P&gt;even manual connect didnot work .&lt;/P&gt;&lt;P&gt;I noticed that esxcli commands are not responding on esxi hosts&amp;nbsp; and there are storage related errors in logs.&lt;/P&gt;&lt;P&gt;So, we need to being down the host.&lt;/P&gt;&lt;P&gt;vcenter HA is not configured&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Sumit&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jul 2021 13:53:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2856912#M81</guid>
      <dc:creator>sumit_vmw</dc:creator>
      <dc:date>2021-07-12T13:53:09Z</dc:date>
    </item>
    <item>
      <title>Re: Host in not responsing state</title>
      <link>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2900596#M150</link>
      <description>&lt;P&gt;what if you restart the vCenter server appliance?!&lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2022 12:43:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2900596#M150</guid>
      <dc:creator>rajesharihant</dc:creator>
      <dc:date>2022-03-25T12:43:28Z</dc:date>
    </item>
    <item>
      <title>Re: Host in not responsing state</title>
      <link>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2900598#M152</link>
      <description>&lt;P&gt;Try to disconnect and remove from the inventory of the vCenter then added again this should not impact any VM or the host it self&lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2022 12:47:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2900598#M152</guid>
      <dc:creator>Ahmedkhalaf</dc:creator>
      <dc:date>2022-03-25T12:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: Host in not responsing state</title>
      <link>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2900599#M153</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5490585"&gt;@Ahmedkhalaf&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you are unable to connect to the host and cannot restart vpxa agents, you will not be able to move the VMs to another host. You will have to shut down the VMs from guest side and reboot the host afterwards.&lt;/P&gt;&lt;P&gt;Sorry for the bad news.&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2022 13:16:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2900599#M153</guid>
      <dc:creator>stadi13</dc:creator>
      <dc:date>2022-03-25T13:16:43Z</dc:date>
    </item>
    <item>
      <title>Re: Host in not responsing state</title>
      <link>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2923312#M171</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/4741420"&gt;@sumit_vmw&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Before reboot,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the error message once you try to reconnect the host? Do you have a Lockdown mode on? IF so it will prevent hosts to reconnect. You need to go to the console via iDrac/ILO/CMCI and disable it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, try manually resetting&amp;nbsp;&lt;SPAN&gt;vpxa:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Log in to ESXi Shell or SSH as&amp;nbsp;root&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;/etc/init.d/hostd restart&lt;BR /&gt;&lt;BR /&gt;/etc/init.d/vpxa restart&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;OR restart all management services:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;services.sh restart&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If none of the above helped then the only way to recover is hosts reboot and you will get downtime. There is no way to vMotion VMs if hosts is not connected to vCenter.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Aug 2022 09:48:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Arm-Fling-Members/Host-in-not-responsing-state/m-p/2923312#M171</guid>
      <dc:creator>ptarnawski</dc:creator>
      <dc:date>2022-08-11T09:48:54Z</dc:date>
    </item>
  </channel>
</rss>

