VPLEX VPD ID and Encapsulation

Hi Ram,

The "VPD ID" of the virtual-volume is the unique identifier. It is the same as the "naa number". All logical-units presented to VPLEX will have their own VPD numbers provided by their respective arrays. VPLEX puts its own VPD number on virtual-volumes because VPLEX volumes can span multiple back end devices, e.g. RAID-1 and RAID-C and VPLEX can also carve up a single back end device into multiple extents.

The best way to view and track the architecture of a device along with the VPD IDs is the "show-use-hierarchy" command. It will accept wildcards, but will need to resolve the full path to one or more volumes.

Example:

VPlexcli:/> show-use-hierarchy /**/virtual-volumes/device_RPA_LUN1_1_vol

storage-view: VIPR_STORAGE_VIEW (cluster-1)

  consistency-group: CG-Test1 (synchronous)

    virtual-volume: device_RPA_LUN1_1_vol (10G, distributed @ cluster-1, running)

      distributed-device: device_V47G_6_3PAR02_60002 (10G, raid-1)

        distributed-device-component: device_V47G_6_3PAR02_600022017Nov25_230134 (10G, raid-0, cluster-1)

          extent: extent_RPA_LUN1_1 (10G)

            storage-volume: RPA_LUN1 (10G)

              logical-unit: VPD83T3:6006016013302700d8b7b81c26aae311

                storage-array: EMC-CLARiiON-APM00100201782

        distributed-device-component: test_leg_2 (10G, raid-0, cluster-2)

          extent: extent_VPD83T3_6006016013302700edd0e1c80c45e011_1 (10G)

            storage-volume: VPD83T3:6006016013302700edd0e1c80c45e011 (10G)

              logical-unit: VPD83T3:6006016013302700edd0e1c80c45e011

                storage-array: EMC-CLARiiON-APM00100201782

There are also OS specific encapsulation procedures in SolVe

Regards,
Ben