Installing the sas provider upgrade – Dell POWERVAULT MD3620I User Manual
Page 15
Enabling Root Login From A Host Console (ESX Servers Only)
Follow the steps below to enable root login from an ESX host.
1.
Log in as root.
2.
Open the /etc/ssh/sshd_config file.
3.
On the line that contains PermitRootLogin, change no to yes.
4.
Save and close the file.
5.
At a shell prompt, run the following command to reload the service: # service sshd restart.
Enabling Root Login From A Host Console (ESXi Servers Only)
Follow the steps below to enable root login from an ESXi host.
1.
Press F2 to switch to open the configuration menu.
2.
Select Troubleshooting Options.
3.
Select Enable Remote Tech Support.
4.
Select Restart Management Agents.
5.
Press Esc to close the Configuration menu.
Installing The SAS Provider Upgrade
The following section contains separate steps for installing the SAS provider upgrade, depending on whether you are
configuring an ESX or ESXi host.
Installing The SAS Provider Upgrade (ESX 4.1 Servers Only)
Follow the steps below to install the SAS provider upgrade on ESX 4.1 servers:
1.
Use either SFTP or SCP to copy the vmware-esx4.1-SAS-provider.vib file to your target ESX host.
2.
Log in to the ESX 4.1 host as root.
NOTE: If root is not enabled, log in as a shell-enabled user and run su to assume super-user role.
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.
Enter rpm -q lsi-provider.
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.
15