VPLEX: Distributed device showing cluster-1 leg contains cluster-2 extent in GUI

Article Number: 503013                              Article Version:                               Article Type: Break Fix


Product:

VPLEX Metro


VPLEX Series,VPLEX Metro,VPLEX VS2,VPLEX VS6,VPLEX GeoSynchrony 5.5,VPLEX GeoSynchrony 5.4 Service Pack 1,VPLEX GeoSynchrony 5.4 Service Pack 1 Patch 1,VPLEX GeoSynchrony 5.4 Service Pack 1 Patch 3,VPLEX GeoSynchrony 5.4 Service Pack 1 Patch 4

Issue:

The VPLEX GUI displays the anatomy of a distributed device as having a leg containing an extent that is being provisioned from the remote cluster.

 

 

Cause:

An extent used to create each leg of the distributed device has the same name.  This can be determined by navigating to the relevant context in the VPlexcli

 

VPlexcli:/> cd /distributed-storage/distributed-devices/

 

and then run the command     show-use-hierarchy name_of_distributed_device

 

where name_of_distributed_device  is the name of the distributed device you want to look at.

 

Example:

 

VPlexcli:/distributed-storage/distributed-devices> ll

Name                                        Status   Operational  Health  Auto                                                                                            Rule Set Name       Transfer

------------------------------------------  -------  Status       State   Resume                                                                                          ------------------  Size

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

 

sharry_device                              running  ok           ok      true                                                                                            cluster-1-detaches  128K

 

 

 

VPlexcli:/distributed-storage/distributed-devices> show-use-hierarchy day_apps

virtual-volume: day_apps_vol (5G, distributed @ cluster-1, unexported)

  distributed-device: sharry_device (5G, raid-1)

    distributed-device-component: migtest1 (5G, raid-0, cluster-2)

      local-device: EXTENT_MIGRATE_migrationtest0607 (5G, raid-1)

        extent: extent_sharry1_1 (5G)

          storage-volume: VPD83T3:600601xxxxxxxxxxxxxxxxxx (5G)

            storage-array: EMC-CLARiiON-APM001xxxxxxx

    distributed-device-component: sharry_device2017Jul17_083255 (5G, raid-0, cluster-1)

      extent: extent_sharry1_1 (5G)

        storage-volume: sharry1 (5G)

          logical-unit: VPD83T3:600601yyyyyyyyyyyyyyyyyyyyy

            storage-array: EMC-CLARiiON-APMxxxxxxxx

 

Resolution:

The names of the extents are cosmetic.

You can change the name of one of the extents by navigating to the correct context and issuing the command to change the name.

 

Example:

 

From VPlexcli navigate to the relevant context and issue the command to change the name

 

/clusters/cluster-2/storage-elements/extents> set extent_sharry1_1::name extent_sharry1_2

 

After the command executes, you can run the show-use-hierarchy command again to take a look at the new anatomy of the distributed device

 


VPlexcli:/distributed-storage/distributed-devices> show-use-hierarchy day_apps
virtual-volume: day_apps_vol (5G, distributed @ cluster-1, unexported)
  distributed-device: sharry_device (5G, raid-1)
    distributed-device-component: migtest1 (5G, raid-0, cluster-2)
      local-device: EXTENT_MIGRATE_migrationtest0607 (5G, raid-1)
        extent: extent_sharry1_1 (5G)
          storage-volume: VPD83T3:600601xxxxxxxxxxxxxxxxxx (5G)
            storage-array: EMC-CLARiiON-APM001xxxxxxx
    distributed-device-component: sharry_device2017Jul17_083255 (5G, raid-0, cluster-1)
      extent: extent_sharry1_2 (5G)
        storage-volume: sharry1 (5G)
          logical-unit: VPD83T3:600601yyyyyyyyyyyyyyyyyyyyy
            storage-array: EMC-CLARiiON-APMxxxxxxxx

.p