Technical report: vCenter management plug-in for IBM System Storage DS3000, DS4000 and DS5000

.

.

.

.

.

.

.

User guide for version 2.3

Document NS-3770-01 November 2011

© Copyright IBM Corporation, 2011. All Rights Reserved. All trademarks or registered trademarks mentioned herein are the property of their respective holders.

Table of contents
Abstract..................................................................................................................................... 3 Introduction: Overview of the vCenter plug-in ....................................................................... 3
Installation prerequisites .......................................................................................................................... 4 Recommended configurations ................................................................................................................. 4 Downloading the vCenter plug-in ............................................................................................................. 4 Installing the vCenter application server .................................................................................................. 4 Installing the vCenter plug-in ................................................................................................................... 5

Configuring application server and vCenter plug-in .............................................................. 6
Configuring storage-administrator roles................................................................................................... 6 Configuring SAS support on ESX and ESXi hosts .................................................................................. 9 Installing the SAS provider upgrade ...................................................................................................... 10 vCenter plug-in security ......................................................................................................................... 10

vCenter plug-in features for DS3000, DS4000 and DS5000 ................................................. 15
vCenter plug-in features......................................................................................................................... 15 Configuring storage subsystems ........................................................................................................... 15 Adding a storage subsystem ................................................................................................................. 16 Removing a storage subsystem ............................................................................................................ 17 Editing system properties ...................................................................................................................... 18 Configuring storage-subsystem backups............................................................................................... 18

Configuring ESX hosts........................................................................................................... 21
Configuring networks for software iSCSI storage .................................................................................. 25

Configuring ESX hosts........................................................................................................... 26
Storage-subsystem summary ................................................................................................................ 29 Creating arrays ...................................................................................................................................... 30 Formatting logical drives ........................................................................................................................ 31 Decision-making schemes ..................................................................................................................... 31 Creating a logical drive .......................................................................................................................... 32 Flashcopies premium feature ................................................................................................................ 32 Creating a logical-drive copy ................................................................................................................. 34 Enhanced remote mirroring ................................................................................................................... 36 Datastores view ..................................................................................................................................... 40 Storage-subsystem event log ................................................................................................................ 41 Manually unregistering the vCenter plug-in ........................................................................................... 41

Restrictions for vCenter plug-in Version 2.3 ........................................................................ 43
Logical Drive creation fails on an array of RAID Level 5 (200180549) .................................................. 43 Enhanced remote mirroring is not working as expected (200180174) .................................................. 43 Save Config and Save MEL secondary pop-up screens do not appear (200178293) .......................... 43 Delay in updating failed controllers (200184485) .................................................................................. 43

Troubleshooting vCenter plug-in issues .............................................................................. 43
Application server logs ........................................................................................................................... 43 Installation log does not show that the Pegasus service started ........................................................... 44
vCenter management plug-in for IBM System Storage DS3000, DS4000 and DS5000 series storage: User guide for version 2.3

2

I cannot communicate with the application server ................................................................................. 44 I cannot create or delete objects............................................................................................................ 44 How can I maximize client performance ................................................................................................ 44 How do I suppress slow script warning messages? .............................................................................. 45 I cannot make changes to a storage subsystem ................................................................................... 45 vCenter plug-in does not show the new storage subsystem name after a clear configuration operation in the storage management software .................................................................................................... 45 vCenter plug-in displays incorrect error messages ............................................................................... 45

Resources ............................................................................................................................... 46 Trademarks and special notices ........................................................................................... 47

vCenter management plug-in for IBM System Storage DS3000, DS4000 and DS5000 series storage: User guide for version 2.3

3

Abstract
In this paper, you will learn about the VMware VCenter plug-in for IBM System Storage DS3000, DS4000 and DS5000. You will also learn how to install it and configure its many features to your environment’s best advantage.

Introduction: Overview of the vCenter plug-in
The VMware VCenter plug-in for DS3000, DS4000 and DS5000 series storage is a VMware vCenter Server 4.x plug-in that provides integrated management of IBM® System Storage® DS3000, DS4000 and DS5000 subsystems from within a vSphere Client. The vSphere Client is a single management interface that you can use to manage the VMware infrastructure and all of your day-to-day storage needs. You do not need to learn another management tool, so you can focus instead on the entire virtual infrastructure. The vCenter plug-in enables you to perform the following tasks: • Configure ESX and ESXi hosts to DS3000, DS4000 and DS5000 series storage subsystems. • Create and delete logical drives. • Map logical drives from the DS3000, DS4000 and DS5000 subsystems to the ESX host. • View the vCenter datastores on the DS3000, DS4000 and DS5000 series logical drives. You can create hardware flashcopies, logical-drive copies and enhanced remote mirroring when these premium features are enabled on the storage subsystem. The vCenter plug-in uses an application server to facilitate the interface between the vSphere Client and the DS3000, DS4000 and DS5000 series Storage based on the authenticated logged-in user and the privileges assigned to that user's role. The vCenter plug-in requires that a vCenter Server is installed within the environment. The vCenter plugin does not function in a configuration with only a vSphere Client and an ESX host configuration. Figure 1
Communication Details

vCenter management plug-in for IBM System Storage DS3000, DS4000 and DS5000 series storage: User guide for version 2.3

3

copy the file to the system that is the application server. Therefore. The file needs to be copied to 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 you have downloaded the vCenter plug-in software. DS4000 and DS5000 series storage subsystems • No more than 256 objects. DS4000 and DS5000 series storage: User guide for version 2. the following prerequisites must be met. NOTE: The vCenter plug-in is not a direct replacement for the Santricity ES Storage Management Software.35. the installation wizard registers the vCenter plug-in with the vCenter Server. 7. DS4000 and DS5000 series storage with VMware-certified firmware The vCenter plug-in requires one of the following firmware versions: 7. logical drives and disks on each storage subsystem determine the overall performance of the vCenter plug-in.75.70. After the installation is complete. the application server and the vSphere Client. 7. • The VMware vCenter 4. logical-drive copies and flashcopies.77 or 7. which is still required for performing certain storage-administration tasks.60.x server is installed • One of the following servers is available to be the vCenter plug-in application server: • Microsoft® Windows® 2003 server • Windows. such as logical drives. vCenter management plug-in for IBM System Storage DS3000. 2003 R2 server • 32-bit Windows 2008 server • 64-bit Windows 2008 server • 32-bit Windows 2008 R2 server • 64-bit Windows 2008 R2 server • DS3000. 7. DS4000 and DS5000 series storage subsystem vCenter plugin for your environment (x86 or x64) from the IBM web site. Many procedure calls are made to obtain and send changes to the storage subsystems. Recommended configurations The vCenter plug-in uses the SMI-S protocol to communicate with the storage subsystems that are managed within the vSphere infrastructure. The number of managed storage subsystems. but it is not recommended. See the Support Matrix at the IBM web site for the most current versions. Installing the vCenter application server Install the vCenter application server on a different Windows 2003 server or Windows 2008 server than the VMware vCenter Server is installed on. limit the number of managed system components to the following: • No more than 10 DS3000. 7. you can install the application server on the same host as the vCenter Server. per subsystem • No more than 16 enhanced remote mirrors Downloading the vCenter plug-in Obtain the correct version of the DS3000. which require large amounts of data to be passed between the storage subsystems.Installation prerequisites To install and use the vCenter plug-in.3 4 . When adequate resources are available on the vCenter Server system.80.

