Unsolved
This post is more than 5 years old
22 Posts
0
1317
Explanation for the naming convention used by VPLEX when creating storage from pools?
Hi all
Is there an explanation for the naming convention used by VPLEX when creating storage from pools (the automated process)
e.g. VPD83T3:60060160a9203b004e316127fa09e511
What does the above mean and does it relate to the underlying storage e.g. VNX or VMAX
Many thanks
Tadhg
echolaughmk
522 Posts
0
August 11th, 2015 08:00
That string references the UUID of the underlying storage volume being claimed if you are looking at it from a storage volumes perspective:
VPD = Vital Product Data
83T3 - I forget what this means
60060160a9203b004e316127fa09e511 - this should be the LUN WWN of the VNX or VMAX LUN that was presented to the VPLEX that you are trying to claim.
aaronmatson
19 Posts
0
September 25th, 2015 22:00
First off, VPD=Virtual Product Data. There are 2 of these numbers and they can become very confusing. The UUID that you see from the array side is the exact same as the UUID or (VPD) for the storage volume after you claim the volume. However, after you create your extent, device and Virtual Volume that VPD number will change. It will not assign the Virtual Volume a UUID or VPD until after you attach the volume to a storage view inside of VPLEX. That VPD information is going to be different than the storage volume VPD information that you can see. The 83T3 is a simple identifier in VPLEX and there are many other identifiers that you do not see such as (VPD83T1B) which ties into Recoverpoint and logging volumes that you don't see.