Looking for a Micron RealSSD Manager vmw-esx55-micron-rssdm vib

[jackchentoronto]

We are having problem with one SSD disk on our Dell PowerEdge R820 ESXi 6 host, so I need to get the Micron RealSSD Manager package to troubleshoot the disk.

http://www.micron.com/dell/

Has a "RealSSD Manager for SP 145.07.08" , but this package only has a  vmw-esx-micron-rssdm-2.10.5818.00.vib, it's not even for ESXi 5.5

I tried it on our ESXi 6, it couldn't detect the SSD disks.

based on other user's experience http://ymmit.net/2015/02/11/updating-firmware-on-micron-pci-ssd-2/

The older version "RealSSD Manager for SP 145.03.08" actually has a newer version vmw-esx55-micron-rssdm-2.20.11180.00.vib , not sure what's going on on Micron's website.

Anybody has a working vmw-esx55-micron-rssdm-2.20.11180.00.vib or newer version rssdm ? If so, could you please send it to me ?

Thank you very much!

-Jack

[jmass]

I checked with the team that writes RSSDM and that is the most current release (SP 145.07.08), they also said it works on ESXi 6 as well. I will check on the VIB version and figure out the difference.

Were these drives purchased from Dell and have Dell's part number or from another source?

[jackchentoronto]

Thanks Jmass.

The rsssdm in SP145.07.08 only has a vmw-esx-micron-rssdm-2.10.5818.00.vib file and the micron-rssdm file inside it is only 130401 byte, pretty small.

The vmw-esx55-micron-rssdm-2.20.11180.00.vib file from SP145.03.08 should have a micron-rssdm with size 332120, much bigger ( I actually got a copy of the vmw-esx55-micron-rssdm-2.20.11180.00.vib from Tim so I know the correct size for the micron-rssdm in vmw-esx55-micron-rssdm-2.20.11180.00.vib , unfortunately seems it's corrupted, can't even extract it with ar).

