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
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.
Run this command to add a PSA claim rule to mark the device as SSD:
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.
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.
Additional Information
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:
Error adding SATP user rule: Duplicate user rule found for SATP VMW_SATP_LOCAL matching device naa.600508b1abcd97f3d8c54ad763b61234 PSP and PSP Options