51.217 password app-server.51. The IP address defaults to the IP address of the system the installer is running on. the default port number 8084 for the plug-in must be changed to an unused port number. 11. Enter the vCenter administrator's password and click Next. NOTE: If the vCenter plug-in is installed on the same system as an active vCenter Server. 8.225 192. If the CIMOM service is not started before the Jetty service is started. and VMware Update Manager is also installed.51. 6. used during installation.3 5 . Select the local installation directory for the vCenter plug-in manager or click Next for the default.168. Enter the vCenter administrator's user ID and click Next. 7. 3.168.com 192.domain. the IP addresses and the DNS names. you must provide information about the system components.168. 5. To verify a successful installation. select the appropriate radio button and click Next. DS4000 and DS5000 Series Storage2 Name: DS3000.91 192.During the installation process. Review the installation details and click Install if the details are correct. DS4000 and DS5000 Series Storage1 Name: DS3000. Table 1 shows the information required for each component. Change the IP address of the application server when desired. 2.msc command and ensure that the cimserver service was installed and that the cimserver service and the Jetty6-Service service have started. The installation is now complete. Click Next. NOTE: The name of the CIMOM service changes to Pegasus CIM Object Manager. Enter the administrator's email address for alerts and click Next.92 Installing the vCenter plug-in Follow these instructions to install the vCenter plug-in: 1. vCenter management plug-in for IBM System Storage DS3000. Change the Jetty server port number or accept the default (8084 and 8081) and click Next. the CIMOM service must be started before the Jetty service is started. 12. NOTE: If one service fails to respond or stops.89 192. run the services.90 192.51. DS4000 and DS5000 series storage: User guide for version 2.com 192. Table 1 Configuration worksheet example Subsystem component vCenter Server Names vCenter Administrator Name: Application Server Name: DS3000.168. Enter the IP address of the vCenter server and click Next. Click Done to close the installation wizard. such as the storage subsystem names. DS4000 and DS5000 Series Storage3 Name: Storage Administrator User ID: Storage Administrator User ID: Component name VCENTER-4 administrator App-Server DS4800 DS3550 Required information DNS names IP Addresses Password: DNS name: IP Address: IP Addresses: Password: IP Addresses: Password: IP Addresses: Password: User1 Example information vCenter-4.168. 4. such as the storage management software.51. the vCenter plug-in does not show events from external managers.51. Read the introduction screen and then click Next. 9. and if you accept the terms. 10.168.domain. The next screen prompts you for the IP address of the vCenter server on which to install the vCenter plug-in. Read through the license agreement.

After configuring the application server and vCenter server. verify that the port number defined for the Jetty server is enabled to pass through any firewalls in use. verify that the vCenter plug-in was successfully registered with the vCenter server. Creating a role Follow these steps to create the storage-administrator role: 1. The default Jetty TCP port number is 8084 and 8081. the user’s role must be modified to permit access to the vCenter plug-in. Figure 2 vSphere client home page Configuring storage-administrator roles By default. The list of roles and usages appears. Click Roles. When a user requires either read permissions or read/write permissions to access the vCenter plug-in. vCenter management plug-in for IBM System Storage DS3000. DS4000 and DS5000 series storage subsystems. However. On the menu bar. In the Administration area on the vSphere Client Home page. DS4000 and DS5000 series storage: User guide for version 2. The DS3000. select plug-ins > Manage plug-ins. all defined vCenter user IDs have no rights to DS3000. if the vCenter plug-in is disabled with an error message that it cannot communicate with the application server. notice the DS3000/DS4000/DS5000 vCenter Management vCenter plug-in icon in the Solution and Application section of the vSphere Client page. DS4000 and DS5000 vCenter Management plug-in is listed as Enabled. • • • • Open the vSphere Client to the vCenter Server.Configuring application server and vCenter plug-in After the application server and the vCenter plug-in are installed.3 6 .

The Add New Role window opens. as shown in Figure 4. Figure 4 Add new role window vCenter management plug-in for IBM System Storage DS3000.3 7 . DS4000 and DS5000 series storage: User guide for version 2.Figure 3 vCenter plug-in Roles List 2. 3. A pop-up menu appears. Click Add. Click Add Role or right-click.

On the Home screen. 4. a new role must be created that has all of the privileges added to it.4. 2. DS4000 and DS5000 series storage: User guide for version 2. which cannot be modified. To allow Read Only or Read/Write access permissions to the storage subsystems. 6. Note: Existing roles can also be modified to include the storage administrator privileges. select the access permissions to assign to this role. 5. Select the modified role from the drop down box and click OK to apply changes. if the administrator user is used to manage storage. select Hosts and Clusters and then select the vCenter server element and select the Permissions tab. On the Privileges list. 5. type the name of the new role. therefore. Click OK. Click OK to apply permissions to the role. except for the Administrator role.3 8 . Adding a user ID to a role Follow these steps to add a user ID to a role: 1. Click Add and select the user IDs that require access to the storage subsystems. Figure 5 Assign storage-administrator role 3. Note: The administrator role is not editable and. select the appropriate permission from the Storage Administrator group. The administrator user must then be added to this role as the following procedure details. Right-click and select Add Permission to define the users who are members of the Role. vCenter management plug-in for IBM System Storage DS3000. In the Name text box.

with SAS connections. Press F2 to switch to the diagnostic console. This section describes how to upgrade the SAS SMI-S provider. This requires that either Secure File Transfer Protocol (SFTP) or Secure Copy (SCP) is enabled on the ESX or ESXi host. To install the package by remote login. Select Troubleshooting Options. 4. Enabling root login from a console login on ESXi hosts Follow these steps to enable a root login from a console login on ESXi hosts: 1. Press Esc to close the Configuration menu. either create a new user with host login privileges or enable remote logins for the root user. SAS support is available only for ESX and ESXi version 4. you must have root access. When the storage subsystems are already configured. Save and close the file. Open the /etc/ssh/sshd_config file. To use the SAS provider. On the line that contains PermitRootLogin. they cannot view any statistics from the vCenter plug-in. Select Restart Management Agents. change no to yes. DS4000 and DS5000 series storage subsystems. or the storage subsystems are not SAS-connected. Enabling root login from a console login on ESX hosts Follow these steps to enable root login from a console login on ESX hosts: 1.1 and later hosts. an updated version of the LSI SAS SMI-S provider must be installed on the ESX and ESXi hosts. 4. run the # service sshd restart command to reload the service. If they attempt to access a vCenter plug-in feature they receive the User is not authorized to use this plug-in message as shown in Figure 6. 3. the in-box provider does not need to be upgraded. To install the SAS SMI-S Provider upgrade package. it must first be deployed on the ESX or ESXi servers to be configured.3 9 . Log in as root. 5.No access If users are not members of a role that has either the Read Only or Read/Write Storage Administrator permission. 2. 2. At the shell prompt. Select Enable Remote Tech Support. 5. This upgrade is required only to allow the Host to Storage Configuration option to configure SAS connected storage subsystems. Previous versions of ESX and ESXi are not supported. vCenter management plug-in for IBM System Storage DS3000. Figure 6 No Access Message Configuring SAS support on ESX and ESXi hosts For the vCenter plug-in to configure ESX and ESXi hosts to the DS3000. DS4000 and DS5000 series storage: User guide for version 2. 3.

