HP StorageWorks XP Provisioning Manager Installation and Configuration Guide Part number: T1783-96001 First edition: November, 2005
Legal and notice information © Copyright 2005 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents About this guide Revision history Revision tables ....................................................................................................................................................... 8 1 Reviewing Components and Requirements for Provisioning Manager 1-1 Provisioning Manager Features .................................................................................................................. 9 1-1-1 Managing Various Storage Subsystems as a Storage Pool......................
Figures Figure 1-1 Example of a Storage Pool ......................................................................................................................... 9 Figure 1-2 Storage Subsystem and Host Setup ........................................................................................................ 10 Figure 1-3 Provisioning Manager Components .........................................................................................................
Tables Table 1 Document conventions .................................................................................................................................. 6 Table 2 Revisions ....................................................................................................................................................... 8 Table 1-1 Server Operating Systems........................................................................................................................
About this guide This manual describes how to configure the environment settings for and how to install the HP StorageWorks XP Advanced Edition Provisioning Manager. Intended audience This manual is intended for those who use Provisioning Manager to operate or manage a system that uses a storage subsystem (magnetic disk array unit). The readers of this manual should have the following knowledge: • A basic knowledge of SANs (Storage Area Networks).
HP technical support Telephone numbers for worldwide technical support are listed on the HP web site: http://www.hp.com/support/ Collect the following information before calling: • Technical support registration number (if applicable) • Product serial numbers • Product model names and numbers • Applicable error messages • Operating system type and revision level • Detailed, specific questions For continuous quality improvement, calls may be recorded or monitored.
Revision tables Table 2 Revisions Date Edition Revision November, 2005 First Initial release Revision history (start here) Revision history
1 Reviewing Components and Requirements for Provisioning Manager This chapter describes the features and components of Provisioning Manager, prerequisite and related products for Provisioning Manager, examples of system configurations (including the minimum configuration), and requirements for storage subsystems: • Provisioning Manager Features (see section 1-1 ) • Provisioning Manager Components (see section 1-2 ) • System Requirements (see section 1-3 ) • Required Programs (see section 1-4 ) • Re
To search volumes in a storage pool, you can pre-define search conditions for volume allocation. These predefined conditions are called a provisioning plan. Specifying a provisioning plan when you analyze a storage pool or display a list of volumes enables you to narrow down and display only those volumes that are relevant when searching a large number of volumes.
Figure 1-3 Provisioning Manager Components • Provisioning Manager Server forms storage pools from storage subsystems, and allocates volumes to hosts, allowing the user to access the Device Manager agent to manage file systems. NOTE: Install the Provisioning Manager server and the Device Manager agent on different machines. • Provisioning Manager Client allows users to access the server using a web browser.
Figure 1-4 Minimum Hardware Configuration (Example 1) Figure 1-5 illustrates a configuration where the management client is set up in another system. The management client can connect either to a TCP/IP network (intranet) or via the Internet. Figure 1-5 Minimum Hardware Configuration (Example 2) Figure 1-6 illustrates a configuration with multiple storage subsystems and hosts. Note that there is no need to connect hosts in which no Device Manager agent is installed on a TCP/IP network.
Figure 1-6 Hardware Configuration with Multiple Subsystems and Multiple Hosts 1-3-2 Server Operating System Requirements Table 1-1 lists the supported server operating systems.
® ® Windows 2000 See Note 2, 3 and 4 Windows Server™ 2003 (32 bit) See Note 2 and 4 Windows Server™ 2003 (EM64T) See Note 2 and 4 Solaris™ ® Linux (32 bit) Windows 2000 Server SP3 ® Windows 2000 Advanced Server SP3 ® Windows 2000 Datacenter Server SP3 ® Windows 2000 Professional SP3 ® Windows 2000 Server SP4 ® Windows 2000 Advanced Server SP4 ® Windows 2000 Datacenter Server SP4 ® Windows 2000 Professional SP4 Windows Server™ 2003, Standard Edition Windows Server™ 2003, Enterprise Edition Windows Ser
Table 1-3 Supported File System Types Host OS AIX ® ® Linux Supported File System Types Expandable? Remarks HFS No JFS Yes • • • • ext2, ext3 Yes • • • ® Windows 2000 NTFS Yes Windows Server™ 2003 NTFS Yes • • • • • • Solaris™ UFS VERITAS™ File System No Yes • • • • • • When a file system is expanded, stop jobs. File systems can only be displayed. Standard OS file system. Standard OS file system.
Table 1-4 Supported Client Operating Systems That Use a GUI OS Name Version ® (SPARC version) Solaris™ 9 1-3-6 Web Browsers Supported for Management Clients Table 1-5 lists the Web browser versions supported for management clients that use a graphical user interface (GUI). Table 1-5 Web Browsers Supported for Management Clients That Use a GUI Supported Web Browser ® Microsoft Internet Explorer ® Netscape Navigator ® Mozilla Version Remarks Internet Explorer 6.
Table 1-6 Product Names and Versions of Dynamic Link Manager OS AIX HDLM Required Version ® ® ® For AIX 5.1 or AIX 5.2: • Hitachi Dynamic Link Manager 04-00-/G or later (when the Dynamic Link Manager version is 04), • Hitachi Dynamic Link Manager 05-02 or later (when the Dynamic Link Manager version is 05). ® For AIX 5.3: • Hitachi Dynamic Link Manager 05-41 or later Solaris™ When using VERITAS Volume Manager 3.
2 Installing Programs This chapter describes the programs installed onto the management server and host (you do not need to install or configure Provisioning Manager client).
3 Installing the Provisioning Manager Server This chapter describes how to install and uninstall a Provisioning Manager server: • System and Media Requirements (see section 3-1 ) • Installing the Provisioning Manager Server (see section 3-2 ) • Upgrading the Provisioning Manager Server (see section 3-3 ) • Uninstalling the Provisioning Manager Server (see section 3-4 ) • Backing Up, Restoring, and Converting a Database in a Provisioning Manager Server (see section 3-5 ) 3-1 System and Media Requir
• • Number of LDEVs: 1,000. • Number of histories: 1,500. • Number of plans: 50. Large configuration example: • In the following configuration, the estimate of the capacity used by Provisioning Manager is 1 GB. • Number of hosts: 300. • Average number of disks per host: 100. • Number of LDEVs: 30,000. • Number of histories: 45,000. • Number of plans: 1,000. • Installing Provisioning Manager temporarily requires about 50 MB of free hard disk space.
10. The Installation Progress windows display (see Figure 3-7 and Figure 3-8). 11. Installation will be canceled in the following cases: • When you click the Cancel button to cancel the installation. • When an error occurs during installation and an error message displays. If this occurs, eliminate the cause of the error, use the Windows® Add/Remove Programs Utility to uninstall Provisioning Manager, and then reinstall it. 12. The Installation Finished window displays (see Figure 3-9).
Figure 3-3 Installation Server Information Settings Window-Port Number Figure 3-4 Port Number Change Confirmation Window Figure 3-5 Pre-installation Confirmation Window Installing the Provisioning Manager Server 22
Figure 3-6 Message Notifying That User Information Setup Is in Progress Figure 3-7 Setup Status Window Figure 3-8 Message Notifying That Software Information Setup Is in Progress Figure 3-9 Installation Finished Window Installing the Provisioning Manager Server 23
3-2-1 Installing a Provisioning Manager Server in a Cluster Environment When you operate a Provisioning Manager server in a cluster environment, availability of the Provisioning Manager server is enhanced. If you want to operate a Provisioning Manager server in a cluster environment, you must perform setup for a Device Manager server in a cluster environment.
• • Number of hosts: 20 • Average number of disks per host: 50 • Number of LDEVs: 1,000 • Number of histories: 1,500 • Number of plans: 50 Large configuration example: • In the following configuration, the estimate of the capacity used by Provisioning Manager is 1 GB.
Figure 3-10 Installation Startup Window Figure 3-11 Pre-installation Confirmation Window Figure 3-12 Message Notifying That User Information Setup Is in Progress Installing the Provisioning Manager Server 26
Figure 3-13 Setup Status Window Figure 3-14 Message Notifying That Software Information Setup Is in Progress Figure 3-15 Installation Finished Window 3-3-1 Overwrite Installation of Provisioning Manger Server in a Cluster Environment When performing an overwrite installation of the Provisioning Manger server in a cluster environment, follow the procedure for re-installing the Device Manager server in a cluster environment; however, instead of reinstalling the Device Manager server, perform an overwrite i
NOTE: You must start the following services before installing the Provisioning Manager server. If any of the following services have not started, start them in the following order: 1 2 the Common Component services. HiCommandServer. 3-4 Uninstalling the Provisioning Manager Server Before beginning the uninstallation process, check the following: • • Do not uninstall Provisioning Manager unless you need to redo the entire installation process due to a problem.
Figure 3-16 Uninstallation Startup Window Figure 3-17 Pre-uninstallation Confirmation Window Figure 3-18 Message Notifying That Software Information Setting Removal Is in Progress Installing the Provisioning Manager Server 29
Figure 3-19 Setup Status Window Figure 3-20 Uninstallation Finished Window 3-4-1 Uninstalling a Provisioning Manager Server in a Cluster Environment When uninstalling a Provisioning Manger server in a cluster environment, follow the procedure for re-installing the Device Manager server in a cluster environment but, instead of re-installing Device Manager server, uninstall the Provisioning Manager server.
3-5 Backing Up, Restoring, and Converting a Provisioning Manager Server Database When the Device Manager server database is backed up, restored, or converted, the Provisioning Manager server data is also backed up, restored, or converted. For details about backup, restoration, and conversion of the Device Manager server database, see the HP StorageWorks Command View XP Advanced Edition Device Manager Server Installation and Configuration Guide.
4 Configuring the Provisioning Manager Environment This chapter describes the properties of Provisioning Manager server, the properties of a related Device Manager agent, and the environment settings for the Provisioning Manager server and the host: • Overview of Provisioning Manager Server Properties (see section 4-1 ) • Server Properties (see section 4-2 ) • Overview of the Device Manager agent Properties (see section 4-3 ) • The Device Manager agent Properties (see section 4-4 ) • Security Setti
Table 4-1 Summary of Provisioning Manager Server Properties Classification Properties related to server log functionality. File Name logger.properties Property See Section server.history.maxNumber 4-2-1-4 server.history.maxDays 4-2-1-5 server.installTime 4-2-1-6 Logger.loglevel 4-2-2-1 Logger.sysloglevel 4-2-2-2 Logger.MaxBackupIndex 4-2-2-3 Logger.MaxFileSize 4-2-2-4 4-2 Server Properties 4-2-1 Server Configuration Information Properties 4-2-1-1 server.operation.
• HPvMGuiTrace*.log • HPvMGuiMessage*.log • HPvMServerTrace*.log • HPvMServerMessage*.log Provisioning Manager specifies 0, 10, 20, or 30 as the output level for each log output message according to its content, regardless of whether the message type is error, warning, or information. Only messages with an output level that is less than or equal to the value set in this field are output to the trace log or message log.
Table 4-2 The Device Manager Agent Properties Classification File Name Property See Section Properties related to an agent's HTTP communication function. server.properties server.agent.fs.moduleTimeOut 4-4-1-1 server.agent.vm.moduleTimeOut 4-4-1-2 server.agent.os.moduleTimeOut 4-4-1-3 logger.loglevel See Note 4-4-2-1 logger.MaxBackupIndex See Note 4-4-2-2 logger.MaxFileSize See Note 4-4-2-3 Properties related to an agent's log function. logger.
You can specify a value from 1 to 20. Default: 10 4-4-2-3 logger.MaxFileSize You use this property to set the maximum size for the trace log files and error log files that are output by the log output function. When the log file size exceeds the specified value, a new log file is created. When setting a value, you must specify KB or MB as the unit. Otherwise, the specified value is interpreted as being specified in bytes.
5 Troubleshooting This chapter lists problems that might occur during the installation or uninstallation of Provisioning Manager, the corrective actions that you should take in the event of a problem, and output messages: • Troubleshooting information (see section 5-1 ) • Resolving Errors that Occur During the Installation of Provisioning Manager Server (see section 5-2 ) • Error Messages (see section 5-3 ) 5-1 Troubleshooting Information Table 5-1shows general information for troubleshooting while yo
Figure 5-1 Example of An Error Message 5-2 Resolving Provisioning Manager Server Installation Errors Perform the following procedure if an error occurs during installation of Provisioning Manager server: 1. Check the status at the time of the error. Check output messages and operations that were being performed when the error occurred. If an error message has been output, perform the recommended action. For message details, see section 5-3 . 2. Collect information to check the cause of the error.
Table 5-2 Provisioning Manager Installer Error Messages (continues on the following pages) Message ID Message Text Action KARF60021-E The installation directory of Device Manager cannot be checked. Cause: An attempt to install Device Manager might have failed. Action: Device Manager might not be installed correctly, so re-install it. KARF60022-E The installed directory is incorrect. Cause: An attempt to install Device Manager might have failed.
Table 5-2 Provisioning Manager Installer Error Messages (continues on the following pages) Message ID Message Text Action KARF60102-E The entered characters contain an error. Entered characters: Entered characters Cause: The entered characters contain an error. Action: Enter valid characters. KARF60301-E A file required for installation was not found. Cause: A disk error might have occurred during access of the installed file. Action: Make sure that the installation target disk is normal.
Table 5-2 Provisioning Manager Installer Error Messages (continues on the following pages) Message ID Message Text Action KARF60402-E An attempt to delete the product version information set in the registry has failed. Cause: A problem might exist in the OS. Action: Acquire Device Manager's maintenance information, and the trace information at the time of setup, and then contact the Support Center. KARF60403-E An attempt to register uninstallation in the registry has failed.
Table 5-2 Provisioning Manager Installer Error Messages (continues on the following pages) Message ID Message Text Action KARF60602-E An attempt to start the Common Component service has failed. Cause: Single Sign On Service might not be enabled, or a critical error might have occurred in the Common Component. Action: Acquire the log information of Device Manager and Common Component, and then contact the Support Center. KARF60603-E An attempt to stop the Common Component service has failed.
Table 5-2 Provisioning Manager Installer Error Messages (continues on the following pages) Message ID Message Text Action KARF60644-E An attempt to access the Common Component Cause: has failed. An attempt to install Device Manager might have failed. Action: Device Manager might not be installed correctly, so re-install it. KARF60661-E An attempt to set the Web contents for Common Component has failed. Cause: Single Sign On Service, or the Device Manager server service might not be enabled.
Table 5-2 Provisioning Manager Installer Error Messages (continues on the following pages) Message ID Message Text Action KARF60801-E An attempt to delete the installation directory has failed. Cause: The installation directory, as well as a folder or file in the installation directory, are in an active state because of another application. Action: When a folder or a file in a folder is active, deactivate the file or folder, and then delete the directory.
Acronyms and Abbreviations GUI graphical user interface HBA HDLM host bus adapter Hitachi Dynamic Link Manager IA32 IA64 Intel Architecture 32 Intel Architecture 64 LDEV LU LVM logical device logical unit Logical Volume Manager OS operating system SAN SDS SSL SVM storage area network Solstice DiskSuite™ secure socket layer Solaris™ Volume Manager TCP/IP TLS transmission control protocol/internet protocol transport layer security 45
Index B J R Basic, 17 JFS, 15 required products, 13 C L S CD-ROM, 20, 25 cluster environment, 24 Command View XP AE Suite Common Component, 20 logger.properties file, 32, 34 LVM, 17 D management client, 12 management server, 11 maximum number of log files, 34 maximum size of a log file, 34 message ID, 38 Microsoft Cluster Server, 24 Mozilla, 16 SDS, 17 server information: port number, 20 server.
