Installation and User Guide HP StorageWorks Command View SDM Version 1.
Notice Trademark Information (C) Copyright 2003-2005 Hewlett-Packard Development Company, L.P., all rights reserved. Red Hat is a registered trademark of Red Hat Co. C.A. UniCenter TNG is a registered trademark of Computer Associates International, Inc. 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.
Revision History September 2001 Change Added installation configuration drawings. Added HP-UX 11.20 to native supported operating systems. Page 27 22, 26 Changed procedure for implementing browser security. 82 Added command line task summary table. 96 January 2002 Change Updated WWN information to indicate that either the port WWN or the node WNN can be used to identify a host. Page Multiple Added MPE/iX, Tru64, and OpenVMS to non-native operating system support.
July 2002 Change Page Updated contents to reflect that a hardcopy of the Command View SDM User Guide is no longer included. 16 Corrected paths to HA_DIAL_START and HA_DIAL_STOP. 55 Added host port behavior table management to the Command View VA GUI. 93 Added host port (H1, H2) and disk enclosure port (J1, J2) subcomponent parameters to the FRU Location Identifier values. 100 Added armdiag command used for advanced troubleshooting. 107 Added new functionality to the armdsp -p option for HP15.
November 2002 Change Page Added more information on installing on OpenView SAM. 36 Added information on renaming host 57 Added information on VA 7410 firmware version numbering. 115 Added -Core option to armdiag command. 107 Added DISK-PORTS metrics to performance metrics table. 151 Added information on using the armrecover command 189 Added armshell command 195 January 2003 Change Added VA 7110. Removed Enterprise Intergrations as a stand-alone product.
Change Added information on HP StorageWorks SMI-S VA Page 63 July 2004 Change Page Updated secadmin command 201 Updated to Free permenent license for Command View 15 Updated OS Support Updated armdsp command various 119 Removed Appendix A Updated HP OpenView Storage Area Manager info Updated SMI-S information 83 various August 2004 Change Page Added HP-UX 11.
Change Page Updated Figure 1 27 Removed addcliuser, licAdmin, and licUtil commands 96 Updated secadmin command 201 7
contents 1 Product Description 15 HP StorageWorks Command View SDM Software 16 The Software Components 16 Event Reporting Software 17 HP StorageWorks SMI-S for Command View VA disk arrays 19 HP Modular Storage Software Products 20 Operating System Support (Native) 22 Non-Native Supported Operating Systems 22 Sources of Support Information 23 Technical Support and Manual Updates 24 2 Installing Command View SDM 25 Upgrading to a Newer Version of Command View SDM 25 Command View SDM Installation Confi
Saving and Restoring Array Configuration Information 48 Restoring Array Configuration Information 49 Configuring Command View SDM 50 Setting up Remote Client Access 50 Configuring the Command View SDM Web Server 51 Enabling EMS Monitoring 52 Setting the System Display Variable 52 Verifying the Installation 54 Starting/Stopping HostAgent and OpenDIAL 55 Creating LUN 0 56 Adding a New Host to the Management Configuration 57 Renaming a Host 57 Details About the Command View SDM Installation Process 59 Command
SSL Support 75 Port Occupation 75 Viewing Certificates Using the Keytool Command 76 Viewing All Certificates Using the Keytool Command 77 Troubleshooting 77 3 Using the Graphical User Interface 79 The GUI Components 79 Running the Command View SDM GUI 80 User Security 80 Enabling User Security 80 Running the Launcher from the Windows Icon 80 Running the Launcher Using a Command Line 81 Running the Management GUI Directly from a Command Line 81 Running the Launcher from a Web Browser 82 Running the Manag
armcopy 105 armdiag 107 armdiscover 110 armdownload 113 armdsp 119 armfeature 130 armfmt 132 armhost 133 armlog 137 armmgr 139 armperf 148 armrbld 186 armrecover 188 armsecure 191 armshell 195 armtopology 198 secadmin 201 Examples 202 5 Command View SDM User Interface 203 Starting the Command View SDM CVUI 204 CVUI Example 204 CVUI Menu Map 206 6 Array Logs 209 Managing the Size of the Log Files 211 Log Commands 212 logprn 213 logdel 216 armlog 218 About Log Files 219 Directory Structure 219 Perform
7 Solving Problems 223 Contents 13
Contents
Product Description 1 HP StorageWorks Command View SDM is designed to provide storage management for the HP StorageWorks Virtual Array products. Command View SDM provides simple yet sophisticated device management tools for the array. Some of the features and benefits offered by Command View SDM include: ■ Lets you manage an unlimited number of HP virtual arrays from a graphical user interface (GUI), command line user interface (CLUI), or web browser.
HP StorageWorks Command View SDM Software The Command View SDM product includes the HP StorageWorks Command View SDM CD. The Software Components The Command View SDM CD-ROM contains all the software required to manage the HP StorageWorks Virtual Array products. The software components include: ■ Installers - provided for Windows (2000 and 2003), HP-UX, and Linux Red Hat.
■ README file - contains updated support and installation information for your convenience. Event Reporting Software The internal operation of the array is continually monitored and any significant events are recorded. Command View SDM internal event reporting software retrieves event information from the array and reports it to the user.
■ HP-UX — — — — — — — — — Syslog HP EMS HP OpenView NNM (SNMP) HP Top Tools (SNMP) CA Unicenter TNG (SNMP) BMC Patrol (SNMP) Tivoli (SNMP) HP Systems Insight Manager 4.2 (Nimbus) Instant Support Enterprise Edition Events are categorized as Information, Minor Warning, Major Warning, Serious, and Critical. These events also provide descriptions useful for troubleshooting. A current list of events is available from the HP web site: http://docs.hp.com/hpux/content/hardware/ems/RemoteMonitor.
Hewlett Packard supports the new storage standard called the Storage Management Initiative Specification (SMI-S). Hewlett Packard is a contributing member to the Storage Networking Industry Association (SNIA), which is a technical organization chartered to build seamless multi-vendor storage management networks. The SMI-S specification standardizes the interface for SAN management, device control architectures and associated interfaces.
HP Modular Storage Software Products A full line of complementary software products are available to expand the capability of the Command View SDM software. These optional products are listed in the following table. For the most up-to-date information about Modular Storage Software products, visit the HP web site. Table 1 Command View SDM Modular Storage Software Products SOFTWARE PRODUCTS Command View SDM Enables array configuration and management.
Auto Path VA for HP-UX Product Description Enables I/O path fail-over in HP-UX environments with the benefit of I/O load balancing in both failed and non-failed states. — Software Package and 1 Host LTU* (T1060A) — 1 Host Upgrade LTU (T1061A) — 5 Host Upgrade LTU (T1062A) Auto Path VA for Linux Enables I/O path fail-over in Linux environments with the benefit of I/O load balancing in both failed and non-failed states.
Operating System Support (Native) The Command View SDM software is supported on the following operating systems. Because hosts running these operating systems can both access the array and also manage the array using Command View SDM, these are referred to as “native” operating systems. ■ HP-UX* ■ Windows 2000** ■ Windows Server*** ■ Red Hat Linux Advanced Server**** *Command View SDM provides support for HP-UX 11.00, 11.11 (11i 32-bit), 11.23 (V2, Itanium), 11.23 PI on IA, and 11.
■ Novell NetWare ■ HP-UX 10.20 Note Command View SDM provides support for HP-UX 11.23 (IA-64) in a non-HP OpenView environment. Additionally, Command View SDM does not support HP-UX 11.20. Sources of Support Information The README file included on the Command View SDM installation CD contains important support information you should read before installing and using the software.
Technical Support and Manual Updates Technical support is included with all HP StorageWorks Virtual Array products. For details regarding support information, refer to the HP Support Contract provided at the time you purchased the array. For a list of the most current support phone numbers, go to the following HP web site. This web site also has the latest version of this book available for downloading. http://www.hp.
2 Installing Command View SDM This chapter includes procedures for installing Command View SDM on each supported operating system. The installation process differs for each operating system. Once the software is installed, operation of Command View SDM is identical on all platforms. The Command View SDM software can be installed on a host connected directly to the array. Command View SDM can also be installed on a client for remote management.
Command View SDM Installation Configurations The installation of Command View SDM is influenced by a number of factors: the type of hosts connected to the array, other network management tools in use, and your strategy for local or remote management. There are three typical management configurations: ■ Native host - shown in Figure 1, this configuration is typically used when a host accessing the array supports Command View SDM.
Figure 1 Native Host Management Configuration Installing Command View SDM Installing Command View SDM 27
Figure 2 28 Non- Native Host Management Configuration Installing Command View SDM
Figure 3 HP OpenView Storage Area Manager Management Configuration Installing Command View SDM Installing Command View SDM 29
Installing Command View SDM on HP-UX The following procedure describes the steps involved in installing the Command View SDM software on an HP-UX host or client. Minimum System Requirements for HP-UX Before installing the Command View SDM software, verify that the host meets the following minimum requirements. Host ■ HP-UX 11.00/11.11/11.23 IA/11.23 PI on PA/ 11.
Support Plus Hardware/Critical Patch Bundle information can be found on the HP-UX Support Plus CD-ROM, or on the following web page: http://www.software.hp.com/SUPPORT_PLUS/hwe.html Selecting a Host IP Address on Systems with Multiple IP Addresses During installations where multiple IP addresses exist on a host (i.e. multiple LAN cards in a single host), only one of the IP address will be entered into the /etc/opt/sanmgr/hostagent/config/commIpAddr.txt file.
Installation Tips — For the latest information on installing and upgrading the software, refer to the README file on the Command View SDM Installation CD. The README is located in the corresponding operating system directory. — When upgrading to a newer version of Command View SDM, always remove the previous version before installing the new software. — Make sure EMS hardware monitoring is installed and operating on the host before installing Command View SDM.
root 2592 2579 2 15:31:30 pts/tb 0:00 grep pfs 7 If the above processes are not running, execute the following commands, /usr/sbin/pfs_mountd & /usr/sbin/pfsd & 8 Mount the CD device file using the device file and directory from the preceding steps. For example: pfs_mount -t rrip -o xlat=unix /dev/dsk/c2t2d0 /cdrom 9 Run swinstall using the appropriate command: Installing Command View SDM HP-UX 11.00 swinstall -s /cdrom/CommandViewSDM/hpux/ cvsdm_11_00_v109.depot HP-UX 11.
13 If you saved the configuration files from any earlier Command View SDM installation, use them to restore the prior configuration. Before restoring the older files, you may want to compare them with newly installed files (some of the old files may be the same). Note Note For installations with multiple IP addresses, see Selecting a Host IP Address on Systems with Multiple IP Addressesî earlier in this chapter.
CMDVIEWSDM 5 Remove the components. Note If any of the components selected for removal are required by other applications, the component will not be removed and an error message will be displayed. This message can be ignored. Note If you may need the contents of the existing log files, do not perform the next step. The log files may be useful in isolating problems you may have been experiencing with the array.
Installing Command View SDM on Windows The following procedure describes the steps involved in installing the Command View SDM software on a Windows 2000/2003 host or client. Minimum System Requirements for Windows Before installing the Command View SDM software, verify that the host meets the following minimum requirements.
Installation Tips — For the latest software updates, refer to the README file on the Command View SDM CD. The README is located in the corresponding operating system directory. — When upgrading to a newer version of Command View SDM, always remove the old software and save any configuration files.
HP OpenView Storage Area Manager Integration The Command View SDM software integrates into HP OpenView Storage Area Manager (SAM) running on a Windows management station. The process of installing the software on OpenView SAM is the same as on a standard WIndows environment, however you should be aware of the following operational differences when installing on an OpenView SAM management station: ■ The Command View software is only installed on the OpenView SAM management station.
Installation Steps 1 Make sure that SAM is installed and that the SAM Host Agent has been installed on the hosts connected to the array. See "Installing the SAM HostAgent on OpenView SAM" below. 2 Insert the Command View SDM CD into the CD-ROM drive on the host. 3 If upgrading to a newer version of Command View SDM, save any configuration files and remove the old software. See the following section. 4 From the Start menu, select Run. E:\CommandViewSDM\win\setup.
Installing the SAM HostAgent on OpenView SAM When installing the Command View SDM software in a SAM environment, the SAM Host Agent must be installed on hosts connected to the arrays that will be managed. The SAM Host Agent must be installed and running on a host to allow the SAM management client to detect and manage the array . 1 Launch the SAM GUI. 2 Select Tools > Manage Host Agent > Install Host Agent Software. Refer to the SAM on-line help for more information on installing the host agent.
1 Right click on the Command View SDM Launcher icon on the client desk top. 2 Select Properties > Short Cut. 3 In the Target: window, append a space and the host identification to the end of the path displayed. The host can be identified by either its DNS name or IP address. In the following figure, the IP address 10.62.126.238 is added to the target path. 4 Click OK.
Uninstalling HP Command View SDM Software from Windows This procedure describes uninstalling the Command View SDM software. The existing Command View SDM software should be removed before installing a new version of the software. The uninstall process does not automatically delete the array log files. If you want to delete the log files, you will have to do so manually. 1 If you are upgrading to a newer version of Command View SDM, save any configuration files you may have customized.
Installing Command View SDM on Linux Red Hat The following procedure describes the steps involved in installing the Command View SDM software on a Linux Red Hat. Minimum System Requirements for Linux Red Hat Before installing the Command View SDM software, verify that the host meets the following minimum requirements. ■ RHEL AS 3.0 with Kernel version 2.4.
After installation, check the contents of the /etc/opt/sanmgr/hostagent/ config/commIpAddr.txt file. If the correct IP address is not shown, manually enter the correct IP address. Installation Tips. — For the latest software updates, refer to the README file on the HP StorageWorks Command View SDM CD. The README is located in the corresponding operating system directory. — When upgrading to a newer version of Command View SDM, always remove the previous version before installing the new software.
7 Change directories to the /linux install directory by entering: cd /tmp/cmdview/ 8 Untar the file by entering: tar -xvf cvsdm_rhel30_v108.tar 9 Go to /tmp/cmdview/SDM entering: cd /tmp/cmdview/SDM 10 Install the software by entering: sh install_cmdview The installation will take several minutes. Installing Command View SDM Note The Host Agent installer writes a log file to /tmp/ SanMgrInstall.log. The Command View SDM installer writes a log file to /tmp/CommandViewInstall.
What’s Next? ■ If the software was installed on a host connected to an array, refer to "Configuring Command View SDM" on page 50 for additional configuration information. ■ If the software was installed on a client, see "Setting up Remote Client Access" on page 50 for information on assigning client access rights. Note Two Command View SDM daemons are installed on the client that are only required on the host connected to the array. They may be shut down on a client.
Note If there has been a problem with the software or the array, the logs should be retained and used to reference for troubleshooting. If you are certain you will not need to access the logs, they can be removed.
Saving and Restoring Array Configuration Information Several configuration files are used to customize the operation of Command View SDM. Because these files allow you to easily replicate or restore the configuration of your array, it is recommended that you maintain copies of these files. This is particularly important if you plan to upgrade to a newer version of Command View SDM.
them to a temporary directory and restore after installation. Firmware file can be identified by the .frm extension and are typically located in the ...\sanmgr\commandview\client\fwdownload for arrays ...\sanmgr\commandview\client\sbin for JBOD. Should I Save the Host Port Behavior and Secure Manager Tables? Restoring Array Configuration Information After Command View SDM has been installed on the host, the saved configuration can be restored as follows: 1 Replace files access.dat and ContactInfo.
Configuring Command View SDM Once installed, it may be necessary to configure the operation of Command View SDM. Configuration is required to perform the following tasks: ■ Setting up remote client access ■ Configuring the Command View SDM web browser ■ Enabling EMS if necessary (HP-UX only) Setting up Remote Client Access When using a remote client to manage arrays, the client must be granted access rights by the Command View SDM host connected to the array.
wildcards is recommended when connecting from clients configured for dynamic host configuration protocol (DHCP). 3 Save the configuration file. Removing a Client Use the above procedure to remove a host you no longer want to have access. When removing clients it is necessary to stop and restart the HostAgent to implement the change. See "Starting/Stopping HostAgent and OpenDIAL" on page 55.
Enabling EMS Monitoring If EMS monitoring is running on an HP-UX host when Command View SDM is installed, the array(s) will be automatically configured into the event monitoring. In this situation the following steps do not need to be performed. It will be necessary to manually enable EMS if Command View SDM has been installed in the following environments: — Command View SDM is installed on a Windows or Linux host that will be communicating with an HP-UX host running EMS.
cases, this variable is set by the system to the current system at logon. To verify this variable is set, type: echo $DISPLAY The response should be: :0.0 If the DISPLAY variable is not set, the Command View SDM software will throw a Java exception. If this occurs, set the DISPLAY variable by typing: export DISPLAY=:0.
Verifying the Installation You can easily verify the success of the Command View SDM software installation using the following steps. 1 Perform a hardware scan from the host connected to the array to ensure that the host can see the array. On an HP-UX host, this is done using the ioscan -fnkdisk command.
Starting/Stopping HostAgent and OpenDIAL The HostAgent and OpenDIAL services (or daemons) are installed with Command View SDM. These services are started automatically during installation and any time the host is restarted. Both services must be running on the host for Command View SDM to operate. If these services are not running, they must be started manually. HostAgent and OpenDIAL are not needed on a remote Command View SDM client and can be stopped.
■ To start HostAgent and OpenDIAL, enter the following from a command prompt: :\Program Files\Hewlett-Packard\sanmgr\commandview\client\sbin\HA_Dial_Start Creating LUN 0 Many operating systems rely on the presence of LUN 0 to establish a communication path to all LUNs on the array. Consequently, it is recommended that the array always have LUN 0 present. When LUN 0 is created, the array automatically creates an entry in the LUN security table granting Write & Configure access to all hosts.
Adding a New Host to the Management Configuration When adding a new host to your system, you will need to take the necessary steps to ensure the host can access the array. There are two steps to perform: 1 If the host does not use the default controller host port behavior, the host will have to be added to the host port behavior table. See "Creating the Host Port Behavior Table" on page 135 for information on performing this task.
2 When the host name has been changed and DNS is set up to correctly report the new hostname/IP address association, run the following command: armdiscover [managementhost] [-h devicehost] The armdiscover process will detect the new host name and add it and its associated arrays to the database. Deleting and Rebuilding the Device Database In some situations it may be necessary to delete and rebuild the device database.
Details About the Command View SDM Installation Process This section describes in more detail the Command View SDM installation process. It is not essential that you read this material to install the software successfully. It is provided for those who have a desire to understand what is going on behind the scenes. It may also help you solve any problems that occur during the installation.
Figure 4 Command View SDM Architecture Web Browser HP-UX Integration Command View Component Architecture CVSDM Web Server SAM STM Storage Management GUI HP OpenView Storage Area Manager CLUI Launcher CVUI Device Database Device Object armdiscover System Management HP OpenView NNM Top Tools CA SNMP Agent Events Service Logging Service SCSI Gateway Host Agent Log Database NT Event Viewer 60 Installing Command View SDM EMS syslog Storage Device Open DIAL
The Installation Process The following steps identify the main tasks performed during the installation of the software. 1 The installer creates the directory structure on the host and copies the Command View SDM files to the appropriate folders. 2 The OpenDIAL and HostAgent services start, which in turn launch the server components - SCSI Gateway, Logging Service, etc. 3 The armdiscover process is initiated, which causes OpenDIAL to do a discovery of all arrays connected to the host.
/opt/sanmgr/commandview/client/config /opt/sanmgr/commandview/client/sbin /opt/sanmgr/commandview/server/config > /etc/opt/sanmgr/ commandview/server/config /opt/sanmgr/commandview/server/data > /var/opt/sanmgr/ commandview/server/data /opt/sanmgr/commandview/server/logs > /var/opt/sanmgr/ commandview/server/logs /opt/sanmgr/SMI-S/VAProvider/classes /opt/sanmgr/SMI-S/VAProvider/mof /opt/SMI-S/cimom/classes /opt/SMI-S/cimom/mof /opt/sanmgr/cssi/...
HP StorageWorks SMI-S VA (Storage Management Initiative Specification) Introduction SMI-S VA is a component of Command View SDM and resides on the host to which the arrays are connected in the SAN. It runs as a service daemon. To start and stop SMI-S VA, see “"Starting and Stopping SMI-S VA" on page 65. This section describes procedures for configuring and installing SMI-S VA for HP StorageWorks Command View SDM.
■ Other features — Service Location Protocol (SLP) discovery — Java Authentication and Authorization Service (JAAS) — Secure Sockets Layer (SSL) Supported Operating Systems SMI-S VA 1.09 is supported on all the operating systems that support Command View SDM 1.09. See "Operating System Support (Native)" on page 22 for more information. Installing SMI-S VA HP StorageWorks SMI-S VA is automatically installed when the HP StorageWorks Command View SDM software is installed.
Linux ■ Execute the rpm -qa |grep SMI-S command on the destination machine to view the following SMI-S VA packages: — SMI-S_VA-1.09.00-1 — SMI-S_CIMOM-1.0.2-1 Note The CIMOM, by default, runs in the SSL mode on port 5989. When SSL is disabled, the CIMOM runs on port 5988. Starting and Stopping SMI-S VA Installing Command View SDM Windows The display name of the service is HP StorageWorks SMI-S CIMOM (the service name is hpSMISCIMOM).
The daemon can be stopped by running the SMIS_trigger script with the stop option. $./SMIS_trigger stop These commands can be used only by the root user. Note Uninstalling SMI-S VA HP StorageWorks SMI-S VA is automatically uninstalled when the HP StorageWorks Command View SDM software is uninstalled. Configuring SMI-S VA SMI-S VA is automatically installed when you install CV SDM. The following post-installation procedure must be completed prior to using SMI-S VA.
/opt/sanmgr/SMI-S/VAProvider/VAProvider.params Configure the values of the editable parameters as described in Table 3 before managing the VA using HP StorageWorks SMI-S VA. Restart the hpSMISCIMOM service after you modify the configuration parameters. Table 3 Field Parameters in the VAProvider.params file Purpose Modifiable VA Provider class Name No Host IP address of the management host to contact for the array data (default value for the host parameter is 127.0.0.1, which is the localhost).
The VA.provider File Modify the parameters in the VA.provider file as indicated in Table 4. Table 4 Parameters in the VA.provider file Parameters Description AUTHORIZATION_MODULE Specifies the authorization mechanism to be used. The value is the class name of the authorization module. The CIMOM supports the following authorization modules: • BasicAuthorization • JAASAuthorization The default module is JAASAuthorization.
The cim.properties File Modify the parameters in the cim.properties file as indicated in Table 5. Table 5 Parameters in the cim.properties file Field Purpose Set to True to enable SSL. The default value is True. LogResponseSeparate Set to True to separate requests and response packets. LogFilesCount Indicates the number of log files maintained by CIMOM. The default number is 5. Modify this number to increase or decrease the number of log files.
Note Do not modify any parameter that is not listed in the table. The UserAccountsManager.bat file User accounts are organized into groups, and a set of permissions are assigned to each group using JAAS. To manage the user accounts, you must have super user privileges. Use the script file (UserAccountsManager.bat) located in the home directory. This is the directory where the CIM Object Manager is installed. UserAccountsManager.bat file is titled UserAccountsManager.sh in HPUX and Linux.
Note The parameter Group is one of the groups listed by the -LG option. A user name can exist in only one group. To change the user password, execute this command: $ UserAccountsManager -CP -U -O N where: — U is the user name. — O is the old password of the user. — N is the new password for the user.
SLP DAEMON Installer The SMI-S server supports Service Location Protocol Daemon (SLP) discovery and it is mandatory to have the "slpd" (SLP daemon) running on the management host. The SLPD binaries are located on the Web and on the Command View SDM CD. Note After you install the SLP Daemon, a service titled Service Location Protocol is created in the machine. SLP Binaries Location on the Web and CD HP-UX HP-UX Binaries Location on the Web www.software.hp.com HP-UX 11.
CD: /CD Root/ |SMI-S/ |slpd/ |linux/ |slpd.rpm Windows Windows Binaries Location on the CD Installing Command View SDM The Windows slpd binaries are located in the following location on the Command View SDM CD: /CD Root/slpd/windows/setup.exe Managing Passwords for VA LUN Security/ LUN Masking Access The VA provides the capability to password-protect access to the LUN security management interface. The password is entered when the system is configured and is maintained within the array.
3 Modify—Modify a password for the array. 4 List—View all passwords in decrypted form with array World Wide Names (WWNs) in the following format: Array WWN : ----------- ----50060B00000921AB: Passwd -----guestpassword 5 Exit—Exit the password utility. Enter the number of the desired option to perform the operation. The SMI-S VA interface allows you to view and modify LUN Security or LUN Masking data for all the arrays that has a password entry on the management station.
SSL Support By default, SSL is enabled in the provider. SMI-S VA uses an SSL server-side certificate to help clients securely communicate with the SMI-S server. A selfsigned certificate (hpSMIS.cert) is packaged with SMI-S VA. Following is the location of the certificate on different operating systems: Windows C:\Program Files\Hewlett-Packard\SMI-S\cimom HP-UX and Linux /opt/SMI-S/cimom A trust store is a repository of trusted certificates that are recognized by the client program.
1 Import the server certificate into the client trust store. To import the server certificate, complete the following steps: — Copy the server certificate to the client system. — Use the Java keytool to import the certificate into the client trust store. $ keytool -import -alias hpsmis -file hpSMIS.cert -keystore mytruststore 2 You are prompted to enter a password. Note This password is required for modifying mytruststore in the future.
Viewing All Certificates Using the Keytool Command To view all the certificates in a truststore, execute the following keytool command: $keytool -list -v -keystore mytruststore Troubleshooting Table 6 lists the common problems that you may face with SMI-S VA Table 6 Troubleshooting The server did not respond to the CIM requests and the CIM Clients receive "CIM_ERR_FAILED" exception. Solution Installing Command View SDM Problem Determine if the hpSMISCIMOM Service/daemon is running.
Table 6 Troubleshooting Problem SMI-S VA Service failed to start Solution Check the service registration. Check the event log details. SMI-S VA is not able to populate data. Check to see if the directory C:\ProgramFiles\Hewlett-Packard\SMI-S\cimom \persistence\classes\root\VA is empty. If the directory is empty, load the mofs by invoking the batch file LoadMofs.bat present in \SMIS\VAProvider from the cimom directory. For example: C:\...\cimom> \SMI-S\VAProvider\ LoadMofs.
Using the Graphical User Interface 3 The Command View SDM Graphical User Interface (GUI) provides a convenient and familiar interface for managing the array. Using the GUI you can perform most of the tasks involved in the normal day-to-day operation and management of the array. For tasks not available in the GUI, the Command Line User Interface (CLUI) should be used. This chapter describes how to start the GUI and use it to perform common management tasks.
Running the Command View SDM GUI There are several methods for running the Command View SDM GUI, each of which is described here. Note Accessing the array from a remote client requires the proper access Regardless of the method you use to start the GUI, a remote client will need the proper access rights to manage an array. See "Setting up Remote Client Access" on page 50 for more information. Watch Your Case On an HP-UX system, case is important.
1 Double click the Launcher icon. The Command View SDM Launcher window opens displaying an icon for each array connected to the host. The icon indicates the current array status. 2 Double click on an array icon to run the management GUI for the array. You can now begin managing the array. Running the Launcher Using a Command Line On HP-UX and Linux systems, the Launcher is run from the command line.
is the array’s alias, serial number, device file, or world wide name. Running the Launcher from a Web Browser The Command View SDM Launcher and management GUI can be run from a web browser. This provides a convenient method of managing an array from a remote client that does not have the Command View SDM software installed. Note Earlier versions of Command View SDM (1.0 and 1.01) required the installation of a certificate on the browser client for security.
Running the Management GUI Directly from a Web Browser If you know the ID of the specific array you want to manage, you can run the management GUI directly from the browser. 1 Open a browser on the client. 2 Type the following URL into the address field in the browser: http://:4096/cmdviewVA.html?: is the DNS name or IP address of the host to which the array is connected. is the array’s alias, serial number, device file, or world wide name.
A proxy server may need to be configured in order for the plug-in installation to succeed. 4 If the web browser is configured to use a proxy server, the IP address of the OVSAM server should be included in the "Exceptions: Do not use a proxy server for addresses beginning with: " list. 5 The client PC’s web browser will need to authorize installing a HewlettPackard-signed Java applet. It will be prompted to do so automatically when the CV software is launched.
Using the Command View SDM GUI You perform array management tasks using the GUI by selecting the appropriate tabs and pages. For detailed information on using the GUI, access the on-line help by clicking the “?” located in the upper right corner of the screen. Locating Information The GUI interface uses a set of tabs to organize the tasks and information presented. The following table should assist you in determining which tab to use to perform a task.
Table 7 GUI Navigation Overview Tab Identity Status Task/Information Displays general information about the array. Status information is organized into three categories: — Array Status - general array status — Component Status - complete status information for each hardware enclosure in the array. Select the appropriate enclosure icon to display its status.
Table 7 GUI Navigation Overview (Continued) Tab Configuration Task/Information Configuration settings and displays are organized into three categories: ■ Array Settings — — — — — — Alias name Data resiliency RAID level Hot spare mode Automatic include Auto format ■ Port Settings — — — — — Port ID Port behavior Port topology Port data rate Queue Full Threshold — — — — Using the Graphical User Interface ■ Rebuild Settings Priority Type - auto/manual Initiate rebuild Progress indication ■ Host P
Table 7 GUI Navigation Overview (Continued) Tab Diagnostic Task/Information Diagnostic tasks are organized into two categories: ■ Array — Shutdown/Restart — Reset - full or partial — Array status ■ Disk — Include — Down — Disk status Download Firmware can be downloaded to the array controllers, the disk enclosure controllers (LCCs), disks, and the batteries.
Performing Management Tasks from the GUI The following section describes how to use the GUI to perform some of the common tasks involved in the day-to-day management of the array. This is not a complete list of the management tasks available in the GUI. For a complete list of the GUI functionality, see Table 7. These, and all other tasks available from the GUI, are described in the on-line help. The on-line help should be your primary source of information when using the GUI to manage the array.
Caution Deleting a LUN destroys all data on the selected LUN. Make sure any important data is backed up before proceeding. Please be aware of the following! — A LUN will not be deleted if it has existing business copies. — A Business Copy cannot be created from another Business Copy — If the LUN being deleted is very large, the time required to delete the LUN may cause host I/O timeouts. 1 Click the LUN Management tab. 2 Click Logical LUNs. 3 Click the LUN you want to remove in the LUN list.
3 Click Array Settings. 4 Select the Hot Spare mode. 5 Click OK. Using Secure Manager The Secure Manager screen is accessed as follows: 1 Click the LUN Management tab. 2 Click Secure Manager. Enter the password if necessary. Enabling and Disabling Secure Manager 1 On the Secure Manager screen, click Enable/Disable SM. 2 Select Enable or Disable. Enter the password. 3 Click OK. Refer to the GUI help for additional information about enabling or disabling security.
Adding a NodeWWN Table Entry 1 On the Secure Manager screen, click Add Table Entries. 2 In the Participant Type field, select Node WWN. 3 In the Host Name field, select the host or hosts for which you want to create table entries. The World Wide Name field will display all the WWNs associated with the hosts you select. Host names are provided for convenience in displaying and selecting WWNs. The host name is not included as part of the table entry.
Deleting Table Entries 1 On the Secure Manager screen, select the table entries you want to delete. Multiple entries can be selected. 2 Click Delete Entry. 3 Click OK. Copying LUN Permissions 1 On the Secure Manager screen, click Copy Permissions. 2 Enter the number of the LUN from which permissions will be copied. 3 Enter the number of the LUN to which permissions will be copied. 4 Click OK. Each table entry for the source LUN is duplicated for the new LUN.
Adding New World Wide Names 1 On the Host Port Behavior screen, click Add Entries. 2 Click Add New WWN. 3 Enter the world wide name in the WWN field. 4 Click OK. Deleting Host Port Behavior Table Entries 1 On the Host Port Behavior screen, select the table entries you want to delete. Multiple entries can be selected. 2 Click Delete Entry. 3 Click OK. Writing the Host Port Behavior Table to the Array 1 On the Host Port Behavior screen, click Apply Changes. 2 Select the desired write mode: Append or Clear.
Command Line User Interface 4 The Command View SDM Command Line User Interface (CLUI) is a set of utilities that provide complete array management capability. Each utility performs a different management task, such as configuring, reporting status information, and performing rebuilds. The operation of the CLUI is identical for all supported operating systems.
Command Summary Each command and the tasks it is used for are listed in Table 8. Complete descriptions for each command are included in this chapter. Table 8 Command View SDM Command Summary Command armcfg Tasks Create a LUN Delete a LUN Add a disk Down a disk armcopy Manage Business Copy LUNs armdiag Perform advanced troubleshooting.
Table 8 Command View SDM Command Summary (Continued) Command armmgr Tasks Configure hot spares Set array RAID level Set Auto Rebuild On/Off Set Auto Format On/Off Set Auto Include On/Off Set controller host port behavior Set resiliency level Set port loop ID Set fibre channel topology Break advisory lock Set array alias name Identify FRU location Reset the array Manage read and write cache settings Shutdown the array Set Queue Full Threshold armperf Display performance data armrbld Enable/disable Aut
Command Syntax Conventions The following symbols are used in the command descriptions and examples in this chapter. Table 9 Syntax Conventions Symbol <> Meaning Indicates a variable that must be entered by the user. | Only one of the listed parameters can be used (exclusive OR). [] Values enclosed in these brackets are optional. {} Values enclosed in these braces are required. Command View SDM man pages Online man pages are included for each Command View SDM command.
Using Identification Variables When using the Command View SDM CLUI, you must select the array you will be managing. In addition, many commands also require you to identify the component within the array — controller, disk, or LUN — that will be impacted by the command. The following paragraphs describe the identification variables and how they are used in a command. Before using the command, make sure you understand the use and structure of the identification variables.
FRU Identifiers All the Field Replaceable Units (FRUs) within the array are identified using a FRU location identifier, . The FRU location identifier specifies the component to which a command is directed. It has the format: /[component].[subcomponent] The values for the elements of the FRU location identifier are listed in Table 11.
Command View SDM Commands This section describes each Command View SDM command, its use, and its options. Examples are included showing the typical use of the command.
armcfg Description The armcfg command is used to manage LUNs (-L option) and physical disks (-D option). LUN management includes creating and deleting LUNs. Disk management involves adding, downing, and resetting disks. Caution Deleting a LUN will delete all data on the LUN. Backup all vital data on the LUN before deleting it. Note If the LUN being deleted is very large, the time required to delete the LUN may cause host I/O timeouts.
-x { true | false } Activates (true) or deactivates (false) the specified LUN. Performance can be improved by deactivating any LUN you will not be using. Disk Options (armcfg -D) -D Operation will be performed on the disk specified in -a Add the disk specified by . -d [ -v | -F] [-R | -Z ] Down the specified disk. The following options control the downing operation.
Deleting LUNs To delete LUN 17 in the array with the alias of myArray, type the following command: armcfg -L 17 -d myArray Adding Disks After a disk is inserted into the array, it must be added to the array configuration. If auto-include and autoformat are enabled, the disk will be automatically added. If these options are disabled, you will need to manually add a disk.
armcopy Description The armcopy command manages the business copy feature of the array. Syntax armcopy -p -s [ -a { true | false } ] armcopy -s { -x { true | false} | -a { true | false } } armcopy -r armcopy -? Options -a {true|false} Controls the content of the busines copy. When used with both the -p and -s options, a value of true creates a business copy with content linked to the parent LUN data.
-? Display extended help message. Overrides all other switches. Examples Create an empty business copy LUN 7 from parent LUN 3 on array serial number 00USP1001087. armcopy -p 3 -s 7 -a false 00USP1001087 Copy the content of the parent LUN to business copy LUN 4 on array alias Array1. armcopy -s 4 -a true Array1 Copy the content of the business copy LUN to parent LUN 6 on array alias Array1.
armdiag Description The armdiag command provides advanced diagnostic capability for isolating problems with the array. Caution The functionality available using the armdiag command can damage the array and cause data loss if not used properly. In addition, the Virtual Array SCSI Specification is required to use this command. Contact HP support for assistance before using armdiag.
-cf Identifies the file that contains the command descriptor block (CDB). The CDB is specified in hex values (e.g. 0xa0) and defines the operation the array will perform. -Cf filename Identifies the file to which the core data (~48 MB) is sent. If not specified, the core data is sent to standard out. NOTE: When using the -Core option within armshell, the -Cf option should always be used. Using armdiag -Core without the -Cf switch will result in unpredictable behavior.
-p Identifies the password required to perform any SCSI pass-through commands. Contact HP Support for information on using the password. -P Sends a generic SCSI pass-through command to the hardware device identified by -f . -q Suppresses the update output of the -I option. -sf Identifies the file used to store the status bytes of the command. If not present, the status will go to standard out. -W Display extended information about array warning states.
armdiscover Description The armdiscover command performs a discovery that identifies all arrays attached to a host. In addition to being output to the screen, the results of this command are stored in a database file, which is accessed by the armdsp -i command to display array information. Command options allow the discovery and storage of results on remote hosts. Note The armdiscover command should be run after adding a new array to a host on which Command View SDM is already running.
-delete Delete the database entries for all devices discovered on the host specified by . The entries are deleted from the database on the host identified by . This option is useful for deleting entries for a host that is no longer is use. Until the entries are deleted, icons for the arrays that were connected to the host will remain in the database and be displayed in the Launcher window. -n Causes the command to not run OpenDIAL.
Alias Name: green World Wide Name: 50060b000009736f Unique ID: HPA6189A00USP1001119 Product ID: Device Path: Serial Number: Alias Name: World Wide Name: Unique ID: HP-A6188A /dev/rscsi/c25t12d0 00SG04990103 yellow 50060b00000921a3 HPA6188A00SG04990103 Product ID: Device Path: Serial Number: Alias Name: World Wide Name: HP-A6189A /dev/dsk/c4t0d0 00USP1001083 white 50060b00000970bb 112 Command Line User Interface
armdownload Description The armdownload command downloads firmware to the array. Firmware can be downloaded to the array main controllers, battery control circuitry, disk enclosure Link Control Cards (LCC ), and disks. Note Always refer to the README file provided with the firmware for specific download requirements. Caution Only wrapped file formats should be used when downloading firmware to any component on the array.
-D -P Download firmware to the disk identified by the -P option. See the -P option for more information. -I Display a list of controllers (C), Disks (D), LCCs (L), or Battery controller (B) locations and firmware revision codes for the module type specified. -L Download firmware to the disk enclosure LCC controller identified by . Multiple controllers can be specified in the same command.
About Firmware Files The following information should be used when downloading firmware files. ■ Firmware files for the HP StorageWorks Virtual Array products are available at the following locations on the HP Support web: http://www.hp.com/support/va7100 http://www.hp.com/support/va7400 ■ When downloading firmware files, it is recommended that they be put in the following folders: ...\sanmgr\commandview\client\fwdownload for arrays ...\sanmgr\commandview\client\sbin for JBOD.
Removing an Advisory Lock During a firmware download, an advisory lock is installed to gain exclusive access to the component. If a lock is already in place, the download will fail and the following message will be displayed: Failed to set the firmware download advisory lock In this situation, the existing lock must be removed using the following command: armmgr -b FwDownload Once the lock has been removed, retry the firmware download operation.
1 Identify the current product numbers and firmware versions of the disk modules on the array with alias MyArray: armdownload -I D MyArray The following output is displayed: Vendor HP 36.4G HP 36.4G HP 36.4G HP 18.2G HP 18.2G HP 18.2G HP 18.
3 Download the new firmware file to either array controller by entering the following command: armdownload -C A6188AHP10.frm MyArray When new firmware is downloaded to one controller or battery, the new firmware will be automatically copied to the other controller or battery. If a family change version of firmware is being downloaded, an error message will be returned indicating that this is a family firmware version change and must be performed in an offline state.
armdsp Description The armdsp command is used to display status and configuration information for the array identified by . Logical configuration, physical configuration, and current status can all be displayed. A list of the array IDs of all the arrays connected to the host can also be displayed.
-d [] Display disk information. If is not given, display detailed information for all disks installed in the array. If is given and specifies an enclosure (e.g., JA1), display detailed information for all disks in the enclosure at . If is given and specifies a disk (e.g., JA1/D1), display detailed information for disk at only. -e [] Display enclosure information.
-ps Displays the host and disk port metrics. Contact HP support for more information on these metrics. -s Display Array Status, Warnings and Subsystem Parameter information for the array. This includes the configuration settings that control the operation of the entire array. This command will also print the version of Command View. -t Display topology of back end ports. This display identifies the controller paths to each disk in the array, the disk address, and the disk loop map.
Vendor ID:____________________________HP Product ID:___________________________A6218A Product Revision:_____________________A120 Firmware Revision:____________________38370A120P1111031050 Manufacturing Product Code:___________IJMTU00015 Controller Type:______________________HP StorageWorks Virtual Array 7410 Battery Charger Firmware Revision:____5.0 Front Port At M/C1.
Hard Address:_______________________126 Link State:_________________________Link Down Node WWN:___________________________50060b00000970bc Port WWN:___________________________50060b000014a12d Battery at M/C1.
Status:_____________________________Good Port Instance:______________________1 Hard Address:_______________________126 Link State:_________________________Link Down Node WWN:___________________________50060b00000970bc Port WWN:___________________________50060b000014a134 Back Port At M/C2.
need not be a single discharge cycle from 100% to 0%. It could be two cycles of 100% to 50%, four cycles of 100% to 75%, etc. The key factor is that the entire capacity of the battery has been discharged and recharged for each count. The battery initiates a reconditioning cycle when necessary. This causes the battery to go through a full discharge/recharge cycle. Each reconditioning cycle adds to the total Discharge Cycles count.
M/C1.M1 M/D1 M/D2 M/D3 M/D4 M/D5 M/D6 M/D7 M/D8 M/D9 M/D10 M/D11 M/D12 M/D13 M/D14 M/D15 DIMM Disk Disk Disk Disk Disk Disk Disk Disk Disk Disk Disk Disk Disk Disk Disk 1024 3HY090V0 3HY090QH 3HY090Q2 3HY090NS 3HY090WB 3HY06CJE 3HY090VS 3HY06G7D 3HY090PH 3CD0MBYX 3CD0M1JF 3HY090WA 3CD0GE1J 3CD0LHDG 3CD0MEXK Good Good Good Good Good Good Good Downed Good Good Good Good Good Good Good Good Displaying Disk Information Display the information for disk 2 in the main enclosure on array with alias jupiter.
Redundancy Group:_____________________2 Volume Set Serial Number:_____________00000D430000001C Serial Number:________________________3HY090QH Firmware Revision:____________________HP01 Displaying Disk Path Information Display the controller path information for each disk in the array with alias jupiter.
enclosure address (Encl Addr). =================================================== Drives Listed in Physical Loop Order =================================================== M/C1.J1 ------M/D4 M/D3 M/D2 M/D1 M/D10 M/D9 M/D8 M/D7 M/D6 M/D5 M/D15 M/D14 M/D13 M/D12 M/D11 M/C2.J2 ------M/D4 M/D3 M/D2 M/D1 M/D10 M/D9 M/D8 M/D7 M/D6 M/D5 M/D15 M/D14 M/D13 M/D12 M/D11 M/C1.J2 ------------------------------------------------------------------------------------------------- M/C2.
Communication on the loop does not occur in a simple, orderly sequence. The relationship between the physical location of a disk and the order in which it is accessed can be complex. The order in which disk are accessed is important when analyzing port error rate metrics. Knowing the order in which communication on the loop occurs can facilitate isolating the problem.
armfeature Description The armfeature command installs upgrade licenses for increasing the capacity limits for Business Copy VA and Secure Manager VA. Entitlement licenses are purchased as separate options. With the purchase of an option, you receive a license key which is installed using this command. The license key used to implement the feature is case sensitive. Make sure the key is entered exactly as generated. If the key is entered incorrectly, the feature will indicate a status of Disabled.
Examples Display the feature table for array alias Array1. A 500 GB feature has been installed for both Business Copy and Secure Manager LUN security on the array. hpbs9011:# armfeature -r Array1 FEATURE LICENSE KEY STATE ====================================================================== BUSINESS_COPY_500GB 0210E8AD9FD8 Active LUN_SECURITY_500GB FD47411C79C7 Active Display the feature table for array alias green.
armfmt Description The armfmt command allows a user to format the array. The entire array identified by is formatted. Caution armfmt is a destructive command. Data on the array will be destroyed following successful completion of this command. Backup all vital data before performing a format. Syntax armfmt -f [ -h ] armfmt -? Options -f [ -h ] Format the entire array identified by . The -f option formats all disks that are currently included in the array configuration.
armhost Description The armhost command is used to manage the array’s host port behavior table. This table maps each host to an associated operating system-dependent communication protocol or behavior. Each operating system communicates differently with the array, so the array must be aware of what operating system each host is running. The host port behavior table is the mechanism by which the array identifies the host operating system.
-f Identifies the file for the host port behavior table information. Table information read from the array is written to this file, and the content of this file is written to the array to update the table information. Relative or absolute file paths are allowed. If a path is not specified, the current working directory will be used. -h Retrieves the WWN for the hosts identified in , a commaseparated list of DNS names or IP addresses.
created file to the array using the armhost command. If a behavior for a host is not include in the table, the default controller behavior will be used. Creating the Host Port Behavior Table The host port behavior table is created as a text file which is downloaded to the array. The entries in the file are used to create the array’s host port behavior table. The file contains two values per line: one value identifying the WWN of the host, and one value specifying the host operating system.
table. Depending on the operating system, a host’s node WWN may not be passed through multiple host adapters to the array. In this case, the array will see the host’s multiple host adapter WWNs. In this situation, multiple host adapter WWNs must be entered into the table to represent the host. Example Create the host port behavior table on a new array for an environment with three hosts: one HP-UX (with two host adapters), one Windows (with two host adapters), and one Linux (with one host adapter).
armlog Description The armlog command displays the controller and disk logs maintained by the array. These logs contain information useful for diagnosing and troubleshooting. This command involves only event logs and does not display performance logs. Syntax armlog {-c [-s ] [-e ] [-pg ] [-sv ] [-xml]} armlog {-d [-p ]} armlog -? Options -c Display the contents of the array's controller event log.
-pg Display controller logs of the type specified by . Values for can be Events, NV, or Critical. The entries included on each page type are determined by their severity level. See the -sv option for severity levels. Events page includes all entries (levels 0-4); NV page includes entries of moderate severity (levels 2 and 3); Critical page includes entries of the highest severity (level 4). If this option is not included, all logs on the Events page are displayed.
armmgr Description The armmgr command manages the configuration parameters of the array. These settings control the operation of the entire array, consequently, every LUN on the array will be affected by any changes made using this command. This command also allows you to shutdown, restart, and reset the array. Changing some of the array settings may require that the array be reset using the -R option. The user will be prompted to initiate a reset if the modified setting requires this action.
-x {on | off} | armmgr -? For firmware versions HP15 or greater (VA7100/7400) and A000 or greater (VA7410/7110) armmgr {-P {on | off | true | false} | -hd {on | off} | -pd {1GB | 2GB} | -pv | -q | -S {on | off | true | false}} For firmware versions HP11 and greater: armmgr -B {Hpux|WinNT|Win2000|Linux|Solaris|AIX|NetWare|Tru64|MPE|OpenVMS|SunCluster| UnsupportedOS} | -C {raid1+0 | hpautoraid} | -h {None | Automatic
Options -a {on | off } Sets Auto Rebuild on or off. When enabled, redundancy should be rebuilt automatically whenever a drive becomes unavailable. A value of off indicates that rebuilds should not occur until explicitly stated. -b { CreateLun | FwDownload | Security | Select | PassThru | HostPort } Break the advisory lock. For example, if the array aborts a download (or if the download fails to complete), portions of the GUI may stop functioning due to an advisory lock being set.
-d Set the fibre channel to its default settings. -D Set the array alias name (limited to 256 bytes). -f {on | off} Set Auto Format Drive on or off. Default is on. When enabled, any disk that does not have 520-byte sectors will be automatically reformatted when installed in the array. If the disk already has 520-byte sectors, no formatting operation will take place. -h {None|Automatic| LargestDisk | LargestTwoDisks} Specify Hot Spare operation. Default is Automatic. None - no hot spare.
-J {SingleController | Secure | Normal | RestrictedNormal | HighPerformance} Set Resiliency Level. This option sets the level of protection offered by data resiliency. It determines how often the contents of the controller maps are copied to the disk. Keeping the map information on the disks protects against controller map loss. SingleController is used if the array is operating with only one controller.
-p Set the current state of the scrubbing policy can take any one of the following values: start, disable. -P {on|off|true|false} Controls whether the cache will perform a read ahead operation on the LUNs being accessed, which may improve performance in some environments. A value of on (true) will enable the read ahead operation. A value of off (false) will disable it. NOTE! This feature is disabled by default.
-q Set the Queue Full Threshold to . For the VA 7400 and VA 7100 arrays, must be in the range of 0 to Max Queue Threshold, which can be determined using the armdsp -s command. If “0” is used, it will set the Queue Full Threshold to its default value, which varies by firmware revision. For the VA 7110 and VA 7410 arrays, must be in the range of 1 to Max Queue Threshold. There is no default value for these arrays.
-S {on | off | true | false} Disable secondary path information to the host. This option controls whether the array will make the non-optimal (secondary) path to LUNs visible to the hosts. A value of on (true) disables the secondary path. A value of off (false) enables it. NOTE! Disabling the secondary path impacts high-availability. The host cannot failover to the secondary path if the primary path is disrupted. -t Set Capacity Threshold warning to the percentage specified by .
Examples Set port behavior for host port 2 on controller 1 to NetWare on array serial number 00786b5c0000. armmgr -B NetWare M/C1.H2 00786b5c0000 Assign an alias of AutoRAID1 to array serial number 00USP1001087. armmgr -D AutoRAID1 00USP1001087 Select RAID level 1+0 for array identified by device file /dev/dsk/c2t0d0. armmgr -C raid1+0 /dev/dsk/c2t0d0 Identify disk 6 in disk enclosure 3 on FC loop 2 on array AutoRAID3 by flashing its LED.
armperf Description The armperf command displays array performance data. Syntax armperf {-c } [-u [,, . . .]] [-m “ [,, . . .]”] [-s ] [-e ] [-n ] [-x export_type] armperf -i armperf -? Options -c Identifies the category for the specified metrics. Metrics are organized into four categories: LUN, ARRAY, DISK, or OPAQUE. Not all metrics are available for each category.
-s The starting time of the range for which metrics will be displayed. Default is the earliest available record in the performance logs. Format of the time option: MMDDhhmm[YYYY] MM=month DD=day of month hh=hour in 24 hour format mm=minutes YYYY=year. -e The end time of the range for which metrics will be displayed. Default is the latest available records in the performance logs. Format of the time option is identical to starttime.
Display the three LUN-based metrics identified by the -m option. Limit the display to the time period of August 5 from 7:00 am to 8:30 am on array with WWN 2002a00b880005c0. armperf -c LUN -s 08050700 -e 0805830 -m “Host Reads, Host Writes,Total I/O” 2002a00b880005c0 Performance Metrics Table 12 lists the metrics maintained by the array. The categories for which each metric is available is identified.
Table 12 Performance Metrics Metric Categories 1 Hour Write Working Set ARRAY 11 Hour Write Working Set OPAQUE 24 Hour Write Working Set Description/Usage The number of clusters that have been written approximately within the time frame specified by the metric. Usage AutoRAID attempts to keep the write working set in RAID 1+0 storage to provide the best random write performance. These metrics are used by AutoRAID to implement that policy.
Table 12 Performance Metrics (Continued) Metric Cache Pages Written Categories ARRAY LUN Description/Usage The number of write cache pages written to disk in response to host write commands. Each write cache page is counted as a single cache page written independent of the number of disk write commands used to write the page. Disk writes generated by array internal policy operation are not counted as cache pages written.
Table 12 Performance Metrics (Continued) Metric Categories Command Aborts Received (1.05 release) OPAQUE (7100/ 7400/7110) The number of SCSI abort requests received. OPAQUE (7100/ 7400/7110) The number of SCSI commands received. BACKENDPORT The number of commands to targets on the back end loop that were aborted before they completed due to excessive execution time. Abort Sequences Received (prior to 1.
Table 12 Performance Metrics (Continued) Metric Corrected Read Errors Without Delay Categories Description/Usage DISK-PORTS An error correction was applied to get perfect data (like ECC on-the-fly). "Without substantial delay" means the correction did not postpone reading of later sectors (e.g., a revolution was not lost). The counter is incremented once for each logical block that requires correction.
Table 12 Performance Metrics (Continued) Metric Categories Corrected Read Errors With Retry DISK-PORTS Description/Usage Specifies the counter counting the number of errors that are corrected by applying retries. This counts errors recovered, not the number of retries. If five retries were required to recover one block of data, the counter increments by one, not five. The counter is incremented once for each logical block that is recovered using retries.
Table 12 Performance Metrics (Continued) Metric Categories Description/Usage Corrected Write Errors With Retry DISK-PORTS Specifies the counter counting the number of errors that are corrected by applying retries. This counts errors recovered, not the number of retries. If five retries were required to recover one block of data, the counter increments by one, not five. The counter is incremented once for each logical block that is recovered using retries.
Table 12 Performance Metrics (Continued) Metric Host Reads Categories Description/Usage ARRAY The total number of host read commands completed. LUN Usage This metric is used as the basis to compute the Read Rate metric. It can be used along with the Host Writes metric to determine the read/write ratio characteristic of the workload. Host Writes ARRAY The total number of host write commands completed. LUN Usage This metric is used as the basis to compute the Write Rate metric.
Table 12 Performance Metrics (Continued) Metric Link Failure Count Categories Description/Usage FRONTENDPORT, BACKENDPORT The number of times a NOS primitive sequence or another failure of N_Port initialization protocol caused a transition into the link failure state. Usage Each of the port error counters provides a general indication of the quality of port operation.
Table 12 Performance Metrics (Continued) Metric Logical Blocks Written Rate (1.05 release) Logical Blocks Written Throughput (prior to 1.05) Loss of Signal Count Categories ARRAY LUN Description/Usage The average number of logical blocks transferred per second by write commands. Usage This metric is a measure of the performance level being achieved for writes and also provides some indication of the demand level of the host workload. High write rate will not be achieved when the workload demand is low.
Table 12 Performance Metrics (Continued) Metric Make Space For Write Invocations Categories OPAQUE Description/Usage The number of times the make space policy has been invoked. Usage The make space policy runs only in foreground on demand when free disk space is needed to post data from the write cache so that space can be freed up in the write cache to process host write commands. This can cause a significant delay in processing of the host write commands that are waiting.
Table 12 Performance Metrics (Continued) Metric New RAID 1+0 Writes Categories OPAQUE Description/Usage The number of write operations to previously unwritten LUN addresses posted out of the write cache to RAID 1+0 storage. Usage New writes are host writes to LUN addresses that have not been written since the LUN was created. AutoRAID will decide whether to place write data into RAID 1+0 or RAID 5 DP storage when it is posted out of the write cache.
Table 12 Performance Metrics (Continued) Metric New RAID 5 DP Writes Categories OPAQUE Description/Usage The number of write operations to RAID 5 DP storage that caused allocation of new space in RAID 5 DP. Usage New writes are host writes to LUN addresses that have not been written since the LUN was created. Rewrites are host writes to LUN addresses that have already been written at least once since the LUN was created.
Table 12 Performance Metrics (Continued) Metric Categories Number of Forced Unit Access Commands ARRAY LUN Description/Usage The number of host read and write commands processed while the Forced Unit Access condition was in effect. When the Forced Unit Access condition is in effect for a read command, any data in the read cache addressed by the read command is discarded and fetched from disk again.
Table 12 Performance Metrics (Continued) Metric Optimize Invocations Categories OPAQUE Description/Usage The number of times the optimize policy has been invoked. Usage The optimize policy runs only in background when idle time is available in the array. It attempts to keep the array operating optimally by keeping the write working set in RAID 1+0 storage and by maintaining a minimum threshold of free disk space.
Table 12 Performance Metrics (Continued) Metric Categories Relative values of metrics Invocations Description/Usage Possible scenarios Relocations High High The array has idle time available for optimization and optimization is occurring. High Low The array has enough idle time to allow the optimize policy to be invoked but not enough idle time to allow optimization work to make progress.
Table 12 Performance Metrics (Continued) Metric Port-A Invalid CRC Count Categories DISK-PORTS Description/Usage Count of the number of write data frames that have been received with invalid CRCs on Port A. These errors are only detected when this drive is the target of the data transfer Usage Each of the port error counters provides a general indication of the quality of port operation.
Table 12 Performance Metrics (Continued) Metric Port-B Invalid CRC Count Categories Description/Usage DISK-PORTS Count of the number of write data frames that have been received with invalid CRCs on Port B. These errors are only detected when this drive is the target of the data transfer Usage Each of the port error counters provides a general indication of the quality of port operation.
Table 12 Performance Metrics (Continued) Metric Protocol Error Count Categories Description/Usage FRONTEND- The number of N_Port protocol errors detected and LRR PORT, primitive sequences received while the link was up. BACKENDUsage PORT Each of the port error counters provides a general indication of the quality of port operation. Any significant counts in any of the port error counters is an indication that port or link operational quality may be having an effect on performance.
Table 12 Performance Metrics (Continued) Metric RAID 1+0 Writes in Place Categories OPAQUE Description/Usage The number of write operations to previously written LUN addresses posted out of the write cache to RAID 1+0 storage. Usage Rewrites are host writes to LUN addresses that have already been written at least once since the LUN was created. AutoRAID will decide whether to place write data into RAID 1+0 or RAID 5 DP storage when it is posted out of the write cache.
Table 12 Performance Metrics (Continued) Metric RAID 1+0 Allocation (1.05 release) Categories ARRAY RAID 1+0 Capacity (absolute) (prior to 1.05) Description/Usage The number of logical blocks in the array that are stored using the RAID 1+0 storage method. It is a sum of the RAID 1+0 Allocation metrics from each configured LUN. Usage RAID 1+0 provides better random write performance than RAID 5 DP.
Table 12 Performance Metrics (Continued) Metric RAID 1+0 to RAID 5 DP Relocations Spawned by MakeSpace Categories OPAQUE Description/Usage The number of clusters that were relocated by the make space policy from RAID 1+0 to RAID 5 DP storage. Usage RAID 5 DP provides better storage efficiency than RAID 1+0.
Table 12 Performance Metrics (Continued) Metric RAID 5 DP Allocation (1.05 release) Categories ARRAY RAID 5 DP Capacity (absolute) (prior to 1.05) Description/Usage The number of logical blocks in the array that are stored using the RAID 5 DP storage method. It is a sum of the RAID 5 DP Allocation metrics from each configured LUN. Usage RAID 5 DP provides better storage efficiency than RAID 1+0 and approximately equivalent sequential write performance.
Table 12 Performance Metrics (Continued) Metric RAID 5 DP to RAID 5 DP Relocations Spawned by MakeSpace Categories OPAQUE Description/Usage The number of clusters that were relocated by the make space policy from RAID 5 DP to RAID 5 DP storage. Usage The RAID 5 DP storage areas can become filled with holes of empty space that need to be garbage collected to make the space available as free space for write data posted from the write cache.
Table 12 Performance Metrics (Continued) Metric RAID 5 DP Writes in Place Categories OPAQUE Description/Usage The number of write operations to previously written LUN addresses posted out of the write cache to RAID 5 DP storage. Usage Rewrites are host writes to LUN addresses that have already been written at least once since the LUN was created. AutoRAID will decide whether to place write data into RAID 1+0 or RAID 5 DP storage when it is posted out of the write cache.
Table 12 Performance Metrics (Continued) Metric Read Cache Size (absolute) Categories ARRAY Description/Usage The capacity of memory allocated to the read cache (in Kbytes). Usage The capacity of the read cache is based on the amount of memory installed in the controllers. If other metrics indicate the read cache is not effectively servicing the host read workload, it may be possible to increase performance by installing more controller memory.
Table 12 Performance Metrics (Continued) Metric Read Command Latency range Categories ARRAY LUN Description/Usage The number of read commands that were received and completed within the time range specified by the metric. The supported time ranges are: 0-2.55 ms 2.56-5.11 ms 5.12-10.23 ms 10.24-20.47 ms 20.48-40.95 ms 40.96-81.91 ms 81.92-163.83 ms 163.84-327.67 ms 327.68-655.35 ms >655.35 ms The following additional time ranges are supported only on VA 7410: 655.36ms-1.30S 1.31-2.61S 2.62-5.23S 5.
Table 12 Performance Metrics (Continued) Metric Read ECC Usage Categories Description/Usage DISK-PORTS Specifies the counter that counts the total number of retries of the number of times the retry algorithm is invoked. If after five attempts an error of type "Corrected Read Error With Retry" is recovered, then five is added to this counter.
Table 12 Performance Metrics (Continued) Metric Total Cache Pages Accessed Categories ARRAY LUN Description/Usage The total number of disk read and write commands used to fetch and post data to and from the read and write caches. It is a sum of the Cache Pages Read and Cache Pages Written metrics. See the descriptions of those two metrics for more detailed information. Disk read and writes generated by array internal policy operation are not counted as cache pages accessed.
Table 12 Performance Metrics (Continued) Metric Total I/O Categories ARRAY LUN Description/Usage The total number of host read and write commands completed. Usage This metric is used as the basis to compute the Total I/O Rate metric. Total I/O Rate (1.05 release) ARRAY Total I/O Throughput (prior to 1.05) LUN The average number of host read and write commands completed per second.
Table 12 Performance Metrics (Continued) Metric Total Logical Blocks Transferred Rate (release 1.05) Total Logical Blocks Throughput (prior to 1.05) Total Mbytes Read Categories ARRAY LUN Description/Usage The average number of logical blocks transferred per second by read and write commands. Usage This metric is a measure of the performance level being achieved by the array and also provides some indication of the demand level of the host workload.
Table 12 Performance Metrics (Continued) Metric Total Uncorrected Read Errors Categories DISK-PORTS Description/Usage The total number of blocks for which an unrecoverable data error has occurred. Usage Each of the read error counters provides a general indication of the quality of read operations. Any significant counts in any of the read error counters is an indication that drive operational quality may be having an effect on performance.
Table 12 Performance Metrics (Continued) Metric Write Cache Hits Categories ARRAY LUN Description/Usage The number of cache page accesses that were satisfied immediately from data that was stored in the write cache when processing host write commands. A host write command that spans multiple write cache pages will count a write cache hit for each write cache page that was immediately available in the write cache when the write command was processed.
Table 12 Performance Metrics (Continued) Metric Write Cache Size (absolute) Categories ARRAY Description/Usage The capacity of memory allocated to the write cache (in Kbytes). The write cache memory is non-volatile and mirrored between the dual controllers. Usage The capacity of the write cache is based on the amount of memory installed in the controllers.
Table 12 Performance Metrics (Continued) Metric Write Command Latency range Categories ARRAY LUN Description/Usage The number of write commands that were received and completed within the time range specified by the metric. The supported time ranges are: 0-2.55 ms 2.56-5.11 ms 5.12-10.23 ms 10.24-20.47ms 20.48-40.95 ms 40.96-81.91 ms 81.92-163.83 ms 163.84-327.67 ms 327.68-655.35 ms >655.35ms The following additional time ranges are supported only on VA 7410: 655.36ms-1.30S 1.31-2.61S 2.62-5.23S 5.
Table 12 Performance Metrics (Continued) Metric Write ECC Usage Categories Description/Usage DISK-PORTS Specifies the counter that counts the total number of retries of the number of times the retry algorithm is invoked. If after five attempts an error of type "Corrected Write Error With Retry" is recovered, then five is added to this counter.
armrbld Description The armrbld command manages the array rebuild process. It allows a user to initiate, cancel, monitor the progress of, or modify the characteristics of, a rebuild. Note The virtual array rebuilds data online. Performing a rebuild should not impact array availability or overall array performance. Syntax armrbld {-r | -c | -p | -a {on | off} | -P {high | low}} armrbld -? Options -a {on|off} Enable (on) or disable (off) Auto Rebuild.
Examples Display the current state of a rebuild on host with alias blue. In this example the host is not currently performing a rebuild. hpbs9011:# armrbld -p blue Rebuild status: Vendor ID = HP Product ID = A6188A Rebuild progress = No rebuild in progress Auto Rebuild is = ENABLED Rebuild priority is = LOW The array is not currently rebuilding.
armrecover Description The armrecover reconstructs data mapping and array configuration in the event of the loss of NVRAM contents. The data maps are reconstructed using the latest copy of mapping information stored on the disk drives. Part of the recovery operation includes performing a parity scan on the contents of the entire array to validate the accuracy of the maps and to correct any drive parity inconsistencies. This process can take up to several hours depending on the amount of data on the array.
-p Begin the recovery in non-interactive mode. If there are multiple volume sets on the array, a list of the volume set numbers will be displayed. If there is only one volume set on the array, the recovery will be done on it. This option provides a mechanism to pass volume set information to a script designed to perform a recovery. -s Returns the recover ability status of the array, as well as the status of a recovery in progress.
■ If an error occurs while the recover process is run on an array that does not have a genuine map loss condition, the array will be left in a Recovery Failed warning state. If there are no other errors generated, the array will function in this state. To clear the Recovery Failed warning state, run a complete (successful) recover again.
armsecure Description The armsecure command manages the Secure Manager features of the array. For information on using Secure Manager, refer to the hp surestore secure manager virtual array installation and user guide included with the Secure Manager Software Media Kit (T1003). This document describes in detail the format of the Secure Manager table. .
-cp Copies permissions from one LUN to other LUNs, or from one WWN to other WWNs. The current Secure Manager table is read from the array, new table entries are made to copy the specified permissions, and the table is written back to the array. -d Disables Secure Manager on the array. The Secure Manager table is not altered. When Secure Manager is disabled, all LUNs are accessible to all hosts. -e Enables Secure Manager on the array.
-p Specifies the password required to execute the command. The password must match the one set on the array, or the command will fail. This is required for all forms of the command. The password can be from one to eight characters long. Any printing character is legal, but it is best to avoid blanks and other special characters. The password “AUTORAID” is the initial password set at the factory. This is also the password set from the Virtual Front Panel if the real password is lost.
-wd Identifies the destination WWN or WWNs to which permissions will be copied. Entries matching those of the source WWN will be created for each destination WWN. This option is only used with the -cp and -ws options. WWNList can be a single WWN or a comma separated list of WWNs. -ws Identifies the source WWN from which permissions will be copied. WWN must already exist in the security table on the array. This option is only used with the -cp and -wd options. -? Display help message.
armshell Description The armshell command provides an environment for executing multiple CLUI commands without the overhead imposed in the standard environment. When executing a command in the standard environment, each command opens the Java Virtual Machine (JVM), executes, then closes the JVM. When executing multiple commands, this continued opening and closing of the JVM increases the time required for command execution.
> filename Use the specified file as standard output. If the file does not exist, it is created. If the file exists, it is overwritten. If more than one argument is given, only the first argument is used. All other arguments are ignored. cd [directory] Change the current working directory. If no argument is given, nothing occurs. If a directory is specified in absolute terms then it becomes the new working directory.
Examples This example launches armshell and turns on command echo: armshell -e on This example launches armshell and executes the commands stored in file test.bat: armshell
armtopology Description The armtopology command provides topology information about hosts and attached virtual arrays connected to the hosts for each LUN in the array. The command displays associated path information for each LUN which includes: host name (DNS or IP), host Node WWN, Port WWN, array product number, array serial number, array controller (1 or 2), redundancy group (1 or 2), LUN number, and device path (from host to LUN).
The following example output would be produced for this command: Host Host Node WWN Host Port WWN Product SerialNumber C RG LUN Device path ------------------------------------------------------------------------------------host1 50060b000005aed6 50060b000005aed7 A6188A 00USP1001064 1 1 1 \\.
Table 13 armtopology Output Parameters Key value Description Column width at_HOST at_ONWWN at_OPWWN at_RNWWN at_RPWWN at_LUNID at_LUNWWN at_RG at_CONTROLLER at_DB_ID at_DB_VEND at_DB_PROD at_DB_SN at_DB_REV at_DB_NWWN Host Host Node WWN Host Port WWN Device Node WWN Device Port WWN LUN LUN WWN RG C Device Unique ID Vendor Product ID Serial Number Rev Device Node WWN -21 16 16 16 16 4 32 2 2 36 8 16 13 4 at_DB_PWWN Device Port WWN 16 at_DB_ALIAS Device Alias 10 at_DB_HWPATH HW Path 8 at_DB_D
secadmin Description The secadmin command configures the user to use the CVSDM GUI and CLUI. Note Regardless of what group a user is in (user/administrator), all users are allowed access to all CVSDM CLUI and GUI commands. Only users in the Administrator group are allowed to configure and manage users for the GUI and CLUI using the secadmin command. Syntax < CMD-SCRIPT > -user -pass < CMD-SCRIPT > -user -pass ARGS: [user1 passwd1 ...
Option Description g Prompts user to enter "User name:" / "Password" and "Select group (a|u):". On entering valid options, a user will be added to the security database. A user that belongs to the Administrator (a) group can manage other users and log in as a GUI user. A user that belongs to the user (u) group can log in as a Command View GUI user and perform all SDM operations using the GUI. c Prompts user to enter "User name:" / "Host name:".
Command View SDM User Interface 5 The Command View SDM User Interface (CVUI) adds a simple, text menubased interface as a front end to the Command View SDM commands. Some of the benefits the CVUI offers include: ■ Full functionality - the CVUI provides the same complete management capability and functionality as the Command Line User Interface (CLUI). ■ Ease of use - the menu structure relieves you of the need to memorize command syntax. This is useful if you use the command infrequently.
Starting the Command View SDM CVUI The Command View SDM User Interface is started from a command line. To start the interface, enter the appropriate command: cvui << On a local host cvui -h << From a remote client cvui -h {array_id} << From a remote client - connects to specified array CVUI Example The following example illustrates the process of starting the CVUI and selecting an array to manage. The process involves inputting the value for the desired selection.
Several levels of menus are required to execute a command. Continue entering the number of the operation until the action is performed. CVUI Configuration For CVUI configurable options, refer to the comments in the following files: Windows 2000/2003: :\Program Files\Hewlett-Packard\sanmgr\commandview\client\sbin\cvui.cmd HP-UX and Linux: /opt/sanmgr/commandview/client/sbin/cvui CVUI Screen Exporting ROWS and COLUMNS The CVUI uses the environment variables ROWS and COLUMNS.
CVUI Menu Map The following map shows the main structure of the CVUI menus (some additional levels are not shown). For additional help on the operation of the CVUI interface, select “h” from any CVUI screen.
HP Array Main --- Diagnostic----------------- ResetFRU DownFRU IncludeFRU FormatDisks Scrubbing RecoverNVRAM BreakAdvisoryLock Configure ----------------- Alias AutoFormatDrive CapacityDepletionThreshold ReadCacheDisable RebuildPriority WriteCacheEnable DisableNVRAMonUPSAbsent SimplifiedResiliencySetting AutoInclude AutoRebuild HotSpare LUNCreation Limit RAIDLevel EnableOptimizePolicy EnablePrefetch DisableSecondaryPathPresentation Configure Fibre.............
Security -------------------- ClearTable Disable Enable SetSecurityTable GetSecurityTable ChangePassword LicensedFeatures ------.
6 Array Logs The array continually monitors and records information reflecting the current operating state of the array. This information is stored by the array in its internal memory. The Command View SDM software reads this information and stores it in log database files on the host. An overview of array log management is shown in Figure 5.
Figure 5 Array Log Management logdel (Clears Log Files) stdout Host Array Log Entries Log Database Files logprn OR Log Text File .
Managing the Size of the Log Files Over time, the log database files can become quite large. To avoid consuming excessive disk space, you can restrict the size of the files. There are two options for managing the size of the log files. ■ Manually delete the files using the logdel command. For more information on the logdel command, refer to "logdel" on page 216. ■ Configure the operating parameters to automatically limit the log file size.
Log Commands Three utilities and their associated commands are available for managing the array logs. ■ logprn - used to view historical logs ■ logdel - used to delete historical logs ■ armlog - used to read the current controller and disk logs These commands and some detail on the format and structure of the log files is discussed in this section.
logprn Description The logprn command reads log entries from log database files and directs them to stdout (screen). The output can also be redirected to a text file, which is required for the Command View SDM log tool operation. The log entries retrieved can be limited by setting the start and stop range option. A filter option (-t) can be used to define the exact type of log entries to retrieve.
-sv Filters the log entries based on severity. Only log entries with the specified severity or greater will be displayed. Severity values are 0, 1, 2, 3, 4, with 0 being the highest severity. -t Specifies the type of log entries to view. Valid types are: TargetDeviceEvent HostEvent ControllerEvent ChangeEvent AbtermEvent Device = Controller log files, only Software State = Usage log files only All = Both Controller (Device) and Usage (State) log files. -b Output is brief format.
logprn -a myarray -s 111908302000 -e 010115302001 -t Device -v This command will produce the following output (only one entry shown): = = = = = = = = = = = = 50060B000008A085 October 13, 2000 8:27:34 AM EDT HP VA7100 VirtualArray 90339 M/C1 374 1 2447 Controller Event of the error provided here. Standard Output Display all log entries to standard out for the local host.
logdel Description The logdel command deletes log database files. Only files older than two months old can be deleted; two full-calendar months of files are always saved and cannot be deleted. This command also allows you to delete specific log file types or to delete all log file types. See "About Log Files" on page 219 for information about log file types).
-t Identifies the type(s) of log files to delete. Valid types are: Device (controller) State (usage) All -? Display help message. Overrides all other switches. Examples Delete all the logs on array serial number 00USP1001089. Delete all entries up to August 2001.
armlog The armlog command reads controller event log messages directly from the array. The armlog command is described on page 137.
About Log Files There are two types of log database files, as mentioned earlier, generated by the array: controller logs and usage logs. Each type of entry is stored in its own log database file. ■ Controller (Device) Logs - Controller log entries are generated from the internal array events. Command View SDM polls the array every 15 minutes to retrieve log entries. These log entries are stored in controller log database file.
entries. The file name consists of the creation day (dd) followed by the file type name (ctrlr for controller or usage). The directory for the software database logs is: /commandview/server/logs/software/yyyy-dd/dd-sw.log The entries are organized into directories identifying the year and month (yyyy-MM) the file was created. The file name consists of the creation day (dd) followed by the software (sw) file type name.
Performance Logs In addition to the event logs, array performance data is logged. Performance data is stored in a log structure similar to the event logs. Performance data is logged continually while the array is in operation. A new performance log is created every 24 hours beginning at 12:00 a.m. The array directory structure is shown below: ../commandview/server/logs/performance/arrayuniquename/ YYYY-MM/dd-perf.
Sets the minimum number of days worth of log files to keep. This parameter overrides the PERFORMANCE_DB_MAX_SIZE parameter if the two parameters conflict. The default is seven days. For the default case, a minimum of seven days worth of performance log files will be kept for each device regardless of the max disk space setting. PERFORMANCE_LOG_CLEAN=nn Defines how often (in hours) the performance logs will be checked to see if log files need to be deleted, based on the PERFORMANCE_DB_MAX_SIZE setting.
7 Solving Problems This chapter identifies problems you may encounter when installing and using Command View SDM. It takes you through the steps typically required to solve each problem. If the problem you are experiencing is not include here, the following resources may provide a solution. ■ HP support contact ■ HP support web site ■ HP storage forums PROBLEM Command View SDM stops working when Secure Manager is enabled. Command View SDM cannot manage the array.
2 Identify which LUNs the non-functioning host can access. You will need to know the World Wide Node name of the host to identify its entries in the table. 3 On one of the entries which grants the host access to a LUN, modify the permissions to include configure (C).
■ access.dat - HP-UX, Linux, and Windows (standard installation) ■ authorizedClients.dat - HP OpenView Storage Area Manager To set up remote client access: 1 On the Command View SDM host, open the configuration file in an ascii text editor.
used to populate the Launcher screen. If there is a functional array connected to the host that does not appear in the Launcher screen, it may be necessary to repeat the discovery process. To rediscover the arrays: 1 Check the disk array hardware and make sure it is operating properly, and that the array is connected to the host, switch, or hub. 2 Manually stop the HostAgent and OpenDIAL services. See "Starting/ Stopping HostAgent and OpenDIAL" on page 55. 3 Delete all files in the ..
index Symbols 100 100 100 A access.
capacity threshold setting using armmgr 146 changing thread count 31 checking array status using the GUI 89 client access configuration 40, 50 HostAgent operation 55 Windows 40 command conventions 98 command summary Command View 96 command syntax 98 Command View installing on HP OpenView Storage Area Manager 36 installing on HP-UX 30 installing on Linux 43 installing on Windows 36 Command View SDM command summary 96 Command View VA user interface see CVUI commands armcfg - configure array 102 armcopy 105, 1
D daemons HostAgent 55 OpenDIAL 55 data rebuild See armrbld command deactivating a LUN 103 deleting LUNs 104 Designator 100 device log See controller log DIMM designator M1-M2 100 disabling security (GUI) 91 discovery See armdiscover command disk auto include 142 disk drive designator D1-D15 100 disk enclosure designator JA0-JA5 100 disk enclosure port designator J1-J2 100 display variable, setting 52 downing a disk using armcfg 103 download firmware See armdownload downloading firmware on-line or off-line
H J host port behavior file, creating 133 setting using armmgr 141 host port designator H1-H2 100 HostAgent client operation 55 hostagent installing on OpenView SAM 40 hostname 99 hot spare mode setting using armmgr 142 hots port behavior table managing using the GUI 93 HP EMS 17 HP OpenView SAM authorized clients 50 HP-UX installing Command View 30 minimum system requirements 30 patches 30 software support 35 JBOD.
managing array capacity using the GUI 89 managing host port behavior table using the GUI 93 managing LUN security using the GUI 91 map reconstruction See armrecover command memory designator MP1 100 metrics, performance 151 minimum system requirements HP-UX 30 Linux 43 Windows 36 modular storage software products 20 MP1 100 MPE/iX 22 N NetWare 22 new host, adding to management configuration 56 non-native operating systems 22 NVRAM, disabling 146 non-native 22 other products 20 Out of Memory error 31 P pa
renaming a host 57 reset fibre channel 141 resetting array using armcfg 103 resetting the array using armmgr 145 resilience level setting using armmgr 143 restart array 145 restoring array configuration 49 S security armsecure command 191 LUN armsecure command 191 password armsecure command 193 user enabling 80 serial number 99 services HostAgent 55 OpenDIAL 55 setting display variable 52 shutdown array 145 SNMP applications 17 Solaris 22 solving problems 223 state log See usage log status, reporting See a
