Dell EMC Unity: How to address "Delete Status: unsupported" issue for VPlex provisioned Unity volume(User Correctable)

           

   Article Number:     530923                                   Article Version: 2     Article Type:    Break Fix 
   

 


Product:

 

Dell EMC Unity 300,Dell EMC Unity 300F,Dell EMC Unity 350F,Dell EMC Unity 380,Dell EMC Unity 380F,Dell EMC Unity 400,Dell EMC Unity 400F,Dell EMC Unity 450F,Dell EMC Unity 480,Dell EMC Unity 480F,Dell EMC Unity 500,Dell EMC Unity 500F

 

Issue:

 

 

This is regarding VAAI UNMAP plug-in issue, delete status is showing unsupported:   

[root@ESXi:/] esxcli storage core device vaai status get -d naa.<WWN>   VAAI Plugin Name: VMW_VAAIP_CX   ATS Status: supported   Clone Status: supported   Zero Status: supported   Delete Status: unsupported <<<<<<<<<    
   
    The UNMAP feature became available for Unity arrays from VPLEX 6.0 Service Pack 1. So, must confirm if the VPlex is running on the correct version code that supports UNMAP.   
   
    But, when the VPlex is running on the version that supports the UNMAP feature for Unity, the UNMAP feature reports unsupported. The use of UNMAP is limited to Thin provisioned volumes. So, need to check if the the LUNs are thin provisioned or not:   
        
[root@ESXi:~] esxcli storage core device list -d naa.<WWN>   <Output is truncated>   .   .   Thin Provisioning Status: unknown <<<<<<< It means that the LUNs are thick provisioned    
   
   
   
   
   
                                                                

 

 

Cause:

 

 

The version running on VPlex doesn't support the 'unmap' feature for Unity.    
   
    OR   
   
    If the VPlex is running on the version that supports the UNMAP feature for Unity, the cause is that the LUNs are thick provisioned or the LUNs are thin provisioned on Unity, but thin-enabled-feature on VPlex virtual-volume is disabled.
                                                           

 

 

Resolution:

 

 

If the VPlex is not running on the version that supports the UNMAP feature for Unity. Customer to upgrade VPlex to 6.0 SP 1, which supports thin UNMAP.   
   
    Else,   
   
    Checks on VPlex :   
   
    1. verify if the storage-volume provisioned to VPlex is thin capable :   
        

