Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
BootBank_misc-cnic-register_1.78.75 Does not find in the depot
We using Lenono blades and recently created a custome image based off of Lenovo's ESXI 6 Update 2 image that does not include VIB that we do not need to reduce the size in the bootbank. Below is a list of all VMs remove from running host and from the new image. The running how are running fine. We recently installed ESXI 6 on a new blade and we I tried to push updates to it via Update Manager I got the following message VMware_BootBank_misc-cnic-
esxcli software vib remove -n "qlogic-cna-provider"
esxcli software vib remove -n "qlnativefc"
esxcli software vib remove -n "ima-qla4xxx"
esxcli software vib remove -n "net-bna"
esxcli software vib remove -n "net-qlcnic"
esxcli software vib remove -n "net-qlge"
esxcli software vib remove -n "scsi-bfa"
esxcli software vib remove -n "brcdprovider_esx55"
esxcli software vib remove -n "scsi-qla4xxx"
esxcli software vib remove -n "net-igb"
esxcli software vib remove -n "net-ixgbe"
esxcli software vib remove -n "scsi-bnx2i"
esxcli software vib remove -n "scsi-bnx2fc"
esxcli software vib remove -n "net-tg3"
esxcli software vib remove -n "net-cnic"
esxcli software vib remove -n "net-bnx2x"
esxcli software vib remove -n "net-bnx2"
esxcli software vib remove -n "misc-cnic-register"
esxcli software vib remove -n "brcm"
esxcli software vib remove -n "qlogic-cna-provider"
esxcli software vib remove -n "qlnativefc"
esxcli software vib remove -n "ima-qla4xxx"
esxcli software vib remove -n "net-bna"
esxcli software vib remove -n "net-qlcnic"
esxcli software vib remove -n "net-qlge"
esxcli software vib remove -n "scsi-bfa"
esxcli software vib remove -n "brcdprovider_esx55"
esxcli software vib remove -n "scsi-qla4xxx"
esxcli software vib remove -n "net-igb"
esxcli software vib remove -n "net-ixgbe"
esxcli software vib remove -n "scsi-bnx2i"
esxcli software vib remove -n "scsi-bnx2fc"
esxcli software vib remove -n "net-tg3"
esxcli software vib remove -n "net-cnic"
esxcli software vib remove -n "net-bnx2x"
esxcli software vib remove -n "net-bnx2"
esxcli software vib remove -n "misc-cnic-register"
esxcli software vib remove -n "brcm"
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
You've removed a VIB from your ESXi installation, and the Update has a dependency on the VIB you've removed.
Thanks I figured that, Do you know what this VIB is? Anyway I can download it from Vmware or grab it from anther host? Originally when I was working with support to create the image they did not seem to see any issue removing the VIB in question
Do you know what this VIB is? Anyway I can download it from Vmware or grab it from anther host?
We work in development building images, and testing in our labs, and then updating with Update Manager, and then testing.
I would start with misc-cnic-register, if you don't have the vibs to hand on your imaging machine, grab from another host.
but you may have a period of testing ahead.
Originally when I was working with support to create the image they did not seem to see any issue removing the VIB in question
and you believed them ? I would have thought by now you would have had enough experience to know, you are more experienced working in the real world, than VMware Support Engineer!
Thanks... Regarding your statement "I would start with misc-cnic-register, if you don't have the vibs to hand on your imaging machine, grab from another host."
I do not have an image machine an build the ISo using image builder. I check other host but the file in question is not in a VIB format in the bootbank.
I cannot find out any information om what this VIB is used for.
I do not have an image machine an build the ISo using image builder. I check other host but the file in question is not in a VIB format in the bootbank.
I cannot find out any information om what this VIB is used for.
I thought about this some more and realized i new the answer to my own question but just had to talk through it. I download the Offline bundle and extracted it and reinstalled the VIB. What I do not understand is this VIB is has a Qlogic tag on it yet our blade on uses Emulex and confused as to why an update in update manager was looking for it.
It may not be anything to do with Emulex, Qlogic but just dependencies, and what update manager expects to be present.
e.g. we have seen the following work
-SoftwarePackage misc-cnic-register,net-cni
but, if you just use a single package it will fail.
the devil is in the detail of the XML files.
e.g. we have seen the following work
-SoftwarePackage misc-cnic-register,net-cni
but, if you just use a single package it will fail.
the devil is in the detail of the XML files.
You are very wise as always and Vmware support told me the something. What they stated is what when customer create a custom image and run into a issue where a VIB has a dependency they install the missing VIB then remove it once the updates are installed. Is this true from your experience?
We don't operate like that, we spend many months building custom images for clients, and test, test, test and test, upgrades and updates against them (yes updates and upgrades are different from a VMware POV), we slim down images for specific builds, with only hardware which is in use (FC HBA, NICS), or going to be used, e.g. build is documented against each Vendor, Make and Model, Firmware versions, and signed off in a Document Build.
These builds then enter production, and should never have any issues in the future, of upgrades, updates via VUM, Offline, ISO upgrades. Each build is documented, as to what is included and excluded.
If a Dependency is required its in.
We do this, because as Consultants, we may not be around in the future, for whoever supports the environment!
So back to your question.....you remove it, you've got to put it back next time to do the update....
it's a bit like the The Hokey Cokey that approach!
These builds then enter production, and should never have any issues in the future, of upgrades, updates via VUM, Offline, ISO upgrades. Each build is documented, as to what is included and excluded.
If a Dependency is required its in.
We do this, because as Consultants, we may not be around in the future, for whoever supports the environment!
So back to your question.....you remove it, you've got to put it back next time to do the update....
it's a bit like the The Hokey Cokey that approach!
Premium Content
You need an Expert Office subscription to comment.Start Free Trial