The drives are directly purchased from Dell ( can't locate the part number right now, Micron part number P420m2DMTFDGAR700MAX ). Dell support hasn't able to find the working rssdm for me yet.

[jackchentoronto]

I installed the rssdm from 145.07.08:

esxcli software vib list | grep -i micron

mtip32xx-native                3.9.4-1OEM.550.0.0.1331820            MICRON  VMwareCertified   2015-12-03

micron-rssdm                   2.10.5818.00-01                       Micron  PartnerSupported  2015-12-03

It couldn't find the devices:

/opt/micron/bin/rssdm -L

CMD_STATUS   : Unable to find any P320 drives connected

STATUS_CODE  : 10

The server does have two SSD disks:

esxcli vsan storage list | grep ^t10

t10.ATA_____Micron_P420m2DMTFDGAR700MAX______________serial1

t10.ATA_____Micron_P420m2DMTFDGAR700MAX______________serial2

[dedwardsmicron · Accepted solution]

Many apologies for the late response.  We've been trying to figure out the proper version of RSSDM and where it should be downloaded from.

You have the latest RSSDM utility from Dell.  There is a newer version of RSSDM in Micron's service pack repository that has a fix that was not released in Dell's service pack version.  Downloading what we call a general distribution service pack should fix your problem.

Access to the service pack does require user login to access and apparently the web site doesn't make it easy to acquire a specific link to a download.

I was able to find the appropriate service pack with our "general distribution" version by searching for "micron SP 145.07.00".  In the results you should find a link to a download such as:

Support Pack Version 145.07.00_Linux_VMware Release for Distribution.

Support Pack Version 145.07.00_Linux_VMware - Contains, Drivers, RSSDM, Install Guides

When you download the file it will have a file name of "B145.07.00_Linux_VMware.gz", and if you unzip it you will find a vmware 5.5 version of RSSDM .vib installer.  This will also work in 6.0.

Please reply to this thread with your results,

D.

P.S. the desired RSSDM version is: 2.20.11180.00

[jackchentoronto]

Awesome! Downloading it now, will update the result later.

[jackchentoronto]

removed old rssdm, then installed the new one, not it's working 🙂

/opt/micron/bin/rssdm -L

Drive Id             : 0

Device Name          : mtip_rssd0

Model No             : Micron P420m-MTFDGAR700MAX

Serial No            : 00000000AAAAAAA

FW-Rev               : B2085108

Total Size           : 700.15GB

Drive Status         : Drive is in good health

PCI Path (B:D.F)     : 03:00.0

Vendor               : Micron

Temp(C)              : 53

Drive Id             : 1

Device Name          : mtip_rssd1

Model No             : Micron P420m-MTFDGAR700MAX

Serial No            : 00000000BBBBBBB

FW-Rev               : B2120508

Total Size           : 700.15GB

Drive Status         : Drive is in good health

PCI Path (B:D.F)     : 44:00.0

Vendor               : Micron

Temp(C)              : 65

Drive information is retrieved successfully

CMD_STATUS   : Success

STATUS_CODE  : 0

Copyright (C) 2014 Micron Technology, Inc.

[dedwardsmicron]

Fantastic!  For anyone else who finds this article useful, I found a hard link to the service pack files SP 145.07.00 mentioned previously:

http://www.micron.com/~/media/documents/products/software/b145,-d-,07,-d-,00_linux_vmware.gz

D.

[jackchentoronto]

Thanks Edward, I have a related questions:

I have SSD disks with firmware B2085108 , I would like to upgrade them to B2180108. According to https://www.micron.com/resource-details/0182baaf-ac55-4c80-9f38-cabc6195cd21

I need to do secure erase after firmware upgrade. I just want to confirm this is the correct procedure:

1. turn host into maintenance mode.

2. drop existing diskgroups ( evacuate data ).

3. upgrade firmware

4. reboot

5. secure erase disk

6. recreate diskgroups

Are those the correct steps ?

Thanks!

-Jack

[PhilD12345]

I've been through this process a few times. You have it mostly right, except for #4. I corrected it below.

1. turn host into maintenance mode.

2. drop existing diskgroups ( evacuate data ).

3. upgrade firmware

4. power cycle the computer. That is to say power off, then power back on. A reboot will not work.

5. secure erase disk

6. recreate diskgroups

Excuse the use of my personal VMware account and not the one from my employer (micron) for the user name.

[jackchentoronto]

Thanks Phil.

I upgraded  the firmware on our ESXi hosts, now I have a new issue, Vmware suggested I should contact the vendor to trouble shoot it. I am wondering what's the best way to get support from Micron team?

We have a 4 hosts vSAN cluster with 8 Micron P420M SSD disks, after the firmware upgrade, I saw some repeated error for 2 of the SSD disks on two different hosts:

server 1's vmhba2:

Description Type Date Time Task Target User

LSOM SSD 5213d40f-45c6-5c8f-9d2d-fd612361df5a Congestion State: Exceeded. Congestion Threshold: 200 Current Congestion: 204. Error 12/8/2015 3:51:57 AM 10.4.33.113

...

server2 's vmhba1:

Description Type Date Time Task Target User

LSOM SSD 529a1bb7-2647-99b1-092a-96cc649ad5c9 Congestion State: Exceeded. Congestion Threshold: 200 Current Congestion: 204. Error 12/8/2015 6:47:00 PM 10.4.33.115

...

from the vobd.0 log files for server1, seems it started at :

2015-12-08T08:16:34.331Z: [scsiCorrelator] 18138374336us: [vob.scsi.device.io.latency.high] Device t10.ATA_____Micron_P420m2DMTFDGAR700MAX______________0000000015050F0B77C0 performance has deteriorated. I/O latency increased from average value of 756 microseconds to 18011 microseconds.

2015-12-08T08:16:34.331Z: [scsiCorrelator] 18138749203us: [esx.problem.scsi.device.io.latency.high] Device t10.ATA_____Micron_P420m2DMTFDGAR700MAX______________0000000015050F0B77C0 performance has deteriorated. I/O latency increased from average value of 756 microseconds to 18011 microseconds.

2015-12-08T08:16:35.190Z: [scsiCorrelator] 18139233685us: [vob.scsi.device.io.latency.improved] Device t10.ATA_____Micron_P420m2DMTFDGAR700MAX______________0000000015050F0B77C0 performance has improved. I/O latency reduced from 18011 microseconds to 3516 microseconds.

2015-12-08T08:16:35.190Z: [scsiCorrelator] 18139608414us: [esx.clear.scsi.device.io.latency.improved] Device t10.ATA_____Micron_P420m2DMTFDGAR700MAX______________0000000015050F0B77C0 performance has improved. I/O latency reduced from 18011 microseconds to 3516 microseconds.

2015-12-08T08:16:36.935Z: [scsiCorrelator] 18140978167us: [vob.scsi.device.io.latency.improved] Device t10.ATA_____Micron_P420m2DMTFDGAR700MAX______________0000000015050F0B77C0 performance has improved. I/O latency reduced from 3516 microseconds to 1512 microseconds.

2015-12-08T08:16:36.935Z: [scsiCorrelator] 18141353231us: [esx.clear.scsi.device.io.latency.improved] Device t10.ATA_____Micron_P420m2DMTFDGAR700MAX______________0000000015050F0B77C0 performance has improved. I/O latency reduced from 3516 microseconds to 1512 microseconds.

Then this happened :

2015-12-08T08:42:53.301Z: [VsanCorrelator] 19717312272us: [vob.vsan.lsom.congestionthreshold] LSOM SSD 5213d40f-45c6-5c8f-9d2d-fd612361df5a Congestion State: Exceeded. Congestion Threshold: 200 Current Congestion: 204.

2015-12-08T08:42:53.302Z: [VsanCorrelator] 19717719793us: [esx.problem.vsan.lsom.congestionthreshold] LSOM SSD 5213d40f-45c6-5c8f-9d2d-fd612361df5a Congestion State: Exceeded. Congestion Threshold: 200 Current Congestion: 204.

2015-12-08T08:42:53.309Z: [VsanCorrelator] 19717320667us: [vob.vsan.lsom.congestionthreshold] LSOM SSD 5213d40f-45c6-5c8f-9d2d-fd612361df5a Congestion State: Normal. Congestion Threshold: 200 Current Congestion: 140.

...

2015-12-08T08:43:22.807Z: [VsanCorrelator] 19746817696us: [vob.vsan.lsom.congestionthreshold] LSOM SSD 5213d40f-45c6-5c8f-9d2d-fd612361df5a Congestion State: Exceeded. Congestion Threshold: 200 Current Congestion: 204.

2015-12-08T08:43:22.807Z: Event rate limit reached. Dropping vprob: esx.problem.vsan.lsom.congestionthreshold

2015-12-08T08:43:22.816Z: [VsanCorrelator] 19746825471us: [vob.vsan.lsom.congestionthreshold] LSOM SSD 5213d40f-45c6-5c8f-9d2d-fd612361df5a Congestion State: Normal. Congestion Threshold: 200 Current Congestion: 128.

2015-12-08T08:43:22.816Z: Event rate limit reached. Dropping vprob: esx.problem.vsan.lsom.congestionthreshold

2015-12-08T08:45:57.000Z: Successfully sent event (esx.problem.vsan.lsom.congestionthreshold) after 1 failure.

Then after 2015-12-08T08:45:57.000Z, the error is gone and never come back.

It happened around 3AM EST time, nobody was really doing anything on the system. What might cause the SSD performance deteriorate ?

[jackchentoronto]

BTW, the error didn't last long, it happened on each server for less than 10 minutes, then they haven't came back so far. But when it was happening, it generated lots of error every seconds.