VPlexcli:/clusters/cluster-1/storage-elements/storage-volumes> llName                               VPD83 ID                  Capacity  Use        Vendor   IO Status    Type         Thin     Provision  Thin---------------------------------  ------------------------  --------  ---------  -------  -----------  -----------  Rebuild  Type       Capable---------------------------------  ------------------------  --------  ---------  -------  -----------  -----------  -------  ---------  -------VPD83T3:514f0c5b94e0002c           VPD83T3:514f0c5b94e0002c  15G       used       Unity    alive        normal       false    legacy     true    
   
    2. Verify if thin enabled feature on VPlex virtual-volume is enabled :   
   
    VPlexcli:/clusters/cluster-1/virtual-volumes/testvolume_vol>  ll     
      Name Value     
      -------------------------- ----------------------------------------     
      block-count 3932160     
      block-size 4K     
      cache-mode synchronous     
      capacity 15G     
      consistency-group -     
      expandable true     
      expandable-capacity 0B     
      expansion-method storage-volume     
      expansion-status -     
      health-indications []     
      health-state ok     
      locality local     
      operational-status ok     
      recoverpoint-protection-at []     
      recoverpoint-usage -     
      scsi-release-delay 0     
      service-status running     
      storage-tier -     
      supporting-device testvolume     
      system-id testvolume_vol     
      thin-capable true     
      thin-enabled disabled <--- thin enabled is not set!!     
      volume-type virtual-volume     
      vpd-id VPD83T3:6000144000000010b021768279d4285d
   
        
    3. Enable the thin feature on the virtual volume, if it's disabled:   
   
    VPlexcli:/clusters/cluster-1/virtual-volumes/testvolume_vol>set thin-enabled 1   
   
    Checks on ESXi :    
   
    4. Scan storage on ESXi server. It can be done both via command line and VCenter.   
   
    [root@ESXi:/] esxcli storage core adapter rescan --all   
   
    5.Run the storage core path command against the VPlex virtual-volume Naa id i :   
   
    [root@ESXi:/] esxcli storage core path list     
      fc.20000024ff548aa8:21000024ff548aa8-fc.5000144047b02176:50001442d0217600-naa.6000144000000010b021768279d4285d     
      UID: fc.20000024ff548aa8:21000024ff548aa8-fc.5000144047b02176:50001442d0217600-naa.6000144000000010b021768279d4285d     
      Runtime Name: vmhba2:C0:T3:L0     
      Device: naa.6000144000000010b021768279d4285d     
      Device Display Name: EMC Fibre Channel Disk (naa.6000144000000010b021768279d4285d)     
      Adapter: vmhba2     
      Channel: 0     
      Target: 3     
      LUN: 0     
      Plugin: NMP     
      State: active     
      Transport: fc     
      Adapter Identifier: fc.20000024ff548aa8:21000024ff548aa8     
      Target Identifier: fc.5000144047b02176:50001442d0217600     
      Adapter Transport Details: WWNN: 20:00:00:24:ff:54:8a:a8 WWPN: 21:00:00:24:ff:54:8a:a8     
      Target Transport Details: WWNN: 50:00:14:40:47:b0:21:76 WWPN: 50:00:14:42:d0:21:76:00     
      Maximum IO Size: 33553920Get Vplex virtual volume NAA
   
   
    6. Before creating partition or datastore on the volume, ESXi can not get Thin Provisioning status for that volume, thus it still reports that the feature is not supported:    
        
    [root@ESXi:/] esxcli storage core device vaai status get -d naa.6000144000000010b021768279d4285d     
      naa.6000144000000010b021768279d4285d     
      VAAI Plugin Name:     
      ATS Status: supported     
      Clone Status: supported     
      Zero Status: supported     
      Delete Status: unsupported
   
   
    [root@ESXi:/] esxcli storage core device list -d naa.6000144000000010b021768279d4285d     
      naa.6000144000000010b021768279d4285d     
      Display Name: EMC Fibre Channel Disk (naa.6000144000000010b021768279d4285d)     
      Has Settable Display Name: true     
      Size: 15360     
      Device Type: Direct-Access     
      Multipath Plugin: NMP     
      Devfs Path: /vmfs/devices/disks/naa.6000144000000010b021768279d4285d     
      Vendor: EMC     
      Model: Invista     
      Revision: 5520     
      SCSI Level: 4     
      Is Pseudo: false     
      Status: on     
      Is RDM Capable: true     
      Is Local: false     
      Is Removable: false     
      Is SSD: false     
      Is VVOL PE: false     
      Is Offline: false     
      Is Perennially Reserved: false     
      Queue Full Sample Size: 0     
      Queue Full Threshold: 0     
      Thin Provisioning Status: unknown     
      Attached Filters:     
      VAAI Status: supported     
      Other UIDs: vml.02000000006000144000000010b021768279d4285d496e76697374     
      Is Shared Clusterwide: true     
      Is Local SAS Device: false     
      Is SAS: false     
      Is USB: false     
      Is Boot USB Device: false     
      Is Boot Device: false     
      Device Max Queue Depth: 64     
      No of outstanding IOs with competing worlds: 32     
      Drive Type: unknown     
      RAID Level: unknown     
      Number of Physical Drives: unknown     
      Protection Enabled: false     
      PI Activated: false     
      PI Type: 0     
      PI Protection Mask: NO PROTECTION     
      Supported Guard Types: NO GUARD SUPPORT     
      DIX Enabled: false     
      DIX Guard Type: NO GUARD SUPPORT     
      Emulated DIX/DIF Enabled: false
   
   
    7. Create datastore on the volume or manually create partition table for the volume, thin provision status will change to yes and unmap will 'change to supported'.   
   
    [root@ESXi:/] esxcli storage core device list -d naa.6000144000000010b021768279d4285d     
      Is VVOL PE: false     
      Is Offline: false     
      Is Perennially Reserved: false     
      Queue Full Sample Size: 0     
      Queue Full Threshold: 0     
      Thin Provisioning Status: yes
   
   
    [root@ESXi:/] esxcli storage core device vaai status get -d naa.6000144000000010b021768279d4285d     
      naa.6000144000000010b021768279d4285d     
      VAAI Plugin Name:     
      ATS Status: supported     
      Clone Status: supported     
      Zero Status: supported     
      Delete Status: supported
   
   
    8. After executing the above steps, if the ESXi still fails to update the unmap status, please check for the VMware KBA and investigate from ESXi side. https://kb.vmware.com/articleview?docid=2048466                                                           

 

 

Notes:

 

 

Please refer to the below document:   
   
    https://support.emc.com/docu81003_VPLEX-GeoSynchrony-6.0-Service-Pack-1-and-Patches--Release-Notes.pdf?language=en_US