1. Log in to the host as root, using either the Console DCUI or SSH.
   
2. If the device is currently in use, ensure the virtual machine(s) accessing the device are powered off and if it contains a mounted datastore, ensure that the datastore is unmounted. For more information on the unmounting operation, see Unmounting a LUN or detaching a datastore/storage device from multiple ESXi 5.x hosts (2004605).
   
   
3. Run this command and identify the device to be tagged and its SATP:
   
   # esxcli storage nmp device list
   
   You see output similar to:
   
   naa.6006016015301d00167ce6e2ddb3de11
   Device Display Name: DGC Fibre Channel Disk (naa.6006016015301d00167ce6e2ddb3de11)
   Storage Array Type: VMW_SATP_CX
   Storage Array Type Device Config: {navireg ipfilter}
   Path Selection Policy: VMW_PSP_MRU
   Path Selection Policy Device Config: Current Path=vmhba4:C0:T0:L25
   Working Paths: vmhba4:C0:T0:L25
   
   
4. In this sample output, the SATP is VMW_SATP_CX. This may vary depending on your environment. For example, the SATP may be VMW_SATP_LOCAL. Ensure to use the correct SATP in these steps.
   
   Notes:
   • In this procedure, the device ID naa.6006016015301d00167ce6e2ddb3de11 is used. Use the device ID returned for your own device in these steps.
   • If you have the SSD drives in the RAID 1 setup, and the RAID controller you are using does not support NON-RAID mode or Pass-Through Mode, then you must re-configure your SSD drives in a RAID 0 setup.
     
     
5. Run this command to add a PSA claim rule to mark the device as SSD:
   
   # esxcli storage nmp satp rule add --satp=SATP_TYPE --device naa.6006016015301d00167ce6e2ddb3de11 --option "enable_ssd"
   
   For example:
   
   # esxcli storage nmp satp rule add --satp=VMW_SATP_CX --device naa.6006016015301d00167ce6e2ddb3de11 --option "enable_ssd"
   
   Note: Run this command to enable local and SSD at the same time:
   
   # esxcli storage nmp satp rule add –-satp=VMW_SATP_LOCAL –-device naa.6006016015301d00167ce6e2ddb3de11 --option "enable_local enable_ssd"
   
   For example:
   
   # esxcli storage nmp satp rule add --satp=VMW_SATP_LOCAL --device naa.6006016015301d00167ce6e2ddb3de11 --option "enable_local enable_ssd"
   
   You must restart the ESXi host for the changes to take effect.
   
   
6. Run this command to unclaim the device:
   
   # esxcli storage core claiming unclaim --type=device --device naa.6006016015301d00167ce6e2ddb3de11
   
   Note: If you have a local SSD device, the device might not be detected after you apply the rule to unclaim the device. After you restart the ESXi host, you can verify that the device has the rule applied.
   
   
7. Run these commands to reclaim the device:
   
   # esxcli storage core claimrule load
   # esxcli storage core claimrule run
   # esxcli storage core claiming reclaim -d naa.6006016015301d00167ce6e2ddb3de11
   
   
8. Run this command to check the SSD status:
   
   # esxcli storage core device list -d naa.6006016015301d00167ce6e2ddb3de11 | grep SSD
   
   You see output similar to:
   
   naa.6006016042fa19010a12d9b16d6ade11
   Display Name: DGC Fibre Channel Disk (naa.6006016042fa19010a12d9b16d6ade11)
   Size: 204800
   Device Type: Direct-Access
   Multipath Plugin: NMP
   Devfs Path: /vmfs/devices/disks/naa.6006016042fa19010a12d9b16d6ade11
   Vendor: DGC
   Model: RAID 5
   Revision: 0220
   SCSI Level: 4
   Is Pseudo: false
   Status: on
   Is RDM Capable: true
   Is Local: false
   Is Removable: false
   Is SSD: true
   Is Thin Provisioned: unsupported
   Attached Filters:
   VAAI Status: unknown
   Other UIDs:
   vml.02000100006006016042fa19010a12d9b16d6ade11524149442035
   
   
   Notes:
   
   • You can use a generic vendor model notation as an alternative to device/LUN. For example:
     
     # esxcli storage nmp satp rule add --satp VMW_SATP_CX --vendor "foo" --model "bar" --option "enable_ssd"
     
     
   • Do not change the SATP is required for the device to function.
   • To untag the device, you must perform the entire process in reverse; you must remove the claimrule, unclaim the device, load the claimrules again, and then reclaim.
   • You must restart the ESXi host to tag the local datastore (if ESXi is installed locally) as the SSD drive.

• When adding a new rule, if you receive an error stating that there was a duplicate rule found, you may need to remove the rule and add it again with the correct SSD flag. For example:

# esxcli storage nmp satp rule add --satp VMW_SATP_LOCAL --device naa.600508b1abcd97f3d8c54ad763b61234

Error adding SATP user rule: Duplicate user rule found for SATP VMW_SATP_LOCAL matching device naa.600508b1abcd97f3d8c54ad763b61234 PSP and PSP Options

• Remove the existing rule, and then re-add:

# esxcli storage nmp satp rule remove --satp VMW_SATP_LOCAL --device naa.600508b1abcd97f3d8c54ad763b61234

# esxcli storage nmp satp rule add --satp VMW_SATP_LOCAL --device naa.600508b1abcd97f3d8c54ad763b61234 --option "enable_ssd"

• Run this command to verify the added VMW_SATP_LOCAL satp rules:
  
  esxcli storage nmp satp rule list --satp=VMW_SATP_LOCAL