You should see Unpacking cross_lsi-provider. 10. Installing the SAS provider upgrade Follow these steps to install the SAS provider upgrade: 1. Reboot the host after stopping any running VMs. Click OK to save changes.04. Connect the vCenter client directly to the ESX/ESXi host to be configured. Enter esxupdate -b file:$PWD/vmware-esx-provider-lsi-provider. 2. vCenter management plug-in for IBM System Storage DS3000.command to assume the super user role. After logging in as this new user. 6.1. If this certificate has not been added to the system's Trusted Root Certification Authorities store. Enter either rpm -q lsi-provider for ESX or esxupdate --vib-view query | grep lsiprovider for ESXi hosts.1 host as root.24-140815 retired 11. After the update. You should see the following information: cross_lsi-provider_410. verify that the update was applied with rpm -q lsi-provider for ESX or esxupdate --vib-view query | grep lsi-provider for ESXi hosts. Upon reboot. enter esxupdate --vib-view query | grep lsi-provider. a Security Alert dialog box appears. If root is not enabled. 2. 4. log in as a shell-enabled user and use the su .04.24-260xxx pending.Creating a new user login Follow these steps to create a new user login: 1. 8. 5. log in as a shell-enabled user and use the su . 7.vib file is located.3 10 . Log in to the ESX/ESXi 4. If root is not enabled. a SSL certificate was generated for the vCenter Server system. 4. DS4000 and DS5000 series storage: User guide for version 2. Supply the relevant information for the new user and select Grant shell access to this user.command to assume the super user role.24-140815. 5.V0.vib file to the target ESX host or SCP the file to the target ESXi host. use the su . The version listed should be lsi-provider-410.V0. 12.installed cross_lsi-provider_410.V0. vCenter plug-in security This section reviews the process of ensuring vCenter plug-in security.04. Right-click and select Add. 3. 6. 9.vib -nodeps --nosigcheck --maintenancemode update when the . If not. 3.vib file is located in the same directory that esxupdate is being executed from. From the shell prompt type.command to assume the super user role. During the vCenter Server installation process. Select the User & Groups tab in the Home > Inventory > Inventory window. change $PWD to the directory where the . Either SFTP the vmware-esx-provider-lsi-provider. vmware -v to verify that the version is 4. Installing lsi-provider and Cleaning up lsi-provider. Accepting and installing the trusted SSL certificate The vCenter plug-in uses Secure Sockets Layer (SSL) to communicate securely between the vSphere server and the application server.

Figure 7 SSL Security Alert Message To avoid this message. vCenter management plug-in for IBM System Storage DS3000. you can import the install-generated certificate into the systems Trusted Root Certification Authorities store by clicking View Certificate and then clicking Install Certificate.3 11 . Click Next in the Certificate Import Wizard dialog box. DS4000 and DS5000 series storage: User guide for version 2. Figure 8 Install Certificate Dialog Box 1.

Figure 9 Certificate Import Wizard Dialog Box 2. Select Trusted Root Certification Authorities folder. Click Browse. 4. vCenter management plug-in for IBM System Storage DS3000. DS4000 and DS5000 series storage: User guide for version 2. 3. Select Place all certificates in the following store.3 12 .

DS4000 and DS5000 series storage: User guide for version 2. vCenter management plug-in for IBM System Storage DS3000. 7.3 13 . Click Finish. Click OK. 6. Click Next. 8. Verify the information and click Yes to add the certificate to the trust store.Figure 10 Select Certificate Store Dialog Box 5. The Security Warning message appears.

The warning message shown in Figure 12 appears. Figure 12 IE Enhanced Security Message vCenter management plug-in for IBM System Storage DS3000. click Add. the enhanced security configuration blocks content from the web site.3 14 . a warning message stating the certificate does not match the site name continues to appear. To establish a trust relationship with the application server. If the names do not match. DS4000 and DS5000 series storage: User guide for version 2.Figure 11 Security Warning Message Note: The subject name of the system in the certificate must match the system name of the vCenter Server on the vSphere Client login screen. Enhanced IE security When Microsoft's Enhanced IE Security is installed on the vSphere Client system.

DS4000 and DS5000 series storage subsystem.vCenter plug-in features for DS3000. DS4000 and DS5000 series storage. DS4000 and DS5000 This section discusses the vCenter plug-in features for the DS3000. DS4000 and DS5000 series storage: User guide for version 2. Click the DS3000.3 15 . Figure 13 DS3000. DS4000 and DS5000 vCenter Management plug-in icon on the vSphere Client Home page under Solutions and Applications. follow these steps: 1. vCenter plug-in features The following vCenter plug-in features enable the integrated management of DS3000. DS4000 and DS5000 vCenter Management plug-in icon vCenter management plug-in for IBM System Storage DS3000. DS4000 and DS5000 series storage subsystems: • • • • • • • Subsystem Manager view Copy services management A configuration wizard for ESX and ESXi host storage Logical-drive management of storage subsystems Datastores to logical drive details Event log viewer for storage subsystem events Automatic and manual storage subsystem configuration backup Configuring storage subsystems To use the vCenter plug-in to create or modify logical drives on the DS3000.

A dialog box appears with the DNS Name or IP Address text boxes and the Password text box. Figure 14 vCenter plug-in Subsystem Manager view Adding a storage subsystem Follow these steps to add a storage subsystem: 1. To open the Storage Subsystem Manager view. In the Commands area of the vCenter plug-in Subsystem Manager view. click Add Subsystem.3 16 . DS4000 and DS5000 series Storage icon.2. The Storage Subsystem Manager view shows a list of known storage subsystems and lets additional storage subsystems be added or removed. 2. click the VCenter plug-in for DS3000. vCenter management plug-in for IBM System Storage DS3000. DS4000 and DS5000 series storage: User guide for version 2.

