{"id":230,"date":"2019-04-15T09:33:47","date_gmt":"2019-04-15T07:33:47","guid":{"rendered":"https:\/\/vmoller.dk\/?p=230"},"modified":"2019-07-03T07:25:09","modified_gmt":"2019-07-03T05:25:09","slug":"vsan-health-hosts-with-connectivity-issues","status":"publish","type":"post","link":"https:\/\/vmoller.dk\/index.php\/2019\/04\/15\/vsan-health-hosts-with-connectivity-issues\/","title":{"rendered":"vSAN Health: \u201cHosts with connectivity issues\u201d"},"content":{"rendered":"\n<p>I have lately been involved in two vSAN installation that had this alert in vSAN Health pane.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"551\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2019\/04\/HealthCheckError-1024x551.jpg\" alt=\"\" class=\"wp-image-232\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2019\/04\/HealthCheckError-1024x551.jpg 1024w, https:\/\/vmoller.dk\/wp-content\/uploads\/2019\/04\/HealthCheckError-300x161.jpg 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2019\/04\/HealthCheckError-768x413.jpg 768w, https:\/\/vmoller.dk\/wp-content\/uploads\/2019\/04\/HealthCheckError.jpg 1137w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption>Hosts with connectivity issues<\/figcaption><\/figure>\n\n\n\n<p>Another side effect is that the hosts on the warning list is unable to enter maintenance mode.<\/p>\n\n\n\n<!--more-->\n\n\n\n<p>Both environments were running on Lenovo servers and with Lenovo RAID controllers and was recently updated to ESXi 6.7 update 1. The problems started a few days after \u201cupdate 1\u201d was installed.<\/p>\n\n\n\n<p>After a couple of conversations with VMware support, they finally discovered that the error lies in the way that ESXi uses the \u201cStorCLI\u201d utility, that we installed earlier to make sure that Health Check is able to check the storage controller firmware version.<br><\/p>\n\n\n\n<p>Since we know that the storage controller is supported, we decided to remove the StorCLI utility and that solved the problem!<\/p>\n\n\n\n<p>Steps involved (on all hosts, one at a time):<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Put the host in maintenance mode \u2013 if it refuses then run this command on the host: \u201c\/etc\/init.d\/vsanmgmtd restart\u201d and try again<\/li><li>When the host has entered maintenance mode, uninstall StorCLI with the following command: \u201cesxcli software vib remove -n vmware-storcli-007.0405.0000.0000\u201d<\/li><li>The version number can be different \u2013 you can use \u201cesxcli software vib list\u201d to find the exact version number.<\/li><li>Reboot<\/li><\/ul>\n\n\n\n<p>If you want to know why we initially install StorCli you may look at my colleagues blog over here: <a aria-label=\"https:\/\/www.virtual-allan.com\/vsan-health-and-controller-firmware-n-a\/ (opens in a new tab)\" href=\"https:\/\/www.virtual-allan.com\/vsan-health-and-controller-firmware-n-a\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/www.virtual-allan.com\/vsan-health-and-controller-firmware-n-a\/<\/a><\/p>\n\n\n\n<p>Please note that this bug is not related exclusively to Lenovo servers, since other vendors uses the same controller chips and StorCLI utility.<br><\/p>\n\n\n\n<p>VMware has confirmed that they are working on fix.<\/p>\n\n\n\n<p><em>Update 3\/7-2019:<\/em><br>VMware has published an KB on this subject: <a aria-label=\" (opens in a new tab)\" rel=\"noreferrer noopener\" href=\"https:\/\/kb.vmware.com\/s\/article\/68149\" target=\"_blank\">KB68149<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>I have lately been involved in two vSAN installation that had this alert in vSAN Health pane. Another side effect is that the hosts on the warning list is unable to enter maintenance mode.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[20,6,8,7],"tags":[32,23,26,33,4],"class_list":["post-230","post","type-post","status-publish","format-standard","hentry","category-esxi","category-vmware","category-vsan","category-vsphere","tag-connectivity-issues","tag-esxi","tag-vsan","tag-vsanhealth","tag-vsphere"],"_links":{"self":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/230","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/comments?post=230"}],"version-history":[{"count":9,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/230\/revisions"}],"predecessor-version":[{"id":273,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/230\/revisions\/273"}],"wp:attachment":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/media?parent=230"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/categories?post=230"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/tags?post=230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}