{"id":150,"date":"2018-11-17T21:53:50","date_gmt":"2018-11-17T19:53:50","guid":{"rendered":"https:\/\/vmoller.dk\/?p=150"},"modified":"2018-11-17T22:37:41","modified_gmt":"2018-11-17T20:37:41","slug":"vsan-health-check-reports-n-a-with-lenovo-n2215-hba","status":"publish","type":"post","link":"https:\/\/vmoller.dk\/index.php\/2018\/11\/17\/vsan-health-check-reports-n-a-with-lenovo-n2215-hba\/","title":{"rendered":"vSAN Health check reports N\/A with Lenovo N2215 HBA"},"content":{"rendered":"<p>A couple of days ago I was visiting a customer to setup their Lenovo host to run vSAN \u2013 after the initial setup of vSAN kernel IPs, disk groups and so on, I took a look at the \u201cVSAN Health check\u201d to make sure that everything was healthy and supported.<\/p>\n<p>Under the \u201chardware compatibility\u201d part all checkmarks where green, but the Controller firmware version was not detected \u2013 so I did found it a bit strange that it reports the disk controller as supported without knowing what version it actually was running.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-161\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/Controller-is-FW-is-certified.jpg\" alt=\"\" width=\"313\" height=\"29\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/Controller-is-FW-is-certified.jpg 313w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/Controller-is-FW-is-certified-300x28.jpg 300w\" sizes=\"auto, (max-width: 313px) 100vw, 313px\" \/><br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-159\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/controller-NA.jpg\" alt=\"\" width=\"358\" height=\"43\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/controller-NA.jpg 358w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/controller-NA-300x36.jpg 300w\" sizes=\"auto, (max-width: 358px) 100vw, 358px\" \/><\/p>\n<p>This issue is not new to me, as I have seen it a couple of times before, but this time it was different after all.<\/p>\n<p><!--more--><\/p>\n<p>Normally when I setup Lenovo servers for vSAN I need to install the StorCLI to be able to see the firmware version of the disk controller \u2013 that is normal for LSI based disk controller and is documented by my colleague Allan Kj\u00e6r in <a href=\"https:\/\/www.virtual-allan.com\/vsan-health-and-controller-firmware-n-a\/\" target=\"_blank\" rel=\"noopener\">this blog article!<\/a><\/p>\n<p>The difference here was that the disk controller in this server was a Lenono N2215 HBA (N2200 series) and this time it wasn\u2019t the StorCLI that was needed, but instead the SAS3FLASH utility.<\/p>\n<p>But I was not able to find this utility from the Lenovo website, but the \u201cAsk VMware\u201d button in vSAN heath gave me a hint that I could be found at the \u201cBroadcom Support page\u201d<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-158\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/sas3flash-notice.jpg\" alt=\"\" width=\"1128\" height=\"202\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/sas3flash-notice.jpg 1128w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/sas3flash-notice-300x54.jpg 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/sas3flash-notice-768x138.jpg 768w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/sas3flash-notice-1024x183.jpg 1024w\" sizes=\"auto, (max-width: 1128px) 100vw, 1128px\" \/><\/p>\n<p>But again I couldn\u2019t find the download under the HBA chipset model that was in the server, so I just selected a different controller and actually found the SAS3FLASH utility: <a href=\"https:\/\/www.broadcom.com\/support\/download-search\/?pg=Storage+Adapters,+Controllers,+and+ICs&amp;pf=Storage+Adapters,+Controllers,+and+ICs&amp;pn=SAS+9305-24i+Host+Bus+Adapter&amp;pa=&amp;po=&amp;dk=\" target=\"_blank\" rel=\"noopener\">Link to download<\/a><\/p>\n<p>The SAS3FLASH.zip file was extracted and the NDS version vib file was uploaded to a VMware datastore (vmware-esx-sas3ircu.vib).<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-164\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/sas3flash-install.jpg\" alt=\"\" width=\"1237\" height=\"167\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/sas3flash-install.jpg 1237w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/sas3flash-install-300x41.jpg 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/sas3flash-install-768x104.jpg 768w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/sas3flash-install-1024x138.jpg 1024w\" sizes=\"auto, (max-width: 1237px) 100vw, 1237px\" \/><\/p>\n<p>After the installation of the utility from ESXi SSH shell, \u201cvSAN Health Check\u201d was able to report the installed firmware version. Hurray!<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-168\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/Firmware-reported-certified.jpg\" alt=\"\" width=\"875\" height=\"98\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/Firmware-reported-certified.jpg 875w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/Firmware-reported-certified-300x34.jpg 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/Firmware-reported-certified-768x86.jpg 768w\" sizes=\"auto, (max-width: 875px) 100vw, 875px\" \/><\/p>\n<p>My guess is that the StorCLI utility is for RAID based controllers (that runs in HBA \/ Pass-through mode) and SAS3FLASH might be for the HBA (non RAID) controllers &#8211; just my guess!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A couple of days ago I was visiting a customer to setup their Lenovo host to run vSAN \u2013 after the initial setup of vSAN kernel IPs, disk groups and so on, I took a look at the \u201cVSAN Health check\u201d to make sure that everything was healthy and supported. Under the \u201chardware compatibility\u201d part [&hellip;]<\/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":[11,8,7],"tags":[23,28,27,24,26],"class_list":["post-150","post","type-post","status-publish","format-standard","hentry","category-vcenter","category-vsan","category-vsphere","tag-esxi","tag-firmware","tag-lenovo","tag-vcenter","tag-vsan"],"_links":{"self":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/150","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=150"}],"version-history":[{"count":19,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/150\/revisions"}],"predecessor-version":[{"id":177,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/150\/revisions\/177"}],"wp:attachment":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/media?parent=150"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/categories?post=150"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/tags?post=150"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}