Figure 15 Add Subsystem dialog box 3. type the IP address or name of the storage subsystem’s controller B. click Remove Subsystems. DS4000 and DS5000 series storage: User guide for version 2. In the DNS name or IP address 1 text box. 6. The Remove Subsystems Properties dialog box appears. type the IP address or name of the storage subsystem’s controller A. 4. In the Password text box. vCenter management plug-in for IBM System Storage DS3000. Select the storage subsystem to be removed and click OK. Click Add. In the DNS name or IP address 2 text box. 5.3 17 . 3. Removing a storage subsystem Follow these steps to remove the storage subsystem: 1. In the vSphere Client Storage Subsystem Manager view. 2. type the password for the storage subsystem to be added to the vCenter plug-in.

active read/write commands to the subsystem. Caution: The vCenter plug-in does not back up data residing on the storage subsystem. on the storage subsystem. click the storage subsystem name. The vCenter plug-in displays the properties of the storage subsystem whether the passwords match or do not match. logical-drive copies and enhanced remote mirrors are not saved to the script file. however. Open the Storage Subsystem Manager view. vCenter management plug-in for IBM System Storage DS3000. The dialog box appears. Resolving a password mismatch If the vCenter plug-in password and the storage subsystem password do not match. Objects such as flashcopies. fail. such as Create and Delete. These script files facilitate the restoration of the storage subsystem configuration. Changing a storage-subsystem password Follow these steps to change the storage-subsystem password: 1. either from the vCenter plug-in or from the storage management software. DS4000 and DS5000 series storage management software. In the left pane. Figure 16 Edit Subsystem Properties dialog box 4.3 18 .3 of the vCenter plug-in supports storage subsystem configuration backups to script files that can be applied to a storage subsystem from the DS3000. type the new subsystem password and click OK. In the Password text box. click Edit Subsystem Properties. You must use a standard backup strategy to recover user data that resides on the logical drives. The vCenter plug-in Automatic Save Configuration feature performs a save configuration of the storage subsystem after a configuration event has occurred on the storage subsystem. its properties appears in the right pane. Data stored on the logical drives is not saved. Note: Only the base storage subsystem configuration information is saved.Editing system properties This section explains how to edit the system properties. such as Read and View. logical drive names and logical drive capacities. Changing a storage-subsystem password describes how to resolve a password mismatch. 3. array configurations. Configuring storage-subsystem backups Version 2. you can run passive read-only commands. DS4000 and DS5000 series storage: User guide for version 2. such as storage subsystem name. 2. Caution: Only the configuration information for the storage subsystem is saved during a save configuration operation. In the right pane.

at the time of the event on the storage subsystem. 3. 3. Select the Enable automatic save configuration check box. the timer is reset to four minutes. 4. a save configuration is performed. 2. The storage subsystem properties appear in the right pane. Open the Storage Subsystem Manager view. Open the Storage Subsystem Manager view. perform the procedure below: 1. click Automatically Save Configuration. Figure 17 Automatic Save Configuration message box Note: The automatic backup script files are located in the “C:\Program Files (x86)\IBM DS3000 DS4000 DS5000 vCenter Management Plug-in\jetty\savecfg” directory. perform these steps: 1. If another modification event occurs within the four-minute time window. click the name of the storage subsystem. The storage subsystem properties appear in the right pane. If within that four-minute time window. 5.3 19 . Click OK to enable automatic configuration backups. To enable automatic backups of the storage subsystem base configuration. To disable automatic save configuration. The Automatically Save Configuration dialog box appears. they are persisted between restarts of the vCenter plug-in application server and vCenter Server. When no modification events are detected on the storage subsystem within the four-minute time window. vCenter management plug-in for IBM System Storage DS3000. Performing a manual save configuration To perform a manual save configuration. Automatic Save Configuration maintains the last 15 save configuration script files. In the right pane. 2.A storage subsystem modification event starts a four-minute timer. In the left pane. After automatic configuration backups are enabled. Enabling automatic save configuration backups These backups can be set to automatic or manually initiated. clear the box in the Automatically Save Configuration dialog box. no other configuration events have occurred on the storage subsystem. select the name of the storage subsystem. In the left pane. In the right pane. DS4000 and DS5000 series storage: User guide for version 2. click Automatically Save Configuration. a save configuration occurs. The Automatically Save Configuration dialog box appears. on the application server.

Figure 18 Manually save configuration message box 4. vCenter management plug-in for IBM System Storage DS3000. Figure 19 File Download Dialog Box 5. DS4000 and DS5000 series storage: User guide for version 2. The Save As dialog box appears. The File Download dialog box appears. Click OK. Click Save.3 20 .

7. Configuring ESX hosts The vCenter plug-in allows an ESX host to be automatically configured to use a DS3000. DS4000 and DS5000 storage subsystems is Most Recently Used (MRU). To ensure optimum performance for the ESX host with more than two HBAs. DS4000 and DS5000 series storage: User guide for version 2. Click Save. The default ESX multipathing mode for DS3000. DS4000 or DS5000 series storage by detecting the installed host bus adapters (HBAs) within the ESX host and configuring new hosts on the storage subsystem with the Worldwide Names (WWNs) of the HBAs from the ESX host. This method allows for the maximum I/O throughput from the ESX host to the storage subsystem. vCenter management plug-in for IBM System Storage DS3000. Using this method requires proper SAN configuration and balancing of LUNs between hosts/host groups.3 21 .Figure 20 Save As Dialog Box 6. Select the location and file name with which to save the backup configuration script. Figure 20 shows a properly configured two HBA port ESX host SAN configuration utilizing two fabric switches and a dual controller storage subsystem. the ESX host should be configured to use the storage subsystem in pairs of HBAs.

vCenter management plug-in for IBM System Storage DS3000. If a Fibre Channel (FC) switch or HBA fails.3 22 . DS4000 and DS5000 series storage: User guide for version 2. A complete loss of access to storage occurs if any other element fails. the ESX host can still access the remaining controller. the alternate switch still connects to both storage controllers in the storage subsystem. and all logical drives fail over to that controller. If a storage controller also fails.Figure 21 Dual Port HBA Configuration This example shows a fully redundant fabric configuration.

Figure 22 Single Failure Figure 23 Double Failure vCenter management plug-in for IBM System Storage DS3000. DS4000 and DS5000 series storage: User guide for version 2.3 23 .

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.This method works well to maintain the in-case of a hardware failure. the Automatic ESX host configuration utility cannot determine which HBAs are configured to each zone in the fabric. From the storage subsystem. This same methodology can be used to group additional HBAs in the same manner. Therefore.3 24 . DS4000 and DS5000 series storage: User guide for version 2. however. This does require additional management to balance the LUNs between the host (or host groups) to fully use the FC bandwidth between all HBA groups. Figure 24 Quad HBA Port Configuration 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). vCenter management plug-in for IBM System Storage DS3000. only one HBA is active at a time. Figure 24 shows how an 8-port HBA configuration can be configured. When this method is used in the subsystem. it is recommended that you group the HBAs in pairs and create virtual hosts for each pair of HBAs. To achieve higher I/O throughput from the ESX host to the storage subsystem. and the user must verify that a single HBA is connected to both fabric zones for each HBA pair group. MRU only maintains one active path for each HBA group. if you have an ESX host with four HBAs. the second pair of HBAs is defined as a separate host and logical drives can then be mapped directly to the new host or host group.

