Home » Dell Manuals » Storage Devices » Dell PowerVault MD3660f » Manual Viewer

Dell PowerVault MD3660f Dell PowerVault MD Storage Array VMware vCenter Plug-i - Page 14

Installing the SAS Provider Upgrade

View all Dell PowerVault MD3660f manuals

Add to My Manuals
Save this manual to your list of manuals

Page 14 highlights

5 At a shell prompt, run the following command to reload the service: # service sshd restart To enable root login from a host console (ESXi only): Use these steps to enable root login from an ESXi host. If you are using an ESX host, see the following section. 1 Press the F2 key to switch to open the configuration menu. 2 Select Troubleshooting Options. 3 Select Enable Remote Tech Support. 4 Select Restart Management Agents. 5 Press the Esc key to close the Configuration menu. Installing the SAS Provider Upgrade This section contains two separate sets of steps for installing the SAS provider upgrade, depending on whether you are configuring an ESX or ESXi host. Installing the SAS Provider on ESX 4.1 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 the su command 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. Then, enter the su command to assume super-user role. 4 Enter rpm -q lsi-provider. The version listed is lsi-provider-410.04.V0.24-140815. 5 Enter the following command, all on the same command line: esxupdate -b file:/vmware-esx4.1-SAS-provider.vib --nodeps --nosigcheck -maintenancemode update NOTE: The esxupdate command shown above assumes that the .vib file located in the / directory. If it is not, precede the command with the location of the .vib file. The following messages should appear: Unpacking cross_lsi-provider ... Installing lsi-provider ... Cleaning up lsi-provider ... 6 When the installation is complete, run the following command: esxupdate --vib-view query | grep lsi-provider The following messages should appear: cross_lsi-provider_410.04.V0.24-260249 pending,installed cross_lsi-provider_410.04.V0.24-140815 retired 7 Stop any running VMs. 8 Reboot the host. 9 When the host reboot is complete, run the rpm -q lsi-provider command to verify that the upgrade was successfully applied. Dell MD Storage Array vCenter Plug-in | 14

Section	Page
Overview	5
Installation Prerequisites	6
Configuration Limitations	6
Localization Support	6
Logs, Warnings and Error Messages	6
Downloading the MD vCenter Plug-in	6
Upgrading from a Previous Version	6
Application Server Requirements	7
Before You Install the MD vCenter Plug-in	7
Installing the MD vCenter Plug-in	8
Configuring the Application Server and MD vCenter Plug-in	9
Configuring Storage Administrator Roles	10
Creating a Storage Administrator Role	10
Adding an Existing User to the Storage Administrator Role	12
No Access	13
Configuring SAS Support on ESX and ESXi Hosts	13
SAS Support Host Requirements	13
Installing the SAS Provider Upgrade	14
Installing the SAS Provider on ESX 4.1	14
Installing the SAS Provider on ESXi 4.1	15
Installing the SAS Provider on ESXi 5.0	15
MD vCenter Plug-in Security	16
Accepting and Installing the Trusted SSL Certificate	16
Microsoft Enhanced IE Security	19
MD vCenter Plug-in Features	21
MD vCenter Plug-in Features	21
Configuring Storage Arrays	21
Adding a Storage Array	22
Removing a Storage Array	23
Editing System Properties	23
Changing the vCenter Plug-in Password	23
Resolving a Password Mismatch between the MD Storage Array and the vCenter Plug-in	23
Storage Array Configuration Backup	23
Enable Automatic Save Configuration Backups	23
Initiate A Manual Save Configuration	24
ESX/ESXi Host SAN Configuration	27
Configuring ALUA Support	31
Changing Your Default Multipath Policy	31
Adding an SATP Claim Rule to Enable ALUA and Change the Multipath Policy to Round Robin	32
Networking Configuration for Fibre Channel and iSCSI Storage (ESX/ESXi 4.x only)	32
Connecting a Dell MD3600i-Series or MD Dense iSCSI Storage Array	32
Connecting a Dell MD3600f-Series or MD Dense Fibre Channel Storage Array	33
ESX/ESXi Host Configuration Wizard	35
Storage Array Summary	39
Support for Disk Pooling	40
Create Disk Group	41
Formatting Virtual Disks	42
Decision-making Schemes	43
Using the Predictive Scheme to Make Virtual Disk Decisions	43
Using the Adaptive Scheme to Make Virtual Disk Decisions	43
Creating a Virtual Disk	44
Snapshots Premium Feature	44
Creating a Snapshot of a Base Virtual Disk	45
Disabling a Snapshot	45
Re-creating a Snapshot	45
Deleting a Snapshot	45
Creating a Virtual Disk Copy	46
Remote Replication	48
Create Remote Replication	49
Suspending Remote Replication	50
Resuming Remote Replication	50
Changing Remote Replication Roles	50
Testing Remote Replication	50
Changing Remote Replication Parameters	51
Removing Replicated Pairs	51
Mapping a Virtual Disk	51
Datastores View	53
Storage Array Event Log	54
Manually Unregistering the MD vCenter Plug-in	55
Uninstall the MD vCenter Plug-in	56
Troubleshooting MD vCenter Plug-in Issues	57
Application Server Logs	57
I Receive an Error When Attempting to Register the vCenter Plug-in	57
I Cannot Communicate with the Application Server	58
I Cannot Create or Delete Objects	58
How Can I Maximize Client Performance	58
How Do I Suppress Slow Script Warning Messages	58
Why Can I Not Make Changes to the Storage Array?	58
The MD vCenter Plug-in Does Not Show the New Storage Array Name after a Clear Configuration Operation in MDSM	58
Long Timeout for SAS ESX Host Wizard Operation	59
Storage Administrator Privileges assigned to user Group not working	59
Save Dialog Does Not Appear when Attempting to Save Array configuration or MEL	59
Error Loading Arrays Message Displayed	59
Entering an Invalid Alternate Controller IP Address Causes Duplicate Array Entries	59
Add Array DNS Field is Limited to 30 Characters	59
Event log viewer scroll bar goes beyond the limit.	59
ESX Host Name Wraps Unless Window Expanded	60
Getting Help	62

Match case Limit results 1 per page

Dell MD Storage Array vCenter Plug-in

At a shell prompt, run the following command to reload the service:

# service sshd restart

To enable root login from a host console (ESXi only):

Use these steps to enable root login from an ESXi host. If you are using an ESX host, see the following section.

Press the F2 key to switch to open the configuration menu.

Select

Troubleshooting Options

Select

Enable Remote Tech Support

Select

Restart Management Agents

Press the Esc key to close the

Configuration

menu.

Installing the SAS Provider Upgrade

This section contains two separate sets of steps for installing the SAS provider upgrade, depending on whether

you are configuring an ESX or ESXi host.

Installing the SAS Provider on ESX 4.1

Use either SFTP or SCP to copy the

vmware-esx4.1-SAS-provider.vib

file to your target ESX host.

NOTE:

If root is not enabled, log in as a shell-enabled user and run the

command to assume super-

user role.

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. Then, enter the

command to assume

super-user role.

Enter

rpm -q lsi-provider

The version listed is

lsi-provider-410.04.V0.24-140815

Enter the following command, all on the same command line:

esxupdate -b file:/vmware-esx4.1-SAS-provider.vib --nodeps --nosigcheck --

maintenancemode update

NOTE:

The

esxupdate

command shown above assumes that the

.vib

file located in the / directory. If it

is not, precede the command with the location of the

.vib

file.

The following messages should appear:

Unpacking cross_lsi-provider ...

Installing lsi-provider ...

Cleaning up lsi-provider ...

When the installation is complete, run the following command:

esxupdate --vib-view query | grep lsi-provider

The following messages should appear:

cross_lsi-provider_410.04.V0.24-260249 pending,installed

cross_lsi-provider_410.04.V0.24-140815 retired

Stop any running VMs.

Reboot the host.

When the host reboot is complete, run the

rpm -q lsi-provider

command to verify that the upgrade

was successfully applied.