VIB install fail - due to dependency

[barnette08]

I am getting the below error when attempting to install a enic driver manually.  I have tried with the offline bundle .zip as well as the .vib file.  There is not an image profile on this host, can anyone give any insight as to what might be going on here?

[DependencyError]

VIB Cisco_bootbank_net-enic_2.1.2.42-1OEM.550.0.0.1198611 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile.

VIB Cisco_bootbank_net-enic_2.1.2.42-1OEM.550.0.0.1198611 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.

[Shrikant_Gavhan]

Hi barnette08.

Please try below steps and check,

1. unzip the bundle on your computer.

2. move/copy the .vib file to any location on the esxi. (for example /tmp)

3.run the esxcli command with complete path to the vib file.

example:

esxcli software vib install -v /tmp/xxxxxxxxxxx.vib

4. if reboot required, reboot the esxi.

Hope this helps you.

Thanks and Regards,

Shrikant Gavhane.

[Shrikant_Gavhan]

Hi Barnette08,

There is option to force the vib installation ignoring the vib dependancies but it is not recommended.

Please find below.

--force | -f

Bypasses checks for package dependencies, conflicts, obsolescence, and acceptance levels. Really not recommended unless you know what you are doing. Use of this option will result in a warning being displayed in the vSphere Client.

Here is the link.

vSphere Documentation Center

Re: Broadcom Driver VIB Injection Fails

Thanks and Regards,

Shrikant Gavhane

[barnette08]

When running the commands, I typically use the -d for installing a .zip and fall back on the -v for installing .vib files so the syntax is correct.

Also,  I haven't attempted the --force flag yet because I need to look into some things before doing so.  I did want to see if anyone knew anything about the dependency though.  I am attempting to install this enic driver using ESXi 5.1 U1.  Is there possibly a different list of vibs in ESXi 5.5?

[VirtuallyMikeB]

I'm also running into this.  Config includes B200M3 blades, ESXi 5.1U2, VIC 1240, UCSM 2.2(1).  The fnic driver install for 1.6.0.5 works fine, but the enic driver install for 2.1.2.42 does not, giving me the same dependency error.

The image profile it speaks of seems to be the image from which it was installed. For instance, two of my hosts have the following Image Profiles

(Updated) ESXi-5.1.0-1065491-custom

(Updated) ESXi-Customizer

Since we've installed patches and updates since the original installation, I believe that's the "(Updated)" part.  The first Image Profile comes from Cisco's customized ESXi ISO and the second comes from a vanilla ESXi build.  I used the ESXi Customizer tool from v-front.de to bake in drivers.

I haven't been able to resolve the dependency.  I've used the two mentioned ESXi builds, plus updated each to 5.1 Update 2 including Express Patch 4.  For other reasons, we have to stay on 5.1.  Using Cisco's interoperability tool, we have to use the drivers mentioned above.

Edit: I also tried the -f switch to force the install. That sucked. On reboot, the host didn't recognize it's NICs.  A reinstall later and I'm back at the dependency error.

Any thoughts?

-----------------------------------------

Please consider marking this answer "correct" or "helpful" if you found it useful.

Mike Brown

VMware, Cisco Data Center, and NetApp dude

Consulting Engineer

[e-mail]

Twitter: @VirtuallyMikeB

Blog: http://VirtuallyMikeBrown.com

LinkedIn: http://LinkedIn.com/in/michaelbbrown

Message was edited by: Mike Brown

[robmille9]

I ran into the same problem and did the -f, despite your post, and also got 'no nics recognized and had to reinstall.  Updated my version of ESXi to one that was actually on the compatibility matrix with the code on my UCS, and am not having the connectivity issue or the enic/fnic issue now.

[Alistar]

Hello there,

is your ESXi host fully patched with the latest patches? There might have been an important update that introduced a newer version of the driver/vmkAPI.

[LubomirZvolens1]

this was happening to me when I tried to install ESX v5.5 driver on host running ESX v5.1  :smileyhappy:   I simply didn't notice I have different version available and messed it up.

As simple as that. I had mixture of ESX5.5 and 5.1 hosts and I was trying to install wrong driver on ESX5.1.

I see this is old topic, just wanted to provide insight - maybe somebody will need it in future. Make sure driver you are trying to install is intended for the ESX version you are running.

[andcalDQ]

I've had similar experience before, opened a case, and was told by the engineer that I used the wrong vib file. They gave me a seemingly identical file, except it worked.

Now when I look for vib files, I notice 3 seemingly identical files within the .iso and .zip file structure at different nested levels, so I figure I must have just used the wrong one.

One example:

Downloaded the .iso from VMWare with ESXi drivers for a given version of ESXi, mount it, then find 3 seemingly identical files at 3 different locations within  different zip files (one within a nested zip file)

Specifically: here are the 3 paths with F: representing the mounted ISO:

F:\Network\Cisco\VIC\ESXi_6.0U3\ESXi60-enic-2.3.0.14-6004419.zip\net-enic_2.3.0.14-1OEM.600.0.0.2494585.vib

F:\Network\Cisco\VIC\ESXi_6.0U3\ESXi60-enic-2.3.0.14-6004419.zip\ESXi60-enic-2.3.0.14-offline_bundle-6004419.zip\vib20\net-enic\CSCO_bootbank_net-enic_2.3.0.14-1OEM.600.0.0.2494585.vib

F:\Network\Cisco\VIC\ESXi_6.0U3\ESXi60-enic-2.3.0.14-offline_bundle-6004419.zip\vib20\net-enic\CSCO_bootbank_net-enic_2.3.0.14-1OEM.600.0.0.2494585.vib

All 3 vib files have the exact name both are exactly 55 KB, I can't imagine 3 different situations when I would need to use a different file for each, where the proper answer is to provide 3 different but indistinguishable files and the user has to guess which one to use. I'm sure the context of where the file is located within the file structure gives the answer, but translating the path to your situation is not exactly obvious if you don't already know (which I don't).