HP P6000 Command View User Guide Abstract This document describes how to use HP P6000 Command View (formerly HP Command View EVA) to manage HP Enterprise Virtual Array models. It also describes how to use HP P6000 Performance Data Collector (formerly HP Command View EVAPerf) to monitor array performance. This document is intended for HP P6000 Command View software and HP P6000 Performance Data Collector users and administrators.
© Copyright 2004–2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Overview..................................................................................................7 Prerequisites.............................................................................................................................7 HP P6000 Command View software suite....................................................................................7 HP P6000 Command View features............................................................................................
Minimizing the number of snapshots....................................................................................41 Setting virtual disk cache to write-through before a snapshot or snapclone.................................41 Suspending a DR group before a making a snapshot of a virtual disk.......................................41 Minimizing simultaneous replication operations.....................................................................41 HP P6000 Continuous Access software....................
Changing system time causes your session to end.......................................................................64 Navigation pane lists duplicate arrays.......................................................................................65 Failed communication path between management server and array..............................................65 Error messages in the user interface..........................................................................................
11 Support and other resources.....................................................................94 Contacting HP........................................................................................................................94 HP technical support..........................................................................................................94 Subscription service............................................................................................................
1 Overview This chapter provides an overview of the HP P6000 Command View software suite. IMPORTANT: General references to HP P6000 Command View may also refer to earlier versions of HP Command View EVA. P6000 is the new branding for the Enterprise Virtual Array product family.
• HP P6000 Performance Advisor User Guide • HP P6000 SmartStart User Guide HP P6000 Command View features HP P6000 Command View enables you to: • Manage storage security and passwords • License storage systems • Provision storage to hosts • Replicate storage using HP P6000 Business Copy and HP P6000 Continuous Access • Maintain and manage storage systems • Monitor storage system events • Monitor performance data Server-based and array-based management HP P6000 Command View is available in
IMPORTANT: HP P6000 Command View relies on the IP address assigned to the server for management lock verification. Therefore, the HP P6000 Command View server must have a unique IP address to ensure proper control locking. Figure 1 Server-based configuration 1 5 4 3 2 6 1. LAN 4. Browsing computer 2. SAN 5. Hosts 3. Management server 6.
Figure 2 Array-based configuration 1 5 4 2 3 1. LAN 4. Browsing computer 2. SAN 5. Hosts 3. HP EVA4400 storage systems Figure 2 (page 10) shows multiple HP EVA4400 storage arrays and hosts in a Fibre Channel SAN. In this case, each EVA4400 storage array has a factory-installed instance of array-based HP P6000 Command View. Each HP EVA4400 storage array is also connected to a LAN so that users and administrators can browse to each HP P6000 Command View interface.
For more information, see the online help or the HP Management Integration Framework Administrator Guide and the HP Management Integration Framework Maintenance and Service Guide. User interface HP P6000 Command View uses a SPoG interface, which can display multiple HP P6000 storage software applications in a single browser window.
Point of view selectors Located on the lower left of the window, these selectors enable you to select the point of view that is displayed. The selector for the active point of view is colored orange. • When the storage systems point of view is selected, all of the managed and initialized storage systems in the Management Group are displayed in an expandable tree in the navigation pane.
Content pane The content pane displays information and actions that you can perform on the storage system or component that is selected in the Navigation pane. Aspect tabs The displayed aspect tabs depend on your configuration. They display organized content based on your HP storage applications. For example, the Management aspect tab includes content from the HP P6000 Command View application and the Performance tab includes content from the HP P6000 Performance Advisor application.
Content pane Displays information and actions that you can perform on the resource that you selected in the navigation pane. Aspect tabs The displayed aspect tabs depend on your configuration. They display organized content based on your HP storage applications. For example, the Management aspect tab includes content from the HP P6000 Command View application and the Performance tab includes content from the HP P6000 Performance Advisor application.
3. Enter a valid user name and password. This is the same user name and password to log onto the HP P6000 Control Panel. See the HP P6000 Control Panel User Guide. You can also launch HP P6000 Command View from the HP P6000 Control Panel GUI. Internet Protocol support HP P6000 Command View is designed for use with internet protocols as follows: • Server-based versions 8.0.2 and later—IPv4, IPv6, and mixed IPv4/IPv6 networks • Server-based versions earlier than 8.0.
2 Managing security and passwords This chapter explains how to use HP P6000 Command View to manage your storage environment. NOTE: See the HP P6000 Command View online help for detailed procedures related to managing your storage environment. When you install HP P6000 Command View, the initial folders are Virtual Disks, Hosts, Disk Groups, Data Replication, and Hardware. You can create subfolders to further organize and manage your hosts and virtual disks.
IMPORTANT: If your storage system is managed by an instance of server-based HP P6000 Command View, HP strongly recommends that you store or update the password in HP P6000 Command View immediately after creating or changing the password on the storage system. Password formats Storage systems with controller software versions 5.1xx or earlier • Passwords are not case sensitive and include exactly 8 characters. • The letters A–Z in upper or lower case are allowed.
Disabling management of a password-protected storage system Use this procedure to disable management of a password-protected storage system from an instance of server-based HP P6000 Command View. Considerations • You only need to perform this procedure if you no longer want to manage a password-protected storage system from an instance of HP P6000 Command View on a management server.
Reestablishing communication with a password-protected storage system A communication problem between an instance of server-based HP P6000 Command View and a password-protected storage system can be caused when the stored password in HP P6000 Command View does not match the password that is set on a storage system. This can occur when: • The password on a storage system has been changed. • Controller software on a storage system has been updated to a newer version.
2. Perform the following steps from the SIM server: a. Discover the HP P6000 Command View management server. Wait until the initial data collection for the attached arrays completes. b. c. d. Select the array from the SIM page. Select the Tools & link tab. Launch HP P6000 Command View using the URL of the HP P6000 Command View web-based element manager. An HP P6000 Command View login window opens. e. Enter your username and password. NOTE: 20 Subsequent logins do not prompt for username and password.
3 Licensing HP P6000/EVA storage systems Licenses to use and license keys License types The following types of licenses to use (LTUs) are available for HP P6000/EVA storage systems: • HP P6000 Command View LTUs. These LTUs are required to manage a given storage system with HP P6000 Command View. Each HP P6000 storage system must be licensed with the appropriate HP P6000 Command View LTUs to be in compliance with the End User License Agreement. • HP MPX200 LTUs.
Data migration licenses HP P6000 Command View and the MPX200 iSCSI controller support the Data Migration licenses. Figure 5 Initalized Storage System Properties window FCIP licenses The MPX200 iSCSI controller supports FCIP licenses. Model upgrade licensing Only data-in-place upgrades are supported. Model upgrade is supported as shown Table 1 (page 22).
Obtaining license keys To obtain a license: 1. Browse to HP Webware at http://webware.hp.com/. 2. Click Generate New Licenses. 3. Enter a username and password. 4. Enter the Order Number which can be found on your License Entitlement Certificate. 5. Select the licenses to purchase, and provide the WWN. For more information about HP P6000 Command View LTUs, browse to: http://h18006.www1.hp.com/products/storage/software/cmdvieweva/index.html Under Product Information, click CV EVA Licensing.
Validating the license Validation occurs automatically to verify the license installation. If there is a problem with the installation, one of the following messages appears: Message Description ERROR: License String is not regular structure please install the correct license string The license text does not fit the standard structure of a license text, or contains error in checksum/any error. ERROR: Cannot add expired license to EVA You have entered an expired temporary license.
4. Click Import Licenses to complete the operation. Deleting incorrectly entered license keys If a license key for an array is entered incorrectly (for example, a license is entered with the correct WWN, but with the incorrect model number), the license will appear under the Licensing tab but the licensed option might not work properly. Enabling a licensed option can include installing multiple license keys.
4 Provisioning storage Provisioning is the industry-standard term for providing networked storage to application servers. With HP P6000/EVA storage systems, provisioning includes the following general steps: 1. Creating one or more disk groups on a storage system. 2. Creating virtual disks within disk groups and assigning attributes, such as size and redundancy level. 3. Adding hosts as consumers of the storage on a storage system. 4.
Disk types The disk type specifies the type of physical disk drives that can be included in a disk group. The types are: Online disk type. All physical drives must be Fibre Channel or enterprise SAS drives. This disk type provides first tier performance and reliability. Near-online disk type. All physical drives are lower cost, lower performance hybrid Fibre Channel or midline SAS disk drives. Hybrid drives are dual ported, Fibre Attached Technology Adapted (FATA) drives.
Number of physical disks in a group • With online and near-online disk types, the minimum number of physical disks is 8. • With the solid state drive disk type, the minimum number of physical disks is 6. • If the number of disks is not specified when creating a disk group, the minimum is assigned. If the minimum number of disks is not available, the disk group cannot be created. • There is no maximum number of physical disks.
• Available, Vraid5. Shows the estimated capacity, if the entire disk group was used for Vraid5 virtual disks. • Available, Vraid6. Shows the estimated capacity, if the entire disk group was used for Vraid6 virtual disks. XCS 10000000 • Total capacity. Shows the formatted physical disk drive capacity of the disk group. • Allocated capacity. Shows the amount of disk group capacity that is being used for virtual disks. • Available capacity (estimated).
Virtual disks HP P6000/EVA storage systems use a form of virtualization called virtual disks (vdisks) to store data. Host computers see virtual disks as real storage objects, exactly as they would see physical disks with the same characteristics. Newly installed HP EVA storage systems are not pre-configured with virtual disks. After you initialize the storage system and create disk groups, you can create virtual disks in the sizes and Vraid types that you need.
NOTE: The GUI only displays action buttons that are supported in your configuration. Considerations CAUTION: Ensure that your host operating system can handle changes in volume size before you change the underlying virtual disk size. Changing the size on some operating systems can cause instability or data loss. • XCS 10000000 supports online migration without disrupting host workload.
Hosts A host is a computer that runs user applications that consume storage on a networked storage system. There are three types of hosts—Fibre Channel (FC), Fibre Channel over Ethernet (FCoE), and iSCSI. • FC hosts connect to a fabric through Fibre Channel adapters (FCAs) and access storage directly through the array controllers. • FCoE hosts connect to the array through an iSCSI/FCoE module in the P6000 controller (01 or 02).
• You can add a host by specifying an IP address (IPv4 or IPv6), a fully qualified domain name (FQDN), or a host alias. • If you attempt to add a host without providing an IP address, a confirmation window opens. • You can define the number of host ports and other parameters in HP P6000 Command View after the host is added. Presentation Presentation is the act of making a virtual disk known to a host so that I/O to the disk can occur.
space allocated does not need to be contiguous. In the event that the allocated capacity reaches the physical disk capacity, the write operation fails.
5 Replicating storage Replication is an industry-standard term for making copies or backing up data. With HP P6000/EVA storage systems, entire virtual disks can be replicated locally or remotely using a variety of methods: • HP P6000 Business Copy (local replication). Make local copies of virtual disks using snapclones, snapshots, mirrorclones and preallocated containers. Replicated virtual disks are located on the same storage system as the source. • HP P6000 Continuous Access (remote replication).
Snapclones cannot be created when the disk to be replicated is: • A snapshot • A disk that has a snapshot or mirrorclone • In the process of normalizing (snapclone in progress) or being deleted (P6000 Command View running XCS 10000000 or earlier) See also, “Optimizing snap creation” (page 40). Snapshots A snapshot is a dependent point-in-time copy of a virtual disk. It is dependent because data is not actually copied to the snapshot until it is overwritten on the source.
capacity available to create virtual disks decreases. Before you allocate space for new virtual disks, ensure that you reserve enough space for all demand-allocated snapshots in the disk group. The capacity required for a demand-allocated snapshot depends on how much of the source disk is modified. This value is unique for each application, but can range from 0% to 100% of the source disk capacity.
• XCS 10000000 supports online mirrorclone migration, which allows you to switch the roles of a source virtual disk with its synchronized mirrorclone. See “Mirrorclone migration” (page 33). • A mirrorclone can be presented only if the mirror link is stopped (fractured). For more information, see the HP P6000 Replication Solutions Manager Release Notes. A mirrorclone cannot be created if the intended source virtual disk is: • A snapshot or has any snapshots.
Mirrorclone states The following mirrorclone states are reported by the replication manager. Mirrorclone state Remarks Fractured There is no replication activity between the mirrorclone virtual disk and its source virtual disk. At the instant of the fracture, data on the mirrorclone is identical to its source. After a fracture, data on the two disks might no longer be identical due to host I/O to the source or the mirrorclone.
Optimizing replication performance Planning for host I/O workloads For the best snapshot and snapclone performance, create and delete snapshots and snapclones during low-demand periods for host I/O, or configure the array to meet performance demands during snapshot and snapclone activities. • Snapshot and synchronized mirrorclone activity is driven by the host I/O and must compete with the I/O workload on the disks. • Snapclones and fractured mirrorclones operate independently of host I/O workload.
Minimizing snapclone workloads A snapclone copies the entire source disk without stopping. However, creating a snapclone creates an additional workload on the snapclone's disk group while the data is being copied. You may observe an increase in command response time and a decrease in the disk group's maximum I/O during the copy operation. This performance impact ceases when the copy operation completes. For optimum snapclone performance: • Create snapclones during low-demand periods.
HP P6000 Continuous Access software HP P6000 Continuous Access is a licensed feature of HP P6000/EVA storage systems that enables you to: • Create DR groups and remote copies of virtual disks on two separate HP P6000/EVA storage systems. • Fail over (reverse) the direction of replication between storage systems. • Suspend and resume remote replication. • Configure various DR group parameters. NOTE: This information about HP P6000 Continuous Access software is abridged.
(only a portion of the display is shown) Creating DR groups You can use server-based HP P6000 Command View to create DR groups, remotely replicate virtual disks from one storage system to another, and perform actions. Array-based HP P6000 Command View only allows you to view DR groups that are on that array. NOTE: This information about HP P6000 Continuous Access software is abridged. For more information, see the HP P6000 Continuous Access Implementation Guide and the HP P6000 Command View online help.
Fibre Channel switches typically offer two types of frame routing between N_Ports: • Source ID/Destination ID (SID/DID) routing, which transfers all exchanges through the fabric using the same path • Exchange-based routing, which transfers all frames within an exchange using the same path, but other exchanges may use alternate paths NOTE: B-class switches refer to SID/DID protocol as in-order delivery routing. C-class switches refer to SID/DID protocol as flow-based load balancing .
6 Maintaining and managing HP P6000/EVA storage systems This chapter describes how to use HP P6000 Command View to maintain the arrays. Initializing storage systems If Insight Remote Support is installed on the management server (server-based management), see the documentation for instructions on adding entitlement details for the new array at: http://h18023.www1.hp.com/support/svctools/webes/ When you install an array, it appears as an uninitialized storage system.
4. Enter the following commands at the system prompts: C:\Program Files\Hewlett-Packard\svctools\common\bin> desta snmp on Which host(s) should receive service traps for logged calls (comma-separated) [127.0.0.1]: Which Trap type to use (Enter 2 or 3) [null]: 3 SNMP Service Trap notification is now enabled. The desta snmp command enables or disables support notification to management applications.
3. Under Service, select elect Configure User-Initiated Service Mode (USIM). The Configure User-Initiated Service Mode page opens. 4. 5. 6. Enter your name and reason for suppressing support calls in the Reason box. Enter the amount of time for the storage system to remain in service mode. Click Start service mode. When service mode is enabled, the Configure User-Initiated Service Mode window displays Support calls to HP disabled and the amount of time remaining in service mode.
Figure 7 HSV210A controller rear view Figure 8 HSV300 controller rear view Figure 9 HSV400 controller rear view Figure 10 HSV450 rear view Figure 11 HSV340/HSV360 controller enclosure (FC version) rear view 48 Maintaining and managing HP P6000/EVA storage systems
Figure 12 HSV340/HSV360 controller enclosure (FC-iSCSI version) rear view Figure 13 P6000 EVA iSCSI/FCoE controller enclosure (rear view) Hardware Depending on the array model, hardware can typically include iSCSI devices, racks (cabinets), controller enclosures, and disk enclosures (physical disk drives). Working with hardware in HP P6000 Command View The hardware folder for an HP P6000/EVA storage system includes all detected hardware.
(only a portion of the display is shown) Verifying hardware status To view status of a hardware component, select the component and review its properties page. See the HP P6000 Command View online help for detailed procedures. Storage system identity information The Controller Enclosure Properties page, General tab lists information about your storage system, including model, product number, and serial numbers.
4. Click Perform Remote Service Test.
NOTE: If an unmanaged array is moved from the initialized state to an uninitialized state by the managing HP P6000 Command View instance, the passive HP P6000 Command View instance does not display this change until the node is clicked or the array is refreshed on the navigation pane. Configuring iSCSI devices You can use HP P6000 Command View to manage EVAs that include iSCSI devices (called the iSCSI connectivity option). If your configuration includes iSCSI controllers, configure them as follows: 1.
7 Monitoring storage system events This chapter describes how to manage events using HP P6000 Command View. Events overview Events track the progress of actions, both normal and exceptional, that occur on the array. Examples of typical events are creating virtual disks or initializing an array. Examples of exceptional events are an incomplete function or a reduction in array capabilities. Normal events are more common than exceptional events.
A normal event is informational and requires no action by you. An example of a normal event would be the controller reporting that creation of a virtual disk has completed. An example of an exceptional event would be a disk enclosure that has lost communication on a Fibre Channel loop. CAUTION: Uninitializing an array deletes all of the controller events cached in the controllers. For more information about uninitializing an array, see “Uninitializing storage systems” (page 47).
The following information is provided for each management server event: • Date/Time—The date and time that the event occurred. • Severity—The severity types are informational, critical, warning, and undetermined. • Event Source—Name of the controller on which the event occurred. The name and worldwide ID of all controllers appears at the top of the event log. • Description—The text description of the event.
2. 3. 4. Select Configure SNMP/event log notification. Select Configure SNMP host notification list. Click Modify host list. The Modify Host Notification window opens. 5. In the Host Name box, enter the domain name or IP address of the host. The designated host should begin receiving SNMP traps. If the host is not receiving traps, restart the HP P6000 Command View service. Applying a customized host notification list To apply a customized host notification list to HP P6000 Command View: 1.
7. When you finish configuring event notification, click OK. The System Options window opens. You will now receive only events of the severity you selected. Selecting individual events To select which individual events cause an SNMP notification message to be sent: 1. From the Initialized Storage System Properties window, click System options. The System Options window opens. 2. 3. 4. 5. Under notification, select Configure SNMP/event log notification.
To obtain the updated parse file: 1. Contact HP Support and request an updated parse file. For contact information, see “HP technical support” (page 94). HP Support will email the parse file to you and instruct you where to store it on the management server. 2. From the Initialized Storage System Properties window, click View events. The View Events window opens. 3. 4. Select either Controller Event Log or Controller Termination Event Log as the event type. On the event log window, click Send parse file.
Sending the event file If you contact HP Support for assistance, be prepared to provide a copy of the current event file, which is the current output translated from the controller. To send the event file to HP Support: 1. Go to the appropriate event log: 2. 3. • In Management, click Event file. • In Controller Event, click Log file. • In Controller Termination Event, click Log file. When prompted, save the file to your local hard drive. Email the file to the support technician.
8 Configuring HP P6000 Command View (advanced tasks) This chapter describes configuration options for the HP P6000 Command View user interface and is for advanced tuning only. For information about other configuration options available from the Server options window, see the HP P6000 Command View online help. Setting user interface options To set user interface options: 1. Select the Settings point of view. 2. In the Session pane, click Management Options. The Management Options window opens. 3.
Setting audit logging options With server-based management, use the Audit Logging Options feature to capture activities that occur in the HP P6000 Command View user interface.
IMPORTANT: If you change the log location to the local server, you must enter the new location in the Log location box in the Log to a file section of the Audit Logging Options window in the user interface, and then click Save Changes. Selecting Disabled in the Log to a file section disables the audit log completely. It does not disable logging to a remote server only. If, for some reason, the logs cannot be placed in the requested location, an error message is displayed.
To change the user name and password for HP P6000 Command View array-based management: 1. Open the browser. 2. Enter the following: https://management_module_IP_address:2373 NOTE: If you are running management module firmware versions earlier than 0001.1000, the IP address for the port will be 2372, rather than 2373. 3. 4. Log into the HP P6000 Control Panel. To change administrator login credentials: a. Select Configure Administrator login options. b.
9 Troubleshooting HP P6000 Command View This chapter provides recommendations for optimizing performance and describes issues you may encounter and how to resolve them. Optimizing performance Consider the following tips to optimize performance: • Minimize the number of non-administrative users connected to the array. • Open only one GUI session to HP P6000 Command View at a time.
Explanation / Resolution Login sessions expire after a period of time. Advancing the system clock forces the HP 6000 Command View session to expire and you must log back in. Navigation pane lists duplicate arrays Problem Arrays that were zoned out and then imported back to appear twice in the HP P6000 Command View navigation pane with Windows system based management. Explanation / Resolution Restarting the HP P6000 Command View instance that the arrays were zoned away from removes the duplicate arrays.
Error messages in the user interface Problem When performing tasks in the user interface, an error message such as This page cannot be displayed appears. Explanation / Resolution Verify that the browser settings are correct. For more information, see the browser settings in the HP P6000 Command View Installation Guide. If the browser settings are correct, clear the browser cache: For 1. 2. 3. Internet Explorer: Select Tools→Internet Options. On the General tab, under Browsing History, click Delete.
Failed transceiver When a transceiver (or Gigabit Interface Converter (GBIC)) fails, the Disk Enclosure Properties window displays the following information: • On the Power tab, the operational state displays Good. • On the Cooling tab, the status of the sensors displays OK. • On the I/O-Comm tab, the operational state of the I/O modules displays Bad or Not Installed. See the user guide for your controller to view the event log entries for this entity.
1. 2. Review the client filter list and do one of the following: • If the denied computer is not on the client list and you want to allow access, add the client computer's IP address to the list. • If you want to allow access for all computers, disable the client filter. If the denied computer is on the list, review the following: a. Proxy server configuration.
Version numbers differ Problem The HP P6000 Command View version displays inconsistently across different windows. Explanation / Resolution The appearance of the HP P6000 Command View version differs, depending on which window you are accessing. Sometimes the date is displayed; other times the build number is displayed. For example, the Login page displays 09.00.00.090131 (date), and Add/Remove Programs displays the master installer build number (9.0.0.88) instead of the HP P6000 Command View build number.
10 Monitoring array performance using HP P6000 Performance Data Collector With HP P6000 Command View server-based management, you can use HP P6000 Performance Data Collector (formerly HP Command View EVAPerf) to monitor and display array performance metrics from a command line interface or a graphical user interface.
These components are applicable only when the server and client are installed together. When installed individually, the contents of the directory vary, based on the component installed. IMPORTANT: When a controller reboots, the connection between the client to the server must be reestablished.
Table 2 HP P6000 Performance Data Collector valid object_type values (continued) Value of object_type Information displayed by the command state_disk Disk state changes state_drm DRM group state changes state_array Array state changes NOTE: Start_time and end_time are in mm-dd-yyyy hh-mm-ss format. The object_id is an optional parameter.
HP P6000 Performance Data Collector prompts you for a password. Note that: • This command accepts the HP P6000 Command View access information provided as is. It does not validate the information by connecting to the specified HP P6000 Command View. To verify whether the provided information can be used to communicate with the specified HP P6000 Command View, another command is provided. • This command results in the overwriting of any previously configured HP P6000 Command View access information.
• By default, a directory with the name performance_history is created in the install directory, where all the state and performance data is logged. If this is changed, you must ensure that the directory specified as the root directory for logging exists. Otherwise, state and performance data will not be logged. • Minimum number of days for which logs must be retained is 1. Specifying any value other than yes for perf_logging and state_logging parameters results in logging being turned off.
NOTE: HP recommends that you not use the remote logging feature for array performance logging. The HP P6000 Performance Data Collector client and server should be running on the same system to gather logging for performance and state data. Table 4 HP P6000 Performance Data Collector logging configuration file parameters Parameter Description state_logging Controls the tracking and logging of state changes. If set to yes, the performance data logging must be enabled. Default is no.
username is the account username on the server running the HP P6000 Performance Data Collector service. The user is a member of HP Storage Admins or HP Storage Users group. This is required only if SSL is enabled. The user is prompted for a password. usessl is the switch that will enable an open SSL connection. If SSL is enabled, the user account used for logging in should belong to either the HP Storage Admins or HP Storage Users group. The parameter evapdcs.
Backward compatibility Table 5 (page 77) shows the HP P6000 Performance Data Collector compatibility matrix. Table 5 HP P6000 Performance Data Collector server-client compatibility matrix HP Command View EVAPerf remote client version HP Command View EVAPerf Possibility of remote service version collection of metrics 8.0 or later 7.0 or earlier Yes Prohibited commands do not work. 7.0 or earlier 7.0 or earlier No None 8.0 or later 8.0 or later Yes Prohibited commands do not work. 7.
2. Enter the evaperf fn [short] command. The fnames.conf file is created. Any friendly name information that exists for the management servers running HP P6000 Command View and listed in the fnamehosts.conf file is extracted from HP P6000 Command View and stored in the fnames.conf file, located in INSTALLROOT.
Using short names If the friendly names you created in HP P6000 Command View are impractical for the HP P6000 Performance Data Collector command line interface, you can substitute contractions for full names in the fnames.dict file. When you install HP P6000 Performance Data Collector, the fnames_sample.dict file is also installed. You can either: • Rename this file to fnames.dict and modify its contents to include the short names. • Create a separate file called fnames.dict using a standard editor.
Using the command line interface You can use the HP P6000 Performance Data Collector command line interface to display array performance data in a tabular format. The procedures in this section assume you are familiar with command line interfaces. Viewing arrays To view arrays that are visible to HP P6000 Performance Data Collector: 1. Launch HP P6000 Performance Data Collector from the desktop icon. 2. Enter the following command: evaperf ls The visible arrays are listed.
Filtering data You can filter the data that is collected for specific items, such as a word or a host port name. For example, enter the following command: evaperf as -sz array1 array2 -fd test The output indicates where test appears on array 1 or array 2. Specifying data output in multiple files You can generate output for several commands and save the output for each command in a separate file, organized by array.
After generating the TLViz-formatted files from evaperf all output, you can build the Microsoft Access database EVADATA.MDB: 1. Click Browse and select the evaerf all command out file. 2. Select Build Access Database. 3. Open the EVADATA.MDB file to view the database tables. HP TLViz has limited space to display names (30 characters maximum). Included with the TLViz-formatted files are map files (PDISK-MAP.txt and VDISK-MAP.
Table 6 HP P6000 Performance Data Collector commands (continued) Command Description fn [short] Performs the following series of tasks: • Scans the hosts on the friendly name host list. • Queries HP P6000 Command View on each host for known friendly name information. • Adds the friendly name information found to the fnames.conf file. h, help, or evaperf without Displays help for HP P6000 Performance Data Collector. a modifier hc Displays host connection information.
Table 6 HP P6000 Performance Data Collector commands (continued) Command Description vdrlg [lunwwn] Graphs virtual disk read latency histograms for all LUNs or a specific WWN. This command is available on the HSV200 series of controllers onward. vdwl Displays virtual disk write latency histograms. This command is available on the HSV200 series of controllers onward. vdwlg [lunwwn] Graphs virtual disk write latency histograms for all LUNS or a specific WWN.
Table 7 HP P6000 Performance Data Collector command modifiers (continued) Modifier Description -nots Specifies that a time stamp not be included in the CSV output. -od Specifies the directory in which the output files from the mof command are saved. -szarray [array]* Limits array data collection to the specified arrays. You must enter at least one array and you can use this modifier with any command. When specifying arrays, you can use either the array's WWN or friendly name.
1. Start Windows Performance Monitor. The Performance window opens. 2. Right-click in the graphics area. A menu opens. 3. Select Add Counters. The Add Counters dialog box opens. To view a description of a counter, select a counter, and then click Explain. 4. 5. 86 Click Use local computer counters and, in the adjacent box, select the host on which HP P6000 Performance Data Collector is running. From the Performance object box, select an object to monitor (for example, HP EVA Storage Array).
6. 7. 8. Click All counters, or select counters to view. Click All instances, or select instances to view. Click Add to add the counters to the window. The utility begins displaying the performance metrics of the selected object. 9. To add other objects, repeat the steps. To remove metrics, select the metric from the list and click the remove icon, which appears as an X. 10. To close the utility, click Close.
The following identifying information is common to several objects: • Ctlr—The controller for which metrics are being reported. This field shows the last four digits of the controller serial number. • Node—The array from which data has been collected. • GroupID—The disk group to which the virtual or physical disk belongs. Not all metrics that are available in the command line interface are available in Windows Performance Monitor.
The counters are: • Read Hit Req/s—The number of read requests per second completed from the array cache memory. Data may reside in the cache memory due to a previous cache miss or because of a prefetch operation generated by a sequential read data stream. • Read Hit MB/s—The rate at which data is read from the array cache memory because of read hit requests. • Read Hit Latency—The average time it takes to complete a read request (from initiation to information receipt) from the array cache memory.
• Average Read Hit Latency—The average time it takes to complete a read request (from initiation to information receipt) from the array cache memory. • Total Read Miss Req/s—The total number of read requests (per second) that failed to complete from the array cache memory and were completed from physical disks instead. • Total Read Miss Data Rate—The total rate at which data is read from physical disks because the data was not present in the array cache memory.
• Read Latency—The amount of time it takes to complete a read request (from initiation to information receipt) through a host port. The time is an average of the read request latency for all virtual disks accessed through this port, and includes cache hits and misses. • Write Req/s—The number of write requests (per second) completed from each host port. • Write MB/s—The rate at which data is written from each host port.
The counters are: • Average Drive Queue Depth—The average number of all active requests to each disk in the disk group, over all the disks in the disk group. • Average Drive Latency—The average time between when a data transfer command is sent to a disk and when command completion is returned from the disk. The time is not separated into read and write latencies.
• Write In MB/s—The rate at which data is written to an array because of write activity to the members of the source array. The write activity includes host writes, merges, and replication retries. A merge is an action initiated by the source array to write new host data that has been received and logged while a replication write to the destination array was interrupted, and now has been restored.
11 Support and other resources Contacting HP HP technical support Telephone numbers for worldwide technical support are listed on the HP support website: http://www.hp.com/support/ Collect the following information before calling: • Technical support registration number (if applicable) • Product serial numbers • Product model names and numbers • Error messages • Operating system type and revision level • Detailed questions For continuous quality improvement, calls be recorded or monitored.
Websites • HP: http://www.hp.com • HP Storage: http://www.hp.com/go/storage • HP Software Downloads: http://www.hp.com/support/downloads • HP Software Depot: http://www.software.hp.com • HP Single Point of Connectivity Knowledge (SPOCK): http://www.hp.com/storage/spock • HP SAN manuals: http://www.hp.com/go/sdgmanuals • HP Support Center: http://h20566.www2.hp.
A HP array event code formats and descriptions This appendix describes how the hexadecimal number for the event code is formed. Event code format Controller and controller termination event codes appear as 32–bit hexadecimal numbers (for example, 060f4013). The bits in the event code differ slightly for each controller event type. The bits of a controller event have the following format: Table 9 HP array controller event code bits 31............24 23.........16 15........8 7........................
Table 12 HP array software component IDs (continued) ID Description 4 Fault Management 6 Fibre Channel Services 7 Container Services 8 RAID Services 9 Storage System Management Interface b System Services c Data Replication Manager Component d Disk Enclosure Environmental Monitoring Unit Services e System Data Center 42 Host Port 80 Metadata Utilities 83 Diagnostic Operations Generator 84 Diagnostic Runtime Services Corrective action codes You can view the complete list of correc
Table 13 HP array event information packet (EIP) types (continued) Code Title Description 0D Executive Services System Time Change A change in system time occurred. 0E Storage System Management Interface Entity Creation or Deletion A Storage System Management Interface entity was created or deleted. 0F Storage System Management Interface Entity Attribute An attribute of a Storage System Management Change Interface entity has changed.
Dump/restart control codes Table 15 HP array dump/restart control codes Code Description 0 Perform crash dump then restart. 1 Do not perform crash dump, just restart. 2 Perform a crash dump and do not restart. 3 Do not perform crash dump and do not restart.
Glossary This glossary defines terms that are used in this guide or are related to the software. A array A synonym of storage array, storage system, and virtual array. A group of disks in one or more disk enclosures combined with controller software that presents disk storage capacity as one or more virtual disks. array-based management A management structure in which HP P6000 Command View is installed on the management module within the array controller enclosure.
J job A repeatable custom script that automates replication tasks. A job can be simple (for example, create a DR group) or complex (for example, perform cascaded replication). Jobs can be run from the GUI, from the command line, from batch files, or by a scheduler. M management server A server on which HP management software is installed. MIF Management Integration Framework. mirrorclone A copy of a virtual disk that is continually updated to reflect changes in the source.
V virtual array Synonymous with disk array and storage system, a group of disks in one or more disk enclosures combined with control software that presents disk storage capacity as one or more virtual disks. See also virtual disk. virtual disk Variable disk capacity that is defined and managed by the array controller and presented to hosts as a disk. Can be called Vdisk in the user interface.
Index A adding hosts, 32 array initializing, 45 maintaining, 45 monitoring performance, 70 shutting down, 47 starting, 47 uninitializing, 47 verifying health and status, 50 B blower power supply, failed, 67 browser refreshing, 66 right-click menu, 64 C cache setting mode, 41 CLI HP P6000 Performance Data Collector, 80 commands HP P6000 Performance Data Collector, 82 communication path failed, 65 configuring iSCSI devices, 52 container guidelines, 39 containers creating snapclones and snapshots, 40 definit
H O help obtaining, 94 host notification, 55 customized notification list, 56 individual hosts, 55 hosts adding, 32 empty controller host ports, 66 HP support website, 94 technical support, 94 HP P6000 Continuous Access , 42 HP P6000 Performance Data Collector, 70 command line interface, 80 command modifiers, 84 commands, 82 components, 70 displaying metrics, 85 filtering data, 87 friendly names, 77 overview, 70 TLViz formatter, 81 using Windows Performance Monitor, 85 objects and counters, Windows Perfo
demand allocated, 36 description, 36 in jobs, 41 of destination virtual disks, 41 optimizing performance, 41 using containers, 40 specifying the output, 80 storage system initializing, 45 maintaining, 45 monitoring performance, 70 shutting down, 47 starting, 47 uninitializing, 47 verifying health and status, 50 Storage System Scripting Utility, 7 Subscriber's Choice, HP, 94 symbols in text, 95 T technical support HP, 94 text symbols, 95 TLViz, 81 troubleshooting, 64 empty controller host ports, 66 failed b
