If you manage one or more Everpure FlashArrays, you’ve probably needed a quick answer to a simple question: What flash modules are installed, in which slot, and what is the capacity of each one? If this is you, then continue reading for more details.

Purity//FA’s UI and the combination of the CLI commands purehw and puredriveexpose this information, but neither is convenient when you want a clean tabular view across several arrays at once — for example, when planning a capacity expansion, validating that two arrays are configured identically, or feeding the data into a spreadsheet for an asset audit.

If you didn’t figure it out already by the title of the post, this one is about how to map an NVMe-TCP datastore back to a Pure Storage volume by viewing what is known as the EUI ID. In this blog post, I will cover one way to do this as well as explain what is an EUI ID.

I was recently on a call with the storage team for a customer and they were still tracking LUN IDs so they could map them back to a VMware datastore in vCenter. When I noticed them doing this, I let them know they don’t really need to do this anymore. In vCenter it is quite easy to map a datastore back to a Pure Storage volume by viewing what is known as the NAA ID. In this blog post, I will cover one way to do this as well as explain what is an NAA ID.