vDCA550-Objective 1.2-2-Identify and tag SSD and local devices

There is some configuration in vSphere which requires SSD for configuration. Most of the time if we want to test this type of configuration in our lab. We end up have no SSD drive available for LAB environment. It is because SSD are very expense drives.

Fortunately, there is the way. We fool ESXi to believe the LUN as SSD.

Procedure

Let’s choose one storage LUN for sake of demonstration which is Non-SSD. In my case I am choosing “SSD-Tag-Testing” Storage. In First Step we identify our drive whether it is SSD or not, if not then in second step we will make him SSD.

We implement PSA NMP (Native Multipathing Rule) claim rule to achieve this. We will require two things for our configuration.

  • Device ID
  • Storage Array type

Let’s first find device ID and Storage Array Type of “SSD-Tag-Testing” Storage. You can find it from CLI and from GUI as well.

Identify SSD Drive:

From CLI:

To find the device ID against “SSD-Tag-Testing” Storage. SSH to the ESXi host where this storage is mounted and run following CLI command.

#esxcfg-scsidevs –m
vDCA550-Obj-1-2-TagSSD-01 To find whether device is SSD or not.
#esxcli storage core device list | less

(Find “IS SSD” option in our device)

vDCA550-Obj-1-2-TagSSD-02

To Find the Storage array

#esxcli storage nmp device list|less

(Find the Storage Array against our device)

vDCA550-Obj-1-2-TagSSD-03

From GUI:

To find whether device is SSD or not (Storage View in vSphere Classic Client)

vDCA550-Obj-1-2-TagSSD-04

To find the device ID against “SSD-Tag-Testing” Storage (Storage View in vSphere Classic Client)

vDCA550-Obj-1-2-TagSSD-05

Go to the Storage “Properties”-> Multipathing -> See your Storage Array Type as highlighted.

vDCA550-Obj-1-2-TagSSD-06

Tag SSD Drive:

Now we have every thing we need for our claim rule configuration. The next step is to add a PSA claim rule, marking the device as an SSD. We can do this by running the following:

#esxcli storage nmp satp rule add –s VMW_SATP_DEFAULT_AP –d t10.F405E46494C45425837546174494D2958787E4D284248366 –o=enable_ssd

Where –s (SATP) –d (device) –o (option)

vDCA550-Obj-1-2-TagSSD-07

Next we need to unclaim the device in order that we can claim it again using the new rule. run the following CLI Command.

#esxcli storage core claiming reclaim –t device –d t10.F405E46494C45425837546174494D2958787E4D284248366

Where –t (type) –d (device)

vDCA550-Obj-1-2-TagSSD-08

We can then reclaim the device using the following:

#esxcli storage core claimrule load
#esxcli storage core claimrule run (optional)

vDCA550-Obj-1-2-TagSSD-09
Verify

From CLI:

#esxcli storage core device list|less

(check your device “IS SSD” option. It should be true)

vDCA550-Obj-1-2-TagSSD-10

From GUI:

Go to the Storage view in ESXi Classic Client and verify your Datastore “Device Type” Colum

vDCA550-Obj-1-2-TagSSD-11

To Remove the SATP Rule

List the SSD Enable SATP rules. Run the following CLI command

#esxcli storage nmp satp rule list|grep –i “SSD’

vDCA550-Obj-1-2-TagSSD-12
Next remove the SATP and rule and then reclaim the device.

#esxcli storage nmp satp rule remove –s VMW_SATP_DEFAULT_AP –d t10.F405E46494C45425837546174494D2958787E4D284248366 –o=enable_ssd
#esxcli storage core claiming reclaim –d t10.F405E46494C45425837546174494D2958787E4D284248366

vDCA550-Obj-1-2-TagSSD-13
Wait for a while or rescan your storage adapter and verify your rule has been removed.

vDCA550-Obj-1-2-TagSSD-04

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s