11-17-2020 04:47 AM
We have several DC P3520 cards in our VMware virtualization environment with vSAN.
A few days ago we experienced a PSOD with the message telling us there was a stuck IO on an Intel SSDPEDMX020T7. These NVMe disks are part of a hybrid environment and used as flash disks in a diskgroup.
After creating a support request with VMware, we we're told these disk are not supported in a hybrid configuration.
According to the VMware Compatibility Guide, using keyword: SSDPEDMX020T7, we found that they are compatible in a vSAN Hybrid Caching Tier configuration.
Even the Intel SSD Datacenter tool tells us: INTEL SSDPEDMX020T7.
But VMware tells us, when they use the VendorID (8086), DeviceID (0953), Sub-VendorID (8086) en SSID (3705) , it is not supported.
And when we put these ID's in the VMware Compatibility Guide, we find a totally different device: SSDPE2MX020T4 (2000 GB, 2.5-inch) , which, according to the information, is not supported. It's not even correct on the form factor : we have a HHHL AIC, not 2.5-inch.
This leaves us with the question: what's the truth?
Do we have these: Intel® SSD DC P3520 Series SSDPEDMX020T7 (2.0 TB, HHHL AIC) which we specifically looked for, even the labels and isdct tell us,
or do we have these: Intel SSD DC P3500 Series SSDPE2MX020T4 (2000 GB, 2.5-inch), what the ID's give us?
If anybody could help us out... it makes a difference in having a supported environment or not.
11-25-2020 08:52 AM
Hello Josh,
We have not yet had an answer from VMware.
The problem is: we bought hardware based on a model nr./product nr., in this case: SSDPEDMX020T7. We bought these because they are on the VMware Compatibility Guide for vSAN. In our case they are used as caching disk in a hybrid configuration.
But VMware is looking to these cards only by VendorID(VID:8086), DeviceID(DID:0953), Sub-VendorID(SVID:8086) and Sub-DeviceID(SSID:3705). By model nr. we are in a supported configuration, by hardware ID's we're not in a supported configuration. It's not even what we bought.
Even better: after updating the firmware on 4 of these Intel® SSD DC P3520 Series cards to the latetst version (MDV10291: because that's what is supported according to the VMware HCL), the VID, DID and SVID are still the same but the SSID has changed from 3705 to 3707. And you won't find anything with an SSID 3707 on the VMware HCL.
Question: does a firmware upgrade change the SSID to reflect the firmware version it is running?
Kind regards,
RAdV
11-25-2020 03:46 PM
Hello RAdV,
Thank you for your reply.
To answer your question:
"Does a firmware upgrade change the SSID to reflect the firmware version it is running?"
The SSID – Subsystem ID – is like the Device ID, and it identifies a specific device from the Subsystem Vendor. I am not aware if it changes when the firmware is updated since our firmware would keep the same information. In case of installing a specific firmware provided by the OS manufacturer or if you have an OEM SSD, it may change to fit the manufacturer's needs.
We advise you to consult this information with VMware.
Please take into consideration that this information is not SSD dependant, and it is related to OS detection.
We understand your frustration regarding the SSD compatibility with your OS, but VMware is the one that defines which drives and features are compatible with their OS.
We are going to follow up with you again next Monday, the 30th of November 2020, if we do not receive an answer from you. Please let me know if you would like to schedule a different date for the follow-up.
Best regards,
Josh B.
Intel® Customer Support Technician.
11-30-2020 03:48 PM
Hello RAdV,
Greetings from; Intel® Memory and Storage support.
We were reviewing your community thread, which is related to your Intel® SSD DC P3520 Series. We would like to know if you were able to get more information from VMware* related to the SSID behavior.
We are going to follow up with you again next Friday, the 27th of November 2020, if we do not receive an answer from you. Please let me know if you would like to schedule a different date for the follow-up.
We will be looking forward to your reply in case you need further assistance.
Best regards,
Josh B.
Intel® Customer Support Technician
12-01-2020 11:33 AM
Hello Josh,
"The SSID – Subsystem ID – is like the Device ID, and it identifies a specific device from the Subsystem Vendor. I am not aware if it changes when the firmware is updated since our firmware would keep the same information. In case of installing a specific firmware provided by the OS manufacturer or if you have an OEM SSD, it may change to fit the manufacturer's needs."
The firmware update was done with Intel software: https://downloadcenter.intel.com/product/87278/Intel-SSD-Data-Center-Tool on ESXi 7.0 and by following the installation manual. All ID's stayed the same except the SSID. It went from 3705 to 3707. (As shown in the attached files.)
Firmware was MDV10271 and is now MDV10291.
I had contact with VMware about the HCL and there not being an IO-device with SSID 3707 and this was part of their answer:
"I would recommend to engage hardware vendor if they are whiling to cerfitied with vSAN as they need to pass a certification process."
Apart from that, I wondered if it is possible for you to verify these 'problems'?
Kind regards,
RAdV
12-02-2020 02:38 PM
Hello RAdV,
Thank you for your reply.
The SSID depends on the software capability to assigns an ID based on the SSD information, and as VMware told you, they have their formula on how to extract this information, and they are the only ones that can confirm to you why it changed.
As we mentioned: This information is not SSD dependant, and it is related to OS detection.
We do not process hardware validation at our level of support. If Vmware is interested in having any SSD validated and needs our assistance, they will contact us through a different channel of support.
They recommended you contact your vendor. If that is an option, please get in contact with them.
We have provided you with all the available public information, and if you need further assistance, we advise you to contact VMware*.
Best regards,
Josh B.
Intel® Customer Support Technician