Array LUNs (including VNX) have a 128-bit universally unique ID (so called UUID or WWN); 128-bit UUIDs begin with a 6 (this is the NAA - Network Address Authority), and in total are represented by 32 hex characters. For example:
6006016b071e5c98ab5ceb0314159265 (made up by myself for illustration)
This is the string from the VNX that identifies the LUN, and that you should be able to interrogate from the host-side. You could use the EMC command 'inq' with the following syntax (download the correct version of 'inq' for the specific OS:
inq -clar_wwn
Alternatively, each OS will have a native command to interrogate the LUN UUIDs. An ESX example would be the 'esxcli' command - see VMware KB 1003973 ("Obtaining LUN Pathing Information...."). The vSphere client (device list) will also show the NAA-6 LUN UUIDs.
Richard_Butler
84 Posts
0
June 27th, 2017 08:00
Hello Armin2504,
Array LUNs (including VNX) have a 128-bit universally unique ID (so called UUID or WWN); 128-bit UUIDs begin with a 6 (this is the NAA - Network Address Authority), and in total are represented by 32 hex characters. For example:
6006016b071e5c98ab5ceb0314159265 (made up by myself for illustration)
This is the string from the VNX that identifies the LUN, and that you should be able to interrogate from the host-side. You could use the EMC command 'inq' with the following syntax (download the correct version of 'inq' for the specific OS:
Alternatively, each OS will have a native command to interrogate the LUN UUIDs. An ESX example would be the 'esxcli' command - see VMware KB 1003973 ("Obtaining LUN Pathing Information...."). The vSphere client (device list) will also show the NAA-6 LUN UUIDs.
(For Linux native commands Google 'systool')
HTH, Richard.
armin2504
1 Rookie
•
15 Posts
0
June 27th, 2017 20:00
thank you Richard