No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Mapped LUN from OceanStor 5500 V3 on ESXi Hosts appear to be not recognized as SSD

Publication Date:  2018-02-08 Views:  72 Downloads:  0
Issue Description

Mapped LUN from OceanStor 5500 V3 on ESXi Hosts is not recognized as SSD

Alarm Information

After the LUN are Mapped from OceanStor 5500 V3 on the ESXi Hosts they appear to be not recognized as SSD disk.

 

Handling Process

After checking the logs all the disks appear to be fine and no hardware alarm occur.

 

Root Cause

The OceanStor 5500 V3 have the fuction to discover the SSD automatically no need any other configuration.

Solution

Even if the status is Non: SSD the disk are recognized as SSD and the performance is good without being affected.

 

Suggestions

In the worst case , if the disk are not recognized as an SSD disk, need to enable the SSD option on SSD based disks/LUNs that are not detected as SSD by default.

For that :

Log in to the host as root, using either the Console DCUI or SSH

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

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

- Run this command to unclaim the device:

# esxcli storage core claiming unclaim --type=device --device naa.6006016015301d00167ce6e2ddb3de11

- 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


  • - Run this command to check the SSD status:

    # esxcli storage core device list -d naa.6006016015301d00167ce6e2ddb3de11 | grep SSD
      1. END