Hi, I'm running VMware 4.1 Update 1. I have read from a couple places that I'm supposed to upgrade my enic/fnic drivers. I have downloaded the drivers from Cisco's web site but they point me to vmwares web site (except for 5.0 -- they do have a driver for that).
So I downloaded vmware's 4.x drivers. Several different versions. None of them show as applicable when I try to load them through vmware. Most come up as 4.0 which obviously wouldn't be applicable, but the last one was 4.1 and VUM still didn't think it applied.
my fnic driver is 188.8.131.52.2blah
my enic driver is 184.108.40.2061
I used this link to figure the versions out...
I am seeing a similar problem here at a customer site using UCS Firmware 2.0.1q to 2.0.1s and ESXi 5
VMware have an updated fnic driver 220.127.116.11 which is the minimum supported version by Cisco
You should be using the newest enic and fnic drivers, however you can use the enic driver 18.104.22.168a (according to the TAC)
How are they not applicable?
Hope this helps
Which version of UCS is it?
I have seen many problems installing the enic/fnic drivers using VUM, perform a manual install using vSphere CLI (if ESXi) or esxupdate (ESX).
Last versions I used for UCS1.4 were:
Enic - 22.214.171.124
Fnic - 126.96.36.199
However there may be newer versions available now. There are two types available usually, the ones from Cisco will be the latest but won't usually be signed and so you'll need to use the nosig option when installing, or the ones from VMware which may not be as up to date but are signed.
Sent from Cisco Technical Support iPad App
Thanks a lot for your response Jason.
Good info regarding VUM. I did use esxcli on vsphere 5 box (no vcenter = no vum) yesterday so I am familiar with that method.
We just upgraded to UCS 2.01s, but were on 1.4x before. I will try the cli method and thanks for the nosig comment, I figured that out the hard way yesterday
Let me know how you get on with 2.0(1s), I'd be interested to hear if you hit any issues or minor niggles along the way. I tried out 2.0(1t) today and have found a few issues (see discussion re: local storage).
Jason, we don't use local storage so I can't be of help there. My main problem is I get flogi errors which are cosmetic. I get them to go away, then I reboot a VM host and bang they come back. But I will be sure to whine, I mean post, about any things I see.
I have a similar problem only we are upgrading our UCS firmware to 2.1(1a) from 2.0(1q) in order to use the new B200 M3 blades. We need to upgrade our enic and fnic drivers for ESXi 4.1 U2. current versions are 188.8.131.52.2-4mvw for the fnic driver and 184.108.40.2061 for the enic. I used the following link
to determine the new version we need to use and it says that we need 220.127.116.11 for fnic and 18.104.22.168 for enic. I went to VMWARE to download and neither of these versions are available to download. the latest versions that i can find fir cisco cna are 22.214.171.124 for fnic and 126.96.36.199 for enic. We are using the M81KR adapter.
Does Cisco have the drivers available?
The enic and fnic drivers are not on VMWare website as instructed in the compatability Matrix. They are on the firmware 2.1(1a) iso. Found this document which is very good at finding and explaining how to upgrade your enic and fnic drivers on ESXi hosts.
Cisco UCS Virtual Interface Card Drivers for ESX Installation Guide
The firmware version 2.1(1a) that we were upgrading to had the drivers on the ISO. After that very simple.