The document "Nimble Storage for Red Hat Enterprise Linux 6 & Oracle Linux 6" shows how to get the volume serial number using the Linux "scsi_id" command. This document also shows the source code to a small ksh script named "vol-info" that uses the Nimble ssh CLI interface to create a table mapping the cryptic volume serial number into the Nimble "volume name".
This volume serial number -to- volume name mapping is very useful for Linux scripting, since the core identifier of the Nimble iscsi volume is the cryptic serial number.
The scsi serial number displayed using the scsi_id command is read from fields on the SCSI vital product data (VPD) pages, typically VPD page 0x83. There are many other standardized and vendor-specific VPD pages that are used to pass useful information about a SCSI LUN. The Linux command "sg_vpd" can be used to display the contents of these VPD pages.
I understand that Nimble has a very powerful and functional scripting interface using a RESTfull API. and the ssh CLI commands. These interfaces can be used to provide a serial-number to volume-name mapping, as the example Nimble CLI script mentioned above does. However, these interfaces are more complex to use and require some form of secure authentication.
Some storage vendors make the "volume name" and/or "volume description" available using the optional or vendor-specific fields within the SCSI VPD information pages. As such, this information can be easily queried from Linux, and provide information in "human-readable" form.
I tried querying all the SCSI VPD pages that the Nimble storage array advertised as being supported, and found nothing that looked like a "volume name" or "volume description". I did not go searching for hidden VPD pages.
Is there an easy mechanism to retrieve the "volume name" of an attached Nimble iSCSI volume ... from the Linux side? This will likely eventually become a name alias for Linux dm-multipath. The target iqn and SCSI serial numbers are easily available.
Thanks for your help.