VPLEX: Virtual Volume with service status inactive

The virtual volume status of a distributed device shows a service status of "running" on one cluster and a service status of "inactive" on the other cluster as seen below.
 
Example of the device "service-status" showing as "running" on cluster-1:

VPlexcli:/clusters/cluster-1/virtual-volumes/device_problem_volume_vol> ll

Name                        Value
--------------------------  ----------------------------------------
block-count                 104857920
block-size                  4K
cache-mode                  synchronous
capacity                    400G
consistency-group           Consistency_Group_x
expandable                  true
expandable-capacity         0B
expansion-method            storage-volume
expansion-status            -
health-indications          []
health-state                ok
locality                    distributed
operational-status          ok
recoverpoint-protection-at  []
recoverpoint-usage          -
scsi-release-delay          0
service-status              Running  <<<<<      
storage-array-family        symmetrix
storage-tier                -
supporting-device           device_C1_problem_volume
system-id                   device_ problem_volume_vol
thin-capable                true
thin-enabled                disabled
volume-type                 virtual-volume
vpd-id                      VPD83T3:6000144000000010604145145xxxxxx

Example of the device "service-status" showing as "inactive" on cluster-2:

VPlexcli:/clusters/cluster-2/virtual-volumes/device_problem_volume_vol> ll

Name                        Value
--------------------------  ----------------------------------------
block-count                 104857920
block-size                  4K
cache-mode                  synchronous
capacity                    400G
consistency-group           Consistency_Group_x
expandable                  true
expandable-capacity         0B
expansion-method            storage-volume
expansion-status            -
health-indications          []
health-state                ok
locality                    distributed
operational-status          ok
recoverpoint-protection-at  []
recoverpoint-usage          -
scsi-release-delay          0
service-status              inactive   <<<<<    
storage-array-family        symmetrix
storage-tier                -
supporting-device           device_C2_problem_volume
system-id                   device_ problem_volume_vol
thin-capable                true
thin-enabled                disabled
volume-type                 virtual-volume
vpd-id                      VPD83T3:6000144000000010604145145xxxxxx

All other health indicators for the virtual volume are good.

The volume is exported via the "storage-view" on cluster-1 and cluster-2. The "inactive" state as seen on cluster-2 in the example below comes from the fact the there are no front-end ports assigned to the storage-view on cluster-2, yet there are front-end ports declared in the "storage-view" on cluster-1 as shown below:

Example showing front-end ports present in the storage-view in the line "port-name-enabled-status" or "ports" on cluster-1, and no front-end ports listed for cluster-2:

VPlexcli:/> ll /clusters/cluster-*/exports/storage-views/SV_problem_volume

/clusters/cluster-1/exports/storage-views/SV_ problem_volume:
Name                      Value
------------------------  ------------------------------------------------------------------------------
caw-enabled               true
controller-tag            -
initiators                [A_host_HBA0, B_host_HBA1]
operational-status        ok
port-name-enabled-status  [P0000000047A0038A-A0-FC00,true,ok, P0000000047B00458-B0-FC01,true,ok]
ports                     [P0000000047A0038A-A0-FC00, P0000000047B00458-B0-FC01] <<<<<
virtual-volumes           [(0,device_ problem_volume_vol,VPD83T3:6000144000000010604145145xxxxxx,400G)]
write-same-16-enabled     true
xcopy-enabled             true


/clusters/cluster-2/exports/storage-views/SV_problem_volume:
Name                      Value
------------------------  ------------------------------------------------------------------------------
caw-enabled               true
controller-tag            -
initiators                [A_host_HBA0, B_host_HBA1]
operational-status        ok
port-name-enabled-status  []
ports                     [] <<<<<
virtual-volumes           [(0,device_ problem_volume_vol,VPD83T3:600014400000001060414514xxxxxx,400G)]
write-same-16-enabled     true
xcopy-enabled             true

This is a configuration-based issue and is not due to a fault or failing on the VPLEX.

To have the virtual-volume enter a "running" state, the solution is to add front-end ports to the storage-views of the cluster where they show missing, for the virtual-volume that is exported.

For instructions to add / remove front-end ports to a storage-view please consult the VPLEX Admin Guide for the applicable GeoSynchrony version available on Dell Support.