Well to tell you the thruth it doesnt even start.....
I`m trying to install 1000v VIB via CLI directly on the host via SSH.
Here is what I get
esxcli software vib install /tmp/VEM500-201108271.zip
Error: Unknown command or namespace software vib install /tmp/VEM500-201108271.zip
Even to list installed VIBs.
What am I doing wrong ? This is a new ESXi 5 install (upgrade from 4.1)
I spent all day searching I dont see anything regarding my issue anywhere... How is that possible ? Originaly I went from 4.1 to 5 as an upgrade, I`m assuming something went wrong there..... I was never able to use that command esxcli
Is this proper ?
This is waaaaay after the fact on this issue, but hopefully this will help others who have run into this problem:
If you are lazy like me, you cut-and-paste the command for the update, for instance:
esxcli software vib install –d /vmfs/volumes/datastore1/patch/update-from-esxi5.0-5.0_update02.zip
For some bizarre reason, the dash in front of the "-d" command is not interpreted correctly when you cut and paste to an SSH session with an ESXi host.
So either type it all out manually, or replace the dash after you've cut and pasted the command.
It won't look any different, but it's solved the problem for me every time.
In fact, the resaon I'm submitting this is so that it's out there the next time I forget and do a search for "Unknown command or namespace".
Here's the solution for me
Apply this syntax:
esxcli software vib install --depot=/path/to/package.zip
esxcli software vib install --depot=/tmp/dell/OM-SrvAdmin-Dell-Web-7.1.0-5304.VIB-ESX50i_A00.zip
To install Dell Open Manage.
ggathagan's fix worked for me. Pesky little dash. I had cut and paste from our internal wiki that I created when updating one standalone host. Tried another host and it failed. Was really puzzled until I used the same command but this time replacing the pasted dash with a manually entered dash.
First, unpack the archive, then add -v, so it should look like esxcli software vib install -v /path_to_vib_file. For best effect, put the binaries on shared vmfs, it will be available for every esx box in the cluster.
Here is the KB with installing patches from CLI
esxcli software vib install -d /tmp/VEM500-201108271.zip
and make sure you have full acess to the folder, seeing as your probably logged in as Root you should be good to go.
In my humble contribution to this post, this is what I did to solve the installation of vxlan vib on each host,
1.-Download the vib file vxlan.zip from vcns, if blocked check ports or IE settings
2.-copy with SCP to each host in cluster in tmp the .zip file
3.-Intall the vib with this command esxcli software vib install –depot=\tmp\vxlan.zip
4.- run refresh on virtual networking vcenter vcns
5.- if APIPA ip addres on recently created vmkenel port, just go to vds and change it
6.-run resolve in case, or just will see green check mark