HP StorageWorks XP Provisioning Manager User Guide Part number: T1783-96002 First edition: November, 2005 About this guide 1
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 ..................................................................................................................................................... 13 1 Overview of HP StorageWorks XP Provisioning Manager 1-1 The Provisioning Manager Mission ........................................................................................................... 14 1-1-1 Managing Various Storage Subsystems as a Storage Pool.....................................
-1 Restrictions on Host Management ............................................................................................................ 54 4-1-1 Configuring Cluster Software.......................................................................................................... 54 4-2 Restrictions When the Host OS is Windows® ............................................................................................ 54 4-2-1 Prerequisites for the Host ............................................
Managing Storage Pools 5-1 Managing a Storage Pool.......................................................................................................................... 79 5-1-1 Perspective from a Parent Group to Subordinate Groups.............................................................. 80 5-1-2 Perspective from a Child Group to Its Subordinate Groups ........................................................... 81 5-1-3 Number of Volumes That Can Be Displayed.....................................
11-3-2 Collecting Error Information.......................................................................................................... 162 11-4 Server Address Specified during Installation........................................................................................... 165 11-5 Inconsistency in the Display between the Navigation and Information Frames ...................................... 165 11-6 Error Messages ..............................................................................
Figures Figure 1-1 Example of a Storage Pool ....................................................................................................................... 15 Figure 1-2 Setup of Storage Subsystems and Hosts ................................................................................................. 16 Figure 1-3 Principal Components of Provisioning Manager.......................................................................................
Figure 5-29 Move LDEVs Dialog Box when Show LDEVs is Clicked ...................................................................... 102 Figure 6-1 Scope of LU Information Displayed When Using SDS/SVM .................................................................. 106 Figure 6-2 Scope of File System, Device File, and Logical Volume Information Displayed Using SDS/SVM ......... 107 Figure 6-3 Hosts Subwindow and List Objects - Hosts Subwindow ................................................................
Tables Table 1 Document conventions ................................................................................................................................. 10 Table 2 Revisions ...................................................................................................................................................... 13 Table 1-1 Provisioning Manager Operations .............................................................................................................
About this guide This manual provides an overview of the HP StorageWorks XP Advanced Edition Provisioning Manager, describes its operation, and provides step-by-step procedures on how to use its graphical user interface (GUI). Intended audience This manual is intended for those who use Provisioning Manager to operate and manage a system based on a storage subsystem (magnetic disk array unit).
Table 1 Document conventions Convention Element Convention Element Monospace, bold font Emphasis of file and directory names, system output, code, and text typed at the command-line CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: Provides clarifying information or specific instructions. NOTE: Provides additional information.
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 history (start here) Revision history Revision tables Table 2 Revisions Date Edition Revision November, 2005 First Initial release Revision history 13
1 Overview of HP StorageWorks XP Provisioning Manager This chapter explains the features of HP StorageWorks XP Provisioning Manager, its components, and its relationships to other programs. The chapter also summarizes what you can do with Provisioning Manager, and gives an overview of the procedures for installing and operating Provisioning Manager.
Figure 1-1 Example of a Storage Pool As a way to locate volumes in a storage pool, you can use a provisioning plan to pre-define search conditions for volume allocation. Specifying a provisioning plan when you analyze a storage pool or display a list of volumes enables you to display only relevant items when searching from among a large number of volumes.
Figure 1-2 Setup of Storage Subsystems and Hosts 1-2 Provisioning Manager Components Figure 1-3 shows the principal components of Provisioning Manager. Note that Provisioning Manager depends on, and can co-exist on the same server with, Device Manager: • Provisioning Manager server (management server) The Provisioning Manager server controls storage pool management and host settings, based on instructions from the system administrator and the storage user at the host side.
Figure 1-3 Principal Components of Provisioning Manager 1-3 Programs Related to Provisioning Manager Hewlett-Packard sells several products related to Provisioning Manager: Hitachi Dynamic Link Manager Dynamic Link Manager is used to create a redundant configuration for the paths between host ports and storage subsystems. Dynamic Link Manager is a program product that manages access paths to the storage. For details about Dynamic Link Manager, see the manual for Dynamic Link Manager.
Figure 1-4 provides an overview of the operation flow used for installing Provisioning Manager onto a management server. Figure 1-4 Operation Flow for Installing Provisioning Manager When you install a Provisioning Manager client, you do not need to configure installation or environment settings. For details about the browser versions that can be used to operate Provisioning Manager clients and how to work with the GUI, see 2 .
System Administrator Storage Administrator Guest Local System Administrator Local Storage Administrator Local Guest Viewing storage pools or listing volumes Y Y Y Y Y Y Allocating or unallocating volumes Y Y -- Y Y -- Moving volumes Y -- -- Y -- -- Viewing hosts or updating information Y Y Y Y Y Y Viewing file systems Y Y Y Y Y Y Creating, expanding, or deleting file systems Y Y -- Y Y -- Viewing device files Y Y Y Y Y Y Creating or deleting device file
Figure 1-5 Using Provisioning Manager to Manipulate Storage Subsystems The following explains the flow of operations on subsystems that use Provisioning Manager: 1. Install the storage subsystems and hosts. Use Device Manager to install. Installing storage subsystems by using Device Manager allows you to use Provisioning Manager to manage all the LDEVs and LUs defined in the storage subsystems.
Manager to delete the host registration, which removes the host from under the control of Provisioning Manager. 6. To remove a storage subsystem that is no longer needed, use Provisioning Manager to delete the file systems and device files for all hosts that use the storage subsystem you wish to remove. Once you have confirmed that no file system or device file that uses the storage subsystem you wish to remove exists, you can safely remove the storage subsystem from the SAN.
Manager (HDLM). You must install HDLM on each host in advance. Figure 1-6 provides an overview of the relationships between HDLM, the host, the storage subsystem, and the management servers when path redundancy is provided. HDLM manages access paths from a host port to a port in the storage subsystem.
Figure 1-6 Path Redundancy Provided by HDLM 1-7-2 Using Provisioning Manager with Volume Managers If you want to expand a file system that was created with Provisioning Manager, you can use third-party volume manager software. Expanding a file system means increasing the size of the file system whenever it becomes necessary to do so, without affecting the data in the existing files created in that file system.
Figure 1-7 Linking with a Volume Manager (Creating a File System) To expand a file system, the volume manager adds an LU into the volume (disk) group to expand the logical volume as shown in Figure 1-8, then the file system in the logical volume is expanded.
Figure 1-8 Linking with a Volume Manager (Expanding a File System) 1-7-2-1 Types of Volume Managers A Volume Manager must be installed on the host. Some volume managers are provided by default with the host OS. Other volume managers might be available even if they are not provided by default. 1-7-2-2 Setting Up for Volume Managers You can link the volume managers of other manufacturers with Provisioning Manager. Some volume managers are provided by default with the host OS.
1-7-3 About Single Sign-On Functionality You can use the single sign-on functionality of the Command View XP AE Suite Common Component to launch other Command View XP AE Suite products from Provisioning Manager’s GUI, including Device Manager. This functionality automatically permits you to launch other products without having to re-enter your user ID and password.
2 Provisioning Manager Planning and Startup This chapter describes the prerequisites for using Provisioning Manager, and the procedure for starting and logging into the program.
IMPORTANT: The language that is displayed in the Provisioning Manager GUI depends on the language setting in the browser being used. The date format also depends on the browser’s language setting is displayed by default as shown below. Browser time is displayed in 24-hour clock format, regardless of the language setting.
Figure 2-1 Provisioning Manager Title Dialog Box 2. Click the Go to Login page button. The login dialog box is displayed, as shown in Figure 2-2 below. Figure 2-2 Provisioning Manager Login Dialog Box 3. Enter the User ID (user name defined with Device Manager) and Password. NOTE: The default User ID is “system”. The default password is “manager”. The Password is case sensitive. If you enter an invalid password, a login dialog box displays an error message. In such a case, enter the correct password.
Figure 2-3 Login Dialog Box Displaying an Error Message 4. Click the Login button. The main window of Provisioning Manager is displayed (see Figure 2-4). NOTE: When you click the Login button without registering the license information, an error message is displayed in the Login dialog box. Register the license information, and then log in to Provisioning Manager.
Figure 2-5 Provisioning Manager Version Information Dialog Box 2-4 Starting Provisioning Manager Operation After you have logged in to the Provisioning Manager server, you can start Provisioning Manager operation. You can access all the functionality from the main window of Provisioning Manager. To start Provisioning Manager operations: 1. Log in to Provisioning Manager. The List Objects - Provisioning Manager subwindow is displayed (see Figure 2-6). 2.
Figure 2-6 List Objects - Provisioning Manager Subwindow 2-5 Using Provisioning Manager Windows This section describes the frames that make up the Provisioning Manager window and also items shown in the pop-up window. Figure 2-7 shows the frames that make up the Provisioning Manager window.
Figure 2-7 Frames of the Provisioning Manager Window 2-5-1 About the Menu-Bar Frame The menu-bar frame provides commands to control overall operations of Provisioning Manager, such as logging out and displaying version information. When a command link is selected, its associated pop-up dialog box is displayed. The menu-bar frame contains the following items (commands). Tools When you click the Tools link, a dialog box is displayed that allows you to display windows of other programs.
IMPORTANT: The information set by using Device Manager is not automatically displayed in the Provisioning Manager window. When you set the information by using Device Manager, click Refresh to display the latest information.
When you click the Allocation Plans link, a subwindow for starting allocation plan management is displayed in the method frame and information frame. PlanName When you click on the left of the Allocation Plans link, a PlanName is displayed. When you click a PlanName link, a subwindow for starting deletion or editing of an allocation plan is displayed in the method frame and information frame.
2-5-5 About Popup Dialog Boxes Popup dialog boxes display detailed information and commands for performing operations with Provisioning Manager. Figure 2-9 shows an example of a pop-up dialog box. Figure 2-9 Example of a Popup Dialog Box The common items are described below: • Object address The dialog box displayed indicates which object is selected in the navigation frame.
3 Using Provisioning Manager This chapter provides an overview of the main features of Provisioning Manager, with an emphasis on what you can do with the product and how it contributes to improved efficiency.
Figure 3-2 Storage Pool Management in Concept 3-1-2 Storage Pools and Storage Areas Provided by Device Manager A Provisioning Manager storage pool is created by applying the My Storage mechanism provided by Device Manager. • Each My Storage area has a one-to-one correspondence with a storage pool (when storage pools of user groups at lower levels are included). • The hierarchical structure of the logical groups enables hierarchical management of storage pools.
Figure 3-3 Relationships between Logical Groups, User Groups, My Storage Areas, and Storage Pools A storage pool is created for each user group. For each group, the range of the storage pool that can be used (accessed and operated) contains the storage pool of the user group to which the user belongs and the storage pools of any lower-order user groups in the hierarchy of user groups.
3-1-4 Linking Storage Pools with CLPR and SLPR Functions StorageWorks XP12000/XP10000 provide a function (CLPR) for logically dividing caches. StorageWorks XP12000/XP10000 also provides a function (SLPR) for logically dividing resources in storage subsystems. CLPR and SLPR functions enable you to assign a partitioned storage administrator to resources that have been partitioned by purpose and usage. Provisioning Manager displays CLPR and SLPR numbers as logical unit attributes.
Figure 3-4 Creating a Storage Pool by Using the CLPR and SLPR Functions Figure 3-5 Assigning a Volume by Using the CLPR and SLPR Functions Using Provisioning Manager 41
Figure 3-6 Partitioned Resource Administration by Server for Each SLPR NOTE: The configuration shown in Figure 3-6 is also supported for SSP, etc. By installing a server for each SLPR, you can manage resources in a specific SLPR from each server. 3-1-5 Moving Volumes between Storage Pools You can move storage volumes that have not been allocated to a host into other storage pools.
However, if there are any storage pools positioned two or more levels below the specified user group, the figures for the storage pools of any user groups two and more levels below are totaled and added to those for the storage groups of the user groups directly below the specified one. By changing the user group that is specified, you can move your perspective up or down within the user group hierarchy (however, you cannot move your perspective to a user group higher than the user group of the login user).
Figure 3-7 Example of Moving Volumes between Storage Pools 3-2 Allocating and Unallocating Volumes You can allocate a storage volume included in a storage pool to any host managed by a user group, and you can unallocate a storage volume from a host. You can also use a filtering facility defined in a provisioning plan to easily manipulate massive storage volumes that are displayed in a list of unallocated volumes or in a list of allocated volumes.
1. Use the Device Manager host registration function to manually register the host in a system (register the WWN of the host port). 2. Use Device Manager to place the host under the management of the user group that manages the storage pool. 3-2-2 Unallocating a Volume You can select one or more allocated volumes from among those listed to unallocate them from a host.
The process of creating a file system differs depending on whether Hitachi Dynamic Link Manager (HDLM) software is installed on the host, and on whether a volume manager is to be used to manage the file system being created. A subsystem volume (LU) allocated to a host is treated as a raw device by the host. When HDLM is not used, a single raw device is mapped to a single LU.
Figure 3-9 shows the relationship between the file system and device file that can be seen from the host, and the LU in the subsystem. This figure assumes that there are two paths between the host and the subsystem LU for when HDLM is being used.
Figure 3-10 Relationship Between Host File System/Device File and Subsystem LU (Expanding a File System) 3-4-3 Deleting a File System Once you specify the file system you wish to delete, Provisioning Manager can automatically perform the process of deleting the file system. The mount point specified by the user during the file system creation is not deleted.
Figure 3-11 shows the relationship between the device file that can be seen from the host and the LU in the subsystem when no volume manager is being used. This figure assumes that there are two paths between the host and the subsystem LU when HDLM is being used. Figure 3-11 Relationship between Host Device File and Subsystem LU (without Volume Manager) Figure 3-12 shows the relationship between the device file that can be seen from the host and the LU in the subsystem when a volume manager is being used.
Figure 3-12 Relationship between Host Device File and Subsystem LU (with VM) 3-5-2 Deleting a Device File Once you specify the device file you wish to delete, Provisioning Manager can automatically perform the process of deleting the device file. Note, however, that this operation performs only the host-side operations; it does not remove the paths on the subsystem side (it does not release LUNs), it does not release any LUSEs, nor does it release any volumes (LDEVs).
• Model name of the storage subsystem • RAID level of the storage volume (RAID 0, RAID 1, RAID 5, or other) • Drive configuration of the storage volume (3D+1P, 2D+2D, or other) You create a provisioning (allocation) plan in either of two ways: • Create an entirely new provisioning plan • Use an existing plan as a template, change some of its parameters, and then save this changed plan under a different name. In the Add Allocation Plan dialog box, you can add an allocation plan.
CAUTION: • • A user with guest or local guest access permission cannot edit an allocation plan.
There are two levels by which you can view transaction logs. You can view a list of transaction logs or you can view a detailed display of each transaction log in the list. In list view, by specifying the search conditions such as time range, processing status, and user operation’s range, you can narrow down the range that you want to view. For the operation that is being suspended, you can restart the operation from the list view window after user intervention has ended.
4 Working With OS-Based Constraints The following sections describe restrictions and notes on managing a host by using Provisioning Manager. The restrictions and notes are given separately for each OS. When adding a device file, or adding or expanding a file system for a host that is not recognizing any LUs, use Device Manager to register the port WWN of the HBA for the host in advance.
background during host setting operation. Regardless of whether or not the host setting operation is performed, do not stop the process of the diskpart.exe command line utility running in the background.
• The specified mount point is already in use by another file system Provisioning Manager cannot expand file systems in the following cases: • Multiple file systems have been mounted on the same folder • RAID software has been configured in the file system. Volumes cannot be used for file system expansion if any of the following apply: • The volume manager is using a volume on a host where the Device Manager agent version 1.
4-2-5 Restrictions on Related Products Software that cannot be used with Provisioning Manager Provisioning Manager cannot be used on a host where VERITAS™ Volume Manager has been installed. 4-2-6 Improving Windows® Host Performance Provisioning Manager uses the Windows® default settings for all settings that configure the host performance. When you want to improve host performance by specifying the parameters for the file systems and device files, change the appropriate settings manually.
4-2-12 Notes on Changing the Software Configuration For a host for which a host-setting operation has not finished (that is, for a host for which a suspended operation exists in the operation log), do not change any of the software listed below by installing or uninstalling them, or by changing the software version.
If the Provisioning Manager support functionality for the Device Manager agent is not installed, the values for some items may not be displayed. • VERITAS™ File System and VERITAS™ Volume Manager To install VERITAS™ File System and VERITAS™ Volume Manager on the same host, use the same version. If their versions are different, operations cannot be guaranteed.
• The Read/Write permissions have not been set in the LUN Security XP Extension function • The Auto Lun XP attribute has been set • The volume emulation type is not one of the following: OPEN-3, OPEN-8, OPEN-9, OPEN-K, OPEN-E, OPEN-L, OPEN-M, OPEN-V • The volume size is less than 512 MB • Dynamic Link Manager does not exist on the host, and multiple paths are assigned to the volume • The volume is being used as a Differential Management LU In any of the following environments, the file system ca
4-3-6 Setting the Unit of Volume Management In Provisioning Manager, the unit of volume management is an LU or a volume group. If you need to manage volumes in smaller units, use an OS command or volume manager command to manually create, expand, or delete a file system or device file. There is a one-to-one correspondence between volume groups and volumes. The volume group is used only for online expansion of a newly created volume.
The default setting value of the log size for VERITAS™ File System is 16 MB. Change this value as necessary. In UFS, the log size is automatically determined. The maximum log size is approximately 1 MB for each 1-GB file system, and total size is up to 64 MB. 4-3-13 Changing the File System Check at Startup Setting Provisioning Manager specifies that the file system is to be checked at system startup after a file system is created.
• A file system whose mount point hierarchy includes other mount points. • A file system that is being used by a process 4-4-3 Restrictions on Creating a File System and Device File To unify interfaces for creating a file system or a device file, Provisioning Manager changes the following command utility parameters from the default settings. When manually changing a value, follow the input format appropriate for each OS.
Default value: check=false #: Depending on the cluster management software, if a standby configuration is used and this setting is specified so that the file system is checked at startup, it may take time to switch the server when an error occurs. To avoid this, the setting must be changed so that the file system check is not performed at startup. For details, see the documentation for the cluster management software.
4-4-6 Setting the Unit of Volume Management In Provisioning Manager, the unit of volume management is an LU or a volume group. If you need to manage volumes in smaller units, use an OS command or a volume manager command to manually create or expand a file system or a device file. There is a one-to-one correspondence between volume groups and volumes. The volume group is used only for online expansion of a newly created volume.
4-4-14 Ensuring Dynamic Link Manager Operations In any of the following environments, if a Device Manager agent version 1.
4-5-1 Prerequisites for the Host • Device Manager agent You must install the Device Manager agent on a host managed by Provisioning Manager. If the Device Manager agent is not installed, the values for some items may not be displayed. If the Provisioning Manager support functionality for the Device Manager agent is not installed, the values for some items may not be displayed. The Provisioning Manager support functionality for the Device Manager agent is installed on a Device Manager agent 1.
• The volume is mounted on a host where the Device Manager agent has been installed • The volume is being used as a command device • The volume is being used as an S-VOL for Continuous Access XP • The volume is being used as an S-VOL or SP-VOL for Business Copy XP • The volume is being used as a V-VOL or POOL for Snapshot XP • The volume is being used as an on-demand device • The Read/Write permissions have not been set in the LUN Security XP Extension function • The Auto Lun XP attribute has
4-5-2-7 Notes on Changing the Software Configuration For a host for which a host-setting operation has not finished (that is, for a host for which a suspended operation exists in the operation log), do not change any of the software listed below by installing or uninstalling them, or by changing the software version.
• When multiple physical volumes or partitions create one volume group. • When multiple logical volumes exist in one volume group. • When one file system is mounted on multiple mount points. Provisioning Manager can also display snapshot volumes, which look like logical volumes. NOTE: Provisioning Manager cannot display information about volume groups or file systems created in md devices.
Initial setting: Not specified (does not check file systems during system startup) Other than the above setting, Provisioning Manager uses the default performance-related settings in Linux. To improve performance, adjust the settings manually. 4-5-5-2 Notes on Managing Volumes in Small Units For Provisioning Manager, LUs or volume groupsare management units.
You must install the Device Manager agent on a host managed by Provisioning Manager. If the Device Manager agent is not installed, the values for some items may not be displayed. If the Provisioning Manager support functionality for the Device Manager agent is not installed, the values for some items may not be displayed. • Version of VERITAS™ File System Provisioning Manager supports VERITAS™ File System 3.5. When you are using HP-UX 11i v1, the standard file system is VERITAS™ File System 3.3.
• The volume manager is using a volume on a host where the Device Manager agent has been installed • The volume is mounted on a host where the Device Manager agent has been installed • The volume is being used as a command device • The volume is being used as an S-VOL for Continuous Access XP • The volume is being used as an S-VOL or SP-VOL for Business Copy XP • The volume is being used as a V-VOL or POOL for Snapshot XP • The volume is being used as an on-demand device • The Read/Write perm
• The file system uses a volume manager other than Logical Volume Manager • The device file contains partitions Volumes that satisfy one of the following conditions cannot be used for device file addition: • The volume manager is using that volume on a host where the Device Manager agent has been installed • The volume is mounted on a host where the Device Manager agent has been installed • The volume is being used as a command device • The volume is being used as an S-VOL for Continuous Access X
4-6-4-12 Notes on Changing the Software Configuration For a host for which a host-setting operation has not finished (that is, for a host for which a suspended operation exists in the operation log), do not change any of the software listed below by installing or uninstalling them, or by changing the software version.
Supplementary note: To manually specify the setting, specify /etc/fstab. Setting value: 2 Default value: 0 (Do not check the file system at startup) # Depending on the cluster management software, if a standby configuration is used and this setting is specified so that the file system is checked at startup, it may take time to switch the server when an error occurs. To avoid this situation, the setting must be changed so that the file system check is not performed at startup.
2. Execute the vgchange command to remove the high availability cluster mark from the volume group. 3. From the cluster configuration file, delete the volume group that contains the file system or device file to be deleted. 4. Reconfigure the cluster. 5. Execute the vgchange command to enable the volume group. 6. If you want to delete the file system, execute the mount command to mount the file system. 7. Use the GUI to update host information.
Table 4-1 Maximum Setting Values for Functions Creating a Device File and File System Windows® OS Solaris™ OS AIX® OS Linux OS HP-UX OS Number of volume (disk) groups in a system Number of logical volumes per volume group Number of logical volumes in a system -- 255 255 99 256 (see Note 1) 1 1 1 (see Note 2) 1 1 255 255 255 255 256 Number of physical volumes per volume group Number of physical volumes per logical volume Number of file system expansion (addition of LU) times Logical volu
5 Managing Storage Pools This chapter explains how to manage storage pools using Provisioning Manager.
Figure 5-1 User Groups and Access Scopes In this case, the users who belong to the user group P_Group can view the storage pool usage status from the following perspectives: • From P_Group down to its subordinate groups • From C_Group01 down to its subordinate groups • From C_Group02 down to its subordinate groups • From GC_Group down to its subordinate groups NOTE: The storage pools and volume contents are displayed in the windows according to the following rules: • • • For megabytes (MB), only in
• Including Size of Child Groups: displays the storage pool usage status for the access scope of P_Group, which extends to its subordinate groups as shown in the detail below from Figure 5-1. 5-1-2 Perspective from a Child Group to Its Subordinate Groups From the perspective of C_Group01, the storage pool usage status is displayed in the following categories: • Excluding Size of Child Groups: displays the storage pool usage status for the access scope of C_Group01 excluding the access scope of GC_Group.
• Including Size of Child Groups: displays the storage pool usage status for the access scope of C_Group01. The figure below shows the corresponding scope within the scopes illustrated in Figure 5-1. IMPORTANT: As shown in Figure 5-2, when the scope of C_Group01 overlaps the scope of C_Group02, the capacity of the overlapped part is counted in both C_Group01 and C_Group02.
Figure 5-2 Volume Contents: Scope of C_Group01 Overlaps Scope of C_Group02 5-1-3 Number of Volumes That Can Be Displayed A maximum of 16,384 volumes can be displayed in the list of volumes (LDEVs). When the number of volumes in the user group reaches 16,384, a warning message is displayed in the list window. When the number of volumes in the user group exceeds 16,384, create a new child group, and then move the excess volumes to this group to display them.
4. After specifying User Group, click the Show Information button.
Figure 5-5 Show Properties - Storage Pool Subwindow when the Show Information Button is Clicked 5-3 Viewing Storage Pool Usage Status for Each Storage Subsystem Model In the Analyze Per Model - Storage Pool subwindow, you can view the storage pool usage status (total amount, allocated amount, unallocated amount, and usage rate) for each storage subsystem model. NOTE: Information not reflecting the latest status might be displayed when the storage subsystem information is being updated.
IMPORTANT: The sum of the storage sizes of new groups and child groups, including the contents of grandchild groups, equals the sum of new groups, including child groups. However, if there are multiple child groups, and if the access scope of the child groups overlaps, the contents of new groups and child groups, including the contents of grandchild groups, are larger than that of new groups, including child groups. For details, see section 5-1 .
Figure 5-8 Analyze per Model - Storage Pool Subwindow, When Show Information is Clicked 5-4 Viewing Storage Pool Usage Status for Each RAID Level In the Analyze Per RAID Level - Storage Pool subwindow, you can view the storage pool usage status (total amount, allocated amount, unallocated amount, and usage rate) for each RAID level. NOTE: Information not reflecting the latest status might be displayed when the storage subsystem information is being updated.
Figure 5-9 Analyze per RAID Level - Storage Pool Subwindow Figure 5-10 Analyze per RAID Level - Storage Pool Subwindow when Details is Selected Figure 5-11 Analyze per RAID Level - Storage Pool Subwindow when Show Information is Clicked 5-5 Viewing Storage Pool Usage Status for Each Storage Subsystem Series In the Analyze Per Series - Storage Pool subwindow, you can view the storage pool usage status (total amount, allocated amount, unallocated amount, and usage rate) for each storage subsystem series.
To view the storage pool usage status for each storage subsystem series: 1. In the navigation frame, select Storage Pool. The Storage Pool subwindow is displayed in the method frame. The Show Properties - Storage Pool subwindow is displayed in the information frame. 2. In the Storage Pool subwindow, choose Analyze Per Series. The Analyze Per Series - Storage Pool subwindow is displayed in the information frame (see Figure 5-12). 3.
Figure 5-13 Analyze per Series - Storage Pool Subwindow when Details is Selected Figure 5-14 Analyze per Series - Storage Pool Subwindow, When Show Information is Clicked 5-6 Viewing Storage Pool Usage Status for Each Storage Subsystem In the Analyze Per Subsystem - Storage Pool subwindow, you can view the storage pool usage status (total amount, allocated amount, unallocated amount, and usage rate) for each storage subsystem.
• Details: Displays information on storage pools of the groups under the user group to which the logged-in user belongs. Different from Summary in that you can view only the parent group information or the child group information rather than both at the same time. When Details is selected (see Figure 5-16), the User Group button used to specify a user group, the Plan button used to specify an allocation plan, and the Show Information button used to show information are displayed. 4.
Figure 5-16 Analyze per Subsystem - Storage Pool Subwindow when Details is Selected Figure 5-17 Analyze per Subsystem - Storage Pool Subwindow when the Show Information Button is Clicked 5-7 Viewing a List of Unallocated Volumes on a Host In the List Unallocated LDEVs - Storage Pool subwindow, you can view the volumes not allocated on the host.
2. In the Storage Pool subwindow, select List Unallocated LDEVs. In the information frame, the List Unallocated LDEVs - Storage Pool subwindow is displayed (see Figure 5-18). 3. In the List Unallocated LDEVs - Storage Pool subwindow, specify the following items according to the information about the volumes you want to view. • User Group: You can view the volumes available for the specified user group. Select a desired user group from the pull-down list.
Figure 5-19 List Unallocated LDEVs - Storage Pool Subwindow, When Show LDEVs is Clicked 5-8 Allocating a Volume to a Host from a List of Unallocated Volumes In the List Unallocated LDEVs - Storage Pool subwindow, from a list of volumes not allocated on the host, you can allocate volumes on a host. By selecting multiple volumes, you can also create a LUSE. The settings for the selected volume are performed using Device Manager functionality.
• User Group: You can view the volumes available for the specified user group. Select a desired user group from the pull-down list. • Plan: You can view the volumes applicable to the specified application plan. Select a desired allocation plan from the pull-down list. For details about allocation plans, see section 3-2 . NOTE: When the Details button is clicked, the detailed information about the allocation plan specified in Plan is displayed in another window.
Figure 5-21 List Unallocated LDEVs - Storage Pool Subwindow, When Show LDEVs is Clicked 5-9 Viewing a List of Allocated Volumes on a Host In the List Allocated LDEVs - Storage Pool subwindow, you can view the following information for each volume allocated on a host: size, subsystem name, host, type, array group, RAID level, emulation type, attributes, copy type, copy role, default controller, and external subsystem. A maximum of 16,384 volumes can be displayed in the list of volumes.
• Plan: You can view the volumes applicable to the specified application plan. Select a desired allocation plan from the pull-down list. For details about allocation plans, see section 3-2 . NOTE: When the Details button is clicked, the detailed information about the allocation plan specified in Plan is displayed in another window. • Size: You can view the volumes that meet the specified size. Enter the minimum and maximum values for the volume size, and select the units from the pull-down list.
NOTE: Information not reflecting the latest status might be displayed when the storage subsystem information is being updated. In such a case, a warning message is displayed, so wait a while and then reexecute the view operation.
NOTE: The Unallocate Storage button is displayed when any volume in the storage pool accessible for the logged-in user satisfies the specified conditions. This button is not displayed if the access privilege for the logged-in user is Guest or Local Guest. For details, see section 5-11 . 5. To further narrow down the volumes, use filtering. In the list of volumes, from the pull-down list for an item, select the value that corresponds to the desired volumes.
1. In the navigation frame, select Storage Pool. In the method frame, the Storage Pool subwindow is displayed. In the information frame, the Show Properties - Storage Pool subwindow is displayed. 2. In the Storage Pool subwindow, select List Allocated LDEVs. In the information frame, the List Allocated LDEVs - Storage Pool subwindow is displayed (see Figure 5-26). Figure 5-26 List Allocated LDEVs - Storage Pool Subwindow 3.
7. Click the Unallocate Storage button. The Device Manager’s Unallocated Storage - Confirmation dialog box is displayed. If multiple data paths are set, the Device Manager’s Select Paths dialog box is displayed. 8. In the Unallocate Storage - Confirmation dialog box, make sure the selected path, and then perform the release. For details about operation, see the HP StorageWorks Command View XP Advanced Edition Device Manager Web Client User Guide. 9.
Figure 5-28 Move LDEVs Dialog Box 3. Set the following items according to the volumes that you want to move. • User Group: You can view the volumes available for the specified user group. From the pull-down list, select a user group to which the volume that you want to move is related. • Plan: You can view the volumes applicable to the specified application plan. From the pull-down list, select an allocation plan for the volume that you want to move.
8. Click the OK button. The dialog box to confirm volume move is displayed. Click the OK button. A dialog box appears indicating processing is in progress, followed by a dialog box that shows the processing result. 9. Click the Close button. The Processing Result dialog box closes. Processing to move the volumes ends. The processing result can be confirmed from the List Unallocated LDEVs - Storage Pool subwindow. For details, see section 5-7 .
6 Viewing Host Information This chapter describes how to use Provisioning Manager to view a list of hosts, host detail information, and the list of file systems mounted on the host and to update host information.
• A path manager other than Dynamic Link Manager is also used However for an LU managed by a path manager other than Dynamic Link Manager, Provisioning Manager cannot acquire the information managed by the path manager, such as the number of paths and data paths. In HP-UX, however, Provisioning Manager can acquire information about LUs managed by PV-link.
Figure 6-1 Scope of LU Information Displayed When Using SDS/SVM Viewing Host Information 106
Figure 6-2 Scope of File System, Device File, and Logical Volume Information Displayed Using SDS/SVM 6-3 Viewing a List of Accessible Hosts When you log in to Provisioning Manager, Provisioning Manager’s navigation frame displays the hosts for which you have access permission. These hosts can be viewed from the List Objects-Hosts subwindow. To view a list of hosts, expand the tree in the navigation frame, and then choose Hosts. The method frame displays the Hosts subwindow.
NOTE: If the Provisioning Manager support functionality for Device Manager agent is not installed on a host, no information is displayed. If there is no file system on all the hosts that users can access, a No file system exists message is displayed. Figure 6-4 Hosts Subwindow and Analyze per File Systems - Hosts Subwindow 6-5 Viewing Detailed Host Information The Show Properties - host-name subwindow allows you to view detailed information about hosts. To view detailed information about a host: 1.
Figure 6-5 host-name Subwindow and Show Properties – host-name Subwindow 6-6 Updating Host Information The host-name subwindow enables you to update information about the hosts registered in Provisioning Manager. To update host information: 1. In the navigation frame, expand the tree, and then choose Hosts. The information frame displays the List Objects - Hosts subwindow. 2. In the List Objects - Hosts subwindow, select the host whose information you want to update.
7 Managing File Systems This chapter describes how to use Provisioning Manager to manage file systems.
1. In the navigation frame, expand the Hosts tree. A list is displayed of all hosts that are within the access scope of the user. 2. Expand the tree of the desired host. The navigation frame displays File Systems and Device Files. 3. Choose File Systems. The method frame displays the File Systems subwindow, and the information frame displays the List Objects - File Systems subwindow (see Figure 7-1). 4. In the List Objects - File Systems subwindow, view information about the file systems.
• HP-UX: Logical Volume Manager The following file system types are supported for use by the host: • Solaris™: UFS, VERITAS™ File System 3.5, or VERITAS™ File System 4.0 • AIX®: JFS • Windows®: NTFS • Linux: ext2 or ext3 • HP-UX: VERITAS™ File System 3.
1. In the navigation frame, expand the Hosts tree. A list is displayed of all hosts that are within the access scope of the user. 2. Expand the tree of the desired host. The navigation frame displays File Systems and Device Files. 3. Choose File Systems. The File Systems subwindow is displayed. 4. Select Add File System from the File Systems subwindow. The Add File System - Step 1 of 3 dialog box is displayed.
3. If you select a volume that is usable under certain conditions, a dialog box is displayed that indicates the conditions and asks you to confirm that you are sure you want to select this volume. CAUTION: If you use a volume usable under certain conditions, some data may be lost or other hosts may lose the access privileges to the volume. Before using such a volume, check the warning message and make sure that there are no problems. 4.
Figure 7-4 Add File System - Step 3 of 3 (Summary of Changes) The procedure for confirming the settings is described below. The device file might have to be recognized in the middle of operations. The operation related to recognizing the device file differs depending on the system components.
Also, if you click the button without selecting the check box, an error occurs. 3. Click the Confirm button. If a message is displayed during the add file system process, the Add File System - Suspended dialog box is displayed. A message is displayed indicating that the device file needs to be identified. 4. Manually check the device files as described in the manuals for the hardware and software that are being used. 5.
NOTE: The device file types (logical volumes, volume groups, HDLM devices, and raw devices) are displayed as follows: • • • • Logical volumes: LogicalVolume Volume groups: VolumeGroup HDLM devices: RawDevice (HDLM) or RawDevice (HDLM, Partitioned) Raw devices: RawDevice or RawDevice (Partitioned) Figure 7-5 MountPoint and Show Properties - MountPoint Subwindows 7-5 Expanding a File System A file system can be expanded by using the Expand File System dialog boxes, which include Step 1 of 2 (Select Volume)
2. • The volume is being used as an S-VOL or SP-VOL for Business Copy XP. • The volume is being used as a V-VOL or POOL for Snapshot XP. • The Auto Lun XP attribute has been set for the volume. • The volume is being used as an on-demand device. • The Read/Write permissions have not been set in the LUN Security XP Extension function. • The volume emulation type is none of the following: OPEN-3, OPEN-8, OPEN-9, OPEN-K, OPEN-E, OPEN-L, OPEN-M, OPEN-V • The volume size is less than 512 MB.
To select the volume (step 1 of 2 in Expand File System): 1. Depending on the contents you want to display, set the following item on the Expand File System – Step 1 of 2 dialog box (refer to Figure 7-6): Displayed Volumes: Select the volume display range. • Usable Volumes: Of the volumes that the host can use with LUN security, a list is displayed of the usable volumes and volumes usable under certain conditions.
The procedure for confirming the setting selections is described below. The device file might have to be recognized in the middle of operations. The operation related to recognizing the device file differs depending on the system components. For details on the required operation, see section 11-2 , and then see the manuals for the hardware and software that are being used (HBA, volume manager, operating system manual, etc.).
6. In the navigation frame, expand the tree, and then choose Transaction Logs. The information frame displays the List Objects - Transaction Logs subwindow. 7. Check the contents of the operation where the Resume button is displayed in the Action field, and recognize the desired operation. The Resume button is displayed for the processing that was interrupted. Check the contents of the operation where the Resume button is displayed, and make sure that the operation is appropriate.
information, and then retry the operation from the beginning. If you click the OK button without selecting the checkbox, an error occurs. Check the warning message and then select the checkbox. 7. Click OK. A message is displayed indicating that the delete file system process is underway. IMPORTANT: To check the execution status of the processing, check the transaction logs. For details on transaction logs, see section 10-2 .
7. Click the OK button. If a message is displayed during the delete file system process, the Delete File System - Suspended dialog box is displayed. When the process has been completed, the processing result is displayed in the Delete File System - Result dialog box. 8. Release the allocated volume from the List Allocated LDEVs - Storage Pool subwindow. 9.
Figure 7-9 Show Data Path Dialog Box (File System) Managing File Systems 124
8 Managing Device Files This chapter explains how to use Provisioning Manager to manage device files.
2. Expand the tree of the desired host. The navigation frame displays File Systems and Device Files. 3. Choose Device Files. The method frame displays the Device Files subwindow, and the information frame displays the List Objects - Device Files subwindow (see Figure 8-1). 4. View information about the device files in the List Objects - Device Files subwindow. General Information displays the total size of the device files. Object List displays device file information for each device file path name.
• Linux: Logical Volume Manager • HP-UX: Logical Volume Manager To add a device file, perform the following steps: 1. Select Volume (see section 8-3-1 ). Select a volume from the candidates. All volumes that you can use are displayed. Select an appropriate volume. CAUTION: A volume cannot be used to add a device file when any of the following conditions hold: • The volume manager is using the volume on a host where the Device Manager agent has been installed.
Figure 8-2 Add Device File - Step 1 of 3 (Select Volume) To select the volume (step 1 of 3 in Add Device File): 1. Depending on the contents you want to display, set the following item on the Add Device File – Step 1 of 3 dialog box (refer to Figure 8-2): Displayed Volumes: Select the volume display range. • Usable Volumes: Of the volumes that the host can use with LUN security, a list is displayed of the usable volumes and volumes usable under certain conditions.
Figure 8-3 Add Device File - Step 2 of 3 (Specify Parameters) To set the parameters (step 2 of 3 in Add Device File): 1. Set the Volume Manager. Select the volume manager from a pull-down list. 2. After completing the settings, click the Next button. The Add Device File - Step 3 of 3 dialog box is displayed. The next section shows this dialog box and describes the settings to be specified at this step. 8-3-3 Confirming the Settings In this step, you confirm the contents of your settings.
When the processing has been completed, the Add Device File - Result dialog box is displayed, displaying the processing results. 4. In the Add Device File - Result dialog box, check the displayed information. 5. If there is no problem, click the Close button. The window closes. The add device file process has been completed. To confirm the settings when the device file needs to be identified on the host side: 1. Check the contents of the Add Device File - Step 3 of 3 dialog box (refer to Figure 8-4).
NOTE: When a Volume ID is selected from the Volume Information table, you can view the detailed information about the volume. The Device Manager’s Detailed Information - LDEV Number dialog box is displayed. For details about the screen items, see Help for each window. When you click the Show Data Path button in the Volume Information table, a dialog box is displayed to show the following path information: HBA WWN, storage subsystem port, and storage subsystem volume.
deleted. If the host information is not up to date, cancel processing, update the host information, and then perform the operation from the start. If OK is clicked without selecting a checkbox, an error occurs. Check the warning message and then select the checkbox. 7. Click the OK button. A message is displayed indicating that device file deletion processing is underway. IMPORTANT: To check the execution status of the processing, check the transaction logs.
9. If necessary, manually make the system recognize that the volume allocation has been released as described in the manuals for the hardware and software that are being used. 10. In the navigation frame, expand the Device Files tree directly under Hosts, and make sure that the desired device file is not displayed. 11. From the navigation frame, expand tree, and select Transaction Logs. In the information frame, the List Objects - Transaction Logs subwindow is displayed. 12.
9 Managing Provisioning Plans This chapter explains how to manage provisioning (allocation) plans. For information on how to create a provisioning plan, see section 3-6-1 . • About Managing Provisioning Plans (section 9-1 ) • Viewing an allocation plan (section 9-2 ) • Setting an allocation plan to be public or private (section 9-3 ) • Editing an allocation plan (section 9-4 ) 9-1 About Managing Provisioning Plans You can define a provisioning plan as a way to locate volumes in a storage pool.
9-2 Viewing an Allocation Plan In the Show Properties - PlanName subwindow, you can view an allocation plan. To view an allocation plan: 1. From the navigation frame, click Provisioning Plans. 2. Click Allocation Plans, located in the navigation frame immediately below Provisioning Plans. The method frame displays the Allocation Plans subwindow. The information frame displays the List Objects Allocation Plans subwindow (see Figure 9-1). 3.
CAUTION: • • A user with guest or local guest access permission cannot modify the security level.
Figure 9-3 Edit Allocation Plan - PlanName Dialog Box To edit an existing allocation plan and save it under a different name: 1. Create an allocation plan by executing steps 1-5 for editing an allocation plan. 2. When you finish specifying all the settings you need for the new allocation plan, click the Save As button. The Save As - PlanName dialog box is displayed (see Figure 9-4). 3. Enter a name for the new allocation plan. 4. Click the OK button. The Edit Allocation Plan dialog box is displayed.
10 Viewing Transaction Logs This chapter describes how to view transaction logs for Provisioning Manager. • General comments on viewing transaction logs (section 10-1 ) • Viewing transaction logs (section 10-2 ) • Resuming operation after processing is interrupted (section 10-3 ) 10-1 About Viewing Transaction Logs HP StorageWorks XP Provisioning Manager records the operations of users who logged in to Provisioning Manager.
5. Check the contents of the operations. For operations in progress, you can check how far the processing has completed. For failed or interrupted operations, you can check which process failed or was interrupted.
3. In the List Objects - Transaction Logs subwindow, click the Resume button. The interrupted processing resumes, and a window that indicates the progress is displayed.
11 Troubleshooting This chapter lists the error messages that may be issued when problems occur while you are using Provisioning Manager. It also explains the actions you should take in response to the error messages.
3. View the detailed information in the operation log, and then check the item in which the failure occurred and also check the error message. 4. From the error message and the product status, check the error cause and the status of the setup item in which the failure occurred. Remove the error cause if necessary. 5. Manually cancel any setup operation that was interrupted by the error. 6. In the Details - Transaction Logs dialog box, check the items that have been executed. 7.
Table 11-2 Troubleshooting Information: Provisioning Manager Functions Problem Cause Recommended Action A file that is 2 GB or larger cannot be created. The current setting does not allow the use of 2 GB or larger files. If Solaris™ or HP-UX VERITAS™ File System is being used, a setting for using files that are 2 GB or larger is required.
Table 11-4 Troubleshooting Information: Host Information Collection Problem Cause Recommended Action The message “An error occurred in the Device Manager agent. (Device-Manager-Agent-error-message).” or “An error was detected in communication processing with the Device Manager agent. (errormessage)” is displayed in the GUI window. An error may have occurred • in the communication area of the Device Manager agent or Provisioning Manager server.
Table 11-5 Troubleshooting Information: Host Information Display (continues on the next page) Problem Cause Recommended Action Operations that were normally terminated on Provisioning Manager, such as file system and device file creation, are not reflected in the GUI window. A mismatch may have occurred between the host information held by the server and the host status. If mismatch has occurred, eliminate the information mismatch by updating the host from the Host Name subwindow.
Table 11-5 Troubleshooting Information: Host Information Display (continues on the next page) Problem Cause Recommended Action An error occurs when performing host refresh operations on a host. The hldutil command executed Change the during the host refresh operations timed server.util.processTimeOut out. value in the installationdirectory/agent/config/server .properties file as required.
Table 11-5 Troubleshooting Information: Host Information Display (continues on the next page) Problem Cause Recommended Action After the host name of the host machine The host name of the host machine and Carry out the following operations: the host management information of is changed, both the host name that 1 In the host management window of existed from before the change and the Device Manager do not match.
Table 11-5 Troubleshooting Information: Host Information Display (continues on the next page) Problem Cause The name of a volume group, logical The name of a volume group, logical volume, or mount point displayed in GUI volume, or mount point exceeds the is different from the actual name. maximum number of characters that can be displayed in Provisioning Manager. (This problem will not occur when the volume group, logical volume, and mount point are created by using Provisioning Manager.
Table 11-6 Troubleshooting Information: General Host Settings (continues on the following pages) Problem Cause Recommended Action A timeout might have occurred for the Device Manager agent due to a command such as an OS command taking a long time to execute. View the Device Manager agent error log (error.log) to check whether a command execution error has occurred. Also, view the information output in the log to check whether a timeout (java IllegalStateException) has occurred.
Table 11-6 Troubleshooting Information: General Host Settings (continues on the following pages) Problem Cause Recommended Action The setup confirmation window shows an error for a setup operation and setup cannot be executed. The volume specified in the confirmation window was being used by another user before the setup operation started. Select a different volume in the setup window.
Table 11-6 Troubleshooting Information: General Host Settings (continues on the following pages) Problem Cause Recommended Action ® It takes a period of time in the range from a few minutes to 10 minutes or more when a small file system or a small device file is created or expanded. You do not need to take any action. If the host OS is Windows , the diskpart command script is executed several times or 10 times or more. Each time this script is executed, it takes 10 seconds or more.
The size of a file system or device file added using the host setup facility is displayed as smaller than the logical unit size. When you create a file system on a ® Windows host, the message dialog box “ The disk in drive X is not formatted. Do you want to format it now? “ is displayed ® in the Windows window. An error occurs during file system or device file creation.
The number of volume groups that can be created on a system was exceeded. See the documentation for the OS and Volume Manager and check the number of volume groups that can be created in the system. If the created number has reached the maximum, no more volume groups can be created. Delete any unnecessary volume groups (including group files in HP-UX), and then re-execute the addition operation.
Table 11-8 Troubleshooting Information: Host Settings Related to Volume Expansion (continues on the next page) Problem Cause Recommended Action ® An error occurs during file system expansion. On a Windows or Linux host, an attempt was made to expand a file system that was mounted at more than one mount point. None, because this is a result of Provisioning Manager specifications. Provisioning Manager cannot be used to expand a file system that is mounted at more than one mount point.
Table 11-8 Troubleshooting Information: Host Settings Related to Volume Expansion (continues on the next page) Problem Cause Recommended Action The host OS is Linux or HP-UX, and the file system is being used by a process. Use a command such as fuser to determine whether a process is using the file system to be expanded. Once the file system has been made to attain a state in which no one is using it, manually expand the file system using a method such as an OS command. Then, update the host.
Table 11-8 Troubleshooting Information: Host Settings Related to Volume Expansion (continues on the next page) Problem Cause Recommended Action On a Linux host, when an error occurs during expansion of a file system, the file system is not displayed in the GUI window after the host information is updated. On a Linux host, when a file system is being expanded, the file system is initially unmounted. Then, before it is remounted, the following commands are automatically executed.
Table 11-9 Troubleshooting Information: Host Settings Related to Volume Deletion Problem Cause Recommended Action On a Linux host, the file system or device file contains two or more partitions. This is a result of Provisioning Manager specifications. Provisioning Manager cannot be used to delete this type of file system or device file. It can be used to delete a file system or device file that contains no or only one partition.
Table 11-9 Troubleshooting Information: Host Settings Related to Volume Deletion Problem Cause Recommended Action Possible causes are as follows: The file system to be deleted is unmounted. • The volume group containing the device file to be deleted is deactivated. • The file system or device file to be deleted does not exist or has already been deleted. The host information might not be up to date. Check the status of the file system to be deleted on the corresponding hosts.
Table 11-9 Troubleshooting Information: Host Settings Related to Volume Deletion Problem Cause Recommended Action When a file system is deleted, even though an error occurs, the volume that was used for delete operations is displayed in the List Objects - File System subwindow. Multiple users have deleted the same file system concurrently. Deletion of the file system finishes successfully. No action is required.
Table 11-12 Troubleshooting Information: Transaction Log Status (continues on the next pages) Problem Cause Action required adapter that requires manual setup and restart for recognizing the raw device. • You are trying to add or expand a file system or device file in a Solaris™ host that is using both Dynamic Link Manager and VERITAS™ Volume Manager. To add or expand a file system or device file when the host OS is Linux, raw device recognition must be performed through manual settings.
Table 11-12 Troubleshooting Information: Transaction Log Status (continues on the next pages) Problem Cause Action required device file when the host OS is Linux, raw device recognition must be released through manual settings.
11-3-1 Checking the Device Manager Agent Error Log For message text of the error message such as KARF15000-E indicating that an error occurred in the Device Manager agent, a message ID is not attached. In such a case, you need to view the Device Manager agent error log (error.log) to identify the message ID. In accordance with a prefix of the identified message ID, check the error cause and troubleshooting by viewing one of the following: • When the prefix is KARF: See section 11-6 . The error log (error.
For details on the cvxpaegetlogs command of TIA, see the HP StorageWorks Command View XP Advanced Edition Device Manager Server Installation and Configuration Guide.
AIX® or Linux host OS: # /usr/HDVM/agent/bin/TIC.sh TIC command format ® Windows host OS: TIC.bat [-outdir target-location-of-resultDir-directory [-f]] ® Solaris™, AIX , Linux, or HP-UX host OS: TIC.sh [-outdir target-location-of-resultDir-directory [-f]] • Arguments -outdir target-location-of-resultDir-directory Specifies the location of the resultDir directory for storing the acquired error information. Specify the relative path from the execution directory, or the absolute path.
• Arguments /datadir (-datadir) Specifies the absolute path of the name of the directory into which the host information is to be collected. If this argument is omitted, the host information is collected into the current directory.
IMPORTANT: The character strings KAIC, KAIE, KAPM, and KDJE indicate messages issued by Device Manager. • • • pp: A package serial number that indicates a message type (see Table 11-13). mmm: A message number. z: A subscript indicating the message type and message importance (see Table 11-14 Message Type ). Message text This is the message that is output by Provisioning Manager. When an actual message is output, applicable character strings are displayed in place of any italicized text.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code Error Message Description and Recommended Action KARF01003-E The version does not match the version (Device-Manager-version) of Device Manager. The Provisioning Manager server cannot start. KARF01004-I The Provisioning Manager server has stopped. An error occurred while the Provisioning Manager server was being stopped. The Provisioning Manager server could not stop.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code KARF01509-I KARF01510-I Error Message Description and Recommended Action Deletion of the allocation plan has started. parameter Deletion of the allocation plan has finished. Cause: n/a Action: n/a Cause: n/a Action: n/a Cause: The cause depends on the error that occurred immediately before this one. Action: Take action appropriate for the message that was output immediately before this one.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code Error Message Description and Recommended Action KARF01544-E An error occurred in the file system creation operation. KARF01545-I Expansion of the file system has started. parameter Expansion of the file system has finished. return-value An error occurred during expansion of the file system. Cause: The cause depends on the error that occurred immediately before this one.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code Error Message Description and Recommended Action logical volume. Provisioning Manager server. Action: Contact the Support Center. Cause: The host-setting operation is not possible for the specified object. Action: If this problem persists, contact the Support Center. Cause: An internal error occurred. Action: Contact the Support Center.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code Error Message Description and Recommended Action KARF03320-E The specified host-setting operation does not exist or has already finished. (operation ID = operation-ID) KARF03321-E The specified host-setting operation is not suspended, or an instruction to resume it was already received.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code Error Message Description and Recommended Action = allowable-length, invalid item = setting-item) setting. Action: Correct the parameter, and then retry the operation. Cause: An attempt was made to create or update a plan with an invalid character specified in a setting. Action: Correct the parameter, and then retry the operation. Cause: An attempt to load the property file has failed.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code Error Message Description and Recommended Action KARF10013-E The newest information cannot be acquired because the host is currently being refreshed. Information classification: informationclassification KARF10015-E An internal error occurred while user group information was being acquired. An error occurred while the Common Component database was being updated.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code Error Message Description and Recommended Action migrated because the migration-source user group (user-group-name) does not have permission to configure a volume that is in a LUSE configuration. An attempt was made to migrate a volume that is in a LUSE configuration, but permission for the volume was lacking. Action No action is required. Cause Access permission is insufficient for the specified volume.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code KARF10224-W KARF10225-W Error Message Description and Recommended Action The LUN security settings do not match that of the target file system. Make sure that mismatching LUN security settings will not cause problems. The RAID level does not match that of the target file system. Make sure that mismatching RAID levels will not cause problems.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code Error Message KARF12004-E The license key to be entered does not exist in the license key file, or there is no license key file. KARF12005-W An attempt to delete a temporary file has failed. KARF12006-E An attempt to execute license management has failed. KARF15000-E An error occurred in Device Manager Agent. (Device-Manager-Agent-error-message) KARF15001-E An internal server error occurred.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code Error Message KARF15304-E The specified logical volume logical-volumename does not exist. KARF15305-E The specified logical volume logical-volumename is already being used. KARF15306-E The specified volume group volume-groupname does not exist. KARF15307-E The specified volume group volume-groupname is already being used. KARF15308-E The specified device file device-file-name does not exist.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code Error Message Description and Recommended Action KARF15500-E User information for the logged-in user was not found. (user name = user-ID) KARF15600-E The specified object does not exist in the database, or the user does not have access permissions. KARF15601-E A volume that constitutes the specified file system was not found. KARF15602-E The setting operation cannot be executed for the specified host.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code Error Message KARF17002-E The database manager operation is invalid. KARF17003-E An error occurred during a database query. KARF17004-E An error occurred during a database insert. KARF17005-E An error occurred during deletion of a database. KARF17006-I Database-update SQL was executed. (SQL) KARF17007-I Database-query SQL was executed.
Table 11-15 Provisioning Manager Server Messages (continues on the following pages) Error Code Error Message KARF18100-E A required item is missing from the Device Manager Agent response. (item) KARF20000-E An attempt to communicate with the Provisioning Manager server has failed. KARF20001-E The URL is invalid. (URL = URL) KARF20002-E An internal error occurred. KARF20003-E The message with the following message ID cannot be displayed, due to an internal error.
Table 11-16 Provisioning Manager GUI Messages (continues on the following pages) Error Code KARF30702-I KARF30703-E KARF30801-I Error Message Description and Recommended Action start. Source:source-group Destination:destgroup LDEVs:LDEV-IDs The LDEV was successfully moved between pools. An attempt to move LDEVs between pools has failed. Action: n/a - KARF30802-I Addition of the file system will now start.(filesystem-parameter) The file system was successfully added.
Table 11-16 Provisioning Manager GUI Messages (continues on the following pages) Error Code Error Message Description and Recommended Action KARF30823-I Deletion of the device file will now resume. KARF30824-E An attempt to delete a device file has failed. KARF30825-I KARF30829-E An attempt to delete a device file was suspended. An error occurred in the GUI servlet. KARF30830-E An error occurred in the GUI servlet. KARF31051-I Host information will now be refreshed.
Table 11-16 Provisioning Manager GUI Messages (continues on the following pages) Error Code KARF40001-E KARF40002-E KARF40003-E Error Message Description and Recommended Action An error occurred in the GUI servlet. (exception) An error occurred in the GUI servlet. (exception) An error occurred in the GUI servlet. Cause: An error occurred in the GUI servlet. Action: Contact the Support Center. Cause: An error occurred in the GUI servlet. Action: Contact the Support Center.
Table 11-16 Provisioning Manager GUI Messages (continues on the following pages) Error Code Error Message KARF40410-I Register the license. KARF40411W The temporary key will expire in n days on end-date. KARF40412-E The temporary key expired on end-date. KARF40413W The emergency key will expire in n days on end-date. KARF40414-E The emergency key expired on end-date. KARF40415-E An attempt to acquire license information has failed.
Table 11-16 Provisioning Manager GUI Messages (continues on the following pages) Error Code Error Message Description and Recommended Action KARF40803-E The host information might not be up to date, or there might be a problem with the software configuration of the host. KARF40804-E The host information might not be up to date. Refresh the host, wait for the refresh to complete, and then retry the operation. KARF40805-E This file system cannot be expanded.
Table 11-16 Provisioning Manager GUI Messages (continues on the following pages) Error Code KARF40822W KARF40823W KARF40824W Error Message Host: "host",Last updated: "last-updated-time" If the host information is not up to date, an unintended resource might be deleted. Make sure that the host information is up to date, and then execute processing. If it is not up to date, cancel processing, refresh the host information, and then re-execute deletion of the device file.
Table 11-16 Provisioning Manager GUI Messages (continues on the following pages) Error Code Error Message Description and Recommended Action KARF50701-E LDEVs belonging to different subsystems are selected. KARF50702-E No LDEV is selected. KARF50703-I Do you want to move these LDEVs? KARF50704-E The same user group is specified as both the move-source and move-destination storage pool. No plan is selected. Cause: LDEVs belonging to different subsystems are selected in the LDEV list.
Table 11-16 Provisioning Manager GUI Messages (continues on the following pages) Error Code Error Message KARF51106-E Enter a description that uses no more than 255 characters. KARF51113-I Are you sure you want to change the allocation plan "plan-name " to a private plan?If you are sure, click [OK]. Are you sure you want to change the allocation plan "plan-name " to a public plan?If you are sure, click [OK].
Table 11-17 Provisioning Manager Agent Messages (continues on the following pages) Error Code Error Message KARF62006-E A mount point exists on the specified drive. KARF62007-E The specified device file is already being used. KARF62008-E A mount point exists in the specified mount point. KARF62010-E The specified extension size is invalid. KARF62011-E The specified logical volume does not exist. KARF62012-E The specified mount point is already in use.
Table 11-17 Provisioning Manager Agent Messages (continues on the following pages) Error Code Error Message KARF62023-E The logical volume name is invalid. KARF62024-E A process using the specified file system exists. KARF62025-E 2 or more logical volumes are on the specified disk. KARF62026-E A file system that has multiple device files mounted cannot be modified or deleted. KARF62027-E The specified mount point has a snapshot. KARF62028-E The specified logical volume is a snapshot.
Table 11-17 Provisioning Manager Agent Messages (continues on the following pages) Error Code Error Message KARF64001-E A logical volume already exists on the specified physical volume. KARF64003-E Logical volumes or physical volumes exist in the specified volume group. KARF64004-E A mount point exists on the specified drive. KARF64005-I KARF64006-E The logical volume name will be handled as '*'. The physical volume name is invalid. KARF64007-E The specified logical volume already exists.
Table 11-17 Provisioning Manager Agent Messages (continues on the following pages) Error Code Error Message KARF64014-E A logical volume cannot be created on the specified device file. KARF64015-E The information relating to the volume group cannot be acquired. KARF64016-E The character * cannot be used. KARF64017-W Importing to the specified disk was unnecessary. KARF64018-W The specified disk was already Basic. KARF64019-W The specified disk was already Dynamic.
Table 11-17 Provisioning Manager Agent Messages (continues on the following pages) Error Code Error Message KARF64027-E The specified logical volume has a snapshot. KARF64028-E The specified logical volume is a snapshot. KARF64029-E A partition cannot be specified for the device file. KARF64030-I A file or directory that has the same name as the specified name exists under /dev.
Table 11-17 Provisioning Manager Agent Messages (continues on the following pages) Error Code Error Message Description and Recommended Action the system limit. Action: Delete any unnecessary group files, and then retry the operation. Cause: Provisioning Manager cannot be used to operate a logical volume that is being used by the cluster software. Action: Manually perform the following procedure, and then retry the operation: 1 Edit the cluster configuration file. 2 Execute cmapplyconf.
Table 11-17 Provisioning Manager Agent Messages (continues on the following pages) Error Code KARF65012-I Error Message KARF65013-E The cfgmgr command will be executed number of command execution times. The specified raw device still exists. KARF65014-E An unnecessary device file exists. KARF66001-E VolumeManagerAdmin execution error. KARF66002-E FileSystemAdmin execution error. KARF66003-E RawDeviceAdmin execution error. KARF66004-E The specified volume manager type is not supported.
Table 11-17 Provisioning Manager Agent Messages (continues on the following pages) Error Code Error Message Description and Recommended Action KARF67002-E The specified physical volume does not exist. KARF70000-E Internal processing error. KARF70001-E Exception occurred = class name KARF70002-E The specified parameter is invalid. KARF70003-I KARF70004-E Execution command = command, startTime = command start time. Command execution error = command KARF70005-E Program Product is not installed.
Table 11-17 Provisioning Manager Agent Messages (continues on the following pages) Error Code Error Message KARF70015-E The specified entry already exists in Definition file. KARF70016-E The specified mount point does not exist in Definition file. KARF70017-E Definition file cannot be backed up. KARF70018-E Definition file cannot be read. KARF70019-E The entry cannot be removed from Definition file. KARF70020-E Definition file cannot be updated. KARF70021-E The system environment is invalid.
Table 11-18 Messages Common to Provisioning Manager Components Error Code KARF99000-W KARF99001-W Error Message Description and Recommended Action The value specified for logger.MaxBackupIndex in logger.properties is invalid, so the default value will be set and used for startup. The value specified for logger.MaxFileSize in logger.properties is invalid, so the default value will be set and used for startup. Cause: An invalid value is set for the setting logger.
Glossary array group A sequential storage area that has a RAID structure. An array group contains multiple LDEVs. An array group contains user data and parity information, which ensures user data integrity in the event of a hard disk drive failure within the array group. Business Copy XP Functionality that creates a volume replica in the same storage subsystem. CA-XP(Jrnl) (Continuous Access XP Journal): A function for creating replica volumes, such as Business Copy XP and Continuous Access XP.
LUN (logical unit number): A number for identifying a logical unit (LU). LUN security Functionality designed to limit the hosts that are able to access LUs within a storage subsystem. Only hosts (WWNs) for which this function has been used to set a port in a storage subsystem can access the LUs on the path routed through this port. LUSE (LU size expansion): An LU composed of multiple LDEVs. You can create a LUSE on StorageWorks XP12000/XP10000, StorageWorks XP1024/XP128, StorageWorks XP512/XP48.
Table G.
Index Expanding: file system, 117 A accessible hosts, viewing list of, 107 Adding: file system, 111 AIX OS: and Dynamic Link Manager, 66; big vg Format Volume Group, 65; expansion/deletion restrictions, 62; file system check at startup, 65; file system/device file restrictions, 63; improving performance, 65; mount point directory, deleting, 66; unit of volume management, 65 AIX OS, RAID functionality with, 65 allocated volumes on host, viewing list of, 96 allocation plan: Adding, 51; Deleting, 51; Editing,
R RAID functionality with, Solaris OS, 61 RAID functions: caution, 71 S SDS/SVM, 105 secondary primary volume, 200 secondary volume, 200 settings, confirming file system, 114 setup, troubleshooting during, 141 shared volume group, AIX OS, 64 single sign-on, 26 storage group perspectives: C_Group01, 81 storage logical partition, 200 storage pool: viewing overview, 83 Storage pool application example, 37 storage pool management: unit change for, 21 storage pool perspectives: P_Group, 80 storage pool usage s
