{"id":3972,"date":"2019-03-22T16:41:09","date_gmt":"2019-03-22T21:41:09","guid":{"rendered":"http:\/\/www.jasemccarty.com\/blog\/?p=3972"},"modified":"2020-02-16T16:41:29","modified_gmt":"2020-02-16T22:41:29","slug":"vsan-snippets-reporting-drive-location","status":"publish","type":"post","link":"https:\/\/www.jasemccarty.com\/blog\/vsan-snippets-reporting-drive-location\/","title":{"rendered":"vSAN Snippets: Reporting Drive Location & More"},"content":{"rendered":"

An internal request came up asking for the ability to return the enclosure location of a vSAN disk.<\/p>\n

This information can sometimes be returned from the esxcli command utility, for some storage controllers, using the following command:<\/p>\n

\n

esxcli storage core device physical get -d <device id><\/p>\n<\/blockquote>\n

The resulting output looks something like this:<\/p>\n

\"\"<\/a><\/p>\n

Having to perform that command for a large number of disks could take a significant amount of time and could be quite burdensome.<\/p>\n

In the vSphere Client, this information is displayed Cluster > Configure > vSAN > Disk Management<\/strong> section, choosing to show disks By Disk Vendors<\/strong>.<\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

But what if we want to programmatically report this information from PowerCLI?<\/strong><\/p>\n

PowerCLI can already report the storage devices on an ESXi host host using the Get-ScsiLun<\/strong> cmdlet. A significant amount of information is returned from the Get-ScsiLun cmdlet such as the Adapter the disk is attached to, whether the disk is an SSD, if it is eligible for vSAN and more. Unfortunately though, this cmdlet does not report the “Physical Location” property.<\/p>\n

By combining the Get-ScsiLun<\/strong> cmdlet, as well as using the power of Get-EsxCli<\/strong> (version 2 of course<\/a>), this information can be put together to create a quick and easy report for all the hosts in a cluster.<\/p>\n

\"\"<\/a><\/p>\n

This script can be found here: https:\/\/code.vmware.com\/samples\/5539<\/a><\/p>\n

Reporting scripts like this, and more, can be found on the VMware Code<\/a> site and in the PowerCLI Cookbook for vSAN<\/a>.<\/p>\n

This was originally posted on the VMware Virtual Blocks site: https:\/\/blogs.vmware.com\/virtualblocks\/2019\/03\/22\/vsan-snippets-reporting-drive-location\/<\/p>\n","protected":false},"excerpt":{"rendered":"

An internal request came up asking for the ability to return the enclosure location of a vSAN disk. This information can sometimes be returned from … <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3972","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/posts\/3972","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/comments?post=3972"}],"version-history":[{"count":2,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/posts\/3972\/revisions"}],"predecessor-version":[{"id":3974,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/posts\/3972\/revisions\/3974"}],"wp:attachment":[{"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/media?parent=3972"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/categories?post=3972"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/tags?post=3972"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}