Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Enabling the SSD option on SSD based disks/LUNs that are not detected as SSD by default (2013188)

Purpose

This article provides steps to enable the SSD option on SSD based disks/LUNs that are not detected as SSD by default.

Resolution

To enable the SSD option on SSD based disks/LUNs that are not detected as SSD by default:
  1. If the device is currently in use, make sure the virtual machine(s) accessing the device are powered off and the datastore is unmounted (if applicable). For more information on the unmount operation, see Unmounting a LUN or detaching a datastore/storage device from multiple ESXi 5.x hosts (2004605).

  2. 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.

    Note: If you have the SSD drives in the RAID 1 setup, the RAID controller does not pass the correct parameters. This could be a potential issue when obtaining the information for a particular device.

  3. 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.ID --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. --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 reboot the ESXi host for the changes to take effect.

  4. Run this command to unclaim the device:

    # esxcli storage core claiming unclaim --type device --device naa.ID

    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 reboot the ESXi host, you can verify that the device has the rule applied.

  5. Run these commands to reclaim the device:

    # esxcli storage core claimrule load
    # esxcli storage core claiming reclaim -d naa.ID
    # esxcli storage core claimrule run


  6. Run this command to check the SSD status:

    # esxcli storage core device list -d naa.ID

    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 also use a generic vendor model notation instead of 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 that would have been normally 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 reboot 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:

# 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"

See Also

Update History

05/27/2013 - Correct the command under point 2 08/06/2013 - Added step 1 to procedure in Resolution section 04/04/2014 - Added VPLEX supportability under Confidential/Internal Solution.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 9 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 9 Ratings
Actions
KB: