Manual

3. From the shell prompt, enter vmware -v to verify the ESX version as 4.1.
NOTE: If root is not enabled, log in as a shell-enabled user.4. Enter rpm -q lsi-provider.
4. For ESX/ESXi host version:
a) Enter rpm -q lsi-provider for ESX hosts.
b) Enter esxupdate --vib-view query | grep lsi-provider for ESXi hosts.
The version listed is lsi-provider-410.04.V0.24-140815.
5. Enter esxupdate -b file:$PWD/vmware-esx4.1-SAS-provider.vib --nodeps --nosigcheck --
maintenancemode update.
NOTE: The esxupdate command shown above assumes that the .vib file is located in your
current working directory. If it is not, replace $PWD with the directory location of the .vib file.
Several unpacking, installing, and cleanup messages are displayed.
6. When the installation is complete, run esxupdate --vib-view query | grep lsi-provider.
The following messages should be are displayed:
cross_lsi-provider_410.04.V0.24-260xxx pending,installed
cross_lsi-provider_410.04.V0.24-140815 retired
7. Stop any running virtual machines.
8. Reboot the host.
9. When the host reboot is complete, run the following commands to verify the update successfully
installed:
a) For ESX host: rpm -q lsi-provider .
b) For ESXi hosts: esxupdate --vib-view query | grep lsi-provider.
Installing The SAS Provider (ESXi 5.0 and 5.1 Servers Only)
Follow the steps below to install the SAS provider upgrade on ESX 5.0 and 5.1 servers:
1. Run SCP to copy the vmware-esx5.0-SAS-provider.vib file to your target ESXi host.
2. Log in to the ESXi 5.0/5.1 host as root.
NOTE: If root is not enabled, enable it temporarily for this installation.
3. From the shell prompt, enter vmware -v to verify the ESXi version.
4. Enter esxcli software vib install -v file:/vmware-esxi5.0-SAS-provider.vib -f --maintenance-mode on
the same command line.
NOTE: The esxcli command above assumes that the .vib file is located in the / directory. If it is
not, precede the command with the location of the .vib file.
The following messages are displayed:
Installation Result
Message: The update completed successfully, but the system needs to be
rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: LSI_bootbank_LsiProvider_500.04.V0.24-261033
VIBs Removed:
VIBs Skipped:
5. Stop any running virtual machines.
33