AppSync: VPLEX Device mapping failed for device: X with error: extent_X is not 1:1 created on storage volume X and is not supported by AppSync[4]

           

   Article Number:     522310                                   Article Version: 3     Article Type:    Break Fix 
   

 


Product:

 

AppSync,VPLEX Series,AppSync 3.0 SP2

 

Issue:

 

 

   

         
  •         AppSync GUI and logs report the VPlex virtual-volume as not being 1:1 mapped.     
  •      
  •         AppSync is unable to map the VPlex virtual-volume.     
  •      
  •         AppSync GUI shows the following error messages against a VPlex volume;     
  •    
   
      VPLEX Device mapping failed for device:device_X with error: Device:device_X extent:extent_X is not 1:1 created on storage volume:X and is not supported by AppSync.    
                                                             

 

 

Cause:

 

 

AppSync only supports VPlex volumes which were created using the full capacity of a storage-volume.   
    Only fully encapsulated VPLEX volumes are supported by AppSync. 
                                                           

 

 

Change:

 

 

   

         
  •         Customer is provisioning storage on the VPlex.     
  •      
  •         Customer had performed a device/extent migration on the VPlex.     
  •    
                                                             

 

 

Resolution:

 

 

The following steps are to be performed on the VPlex. In the following troubleshooting procedure, a fictitious local virtual-volume, 'device_Symm1000_00AB_1_vol' is used as an example.    
    ​   
    1. Login to the VPlexcli and perform a 'show-use-hierarchy' against the VPlex virtual-volume of interest;   

VPlexcli:/> show-use-hierarchy -t /clusters/cluster-1/virtual-volumes/device_Symm1000_00AB_1_volstorage-view: VPLEX_STORAGE_VIEW (cluster-1)  virtual-volume: device_Symm1000_00AB_1_vol (2T, local @ cluster-1, running)    local-device: device_Symm1000_00AB_1 (2T, raid-0, cluster-1)      extent: extent_Symm1000_00AB_1 (2T)        storage-volume: Symm1000_00AB (2T)          logical-unit: VPD83T3:60000970000196801000533000000111            storage-array: EMC-SYMMETRIX-196801000    
   
    2. Note that the virtual-volume is 1:1 mapped: virtual-volume to storage-volume.   
        
      VPlexcli:/> show-use-hierarchy -t /clusters/cluster-1/virtual-volumes/device_Symm1000_003B_1_volstorage-view: VPLEX_STORAGE_VIEW (cluster-1)  virtual-volume: device_Symm1000_00AB_1_vol (2T, local @ cluster-1, running)    local-device: device_Symm1000_00AB_1 (2T, raid-0, cluster-1)      extent: extent_Symm1000_00AB_1 (2T)        storage-volume: Symm1000_00AB (2T)          logical-unit: VPD83T3:60000970000196801000533000000111            storage-array: EMC-SYMMETRIX-196801000    
   

     
      3. If the virtual-volume reports, 'expandable by X' where X is the respective size, then AppSync will report this volume as not 1:1 mapped due to the extent not consuming the entire storage volume.   

   
     
   
      VPlexcli:/> show-use-hierarchy -t /clusters/cluster-1/virtual-volumes/device_Symm1000_003B_1_volstorage-view: VPLEX_STORAGE_VIEW (cluster-1)  virtual-volume: device_Symm1000_00AB_1_vol (2T, local @ cluster-1, running, expandable by 2M)    local-device: device_Symm1000_00AB_1 (2T, raid-0, cluster-1)      extent: extent_Symm1000_00AB_1 (2T)        storage-volume: Symm1000_00AB (2T)          logical-unit: VPD83T3:60000970000196801000533000000111            storage-array: EMC-SYMMETRIX-196801000            
   

     
      In this case, please follow VPLEX: How to Expand a virtual volume in-order to expand the virtual-volume's underlying components and the virtual-volume itself to utilise it's full capacity.