so the user must manually add the product ID to the SATP in-order to properly configure failover for the DS3000. Ensure that DS3000. Connecting to a DS3000. DS4000 and DS5000 series storage subsystems are not currently listed in the VMware SATP driver.1. Depending on the number of physical NICs that you use for iSCSI traffic. This is accomplished with the following commands before mapping any logical drives from the storage subsystem to the ESX host. the networking setup can be different. From the ESX console. S4000 and DS5000 with VMware ESX 4. DS4000 and DS5000 series is listed in the output. DS4000 and DS5000 series storage subsystem.3 25 . 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. DS4000 and DS5000 series storage: User guide for version 2. Additional information For more information about network configuration for software iSCSI storage. 1. create an iSCSI VM kernel port and map it to a physical network interface card (NIC) that handles iSCSI traffic.0.Figure 25 8 HBA port configuration Configuring networks for software iSCSI storage To configure the network for software iSCSI storage. run the following commands: listrules#esxcli nmp satp addrule -v IBM -M <DS3000/DS4000/DS5000> -s VMW_SATP_LSI #esxcli nmp satp |grep IBM 2. vCenter management plug-in for IBM System Storage DS3000. 260247 DS3000.

3 26 . remove a host or host group and automatically configure the ESX host to another storage subsystem. DS4000 and DS5000 series storage: User guide for version 2. From this wizard. Figure 26 ESX Host Configuration Wizard Menu This launches the Configure ESX Host to Storage Subsystem wizard. you can see how the current ESX host is configured to the storage subsystem (if it is already configured). You can also add a host or host group. Right-click the ESX host and select the Configure ESX Host to Storage Subsystem option from the pull-down menu. navigate to Hosts and Clusters within the vSphere Client and select the ESX host to be configured.Configuring ESX hosts To use the Automatic Host Configuration utility. vCenter management plug-in for IBM System Storage DS3000. rename a host or host group.

You cannot rename or remove existing configured hosts or host groups. You must manually close the progress window after the changes are complete. When the suggested configuration is correct. DS4000 and DS5000 series storage subsystems. Note: To use multiple host groups as described.3 27 . and the Rename and Remove options apply only to the uncommitted changes. the storage subsystem must have the Storage Partitioning premium feature enabled. This groups any unassigned HBA ports into pairs and define a new host and host group for the groups of HBAs.Figure 27 FC Configure ESX host to storage subsystem wizard To automatically configure the ESX host to the DS3000. Suggested changes appear in blue. The wizard displays progress while the requested configuration changes are being made. click OK to apply the changes to the storage subsystem or modify the configuration based on the FC zoning rules from the previous ESX Host SAN Configuration section. vCenter management plug-in for IBM System Storage DS3000. select the storage subsystem to be configured and click Suggest. Existing host and host group configuration changes must be performed from the storage management software. DS4000 and DS5000 series storage: User guide for version 2.

3 28 . DS4000 and DS5000 series storage: User guide for version 2.Figure 28 iSCSI Configure ESX Host to Storage Subsystem View Figure 29 SAS configure ESX host to storage subsystem view vCenter management plug-in for IBM System Storage DS3000.

the number of drive trays. hot spares and capacity usage.3 29 . the number of disks. When the provider is not upgraded. Figure 30 Commit changes The ESX host is now configured to the storage subsystem. and the icon above the servers is red. create new logical drives on the storage subsystem to be used by the ESX host by using the vCenter plug-in. See Datastores View for additional event log details. Next. disk types. the number of controllers. This includes information on the status of the storage subsystem. Figure 31 Storage-subsystem summary vCenter management plug-in for IBM System Storage DS3000. the list of address does not appear. DS4000 and DS5000 series storage: User guide for version 2. The storage subsystem event log is also accessible from this tab by clicking View Event Log. Storage-subsystem summary Clicking a storage subsystem from the Subsystem Manager view displays a summary of the selected storage subsystem. the LSI SAS SMI-S provider must be upgraded to the version included with the install and as described in Installing the SAS provider upgrade. the number of failed controllers.Note: To detect the SAS HBA addresses.

To create a new array. Figure 32 Storage-subsystem logical drives The Create Array command launches a wizard to help you create a new array. Figure 33 Create Array Dialog Box vCenter management plug-in for IBM System Storage DS3000. click Create Array.Creating arrays Selecting the Logical Drives tab shows a logical view that displays how storage capacity is allocated. DS4000 and DS5000 series storage: User guide for version 2. you must select the available free drives. This view also allows you to create new arrays and logical drives. the drives that make up the new array and the RAID level. During this process.3 30 . You also can modify and delete existing logical drives and arrays in this view.

Ensure that each logical drive contains only one VMFS datastore. DS4000 and DS5000 series storage: User guide for version 2. Fewer. The shares assigned to VMs on one host have no effect on VMs on other hosts. use disk shares to prioritize VMs. 5. keep in mind the following considerations: Ensure that each logical drive has the correct RAID level and storage characteristics for applications in the virtual machines (VMs) that use that logical drive. Better performance because there is less contention for a single logical drive. NOTE: Disk shares are relevant only within a given host. and so on. including deciding on the number of logical drives to use and the size of the logical drives. larger logical drives are appropriate for the following reasons: More flexibility to create VMs without asking the storage administrator for more space. Run the applications to determine whether VM performance is acceptable. More. adaptive schemes and disk shares. as the multipathing policy and disk shares are set per logical drive. Label each Datastore according to its characteristics. • • • • • • • • • • • Decision-making schemes When the storage characterization for a VM is not available. More flexibility. • • When you are deciding how to format the logical drives. Create several logical drives with different storage characteristics. Use of Microsoft Cluster Service requires that each cluster disk resource is in its own logical drive. Fewer VMFS datastores to manage. Using the predictive scheme to make logical drive decisions Follow these steps to use the predictive scheme to make logical drive decisions: 1. you must plan how to set up storage for the ESX/ESXi systems.3 31 . More flexibility for resizing logical drives. Allocate logical drives to contain the data for VM applications in the VMFS datastores built on logical drives with the appropriate RAID level for the applications' requirements. 4. smaller logical drives are appropriate for the following reasons: Less wasted storage space. Build a VMFS Datastore on each logical drive. Different applications might need different RAID characteristics. vCenter management plug-in for IBM System Storage DS3000. you can use either the predictive scheme or the adaptive scheme to decide on the logical drive size and number of logical drives to use. refer to the iSCSI SAN Configuration Guide: Using ESX/ESXi with an iSCSI Storage Area Network: Making LUN Decisions in the VMware vSphere Online Library. doing flashcopies. Note: For more information about making logical drive decisions. Use disk shares to distinguish high-priority VMs from low-priority VMs. including predictive schemes. When multiple VMs access the same VMFS datastore. 2. 3.Formatting logical drives Before you format logical drives with VMFS datastores.

