I am building out a new pod at work for my lab. It has four new R730 Dell servers that are completely on the HCL for vSAN. It was important to me, so not only did I confirm that myself but I got someone else to confirm. When I installed vSAN in in our management cluster it was all good. Then I did it in my pod but this time instead of vSphere 6.5 it is 6.0 U3. And when I was done and all was good I saw this:
I had decided at the last minute to use the Dell vSphere build. And it turns out to have an old driver. So I switch to the Dell OpenManage tool as it is what I use for updates and figure it is an easy fix.
But then I see something odd:
First Dell thinks my H730 mini driver version is current. And second, it thinks it is 25.5.0.0018 which is a different set of numbers compared to what vSphere shows.
So this is odd. Now what?
So I talk to the Slack vExpert vSAN channel and Jase answers – and much thanks for that too Jase.
Turns out if I had used the VMware build instead of the dell build I would not have had this issue. And there is an update for the driver if I check the VCG.
Plus, I can update this driver in a number of different ways – not with the Dell OM tool I like so much, but with VUM (example here) – which most of you should use for this, or a CLI method that works fine too.
So lets do the update.
- need to download and extract the update, so that you can upload the .vib file to the /tmp folder on your hosts.
- We can see it in the screenshot above in that it starts with lsi and ends with .vib.
- After the update you will need to do a reboot, so I like to put the host into maintenance mode before I do this update.
- Now we are ready to do the update. If you copied the file to the /tmp folder, you will use a command line like below.
esxcli software vib install -v /tmp/lsi-mr3-6.903.85.00-10EM.600.0.0.2768847.x86_64.vib
- You can see above after I have hit return.
- Now below you can see it has finished.
- So now we restart.
- And we see what we did is good.
So we now know how to solve the problem we started with. While I tested this fix manually, I would most certainly use VUM to push this VIB out everywhere.
BTW, here is some background info on this controller and vSAN.
=== END ===