{"id":2057,"date":"2011-02-12T11:35:11","date_gmt":"2011-02-12T10:35:11","guid":{"rendered":"http:\/\/vmdamentals.com\/?p=2057"},"modified":"2011-02-12T11:35:11","modified_gmt":"2011-02-12T10:35:11","slug":"update-from-esx4-1-to-update1-fails-with-vim-fault-nohost","status":"publish","type":"post","link":"https:\/\/www.vmdamentals.com\/?p=2057","title":{"rendered":"Update from ESX4.1 to update1 fails with &#8220;vim.fault.noHost&#8221;"},"content":{"rendered":"<p><BR><\/p>\n<blockquote><p>Today I decided to update my home lab from vSphere 4.1 to vSphere 4.1u1. Updating vCenter went smoothly. Once I tried to update the first ESX node in the cluster using VMware Update Manager (VUM), it failed with the error &#8220;vim.fault.noHost&#8221;.\n<\/p><\/blockquote>\n<p>Say what? Googling the error did not give away too much detail; all posts on this were way back in the ESX 3.5 times. I hate when this happens. So what to do? Yes I still run ESX in my homelab (I like boot from SAN way too much ;). So off to the logging.<\/p>\n<p>It had been some time since I looked at ESX logs in detail; the amount of &#8220;verbose errors&#8221; are enormous&#8230;. Anyway, it seemed to have something to do with the way vCenter talks (or rather fails in talking) to the node&#8230;<\/p>\n<p>First I tried rebooting the node, then run VUM again to remediate the node agian&#8230; But again it failed. Finally I just removed the node from the cluster (via a hard &#8220;disconnect&#8221; followed by a remove), then re-added the node. After this, the node remediated without issue.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Today I decided to update my home lab from vSphere 4.1 to vSphere 4.1u1. Updating vCenter went smoothly. Once I tried to update the first ESX node in the cluster using VMware Update Manager (VUM), it failed with the error &#8220;vim.fault.noHost&#8221;. Say what? Googling the error did not give away too much detail; all posts [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[278,277,281,24,279,284,280,632,283,99,282],"class_list":["post-2057","post","type-post","status-publish","format-standard","hentry","category-vmware","tag-4-0-update-1","tag-4-0u1","tag-error-updating","tag-esx","tag-update-1","tag-update1","tag-vim-fault-nohost","tag-vmware","tag-vmware-update-manager","tag-vsphere","tag-vum"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts\/2057","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2057"}],"version-history":[{"count":3,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts\/2057\/revisions"}],"predecessor-version":[{"id":2060,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts\/2057\/revisions\/2060"}],"wp:attachment":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2057"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2057"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2057"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}