select the rate from the drop-down list. The Create Logical Drive wizard appears. In the Name text box. Run the applications to determine whether disk performance is acceptable. Disable Flashcopy–Disable the flashcopy of a base logical drive. select the array to use for the new logical drive. DS4000 and DS5000 series storage: User guide for version 2. 4. 6. Click OK to create the logical drive. these additional options are available in the Commands area: • • • • Create Flashcopy–Create a new flashcopy of a base logical drive. 2. From the Array drop-down list. create a larger logical drive. In the Size text box. Place four or five logical drives on the VMFS datastore. • If performance is acceptable. Delete–Delete a flashcopy of a logical drive. 4. Click Create Logical Drive. Recreate Flashcopy–Recreate a disabled flashcopy. type the logical-drive name. select the I/O characteristics of the logical drive. and enable write caching. Build a VMFS datastore on that logical drive. To create a new logical drive. type the size of the new logical drive. 3. In the I/O settings area. Flashcopies premium feature When the Flashcopies premium feature is enabled on the storage subsystem. Use migration to avoid losing VMs when recreating the logical drive. you can put more logical drives on the VMFS datastore.3 32 . Figure 34 Create Logical Drive Dialog Box 2. • If performance is not acceptable. perform these steps: 1. Creating a logical drive After a new array was created. 5. 3.Using the adaptive scheme to make logical drive decisions Follow these steps to use the adaptive scheme to make logical-drive decisions: 1. Create a large logical drive. vCenter management plug-in for IBM System Storage DS3000. you can create new logical drives from the free capacity in the array. repeat the process with a different RAID level. such as RAID 1+0 or RAID 5.

Note: When the size of the flashcopy exceeds the percentage of the base logical drive. Disabling a flashcopy To temporarily deactivate a flashcopy so that it can be used again later. The Flashcopy wizard appears. Deleting a flashcopy Select the flashcopy logical drive in the logical drive’s tree and click Delete in the Commands area. The flashcopy is no longer available for use until it is reestablished by recreating it. The flashcopy process stops. vCenter management plug-in for IBM System Storage DS3000. Highlight the base logical drive and click Create Flashcopy in the Command area.3 33 . highlight the flashcopy logical drive in the logical-drive’s tree and click Disable Flashcopy in the Command area. A new copy of the base logical drive that can be used as the flashcopy is created. DS4000 and DS5000 series storage: User guide for version 2. • Percent of Base Logical Drive–percentage of the base logical drive for the repository. See Recreating a Flashcopy. • Array–the name of the array in which to place the repository logical drive. the base logical drive and the repository logical drives. Figure 35 Create Flashcopy dialog box 2. the flashcopy fails. Change one or more of the flashcopy attributes: • Flashcopy Name–name of the new flashcopy logical drive.Creating a flashcopy of a base logical drive Follow these steps to create a flashcopy of a base logical drive: 1. Recreating a flashcopy To reestablish a deactivated flashcopy. but the relationship remains between the flashcopy. Note: Recreating a flashcopy disables the original flashcopy before the new flashcopy is created. click Recreate Flashcopy in the Commands area. • Flashcopy Repository Name–name of the new repository logical drive.

the following options are available: • • • • • • Create Logical Drive Copy Recopy Stop Logical Drive Copy Change Logical Drive Copy Parameters Remove Copy Pair Refresh Here are the steps to create a new logical-drive copy: 1.3 34 . vCenter management plug-in for IBM System Storage DS3000. Figure 36 Logical Drive Copy management From this tab.Creating a logical-drive copy When the Logical Drive Copy premium feature is enabled on a storage subsystem managed by the vCenter plug-in. all logical-drive copy operations are displayed along with the current status of all logicaldrive copies. the Logical Drive Copy tab appears next to the Mappings tab. Click Create Logical Drive Copy in the Commands area to launch the Logical Drive Copy wizard. DS4000 and DS5000 series storage: User guide for version 2. This tab allows the management of logical-drive copies on the selected storage subsystem. 2. select the source logical drive to use for the logical-drive copy. From this wizard. From the Commands area.

the source logical drive is read-only to the host where the logical-drive copy is presented. the vCenter plug-in uses the feature to create a flashcopy of the source logical drive before the logical-drive copy is initiated. When the Flashcopy premium feature is enabled. The logical-drive copy operation uses the flashcopy logical drive to establish the logical-drive copy.Note: While the logical-drive copy is being established. Figure 37 Select Source Logical Drive 3.3 35 . DS4000 and DS5000 series storage: User guide for version 2. This allows for continued read/write operations to the source logical drive from the host during the established period. Figure 38 Select target logical drive and priority vCenter management plug-in for IBM System Storage DS3000. Click Next to select the target logical drive for the logical-drive copy and the copy priority.

vCenter management plug-in for IBM System Storage DS3000. From the Logical Drive tree view. DS4000 and DS5000 series storage: User guide for version 2. Click Next after reading the introduction wizard page. select the source logical drive for the mirror relationship and click Next. click Create Enhanced Remote Mirror. Select the write mode for the remote mirror and click Next. 2. 5. resuming a mirrored pair. From this tab. the Enhanced Remote Mirroring tab appears within the vCenter plug-in. select the copy set to modify and click Stop Logical Drive Copy in the Commands area. To delete a copy set. existing enhanced remote mirror pairs are displayed along with the Commands area which allows for creation of new mirrored pairs. 3. but does not modify or delete the target logical drive that still contains a copy of the original data from the source logical drive. select the copy set to modify and click Remove Copy Pair. From the drop-down list. Figure 39 Enhanced remote mirroring view Creating an enhanced remote mirror Note: To create an enhanced remote mirror. This removes the logical-drive copy relationship between the two logical drives. To recopy an existing logical-drive copy in the Logical Drive Copy tab. select the secondary logical drive to be the target of the source enhanced remote mirror. Enhanced remote mirroring When the Enhanced Remote Mirroring premium feature is enabled on the storage subsystem. 6. it can be managed from the Logical Drive Copy tab. To stop a copy operation that is occurring. Select the remote storage subsystem for the mirror.After the logical-drive copy is established. suspending an existing mirrored pair. both the local and the remote storage subsystems must be added to the Subsystem Manager view. 1.3 36 . From the Enhanced Remote Mirroring tab. click the copy set and click Recopy. 4. testing mirrored communications or change mirrored parameters. removing a mirrored pair.

