I recently was doing some troubleshooting for a customer that was using my UNMAP PowerCLI script and discovered a change in ESXi 5.5+ UNMAP. The issue was that the script was taking quite a while to complete. After some logic optimizations and increasing timeouts the script was sped up a bit and less timeout errors occurred, but a bunch of the UNMAP operations were still taking a lot longer than expected. Eventually we threw our hands up and said it was good enough. A bit more recently, I was testing a 3rd party UNMAP tool and ran into similar behavior so I dug into it a bit more and found some semi-unexpected changes in how UNMAP works, specifically the behavior when leveraging non-default block iteration counts. Continue reading UNMAP Block Count Behavior Change in ESXi 5.5 P3+
One of the few hard requirements we make to configure best practices on ESXi for the FlashArray is to create a SATP rule. A SATP rule simply describes a certain configuration (mainly around multipathing) for a specific set of devices (usually devices from an array). For the FlashArray, this rule consists of making sure devices are using Round Robin and an I/O operations limit of 1.
esxcli storage nmp satp rule add -s VMW_SATP_ALUA -V PURE -M FlashArray -P “VMW_PSP_RR” -O iops=1 -e “FlashArray SATP Rule”
I wanted to let people know about a fun contest we just started today at Pure Storage for our customers to get involved in that was the brainchild of my esteemed coworker Barkz. In our GUI (also visible when you login to the array CLI) there is a login banner you can create to greet you, or warn you as the case may be. The banner is just an ASCII text box, but we have had a few customers create some cool banners in the form of ASCII images.
In Part 1 of this two-parter, I spoke about our new CLI-based I/O Balance tool customers can use to verify that the I/O coming from their host is balanced across the paths that are configured.
We also have made some enhancements in the GUI for host connectivity reporting. There has been a screen inside the System tab of the FlashArray GUI that reports on the redundancy of host connections to the FlashArray for awhile now: