Dell MD Storage Array VCenter Plug-In User's Guide
Dell MD Storage Array VCenter Plug-In User's Guide
Plug-in
User's Guide
Notes and Cautions
NOTE: A NOTE indicates important information that helps you make better use of
your computer
____________________
Information in this publication is subject to change without notice.
© 2011 Dell Inc. All rights reserved.
Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Trademarks used in this text: Dell™, the DELL logo and PowerVault™are trademarks of Dell Inc. Microsoft® and Windows® are either trademarks
or registered trademarks of Microsoft Corporation in the United States and/or other countries. VMware®, vCenter®, and vSphere® are registered
trademarks or trademarks of VMWare, Inc. in the United States or other countries.
Other trademarks and trade names may be used in this publication to refer to either the entities claiming the marks and names or their products. Dell
Inc. disclaims any proprietary interest in trademarks and trade names other than its own.
Contents | 3
Formatting Virtual Disks ...................................................................................................................................... 35
The Installation Log Not Show that the Pegasus Service Started ............................................................................ 48
The vCenter Plug-in Does Not Show the New Storage Array Name after a Clear Configuration Operation in MDSM ... 49
Contents | 4
Dell MD Storage Array vCenter Plug-in
1
Overview
The Dell MD Storage Array vCenter Management Plug-in Installation and User Guide is a VMware vCenter
Server 4.x Plug-in that provides integrated management of Dell MD Storage Array series from a vSphere
Client. The vCenter Plug-in allows administrators to have a single management interface (vSphere Client) to
manage all of their day-to-day storage needs along with their VMware infrastructure. This alleviates the need
for vCenter administrators to learn another management tool and focus instead on the entire virtual
infrastructure.
The vCenter Plug-in enables the vCenter administrator to configure ESX and ESXi hosts to Dell MD Storage
Arrays, create, map, delete virtual disks from the Dell MD Storage Arrays to the ESX host, and view the
vCenter datastores to Dell MD Storage Array virtual disks. The vCenter Plug-in also allows the creation of
hardware snapshots, virtual disk copies, and remote replication, when these premium features are enabled on
the storage array. The vCenter Plug-in uses an application server to facilitate the interface between the vSphere
Client and the Dell MD Storage Array based on the authenticated logged-in user and the privileges assigned to
that user's role.
NOTE: The vCenter Plug-in requires that a vCenter Server be installed within the environment. The
vCenter Plug-in does not function in a vSphere client and ESX host-only configuration.
Recommended Configurations
The vCenter Plug-in uses the SMI-S protocol to communicate with the storage arrays that are managed within
the vSphere infrastructure. Many procedure calls are made to obtain and send changes to the storage arrays,
which require large amounts of data to be passed between the storage arrays, the application server, and the
vSphere client. The number of managed storage arrays, the number of virtual disks, and the number of physical
disks on each storage array determine the overall performance of the vCenter Plug-in. Therefore, limit the
number of managed system components to the following:
No more than 10 Dell MD series storage arrays
No more than 256 objects, such as virtual disks, virtual disk copies, and snapshots, on each array
No more than 16 remote replications
After you have downloaded the vCenter Plug-in software, copy the file to the system that will be the
application server. Run the vCenter Plug-in installer to launch the installation wizard. The installation wizard
installs a Jetty application server and the SMI-S provider. After the installation is complete, the installation
wizard registers the vCenter Plug-in with the vCenter Server.
During the installation process, you must provide information about the system components, such as the
storage array names, the IP addresses, and the DNS names, used during the installation. Table 1 shows the
information required for each component.
NOTE: When you are upgrading from an earlier version of the vCenter Plug-in, and the storage arrays already have
passwords, re-enter the previous passwords in the updated version of the vCenter Plug-in for each storage array. You cannot
modify the storage arrays until the passwords have been re-entered.
6 Change the IP address of the application server when desired. The IP address defaults to the IP address
of the system the installer is running on. Click Next.
7 The next screen prompts you for the IP address of the vCenter server on which to install the vCenter
Plug-in. Enter the IP address of the vCenter server and click Next.
8 Enter the Administrator's email address for alerts and click Next.
9 Enter the vCenter Administrator's User ID and click Next.
10 Enter the vCenter Administrator's password and click Next.
11 The installation is now complete. Click Done to close the installation wizard.
12 To verify that the application server was installed successfully, run the services.msc command, and
verify that the cimserver service was installed and that both the cimserver service and the Jetty6-Service
service have started.
NOTE: After the application server reboots, the name of the CIMOM service changes to Pegasus CIM Object Manager.
NOTE: In the event one of these services crash or is stopped, the CIMOM service must be started before the Jetty service or
no updates/modifications will occur.
4 In the Name text box, type the name of the new role.
5 On the Privileges list, select the access permissions to assign to this role.
NOTE: The administrator role is not editable and, therefore, if the administrator user will be used to
manage storage, a new role must be created that has all of the privileges added to it. The administrator
user must then be added to this role as the following procedure details.
6 To allow Read Only or Read Write access permissions to the storage arrays, select the appropriate
permission from the Storage Administrator group. See Figure 4.
7 Click OK.
NOTE: Existing roles may also be modified to include the Storage Administrator privileges, except for the
Administrator role, which cannot be modified.
3. From the wizard, click Add and select the User ID (s) that require access to the storage arrays.
4. Then select the modified Role from the drop down box and click OK to apply changes.
5. Click OK to apply permissions to the role.
To use the SAS provider, it must first be deployed on the ESX/ESXi servers to be configured. This requires
that SFTP or SCP be enabled on the ESX/ESXi hosts. Root access is also required to install the package, and to
install the package by remote login, either a new user must be created with host login rights or the root user
must be enabled for remote logins.
NOTE: If root is not enabled, log in as a shell-enabled user, and su to super user.
4 Enter rpm -q lsi-provider for ESX or esxupdate --vib-view query | grep lsi-
provider for ESXi hosts. The version listed should be: lsi-provider-410.04.V0.24-
140815.
5 Enter esxupdate -b file:$PWD/vmware-esx-provider-lsi-provider.vib --
nodeps --nosigcheck --maintenancemode update, this assumes the .vib file is located in
the same directory that esxupdate is being executed from, if not, change $PWD to the directory where
the .vib file is located.
6 You should see Unpacking cross_lsi-provider, Installing lsi-provider, and Cleaning up lsi-provider
7 After the update finishes, enter esxupdate --vib-view query | grep lsi-provider.
You should see the following information:
cross_lsi-provider_410.04.V0.24-260xxx pending,installed
cross_lsi-provider_410.04.V0.24-140815 retired
To avoid this message, you can import the install generated certificate into the systems Trusted Root
Certification Authorities store as listed below:
3 Click Next from the Certificate Import Wizard message box. See Figure 9.
NOTE: The subject name of the system, in the certificate must match the system name of the vCenter
Server during the vSphere Client login screen or you will continue to receive a warning message stating
the certificate does not match the site name.
3 In the DNS name or IP address 1 text box, type the IP address or name of the storage array’s controller
A.
4 In the DNS name or IP address 2 text box, type the IP address or name of the storage array’s controller
B.
5 In the Password text box, type the password for the storage array that you are adding to the vCenter
Plug-in.
6 Click Add.
NOTE: Only the base storage array configuration information is saved. Objects such as snapshots,
virtual disk copies, and remote replications are not saved to the script file.
The vCenter Plug-in Automatic Save Configuration will perform a save configuration of the storage array after
a configuration event has occurred on the storage array, either from the vCenter Plug-in or from MDSM. A
storage array modification event will start a 4 minute timer, on the application server, at the time of the event
on the storage array. If within that 4 minute time window, no other configuration events have occurred on the
storage array, a save configuration will occur. If another modification event occurs within the 4 minute time
window, the timer will be reset to 4 minutes. When no modification events are detected on the storage array
within the 4 minute window, a save configuration will be performed. Automatic Save Configuration will
maintain the last 15 save configuration script files.
NOTE: The automatic backup script files are located under C:\Program Files (x86)\Dell\MD Storage
Array vCenter Plug-In\jetty\savecfg directory.
5 Click Save
A Save As dialog box will be displayed. See Figure 19.
6 Select the location and file name to save the backup configuration script as.
7 Click Save
This method works well to maintain the in-case of a hardware failure; however, MRU only maintains one
active path for each HBA group. Therefore, if you have an ESX host with four HBAs, only one HBA is active
at a time. To achieve higher I/O throughput from the ESX host to the storage array, it is recommended that you
group the HBAs in pairs and create virtual hosts for each pair of HBAs. This allows for a fully redundant
configuration but also allows for two of the HBAs to be active at the same time versus a single HBA. See
Figure 23. From the storage array, the second pair of HBAs is defined as a separate host and virtual disks can
then be mapped directly to the new host or host group. This same methodology can be used to group additional
HBAs in the same manner. This does require additional management to balance the LUNs between the
hosts/host groups to fully use the fibre channel bandwidth between all HBA groups. When this method is used
in the array, the Automatic ESX host configuration utility cannot determine which HBAs are configured to
each zone in the and the user must verify that a single HBA is connected to both fabric zones for each HBA
pair group.
NOTE: The intent of this configuration is to pair the HBAs so that no group of HBA ports would be
contained on a single HBA card (if dual port cards are being used).
Connecting to a Dell MD3600i Storage Array with VMware ESX 4.1.0, 260247
The Dell MD3600i storage array is not currently listed in the VMware SATP driver and therefore requires the
user to manually add the product ID to the SATP in-order to properly configure failover for the MD3600i
storage array. This is accomplished with the following commands before mapping any virtual disks from the
storage array to the ESX host.
From the ESX console, issue the following commands:
#esxcli nmp satp addrule -v DELL -M MD36xxi -s VMW_SATP_LSI
#esxcli nmp satp listrules |grep DELL
Ensure that Dell MD36xxi is listed in the output.
Additional Information
For more information about network configuration for software iSCSI storage, refer to iSCSI SAN
Configuration Guide: Configuring iSCSI Initiators and Storage: Setting Up Software iSCSI Initiators:
Networking Configuration for Software iSCSI Storage in the VMware® vSphere Online Library.
To automatically configure the ESX host to the Dell MD Storage Arrays, select the storage array to be
configured, and click Suggest. This groups any unassigned HBA ports into pairs and define a new host and
host group for the groups of HBAs Figure 26. When the suggested configuration is correct, click OK to apply
the changes to the storage array or modify the configuration based on the fibre channel zoning rules from the
previous ESX Host SAN Configuration section. Suggested changes will be shown in blue, the Rename and
Remove options only apply to the uncommitted changes. You cannot rename or remote existing configured
hosts or host groups. Existing host and host group configuration changes must be performed from MDSM.
The wizard displays progress while the requested configuration changes are being made. You must manually
close the progress window once the changes are complete. See Figure 29.
NOTE: To use multiple host groups as described, the storage array must have the Storage Partitioning
premium feature enabled.
The ESX host has now been configured to the storage array. The next step is to create new virtual disks on the
storage array to be used by the ESX host. New virtual disks are created using the vCenter Plug-in.
The Create Disk Group link launches a wizard to walk you through creating a new disk group (Figure 26).
During this process, you must choose from the available free drives, the drives that make up the new disk
group, and select the RAID level to be used.
When you are deciding how to format the virtual disks, keep in mind the following considerations:
Make sure that each virtual disk has the correct RAID level and storage characteristics for applications in
the virtual machines that use that virtual disk. Make sure that each virtual disk contains only one VMFS
datastore.
When multiple virtual machines access the same VMFS datastore, use disk shares to prioritize virtual
machines.
Fewer, larger virtual disks are appropriate for the following reasons:
More flexibility to create virtual machines without asking the storage administrator for more space.
More flexibility for resizing virtual disks, doing snapshots, and so on.
Fewer VMFS datastores to manage.
More, smaller virtual disks are appropriate for the following reasons:
Less wasted storage space.
Different applications might need different RAID characteristics.
More flexibility, as the multipathing policy and disk shares are set per virtual disk.
Use of Microsoft Cluster Service requires that each cluster disk resource is in its own virtual disk.
Better performance because there is less contention for a single virtual disk.
Disabling a Snapshot
To temporarily deactivate a snapshot so that it can be used again later, highlight the snapshot virtual disk in the
Virtual Disks tree, and click Disable Snapshot in the Command area. The snapshot process stops, but the
relationship remains between the snapshot and the base virtual disk and the repository virtual disks.
Re-creating a Snapshot
To re-establish a deactivated snapshot, click Recreate Snapshot in the Commands area. A new copy of the base
virtual disk that can be used as the snapshot is created.
NOTE: Re-creating a snapshot disables the original snapshot before the new snapshot is created.
Deleting a Snapshot
Select the snapshot virtual disk in the Virtual Disks tree, and click Delete in the Commands area.
From this tab, all virtual disk copy operations are displayed along with the current status of all virtual disk
copies. From the Commands area, the following options are available: Create Virtual Disk Copy, Recopy, Stop,
Change Virtual Disk Copy Parameters, Remove Copy, and Refresh. To create a new virtual disk copy, click
Create Virtual Disk Copy in the Commands area, which launches the Virtual Disk Copy wizard. From this
wizard, select the source virtual disk to use for the virtual disk copy.
NOTE: While the virtual disk copy is being established, the source virtual disk is read-only to the host to
which the virtual disk copy is presented. When the Snapshot premium feature is enabled, the vCenter
Plug-in uses the feature to create a snapshot of the source virtual disk before the virtual disk copy is
initiated and the virtual disk copy operation uses the snapshot virtual disk to establish the virtual disk
copy with. This allows for continued read-write operations to the source virtual disk from the host during
the establish period.
1 Click Next to select the target virtual disk for the virtual disk copy and select the copy priority to use.
Remote Replication
When the Remote Replication premium feature is enabled on the storage array, the Remote Replication tab
appears within the vCenter Plug-in. From this tab, existing remote replication pairs are displayed along with
the Commands area which allows for creation of new replication pairs, suspending an existing replication pair,
resuming a replication pair, removing a replication pair, testing replication communications, or change
replication parameters.
1 From the Remote Replication tab, click the Create Remote Replication link.
2 Click Next after reading the introduction wizard page.
3 From the Virtual Disk tree view, select the source virtual disk for the mirror relationship and click Next.
4 Select the remote storage array for the mirror.
5 From the drop-down list, select the secondary virtual disk to be the target of the source remote
replication.
6 Choose the write mode for the remote mirror and click Next.
7 Review the summary information on the Confirmation page and click Finish to establish the mirror
relationship. See Figure 39.
1 Select the host group or host to which to map the new virtual disk.
2 Select the virtual disk number to use and virtual disk to be mapped.
3 Click OK
NOTE: When your storage array uses multiple groups of HBAs per ESX host, the new virtual disks should
be balanced across all hosts/host groups. Do not add all the virtual disks to a single host/host group; no
I/O balancing can occur in this case.
After the virtual disks have been mapped to the ESX host, the storage adapters on the ESX host must be
rescanned to detect the new storage virtual disks. This action is accomplished from Hosts and Clusters view >>
Configuration tab >> Storage Adapters for the ESX host being configured. See Figure 41.
NOTE: You may need to run the Rescan, from vCenter, twice to detect all of the new storage virtual
disks that have been mapped to the ESX host.
From this view, the user can also verify that the correct number of paths have been configured. By right-
clicking on one of the devices listed under the storage adapter and selecting Manage Paths, a window opens
and shows the number of paths for the target device. There should be 4 paths to each device with two Active
and two Standby as shown in Figure 42.
Additional log files that are useful for technical support to resolve issues are also maintained in this directory,
but these files are generally not in a user-friendly format.
vCenter2debug-x.log.y -- Debug log used by technical support
jetty-service.log -- Jetty service log, used by technical support
<date/time stamp>.request.log -- Log of IP addresses for all Jetty service requests from
clients
The Installation Log Not Show that the Pegasus Service Started
Verify that the cimserver service was started from services.msc window.
NOTE: In the event one of these services crash or is stopped, the CIMOM service must be started before the Jetty service or
no updates/modifications will occur.
The vCenter Plug-in Does Not Show the New Storage Array Name after
a Clear Configuration Operation in MDSM
You can perform a Clear Configuration operation in Modular Disk Storage Manager (MDSM) in two ways:
The Clear Configuration operation on a disk group only deletes the virtual disk configuration. The
storage array name does not change, so the vCenter Plug-in still sees the same storage array name.
The Clear Configuration operation on a storage array clears the entire configuration and changes the
storage array name to the default name. After a Clear Configuration operation, the vCenter Plug-in
considers the storage array to be a first-time installation. For the vCenter Plug-in to recognize the storage
array, perform the following actions:
a Remove the storage array from the vCenter Plug-in.
b In MDSM, rename the storage array.
c Re-add the storage array to the vCenter Plug-in.
Dell provides several online and telephone-based support and service options. Availability varies by country
and product, and some services may not be available in your area. To contact Dell for sales, technical support,
or customer service issues:
1 Visit support.dell.com.
2 Click your country/region at the bottom of the page. For a full listing of country/region click All.
3 Click All Support from Support menu.
4 Select the appropriate service or support link based on your need.
5 Choose the method of contacting Dell that is convenient for you.