Cody put a LOT of work into this script, and I champion him for his efforts. He’s truly a machine. I knew this as an outsider to Pure, and am even more aware of this as I’ve come to work here. But Cody has only so many cycles, so I asked to take on the task of updating the script.<\/p>\n
Why did it need to be updated?<\/h3>\n
Well, some things have changed since the last update (April 15, 2018):<\/p>\n
- \n
- vSphere 6.7 Update 1<\/strong>, which added the Latency SATP option<\/em> (October 16, 2018)
\nThis is a new SATP rule for storage, and while it is available, vSphere 6.x versions of vSphere still have a recommendation of\u00a0iops=1<\/strong>. This is the default<\/em> for vSphere 6.0 Patch 5 or later, vSphere 6.5 Update 1 or later, and vSphere 6.7.
\n.<\/li>\n- vSphere 6.0 P08<\/strong> (September 12, 2019),vSphere 6.5 P03<\/strong> (November 29, 2018) – PR 2078782\/2156841
\nThese releases, along with vSphere 6.7 Update 1<\/em>, address the DiskMaxIOSize<\/strong> recommendation for earlier releases to be 4MB, rather than the 32MB default. Cody covers this in a blog post here: https:\/\/www.codyhosterman.com\/2020\/08\/disk-diskmaxiosize-and-the-blue-screen-of-death\/<\/a> The TL\/DR is that this no longer needs to be changed with more recent releases of vSphere.
\n.<\/li>\n- vSphere 7.0 GA released<\/strong>, which added support for NVMe-oF datastores<\/em> (April 2, 2020)
\nThe Latency SATP added in vSphere 6.7U1 is now the default for Pure Storage FlashArray devices.<\/li>\n<\/ul>\nThe previous release (v4.5) unfortunately required some updates to address the SATP rule change, as well as the DiskMaxIOSize setting, both dependent on the versions of vSphere being used.<\/p>\n
It isn’t uncommon to see several different releases of vSphere installed, and it didn’t make sense to have different scripts for each.<\/p>\n
This script will determine vSphere versions, and check the settings appropriately for different releases.<\/p>\n
Also, now that PowerShell added support (with PowerShell Core) for Windows\/Linux\/Mac OS environments, it only made sense to update it to run on PowerShell Core<\/strong><\/em> as well as PowerShell Desktop.<\/p>\n
I’ve dispensed with the use of forms, as it really isn’t worth the effort on PowerShell Core.<\/p>\n
![\"\"](\"https:\/\/www.jasemccarty.com\/blog\/wp-content\/uploads\/2021\/02\/OLDCHECK1-1024x540.png\")
<\/p>\nThe log generated after each run will be created in the same directory as the execution of the script, and a text menu will allow you to choose either all hosts connected to vCenter or only hosts in a selected cluster.<\/p>\n
![\"\"](\"https:\/\/www.jasemccarty.com\/blog\/wp-content\/uploads\/2021\/02\/NEWCHECK1-1024x476.png\")
<\/p>\nThe output is also a little cleaner as well.<\/p>\n
![\"\"](\"https:\/\/www.jasemccarty.com\/blog\/wp-content\/uploads\/2021\/02\/NEWCHCK2-1024x712.png\")
<\/p>\nWhat it doesn’t do<\/h3>\n
There are a couple of other things that I need to call attention to, that neither the old, nor updated script address. These are:<\/p>\n
- \n
- NVMe-oF configuration – This is not checked yet – I’m hoping to steal some time in Cody’s lab to add this support<\/li>\n
- It doesn’t check Pure volume to Host\/Host Group relationships – Suggest using the Pure Storage Plugin for vSphere version 4.5 or higher to view these<\/li>\n<\/ul>\n
Where can I find it?<\/h3>\n
The updated script can be found in the VMware Scripts repository on Pure Storage Open Connect site on GitHub.<\/p>\n
- vSphere 6.0 P08<\/strong> (September 12, 2019),vSphere 6.5 P03<\/strong> (November 29, 2018) – PR 2078782\/2156841