Sometimes unfortunately there are situations where a vendor’s ESXi image includes a disk controller driver that is not on the vSAN HCL/VCG (VMware Compatibility Guide). Typically it is a new version of the driver which is supported for vSphere, but not yet for vSAN. In that situation, what should you do? So far there are two approaches I have seen customers take:
- Keep running with the included driver and wait for the driver to be supported and listed on the vSAN HCL/VCG
- Downgrade the driver to the version which is listed on the vSAN HCL/VCG
Personally, I feel that option 2 is the correct way to go. The reason is simple, vSphere and vSAN have different certification requirements for disk controllers and the vSAN certification criteria are just more stringent than vSphere’s. Hence, sometimes you see vSAN skipping certain versions of drivers, this usually means a version did not pass the tests. Now, of course, you could keep running the driver and wait for it to appear on the vSAN HCL/VC. If however, you hit a problem, VMware Support will always ask you first to bring the environment to a fully supported state. Personally, I would not want the extra stress while troubleshooting. But that is my experience and preference. Just to be clear, from a VMware stance, there’s only one option, and that is option two, downgrade to the supported version!
Definitely option#2 is correct way. agree
Nobody will be sure current driver will be listed on VCG and when it will be!
So thanks from your article. Actually you write best articles and best useful notes.
But one question as I saw in vSAN HCL it just show raid controller’ model for example P408i or …. and could not see it show driver’s version . Where can we see raid controller driver’ version that support with vSAN ?
Duncan Epping says
Maybe I am missing something, but when you go to the VCG and you click on the controller you have you see the driver? For example:
Totie Bash says
Wait I do remember VSAN HCL or may be compatibility matrix showing firmware and driver version. I always rely on VSAN health check to flag for issues regarding firmware/driver I would imagine that is what most people do.
Agree, what RIGHT way is nr.2. But downgrade drivers give me more stress on just updated VSAN 7.0.1 cluster. Running change object format also take time.
Disagree, what VMware from his side don’t give clients timeline, when testing will be done or make a note when you download HPE iso file from HIS site
Duncan Epping says
I understand, but also keep in mind that the vendor is responsible for testing the drivers. VMware is not involved and does not control their timelines, so it is very difficult for us to communicate their timelines.
Ronald de Jong (@Ronald_DJ_PQR) says
Coincidence, but yesterday I came across just this and did a downgrade of a driver, after vSphere did the upgrade. Not trying to plug my own blog ;), but here it is: https://my-sddc.net/vsan-and-vsphere-compatibility-differences/