HP P6000 User Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Desktop
  5. Pavilion p6000 - Desktop PC
  6. User manual

HP P6000 User Manual

Hewlett-packard personal computer user manual
Hide thumbs Also See for P6000:
Table of Contents

Advertisement

Quick Links

See also: Reference Manual , Reference
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.
HP Part Number: T5494-96527
Published: February 2012
Edition: 14

Advertisement

Table of Contents
loading

Related Manuals for HP P6000

Summary of Contents for HP P6000

  • Page 1 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.
  • Page 2 The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

  • Page 3: Table Of Contents

    Settings point of view...13 Accessing HP P6000 Command View...14 Internet Protocol support...15 2 Managing security and passwords...16 Server-based HP P6000 Command View security groups...16 Array-based HP P6000 Command View security groups...16 Password protection for storage systems...16 Enabling management of a password-protected storage system...17 Disabling management of a password-protected storage system...17...
  • Page 4 Setting a remote location for audit logs...60 Changing port and timeout parameters...61 Changing the login credentials (array-based management)...61 Running HP P6000 Command View in a multi-homed environment...62 9 Troubleshooting HP P6000 Command View...63 Optimizing performance...63 Restarting the HP P6000 Command View service...63 Using the right-click menu...63...
  • Page 5 10 Monitoring array performance using HP P6000 Performance Data Collector...69 Components...69 HP P6000 Performance Data Collector server side logging of performance and state data...70 Performance and state logs retrieval from HP P6000 Performance Data Collector client...70 Configuration file for performance and state data logging...72 Configuring HP P6000 Performance Data Collector...73...
  • Page 6 Documentation feedback...93 Product feedback...93 Related information...93 Documentation...93 Websites...94 Typographical conventions ...94 A HP array event code formats and descriptions...95 Event code format...95 Event code types and descriptions...95 Software component IDs...95 Corrective action codes...96 Event information packet (EIP) types...96 Coupled crash control codes...97 Dump/restart control codes...98...

  • Page 7: Overview

    Earlier versions of HP P6000 Command View were required to be installed on a management server. HP P6000 Command View EVA and Command View EVA 8.1 or later is installed on the management module (9.4 or later on the P6300/P6500 EVAs), eliminating the need for a separate management server.

  • Page 8: Hp P6000 Command View Features

    9). All components of the software suite (HP P6000 Command View, HP P6000 Performance Data Collector, HP Storage System Scripting Utility, HP P6000 Performance Advisor, and SMI-S EVA) can be installed on the server. Server-based management can be used with all P6000 storage arrays.
  • Page 9 The management server is also connected to a LAN so that users and administrators can browse to the HP P6000 Command View interface. HP P6000 Command View does not require hosts to be connected to the LAN. However, a LAN connection can be a requirement of other HP server-based applications.

  • Page 10: Hp Management Integration Framework

    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. HP P6000 Command View does not require hosts to be connected to the LAN. However, a LAN connection can be a requirement of other HP server-based applications.

  • Page 11: User Interface

    If you have Performance Advisor installed, you can view storage system performance information by clicking the Performance tab. The settings point of view is the primary means of viewing and changing options in HP P6000 Command View and HP P6000 Performance Advisor.

  • Page 12: Storage Systems Point Of View

    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.

  • Page 13: Settings Point Of View

    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. For more information about the Performance tab, see HP P6000 Performance Advisor User Guide.

  • Page 14: Accessing Hp P6000 Command View

    Browsing to server-based HP P6000 Command View Open a browser. Using the network name or IP address of the server on which HP P6000 Command View is installed, enter: https://server_name or IP_address:2374 The HP P6000 Command View login window opens.

  • Page 15: Internet Protocol Support

    For server-based configurations, if IPv4 and IPv6 are installed on a single system, HP P6000 Command View starts on the IPv4 address by default. If you want to start HP P6000 Command View on a specific address, you must add the address entry under the webserver section of the cveva.cfg configuration file.

  • Page 16: Managing Security And Passwords

    See the HP Enterprise Virtual Array User Guide. For HP EVA4400, P6300 EVA, and P6500 EVA models, password protection is set using the HP P6000 Control Panel. See the HP P6000 Control Panel User Guide or the HP P6000 Control Panel online help.

  • Page 17: Enabling Management Of A Password-Protected Storage System

    HP P6000 Command View. Considerations You only need to perform this procedure if an instance of HP P6000 Command View on a management server is not enabled to manage a password-protected storage system and you want it to.

  • Page 18: Setting A Password For Hp Eva Storage Systems

    This procedure does not remove or clear a password from the storage system itself. Storage system passwords can only be removed or cleared from an OCP or an HP P6000 Control Panel. To disable HP P6000 Command View to manage a password-protected storage system from the settings point of view: In the session pane, click Management Options.

  • Page 19: Single Sign-On From Hp Systems Insight Manager

    Single sign-on (SSO) enables you to have a single login from HP Systems Insight Manager (HP SIM) by establishing a trust relationship with HP P6000 Command View. A user on HP SIM can go directly to HP P6000 Command View without having to re-enter a user name and password.

  • Page 20: Licensing Hp P6000/Eva Storage Systems

    P6000 Dynamic Capacity Management and thin provisioning. The instant-on key is valid for all arrays managed by an HP P6000 Command View server and enables HP P6000 Command View, HP P6000 Business Copy, and HP P6000 Continuous Access with unlimited capacity for 60 days from the first use.
  • Page 21 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 21).

  • Page 22: Activating An Instant-On License

    Configuring email to receive LTUs If you receive a license by email, HP recommends that you configure your email application to use ASCII format to preserve the format of the information. To change an Microsoft Outlook message format to ASCII: In Outlook, select Tools Options.

  • Page 23: Importing Licenses

    WRSX 4JUN M2UH KMDX CFNX E3QS Paste the license key into the text box. Click Install Licenses. For an alternative method of adding a license, see the HP P6000 Enterprise Virtual Array License Key Installation Instructions. Importing licenses You can import licenses that were exported previously. See From the settings view, click Management Options.

  • Page 24: Deleting Incorrectly Entered License Keys

    The Remove licenses page appears. Select the feature for which to remove licenses. Click Remove Licenses. Reinstall the license keys. For more information, see HP P6000 Enterprise Virtual Array License Key Installation Instructions. Displaying temporary license expiration date You can view the expiration date for the temporary license on the Initialized Storage System Properties page section of the Licensing tab.

  • Page 25: Provisioning Storage

    Working with disk groups The disk group folder for an HP P6000/EVA storage system includes the default disk group, other disk groups that have been created, plus a folder of ungrouped physical disks that are not members of any disk group.

  • Page 26: General Guidelines

    Solid state drive disk type. All physical drives must be solid state drives (SSD). This disk type provides first tier, very high performance and reliability. Disk type support varies with HP XCS controller software versions. The following table summarizes support and typical uses.

  • Page 27: Disk Group Capacity

    If you change the occupancy alarm default values, the critical alarm level must be greater than the warning alarm level. NOTE: HP P6000 Command View 9.x and earlier have a warning alarm level only. The default value is 90%. Disk group capacity Disk group capacity (in GB) is presented differently for different versions of HP XCS controller software.

  • Page 28: Redundancy (Vraid) Levels

    Vraid level on arrays running XCS 10000000 or later, see 32). NOTE: HP strongly recommends that you use Vraid6 if you are using disk drives with a physical capacity of 1TB or greater. Vraid levels are: Vraid0. Is optimized for speed and disk space utilization, but provides no redundancy.

  • Page 29: Virtual Disks

    In HP P6000 Command View 9.3 or later, when a LUN is provisioned with Vraid0 redundancy, the HP P6000 Command View GUI displays an R0 icon on the LUN. If you select Vraid0 when creating a LUN HP P6000 Command View displays a confirmation window to verify that redundancy is not required.
  • Page 30 Do not lock a virtual disk that was created by another user or by an application. ◦ Besides adding a lock owner comment, HP recommends that you use the virtual disk's general comment field to clearly indicate the owner and purpose of the lock. This provides a more permanent record about the lock, should the lock be disabled later.

  • Page 31: Hosts

    P6000 controller (01 or 02). Working with hosts in HP P6000 Command View The hosts folder for an HP P6000/EVA storage system displays all hosts that have been explicitly added to the HP P6000 Command View interface. You can further organize hosts into subfolders that you create and name.

  • Page 32: Presentation

    It is possible to create and present a virtual disk in a single step; however, HP recommends that you create a virtual disk first, then present it after it is created. This leaves HP P6000 Command View free to perform other tasks.
  • Page 33 A storage administrator is planning to create two virtual disks for two new host applications. His HP P6000 storage system currently has a total capacity of 10 TB, with 6 TB unused disk space. The administrator determines that each host application initially requires 2 TB of disk space, but eventually, the host applications will require 4 TB of space.

  • Page 34: Replicating Storage

    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.

  • Page 35: Snapshots

    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 36: Mirrorclones

    If you do not know the capacity required for a demand-allocated snapshot, HP recommends that you reserve a minimum of 10% of the capacity of the source virtual disk times the number of snapshots of the source disk. For example, if you have two demand-allocated snapshots of a 500 GB virtual disk, you would reserve 100 GB (500 GB x 10% x 2) of usable capacity.
  • Page 37 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. Has any snapclones that are in the process of being normalized (P6000 Command View 10000000 or earlier). See also, “Optimizing snap creation”...

  • Page 38: Containers

    Mirrorclone states The following mirrorclone states are reported by the replication manager. Mirrorclone state Fractured Restore in progress Synchronized or normalized Sync in progress Detached Containers A container is disk space that is preallocated for later use as a snapclone, a snapshot, or a mirrorclone.

  • Page 39: Optimizing Replication Performance

    (not by host I/O activity). HP recommends that you plan the migration of virtual disks in advance because migration involves the creation of a mirrorclone in the background which can compete with other I/O activity.

  • Page 40: Minimizing Snapclone Workloads

    The performance impact of an improperly sized (in a performance sense) snapshot or snapclone can cause HP P6000 Continuous Access to suspend replication. System and application performance and availability can be improved when replication is suspended as a planned event rather than an unplanned disruption.

  • Page 41: Hp P6000 Continuous Access Software

    Working with DR groups in HP P6000 Command View The Data Replication folder for an HP P6000/EVA storage system displays the DR groups on that array, and indicates if their DR mode (role) is currently as a source or as a destination.

  • Page 42: Creating Dr Groups

    (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.
  • Page 43 One or more exchanges are used to transfer data and an additional exchange is used for command information. The HP-FC Protocol requires all frames within the transfer to be delivered in order. Therefore, if HP-FC Protocol is used in the fabric, the fabric must use SID/DID routing.

  • Page 44: Maintaining And Managing Hp P6000/Eva Storage Systems

    When you install an array, it appears as an uninitialized storage system. Initializing an array makes it ready for use, binds the controllers as an operational pair (for models other than the HP EVA4400 and P6x00), and establishes preliminary data structures on the array. Initializing also sets up the first disk group, which is called the default disk group.

  • Page 45: User-Initiated Service Mode

    The user-initiated service mode does not change the functionality of HP P6000 Command View, nor its response to events. This mode is solely for HP P6000 Command View interaction with external HP support tools. When user-initiated service mode for a storage system is active: Automated support calls to HP regarding the storage system are stopped.

  • Page 46: Uninitializing Storage Systems

    Support calls to HP disabled and the amount of time remaining in service mode. There are also options for you to Stop service mode or Restart service mode. Uninitializing storage systems See the HP P6000 Command View online help for detailed procedures related to managing your storage environment. CAUTION: If you uninitialize an array, you will lose all virtual disks, associated data, and host presentations that you created for the array.
  • Page 47 Figure 7 HSV210A controller rear view Figure 8 HSV300 controller rear view Figure 9 HSV400 controller rear view Figure 10 HSV450 rear view Figure 1 1 HSV340/HSV360 controller enclosure (FC version) rear view Shutting down the storage system...

  • Page 48: Hardware

    The following graphic shows a sample Controller Properties page. The display will vary, depending on your array type. See the HP P6000 Command View online help for more information about the displays. Maintaining and managing HP P6000/EVA storage systems...

  • Page 49: Verifying Hardware Status

    The remote service test sends a management event for the selected storage system. HP remote services, such as WEBES, can use the event to test that HP P6000 Command View notification is working properly. The test does not change the functionality of HP P6000 Command View, nor its response to events.

  • Page 50: Updating Hp Controller Software

    To change the management server managing an array: Log in to HP P6000 Command View on the management server that you want to manage the array. From the settings point of view navigation pane, select the array and click Discover Storage Systems.

  • Page 51: Configuring Iscsi Devices

    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: Install the iSCSI devices. See HP EVA iSCSI Connectivity Quick Start Instructions for Windows for installation instructions.

  • Page 52: Monitoring Storage System Events

    Normal events are more common than exceptional events. You can use HP P6000 Command View to configure and view these events. Managing events from the HP P6000 Command View user interface is especially useful when you are monitoring multiple arrays.

  • Page 53: Controller Termination Event Log

    For more information about uninitializing an array, see Controller termination event log Controller termination events report that a controller has ceased operation, but do not report on controllers in uninitialized arrays. Viewing events To view events: While viewing the properties of the selected storage system, click View events. The View Events menu opens.

  • Page 54: Viewing Additional Information

    You can specify the hosts that receive the SNMP traps that the management server generates for events. Any SNMP-enabled host in the same network as the array can be used. You can enter individual hosts or you can apply a customized host notification list to HP P6000 Command View.

  • Page 55: Applying A Customized Host Notification List

    The hosts in the notification list should begin receiving SNMP traps. If the hosts are not receiving traps, restart the HP P6000 Command View service in the management server's Services applet. For array-based management configurations, restart HP P6000 Command View in the Server Options menu.

  • Page 56: Selecting Individual Events

    If the event description displays Description not found in parse file, you must update the parse file that the controller uses to populate the event description. This can occur if you upgrade or install HP P6000 Command View on a management server that has not previously run this software.

  • Page 57: Retrieving The Management Information Base

    Contact HP Support and request an updated parse file. For contact information, see technical support” (page HP Support will email the parse file to you and instruct you where to store it on the management server. From the Initialized Storage System Properties window, click View events.

  • Page 58: Sending The Event 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: Go to the appropriate event log: In Management, click Event file.

  • Page 59: Configuring Hp P6000 Command View (Advanced Tasks)

    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.

  • Page 60: Setting Audit Logging Options

    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. A log file captures events generated by these activities: User login and logoff User accessibility (for example, the Access Denied event is generated for users with view-only...

  • Page 61: Changing Port And Timeout Parameters

    This section applies to server-based management only. You cannot change the port or timeout parameters with array-based management. You can change the port that you use to log into the HP P6000 Command View user interface (the default port is 2374). You can also change the timeout parameter, which determines how long inactivity can occur before the browser session times out and requires you to log in again.

  • Page 62: Running Hp P6000 Command View In A Multi-Homed Environment

    StorageWorks HSV folder, open cv-eva.url. Find the line that contains URL=https://localhost:2374, and replace the localhost with the IP address or the FQDN name of the host where HP P6000 Command View is running. IMPORTANT: The HP P6000 Command View server must have a unique IP address to ensure management lock verification.

  • Page 63: Troubleshooting Hp P6000 Command View

    Selecting any of these right-click menu options redirects you to the user interface without the proper context and can display incorrect information. Changing system time causes your session to end Problem Increasing ABM system time via system options set time options logs you out from the HP P6000 Command View GUI. Optimizing performance...

  • Page 64: Navigation Pane Lists Duplicate Arrays

    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.

  • Page 65: Error Messages In The User Interface

    Several boxes on the iSCSI Controller Properties window display unavailable or unknown. Explanation / Resolution This can indicate that the communication link between HP P6000 Command View and the iSCSI device is down. Open a DOS prompt and ping the iSCSI device.

  • Page 66: Troubleshooting Access To Array-Based Hp P6000 Command View

    Problem The logon to array-based HP P6000 Command View indicates Access Denied. Explanation / Resolution The HP P6000 Command View client filter in the HP P6000 Control Panel is enabled and access has been denied. Troubleshooting HP P6000 Command View...

  • Page 67: Virtual Disk Sizes Displayed Incorrectly

    IP address in the list. DNS resolution issue. If the DNS server settings are not configured correctly in the HP P6000 Control Panel, a host name that is added to the client filter list may not be resolved to the correct IP address.

  • Page 68: Version Numbers Differ

    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.

  • Page 69: Monitoring Array Performance Using Hp P6000 Performance Data Collector

    Data Collector (formerly HP Command View EVAPerf) to monitor and display array performance metrics from a command line interface or a graphical user interface. HP P6000 Performance Data Collector is not directly available on array-based management; however, HP P6000 Performance Data Collector can be installed on a host or server with an Fibre Channel connection to the array.

  • Page 70: Hp P6000 Performance Data Collector Server Side Logging Of Performance And State Data

    Performance and state logs retrieval from HP P6000 Performance Data Collector client Historical performance and state change data can be retrieved through the HP P6000 Performance Data Collector CLI. Displaying historical state changes and performance data The following command displays performance data and state changes for objects of a specified type within the specified time range.
  • Page 71 HP P6000 Command View port (usually 2372). No defaults are assumed here; you must specify the port number exactly. username is the HP P6000 Command View user name (the specified user should be a member of HP Storage Admins or HP Storage Users)

  • Page 72: Configuration File For Performance And State Data Logging

    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.

  • Page 73: Configuring Hp P6000 Performance Data Collector

    2. Possible values are from 1–4, where 4 indicates maximum logging. Events and logs HP P6000 Performance Data Collector client log, service log, and Perfmon logs are saved on the system running the HP P6000 Performance Data Collector service. The array system password is stored on the server side.

  • Page 74: Configuration Recommendations

    HP P6000 Performance Data Collector service: evaperf server host port [username] [-usessl] where: is the hostname or IP address of the server running the HP P6000 Performance Data Collector host service. is the TCP port from which the HP P6000 Performance Data Collector data collection service will port receive an RPC request (default is 860).

  • Page 75: Ssl Protocol

    HP P6000 Performance Data Collector service. username 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.

  • Page 76: Backward Compatibility

    You can associate the WWNs of objects, such as arrays, virtual disks, and hosts, with more readable identifiers , as seen in the HP P6000 Command View GUI, called friendly names. For example, you can identify an array that is known by its WWN of 5000- 1 FE1-5000-A9F0 as RSG14HSV1.

  • Page 77: Mapping Worldwide Names To Friendly Names

    HP P6000 Performance Data Collector was installed. Mapping worldwide names to friendly names HP P6000 Performance Data Collector does not map the WWN for virtual disks to the HP P6000 Command View friendly name when the WWN value differs from the unique unit identifier (UUID).

  • Page 78: Using Short Names

    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.

  • Page 79: Using The Command Line Interface

    You can limit the amount of data that is collected and presented, which can be useful if your configuration includes numerous arrays, physical disks, and virtual disks. To limit the arrays for which HP P6000 Performance Data Collector collects data, enter the following command: evaperf as -sz array1 array10 array32 The output contains data only for the specified arrays.
  • Page 80 HP P6000 Performance Data Collector into a TLViz-compatible format. The formatter is installed as part of the HP P6000 Performance Data Collector software, which is installed through the HP P6000 Command View Software Suite. The formatter includes a Microsoft Access database template.

  • Page 81: Commands

    HP TLViz has limited space for displaying names (30 character maximum). Included with the TLViz-formatted files are map files (PDISK-MAP.txt and VDISK-MAP.txt) that map the virtual disk and physical disk names that display in HP TLViz to the LUN and enclosure/bay names that display in the HP P6000 Performance Data Collector output.
  • Page 82 Displays host port statistics. The field Port WWN is included as part of the hps command output in HP P6000 Performance Data Collector. This field provides the WWN of the host port. Displays a list of arrays that are visible to the host.

  • Page 83: Command Modifiers

    HSV200 series of controllers onward. Verifies array passwords for use with HP P6000 Performance Data Collector. Verifies whether HP P6000 Command View is accessible for state data collection. Description Substitutes contractions from the fnames.dict file.

  • Page 84: Using The Graphical User Interface

    Remote performance monitoring with Windows Performance Monitor is not supported. The binary logging feature of Windows Performance Monitor is limited in the number of HP array performance objects it can log simultaneously. Logging works most reliably when you log small numbers and instances of counters.
  • Page 85 The Add Counters dialog box opens. To view a description of a counter, select a counter, and then click Explain. Click Use local computer counters and, in the adjacent box, select the host on which HP P6000 Performance Data Collector is running.

  • Page 86: Data Filtering

    Windows Performance Monitor uses the evapmfilt.conf file, which contains the names of the virtual disks and arrays for which you want to retrieve data. Use the HP P6000 Performance Data Collector command line interface to create or update the evapmfilt.conf file.

  • Page 87: Hp Eva Storage Array

    DR group member. In the output, logical unit number (LUN) is used interchangeably with virtual disk. Virtual disks must be presented to a host to be seen by HP P6000 Performance Data Collector. However, replication volumes on the replication system are visible without being presented. HP P6000 Performance Data Collector also shows DR group membership with the virtual disk table in the DRM Group column.

  • Page 88: Hp Eva Virtual Disk Group

    Total Read Hit MB/s—The total rate at which data is read from the array cache memory because of read hit requests. Monitoring array performance using HP P6000 Performance Data Collector...

  • Page 89: Hp Eva Host Connection

    HP EVA host connection The HP EVA host connection object provides information for each HBA that has a connection to an array. The counters are: Queue Depth, the average number of outstanding requests from each host adapter.

  • Page 90: Hp Eva Physical Disk

    Write Latency—The amount of time it takes for a disk to complete a write request. HP EVA physical disk group The HP EVA physical disk group object provides information about physical disk activity per disk group. For each disk group, metrics are reported that represent the averages of various counters across all the disks in the disk group.

  • Page 91: Hp Eva Dr Tunnels

    This average is weighted by requests per second (HSV200 controller series onwards). HP EVA DR tunnels The HP EVA DR tunnels object reports the intensity and behavior of the link traffic between source and destination arrays. The counters for this object display information only if there is at least one active DR group on the array;...

  • Page 92: Hp Eva Dr Group Information

    Write History Log (WHL) files. The performance metrics are provided for each DR group. The WHL fill and drain rates can be displayed in either MBs or KBs. Creation and management of DR groups is not supported by HP P6000 Command View array-based management.

  • Page 93: 1 Support And Other Resources

    To make comments and suggestions about product documentation, please send a message to storagedocsFeedback@hp.com. All submissions become the property of HP. Product feedback To make comments and suggestions about HP P6000 Command View, please send a message to CVfeedback@hp.com. Related information Documentation...

  • Page 94: Websites

    Websites 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.com/portal/site/hpsc/public/ Typographical conventions Table 8 Document conventions Convention Blue text: Figure 1 (page 9) Blue, underlined text: http://www.hp.com...

  • Page 95: A Hp Array Event Code Formats And Descriptions

    Table 9 HP array controller event code bits 31...24 Software component ID The bits of a controller termination event have the following format: Table 10 HP array controller termination event code bits 31...24 23...16 Software Event number component ID The following table provides the interpretation of each bit.

  • Page 96: Corrective Action Codes

    You can view the complete list of corrective action codes when you select Corrective action code in an event description. Event information packet (EIP) types Table 13 HP array event information packet (EIP) types Code Title Fault Manager Termination Processing Recursive...

  • Page 97: Coupled Crash Control Codes

    Table 13 HP array event information packet (EIP) types (continued) Code Title Executive Services System Time Change Storage System Management Interface Entity Creation or Deletion Storage System Management Interface Entity Attribute Change System Services HSV210 Controller State Change Disk Enclosure Environmental Monitoring Unit...

  • Page 98: Dump/Restart Control Codes

    Dump/restart control codes Table 15 HP array dump/restart control codes Code Description Perform crash dump then restart. Do not perform crash dump, just restart. Perform a crash dump and do not restart. Do not perform crash dump and do not restart.

  • Page 99: Glossary

    A host that is equipped with a replication manager host agent. Enterprise Virtual Array. An HP disk array product that allows pooled disk capacity to be presented to hosts as one or more variably sized physical devices. An EVA consists of disks, controllers, cables, power supplies, and controller software.
  • Page 100 DRAM or EEPROM memory boards, a memory bus board, a CPU, and a battery card. SPoG Single pane of glass. An HP P6000 Command View interface that can display multiple HP P6000 storage software applications in a single browser window.
  • Page 101 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.

  • Page 102: Index

    HP P6000 Performance Data Collector, commands HP P6000 Performance Data Collector, communication path failed, configuring iSCSI devices, container guidelines, containers creating snapclones and snapshots,...
  • Page 103 HP P6000 Command View service, right-click menu, sending the event file, service, HP P6000 Command View, severity levels for events, snapclone guidelines, preallocated,...
  • Page 104 HP Subscriber's Choice for Business, HP support, Windows Performance Monitor displaying metrics, objects and counters, overview, write cache flushing, 104 Index...

Table of Contents