Posted by Brian on Apr 11, 2011 in CLI, vMA, VMware, vSphere | 0 comments
This is not something that I’ve had to do very often. But on a recent customer engagement I was working with the client on setting up some new hosts that were recently purchased. These hosts were purchased with Embedded ESXi on them and additional PCI NICs were added to the config. The additional NICs did not have drivers available in the base ESXi build. Shortly after bringing the first host online we noticed that only the onboard NICs showed up in the list.
A quick search on Google for the Intel part number for the NIC lead me to the family name for the adapter. Then a search over at VMware lead me to the download page for VMware that provided the .ISO file to load the drivers into ESXi for the family of adapters. The process took only a few minutes and since this is something that does not come up that often I thought a short write up might help someone.
There are a few ways that this could be done, since we happened to be running ESXi the options were to use the vMA or vCLI. Since this was a new install and a vMA was not setup yet I just quickly tossed vCLI on a server. Then a quick download of the driver .ISO from VMware and unzip the package into a folder on the server with vCLI installed on it. If you wanted to use the vMA you could mount the .ISO to the virtual CD-ROM of the VM and issue the command against it.
Since I was using vCLI all I needed to do was point the command to a local folder. Here is a sample of the command used to perform the patch.
vihostupdate –server HOSTNAME –install –bundle c:\folder\name_of_file.zip
To run this command your host must be in Maintenance mode and it will then take just a couple of minutes to execute. After the update completes a reboot of the host is needed and then the cards should be available for use.
Brian is a Technical Architect for a VMware partner and owner of this website. He is active in the VMware community and is helps lead the Chicago VMUG group. This blog Virtualize Tips was started to document and remember things that I come across while working with tech.
Mail | Web | Twitter | LinkedIn | More Posts (170)
Posted by Brian on Jul 29, 2010 in CLI, vCenter Server, VMware, vSphere | 0 comments
Now that vSphere 4.1 has been out for a couple of weeks you’ve probably had some time to play with it in a lab. I’m sure you have also spent some time reading the release notes getting up to speed on the large list of new features that were released. After spending time myself getting familiar with many of the new options I wanted to dig in and see what was new with the Command Line Interface in 4.1. Since this is going to play a big part in how you will be managing ESXi hosts once you move your environment over to the platform of the future.
I have grabbed a list of the new commands added to vCLI 4.1, these command will help narrow the gap that had existed between what you could run on the ESX console (COS) and what you could do via the vCLI with an ESXi host. Notice the part at the end where it lists some of the commands that cannot be executed against a vCenter server for a host in lock down mode.
vicfg-hostops – Allows you to examine, stop, and reboot hosts and to instruct hosts to enter and exit maintenance mode.vicfg-authconfig – Allows you to add an ESX/ESXi host to an Active Directory domain, remove the host, and list Active Directory domain information.vicfg-ipsec – Supports IPsec setup.
vSphere CLI 4.1 also includes the following new functionality:
- The following options have been added to
esxcli:
esxcli swiscsi session – Manage iSCSI sessions.esxcli swiscsi nic – Manage iSCSI network interfaces.esxcli swiscsi vmknic – List VMkernel network interfaces available for binding to particular iSCSI adapter.esxcli swiscsi vmnic – List available uplink adapters for use with a specified iSCSI adapter.esxcli vaai device – Display information about devices claimed by the VMware VAAI (vStorage APIs for Array Integration) Filter Plugin.esxcli corestorage – List devices or plugins. Used in conjunction with hardware acceleration.esxcli network – List active connections or list active ARP table entries.esxcli vms – List and forcibly stop virtual machines that do not respond to normal stop operations.
- Some of the parity issues between vSphere CLI and the ESX service console have been resolved.
- You can now run vCLI commands using SSPI (
--passthroughauth) against both vCenter Server and ESX/ESXi systems.
- Lockdown mode allows vSphere administrators to block direct access to ESXi systems. With lockdown mode enabled, all operations must go through a vCenter Server system. The following commands cannot run against vCenter Server systems and can therefore not be used in lockdown mode:
vicfg-snmpvifsvicfg-uservicfg-cfgbackupvihostupdatevmkfstoolsesxclivicfg-ipsec
If you want to run these commands against an ESXi system, turn off lockdown mode using the vSphere Client.
Brian is a Technical Architect for a VMware partner and owner of this website. He is active in the VMware community and is helps lead the Chicago VMUG group. This blog Virtualize Tips was started to document and remember things that I come across while working with tech.
Mail | Web | Twitter | LinkedIn | More Posts (170)
