Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

7304

July 9th, 2014 01:00

VPLEX: Match Storage-Volume VPDs with Virtual-Volume VPD

Hello,

I'm trying to Match the VPDs of the virtual volumes ("../exports/storage-views>ls -f") with the physical volumes ("../storage-elements/storage-volumes>ll").


The goal is, to create a table with the the name of the vplex virtual volume (distributet) and its physical storage volume name (Symmetrix).

I tried it also with the exports, but no chance. I can't find any overlap to match this.

Some ideas?

57 Posts

July 9th, 2014 06:00

You might try this command:

cluster configdump -c cluster-1 -f /var/log/VPlex/cli/configdump.xml

Download then open the file directly with excel. Excel has a built in xml filter. This file may give you the info that you need.

Steve

27 Posts

July 9th, 2014 07:00

The best way to do this (currently) is to determine the virtual volume (VV) VPD ID from the storage view:

ls -t /clusters/cluster_name/exports/storage-views/storage_view_name::virtual-volumes


This will give you a listing similar to:


/clusters/cluster-1/exports/storage-views/licoA247:

Name             Value

---------------  --------------------------------------------------------------------

virtual-volumes  [(0,A247_003A_2_vol,VPD83T3:6000144000000010f033cb2b2e7ff737,512M)]


Now you have the VV VPD ID.



Then you can use the "show-use-hierarchy" command:


show-use-hierarchy /clusters/cluster-1/virtual-volumes/A247_003A_2_vol"

storage-view: licoA247 (cluster-1)

  virtual-volume: \u001B[1;32mA247_003A_2_vol (512M, local @ cluster-1, running)

    local-device: A247_003A_2 (512M, raid-0, cluster-1)

      extent: extent_Symm0874_003A_2 (512M)

        storage-volume: Symm0874_003A (1G, 2 slices)

          logical-unit: VPD83T3:60000970000194900874533030313644

            storage-array: EMC-SYMMETRIX-194900874

Now you have the underlying storage volume's VPD ID.

Please be aware that a given VV may have more than one underlying storage volume depending on it's topology.


The next question is how will you collect all of this information.  The best way is probably by using the API or running a batch of CLI commands.



July 10th, 2014 01:00

Hi,

wow, thanks for this!
Now I was able to solve the problem. But it was not possible with VPD; I used the extents and vv's to match local and remote device to the vv and plex vpd.

July 10th, 2014 01:00

Hi,thank you.
The problem with that output is really to collect all information in a good form. I realized it now with the configdump. But many thanks for showing the VPD matching.

57 Posts

July 10th, 2014 05:00

Your welcome!

Steve

Sent from my iPad

12 Posts

January 14th, 2015 12:00

Thanks Steve

No Events found!

Top