DS4000 and DS5000 series storage: User guide for version 2. Demotes the primary logical drive to the secondary logical drive and disables writes to the logical drive from the primary site. click Resume Enhanced Remote Mirroring in the Commands area under the Enhanced Remote Mirroring tab. vCenter management plug-in for IBM System Storage DS3000. but the mirrored association is maintained.) Changing mirrored roles Changing roles makes the following role changes in the mirrored pair: • • Promotes the secondary logical drive to the primary logical drive and allows read/write access to the logical drive from the remote location. click Suspend Enhanced Remote Mirroring in the Commands area under the Enhanced Remote Mirroring tab.3 37 . click Change Mirrored Roles in the Commands area under the Enhanced Remote Mirroring tab. Resuming enhanced remote mirroring To resume enhanced remote mirroring. and out-of-sync data is resynchronized. Review the summary information on the Confirmation page and click Finish to establish the mirror relationship. To change roles. Figure 40 Enhanced remote mirroring confirmation dialog box Suspending enhanced remote mirroring To suspend enhanced remote mirroring of a mirrored pair.7. I/O between mirrored pairs resumes. The I/O between the mirrored pairs is suspended. (Note: This option is available only for mirrored pairs that have been suspended.

Changing mirrored parameters To modify the parameters of a mirrored pair. 2. perform these steps: 1. click Test Mirrored Communication in the Commands area under the Enhanced Remote Mirroring tab. host groups and logical drive mappings. you can manage hosts. Removing mirrored pairs Removing a mirrored pair breaks the enhanced remote mirroring association between the logical drives at the primary and remote sites.Testing mirrored communication Testing mirrored communication displays round trip-times between mirrored-pair logical drives (displayed as average. From this view. Modify the dialog box to match your requirements for the mirrored pair. To test mirrored communication. To reestablish this status. the resynchronization method and the write mode. DS4000 and DS5000 series storage: User guide for version 2. Figure 41 Logical Drive mapping view vCenter management plug-in for IBM System Storage DS3000. full resynchronization must occur. After the operation completes. such as the synchronization priority. To present a new logical drive to an ESX host. click Add Mapping to start the Add Mapping wizard. the enhanced remote mirroring status between the logical drives is lost. Click Change Mirrored Parameters. shortest and longest round-trip times). use the Mappings tab to present the logical drives to the ESX host for use.3 38 . Mapping logical drives After creating new logical drives.

Click OK. After the logical drives have been mapped to the ESX host. the storage adapters on the ESX host must be rescanned to detect the new storage logical drives. By right-clicking one of the devices listed under the storage adapter and selecting Manage Paths. Select the host group or the host to which to map the new logical drive. Figure 42 Storage Adapters Rescan From this view. DS4000 and DS5000 series storage: User guide for version 2. twice to detect all of the new storage logical drives that have been mapped to the ESX host.3. no I/O balancing can occur in this case. Note: When your storage subsystem uses multiple groups of HBAs per ESX host. Note: You might need to run the Rescan. from vCenter. the user can also verify that the correct number of paths has been configured. 5. Do not add all the logical drives to a single host/host group. vCenter management plug-in for IBM System Storage DS3000.3 39 . 4. a window opens and shows the number of paths for the target device. Select the LUN number to use and the logical drive to be mapped. There must be two active paths and two standby paths to each device. Select Storage Adapters for the ESX host being configured. This action is accomplished under the Configuration tab in the Hosts and Clusters view. the new logical drives should be balanced across all hosts/host groups.

3 40 . LUN number and health status). so selecting a VM in the tree only displays storage elements for the selected VM. the Datastores View tab can be used to understand the mapping of datastores to storage subsystem logical drives. The intent of this view is to provide you with a quick status and view of the datastores and their underlying storage logical drives. This view also shows datastore details (extent.Figure 43 Disk Path Configuration Datastores view After datastores are created on storage subsystem logical drives. capacity and datastore free space. Use this view to identify the storage subsystem where the datastore and associated storage subsystem logical drive reside. DS4000 and DS5000 series storage: User guide for version 2. RAID level. associated host and host group. You can view the logical drive’s health status. The Datastores View is context-sensitive. Figure 44 Datastores View vCenter management plug-in for IBM System Storage DS3000.

DS4000 and DS5000 series storage: User guide for version 2. You can set filters in the Event Log to show either critical events or all events. 6. Click Invoke Method to unregister the extension. DS4000 and DS5000 vCenter Management plug-in) 5.Storage-subsystem event log The vCenter plug-in allows you to view the Event Log for a storage subsystem. Click UnregisterExtension and enter the extension name to be unregistered from the list of available extensions (example: DS3000. you can specify the number of events for the Event Log to retrieve. Click content to navigate to the available Service Content. After changing the Event Log settings.3 41 . By default.168. 3. click View Event Log in the storage subsystem Summary window. Figure 45 Event Log Viewer Manually unregistering the vCenter plug-in If the vCenter plug-in needs to be removed. The event log might contain some duplicate entries.51. Restart the vSphere Client to see the changes.21/mob). • • After changing the number of events to retrieve. as shown in Figure 53. To access the event log. the Event Log retrieves the most recent 100 events. click Save as and click Close. Click ExtensionManager to display a list of registered extensions 4. but from the Retrieve the most recent events drop-down list. the following procedure can be used when it is not possible to uninstall the vCenter plug-in from the application server. vCenter management plug-in for IBM System Storage DS3000. 2. You can view the details for a selected event. click Update. Start a web browser and navigate to the IP address of the vCenter server with /mob appended to the IP address (example: http://192. 1.

select Add/Remove Programs and select the vCenter plug-in package to uninstall the vCenter plug-in and SMI-S provider packages. Use the application uninstaller on the application server at the following location: C:\Program Files\DS3000. On the application server. DS4000 and DS5000 series Storage\Uninstall DS3000. vCenter management plug-in for IBM System Storage DS3000.exe 2. Note: On Windows Server 2008. DS4000 and DS5000 series storage: User guide for version 2. DS4000 and DS5000 series StoragevCenter Management plug-in. 1. select Programs and Features.Figure 46 Manual Unregister Extension Uninstall the vCenter plug-in Use either of the following methods to uninstall the vCenter plug-in. DS4000 and DS5000 series StoragevCenter Management plugin\Uninstall VCenter plug-in for DS3000.3 42 .

Troubleshooting vCenter plug-in issues This section describes how to open and read the vCenter plug-in log file.csv The file is archived every 24 hours and stored for 10 days. Save Config and Save MEL secondary pop-up screens do not appear (200178293) If you try to save a configuration file or a MEL log file. Delay in updating failed controllers (200184485) Timing issues and retry counts cause a delay of three to four minutes before the status of a failed controller is updated to Failed Controller under the Summary tab in the Subsystem Manager. CVSed or a similar viewer. The file is in CSV format.3 This section describes known issues with vCenter plug-in version 2. but the second attempt succeeds. Note: If the file is locked. If you try to change the roles on the secondary storage subsystem after communications with the primary storage subsystem have been lost. DS4000 and DS5000 series storage: User guide for version 2.3 and available workarounds. If you try to create a new logical drive on a storage subsystem when the primary controller is offline. provides answers to some frequently asked questions and describes how to resolve some common problems you might encounter with the vCenter plug-in. open the copied file and view it. an error message appears stating that the password for the storage subsystem is wrong. You can open the file and view it in Notepad. If the first attempt fails.Restrictions for vCenter plug-in Version 2. after which the file is overwritten. create a copy of the file with a different name. perform the save configuration action or the save MEL log action again.3 43 . unexpected behavior appears in the vCenter plug-in under the Enhanced Remote Mirroring tab. the first attempt fails. vCenter management plug-in for IBM System Storage DS3000.y. Logical Drive creation fails on an array of RAID Level 5 (200180549) Logical-drive creation fails on an array of RAID level 5 when one of the storage subsystem controllers is offline. Application server logs All procedures performed from the vCenter plug-in are logged to the following application-server log file: C:\Program Files\DS3000/DS4000/DS5000Series StoragevCenter Management Plugin\jetty\logs\ vCenter2-logx. Enhanced remote mirroring is not working as expected (200180174) Changing roles when the primary storage subsystem is offline displays a new primary and a new secondary subsystem in addition to the previous entry.

no updates or modifications occur. see section Configuring storage-administrator roles. If it is stopped.msc window.y Jetty service log.log Installation log does not show that the Pegasus service started Verify that the cimserver service was started from the services. used by technical support—jetty-service. Note: If the vCenter plug-in is installed on the same system as an active vCenter Server and VMware Update Manager is installed. enable it. I cannot create or delete objects Verify that the user ID has the required storage administrator privileges assigned for the user’s role.Figure 47 vCenter Plug-in Log view Additional log files that are useful for technical support to resolve issues are also maintained in this directory. If the cimserver/Pegasus server service is stopped. so a fast processor with sufficient memory to avoid page swapping. DS4000 and DS5000 is a client-side intensive application. If the Jetty TCP port is not enabled. • • • Debug log used by technical support—vCenter2debug-x. offers the best vSphere Client environment. DS4000 and DS5000 series storage: User guide for version 2. I cannot communicate with the application server Follow these steps: 1. Verify that the Jetty6-Service is started on the application server. For more details about storage administrator roles. How can I maximize client performance The VCenter plug-in for DS3000.request. you must change the default port number 8084 to an unused port number.3 44 . Verify that the cimserver/Pegasus server service is started on the application server. but these files are usually not in a user-friendly format. the CIMOM service must be started before the Jetty service is started. Check the firewall settings to verify that the Jetty Transmission Control Protocol (TCP) port is enabled. Otherwise. vCenter management plug-in for IBM System Storage DS3000.log.log Log of IP addresses for all Jetty service requests from clients—<date/time stamp>. Note: If one of these services fails to respond or stops. 2. start it. 3. start it.

3 45 . change the password in the vCenter plug-in so that the vCenter plug-in password matches the storage subsystem password. The vCenter plug-in displays the properties of the storage subsystem whether the passwords match or do not match. some views might generate a slow script warning message and delay the processing of the view. The storage subsystem name does not change. you can run passive commands from the vCenter plug-in to the storage subsystem. the vCenter plug-in considers the storage subsystem to be a first-time installation. • vCenter plug-in displays incorrect error messages Incorrect error codes might appear because of the limited return codes from the SMI-S Provider. Remove the storage subsystem from the vCenter plug-in. When you troubleshoot incorrect error codes. clears the entire configuration and changes the storage subsystem name to the default name. perform the following actions: 1. You can suppress these warning messages by changing the following registry entries on the storage subsystem from which the vSphere Client is running. vCenter plug-in does not show the new storage subsystem name after a clear configuration operation in the storage management software You can perform a Clear Configuration operation in the storage management software in two ways: • The Clear Configuration operation on an array deletes only the logical-drive configuration. Add the storage subsystem. so the vCenter plug-in still sees the same storage subsystem name.How do I suppress slow script warning messages? Depending on the size of the storage subsystem. • After you change the password on the storage subsystem. but the password in the vCenter plug-in is not changed. In the storage management software. The Clear Configuration operation on a storage subsystem. See Resolving a password mismatch for more information about how to resolve a password mismatch. • When the passwords do not match. DS4000 and DS5000 series storage: User guide for version 2. ensure that you include all detailed information about the errors. rename the storage subsystem.microsoft. I cannot make changes to a storage subsystem You can make changes to the storage subsystem only when the password in the vCenter plug-in matches the password set on the storage subsystem. such as when the storage subsystem password is changed. to the vCenter plug-in. 3. again. • • HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Styles DWORD MaxScriptStatements set to 0xFFFFFFFF The Microsoft Knowledge Base article that describes how to change the registry entries is at http://support. After a Clear Configuration operation. 2. but active commands to the subsystem fail.com/kb/175500. For the vCenter plug-in to recognize the storage subsystem. vCenter management plug-in for IBM System Storage DS3000.

elink.cgi?CTY=US IBM Redbooks® ibm.com/partnerworld/systems/storage IBM Systems on IBM PartnerWorld ibm.com/redbooks IBM developerWorks® ibm.ibmlink.com/partnerworld/systems/IBM Publications Center IBM Publications Center www.com/developerWorks vCenter management plug-in for IBM System Storage DS3000. DS4000 and DS5000 series storage: User guide for version 2.com/public/applications/publications/cgibin/pbi.Resources These web sites provide useful references to supplement the information contained in this document: • • • • • System Storage on IBM PartnerWorld® ibm.ibm.3 46 .

DS4000 and DS5000 series storage: User guide for version 2. Actual environmental costs and performance characteristics may vary by customer. Other company. A current list of IBM trademarks is available on the web at Copyright and trademark information at www.ibm. All Rights Reserved. capability or any other claims related to non-IBM products.S. Information is provided "AS IS" without warranty of any kind. Information concerning non-IBM products was obtained from a supplier of these products. including vendor announcements and vendor worldwide homepages. vCenter management plug-in for IBM System Storage DS3000. the IBM logo and ibm. published announcement material or other publicly available sources and does not constitute an endorsement of such products by IBM. registered or common law trademarks owned by IBM at the time this information was published. other countries or both.Trademarks and special notices © Copyright IBM Corporation 2011. Any references in this information to non-IBM web sites are provided for convenience only and do not in any manner serve as an endorsement of those web sites. IBM. Questions on the capability of non-IBM products should be addressed to the supplier of those products. The materials at those web sites are not part of the materials for this IBM product and use of those web sites is at your own risk. Sources for non-IBM list prices and performance numbers are taken from publicly available information. References in this document to IBM products or services do not imply that IBM intends to make them available in every country. Microsoft. these symbols indicate U. product or service names may be trademarks or service marks of others.com/legal/copytrade.com are trademarks or registered trademarks of International Business Machines Corporation in the United States. Windows.shtml. Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™). All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. IBM has not tested these products and cannot confirm the accuracy of performance.3 47 . other countries or both. Such trademarks may also be registered or common law trademarks in other countries.

Sign up to vote on this title
UsefulNot useful