HP StorageWorks P9000 Application Performance Extender Software User Guide Abstract This document describes how to use the HP StorageWorks P9000 Application Performance Extender Software (P9000 Application Performance Extender) user interface to manage and monitor the performance of applications running on P9500, XP20000 or XP24000 disk arrays.
Legal and notice information Copyright © 2010-2011 by 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 ....................................................................................... 11 Functional representation ........................................................................................................... 12 2 Installing and removing P9000 Application Performance Extender .......... 13 Installing the management station ............................................................................................... Prerequisites ........................................
Proactive License Tracking .......................................................................................................... Permanent License ..................................................................................................................... Meter Based Term license .......................................................................................................... Meter based Term license requirement .........................................................................
Creating and viewing reports ..................................................................................................... Generate Report screen ....................................................................................................... Generating reports ............................................................................................................. Schedule Report screen ......................................................................................................
Glossary .......................................................................................... 117 Index ...............................................................................................
Figures 1 Functional representation of P9000 Application Performance Extender .......................... 12 2 License screen ........................................................................................................ 28 3 Proactive License Tracking ........................................................................................ 31 4 License details window ............................................................................................ 41 5 Delete license window .............
33 Generate report screen ............................................................................................ 79 34 Schedule Report screen ............................................................................................ 81 35 Report schedule update window ............................................................................... 82 36 Alarms screen (Alarm Configuration) ......................................................................... 84 37 Create Alarm window .............
Tables 1 Upgrade support (management station) ..................................................................... 21 2 Upgrade support (communication agent) ................................................................... 22 3 Upgrade support (controller) ..................................................................................... 24 4 Troubleshooting information ..................................................................................... 91 5 Document conventions ....................
1 Overview In a typical Storage Area Network (SAN) environment, multiple I/O intensive applications share storage resources. Not all applications are mission critical, but they compete with the mission critical applications for the same I/O processing requirements. In such situations, there is a need to keep the key (mission critical) applications at a desired performance level and other (non critical) applications at an acceptable performance level.
• Dynamically balance the MP blade utilization of P9500 disk arrays Functional representation Figure 1 shows the working of P9000 Application Performance Extender in a SAN environment. Figure 1 Functional representation of P9000 Application Performance Extender . P9000 Application Performance Extender is typically deployed in a LAN/SAN environment. The management station is deployed in a LAN set up, while the communication agent and the controller can have both LAN and SAN connectivity.
2 Installing and removing P9000 Application Performance Extender This chapter describes the procedure to install the P9000 Application Performance Extender in your SAN environment. IMPORTANT: HP recommends that you meet the prerequisites for all the P9000 Application Performance Extender components prior to initiating installation for quick deployment. The P9000 Application Performance Extender installer kit includes the following: • P9000 Application Performance Extender management station (P9000APEX_MS.
• PostgreSQL Database • PostgreSQL ODBC Driver Prerequisites Before you install the management station: • Read the HP StorageWorks P9000 Application Performance Extender Release Notes for any installation or post-installation requirements specific to the latest release • Ensure that ports 8080, 51101, and 5432 are available for use • Ensure that you have 5 GB of free space in the selected drive • Ensure that JRE 1.
• HP StorageWorks APEX Web Server • HP StorageWorks APEX DB • The software icon for P9000 Application Performance Extender appears on the desktop. • The software is available from the Start menu (for example, Start > All Programs > Hewlett-Packard > HP StorageWorks APEX Management Station > P9000ApplicationPerformanceExtenderManagementStation). Alternatively, open a browser window and enter the following URL to launch P9000 Application Performance Extender: http://
Installing the communication agent on HP-UX and Linux (x86 and x86_64) hosts NOTE: If the HP-UX PHKL_40311 cumulative patch is not installed, the following message is displayed: Please contact HP service to install the "asyncdsk cumulative patch" to get APEX support for I/Os through HP-UX asyncdsk driver. If you do not need support for HP-UX asyncdsk driver or you will get this patch installed later, you can continue with this installation.
NOTE: On Linux hosts, ensure that the driver corresponding to the QLogic HBAs is listed as the first uncommented entry in the /etc/hba.conf file. • For example, on 32 bit Linux hosts, if the /etc/hba.conf file includes the following entries: lpfc /usr/lib/libemsdm.so qla2xxx /usr/lib/libqlsdm.so Change it to the following: qla2xxx /usr/lib/libqlsdm.so lpfc /usr/lib/libemsdm.so • On 64 bit Linux hosts, if the /etc/hba.conf file includes the following entries: lpfc /usr/lib/libemsdm.
To start the communication agent service, run the /sbin/init.d/apex_ca start command. To stop the communication agent service, run the /sbin/init.d/apex_ca stop command. Linux To verify that the communication agent was installed successfully, run the following command to check the status: service apex_ca status To start the communication agent service, run the service apex_ca start command. To stop the communication agent service, run the service apex_ca stop command.
NOTE: You should not cancel the InstallAnywhere application for P9000 Application Performance Extender controller once installation has begun. Prerequisites Before you install the controller, ensure the following: • Read the HP StorageWorks P9000 Application Performance Extender Release Notes for any installation or post-installation requirements specific to the latest release • Ensure that JRE 1.
3. Run ./P9000APEX_ControllerIA64.bin. The Welcome screen is displayed followed by the End User License Agreement. 4. Read and accept the terms of the agreement. The Pre–installation summary is displayed. Follow the instructions to proceed. Verifying controller installation on HP-UX and Linux hosts HP-UX To verify that the controller was installed successfully, run the following command: /sbin/init.d/apex_controller status To start the controller service, execute the /sbin/init.
Upgrading P9000 Application Performance Extender This section describes the procedure to upgrade the P9000 Application Performance Extender management station, communication agent, and controller. For unsupported upgrade paths, the previous version must be removed first. After removing the previous version, install the latest version. For supported upgrade paths, you do not have to remove the earlier version before upgrading to the latest version.
The End User License Agreement is displayed. 4. 5. Read and accept the terms of the license agreement, and click Next. Click Install to proceed. When the installation is complete, the installation Summary window is displayed. 6. Click Done. The license entitlement is displayed. Upgrading the communication agent Communication agent upgrade support Table 2 shows upgrade support for P9000 Application Performance Extender communication agent versions.
The Pre–installation summary is displayed. Follow the instructions to proceed. Linux IA64 host 1. Transfer the P9000APEX_CAIA64.bin to the Linux IA64 host. 2. Run chmod +x P9000APEX_CAIA64.bin to grant execute permission to the P9000APEX_CA.bin file. 3. Run ./P9000APEX_CAIA64.bin. The Welcome screen is displayed. 4. Click Next. The following message is displayed: An earlier version of APEX Communication Agent is installed on the machine. Press OK to Upgrade. 5. Click OK.
to the version in the TO column without removing the earlier version. A blank cell indicates that an upgrade to a later version (without removing the earlier version) is not supported. Table 3 Upgrade support (controller) To P9000 Application Performance Extender version From P9000 Application Performance Extender version 2.2 1.0 2.0 2.1 2.1.1 To upgrade the controller to the latest version: HP-UX and Linux (x86 and x86_64) hosts 1. Transfer the P9000APEX_Controller.bin to the HP-UX or Linux host.
The End User License Agreement is displayed. 6. Read and accept the terms of the agreement. The Pre–installation summary is displayed. Follow the instructions to proceed. Windows host 1. Double-click P9000APEX_Controller.exe to start the installation. The Installation Wizard is displayed. 2. Click Next. The following message is displayed: An earlier version of APEX Controller is installed on the machine. Press OK to Upgrade. 3. Click OK. The License Agreement window is displayed. 4.
NOTE: On a HP-UX host, do not remove the communication agent using the swremove option. Removing communication agent on a Windows host To remove the communication agent on a Windows host: 1. 2. Select Start > Control Panel >Add/Remove Programs. Select HP StorageWorks P9000 Application Performance Extender Communication Agent. The InstallAnywhere window appears, indicating that it will remove the selected software. 3. Click Next.
3 Licensing P9500 disk arrays IMPORTANT: Licensing is applicable only for P9500 disk arrays. P9000 Application Performance Extender follows a band-based pricing structure. For a new purchase, you buy the base license and then purchase all the capacity licenses from the capacity band that matches the total capacity required. For an upgrade purchase, first verify how much capacity is already installed. Then, add to it the amount of capacity you intend to purchase.
P9000 Application Performance Extender supports the following license types: • Instant-on license • Permanent license • Meter based term (MBT) license License screen You can add new licenses and view the status of existing licenses on the License screen. The License screen is displayed when you select License from the Navigation pane. Figure 2 License screen . Item Description License File name Enables you to select a license. Add License Enables you to add a license.
• It is either valid for a period of 120 days from the day you install P9000 Application Performance Extender or until the time you generate, and install a new license for one or more P9500 disk arrays. It cannot be generated from the HPAC license key website. Consider the following example, where P9000 Application Performance Extender is installed on 20th Aug’10 and is controlling a P9500 disk array. The Instant-on license is enabled on the same date and valid until the 19th Dec’10.
Item Description Array Capacity Displays the usable capacity of a P9500 disk array. License Capacity Displays the license capacity as 0. License Status Displays the status as Expired. End date Displays the end date of the grace period. Displays the following status message: Comments No License Installed. Grace Period expire on month, day, year. Please purchase the required P9000 Application Performance Extender licenses now to continue using P9000 Application Performance Extender on this Array.
Item Description License Status Displays the status as Expired. License Capacity Displays the capacity as 0. Displays the following status message: Comments License has expired. Grace Period has expired on month, day, year. Please purchase the required licenses now to continue using P9000 Application Performance Extender on this Array. Where, month, day, year refers to the date till when the grace period is valid.
Figure 3 shows the proactive license tracking screen. Data collection discovers all the P9500 arrays which need to be monitored. You have to select a particular array and enter the notification e-mail id in the License Settings screen before adding any new valid license. Once the grace period starts, the notification mails are sent depending on the notification interval set in the settings.ini file.
IMPORTANT: • Additional usable capacity refers to the usable capacity that is beyond the Permanent licensed capacity. • A Meter based Term license cannot be installed on multiple management stations. • Multiple Meter based Term licenses can be generated and installed on a management station. In such cases, the licenses are used successively.
used only till the first week of January'11, after which it remains unused until the 75TB current usable capacity increases by 50TB, and is constantly used. Following is the suggested Meter based Term license configuration: Generate 1950TB-Days of Meter based Term license to monitor 50TB additional usable capacity for 39 days. The 1950TB-Days are derived based on the following calculation: 50TB * 39 days = 1950TB-Days of Meter based Term license The following figure illustrates the scenario described.
The following figure illustrates the use of Meter based Term license. At the time of installing the Meter based Term license, if the usable capacity is within the Permanent licensed capacity, the installed TB-Days remain dormant till the usable capacity exceeds the Permanent licensed capacity. They are activated only after the Permanent license is completely used.
Column Headings - List of existing licenses section Description Displays N/A. Term (Days) License Status Term (Days) indicates the total number of days when the installed 90TB-Days can be used. In this case, as the usable capacity is within the Permanent licensed capacity limit, the 90TB-Days are dormant and the Term (Days) are not shown. Displays the status as Installed. Displays Never. End Date This is because, the Permanent license which is for an unlimited duration is currently active.
Consider that the 90TB-Days are completely used in the first half of 12/11/2010 and appropriate TB-Days are not yet installed to monitor the 10TB additional usable capacity. As a result, P9000 Application Performance Extender does the following: 1. 2. Enters 60 days grace period at 1:00 PM on the same day and 0TB-Days are available. Begins reduction (negative count) of installed TB-Days.
4. 5. 6. As the usable capacity is beyond the Permanent licensed capacity, P9000 Application Performance Extender enters 60 days grace period on 11/30/2010. 1000TB-Days Meter based Term license are installed on 12/02/2010.
1. 2. 3. 4. A P9500 disk array has a usable capacity of 50TB. A Permanent license is installed on 11/15/2010 to monitor the 50TB usable capacity. 5TB-Days are installed on 11/27/2010, because you plan to use another 1TB usable capacity every day later for five days. If the usable capacity rises beyond the 50TB Permanent licensed capacity on 11/30/2010 and the additional usable capacity equivalent to 1TB-Days is used every day, P9000 uses the 5TBDays completely by 12/04/2010.
3. 4. Enter the registration number in the Registration Number or Product Authorization Key box. Ensure that the registration number is same as that mentioned in the product entitlement certificate. Click Next >>. The Array information input screen appears. The following details are displayed: • Registration number • P9000 Application Performance Extender base license • Additional LTU that you purchased • Usable capacity that the LTU supports 5.
Viewing license details To view the details of a license: 1. Select License from the Navigation pane. The License screen is displayed. 2. 3. Select a P9500 disk array from the List of existing licenses table. Click View Details. The details of the selected array is displayed in the View License Details windowas shown in Figure 4. Figure 4 License details window .
• License Status: Installed • Term (Days): N/A • End Date: Never • After 1:00 PM on 11/30/2010: • License Capacity: 50TB, +100TB-Days Consider that 25TB-Days are used after installation.
NOTE: Reduction or negative counting is only applicable for the installed TB-Days. It is not applicable for Permanent licenses. After 60 days grace period, P9000 Application Performance Extender stops controlling the P9500 disk array. Example scenario 8 Consider the following points: 1. 2. 3. 4. 5. A P9500 disk array has a usable capacity of 50TB. A Permanent license is installed on 11/23/2010 to monitor the 50TB usable capacity.
grace period of 60 days. In such a case, if you install the appropriate TB-Days, P9000 Application Performance Extender ends the grace period for that particular P9500 disk array. Example scenario 8 Consider the following points: 1. 2. 3. 4. 5. A P9500 disk array has a usable capacity of 75TB. A Permanent license is installed on 11/24/2010 to monitor the 75TB usable capacity. Due to a surge in storage requests around 11/30/2010, another 20TB usable capacity is added for a duration of five days.
Violating licensed capacity After 60 days of grace period, P9000 Application Performance Extender considers it as a capacity violation and stops controlling the P9500 disk array. However, it continues to monitor the workload performance and MP blade utilization. During a capacity violation phase, if you do one of the following: • Install a Permanent license or appropriate TB-Days of Meter based Term license for P9000 Application Performance Extender to control the P9500 disk array.
Licensing P9500 disk arrays
4 P9000 Application Performance Extender user interface layout NOTE: • The minimum supported screen resolution is 1024X768 pixels. However, HP recommends that you set the screen resolution of your monitor to 1280X960 pixels or higher to reduce scroll bars. • The time references except for the messages on the message pane of the user interface pertain to the management station time. Status messages refer to the local time zone of the machine on which the browser runs. • The settings.
Figure 7 Change password screen . Enter the new password in the respective text boxes and click Save. After successful login, the Home screen (see Figure 8) is displayed. Figure 8 Home screen .
• Message pane • Title pane Figure 9 P9000 Application Performance Extender user interface . 1. Navigation pane — Helps you navigate to the high level tasks that you can perform using P9000 Application Performance Extender. 2. Content pane — Displays information about the task you select in the navigation pane and presents actions you can perform. 3. Message pane — Displays the error messages and the status of the actions performed. 4. Title pane — Displays the product name and logo.
P9000 Application Performance Extender user interface layout
5 Using P9000 Application Performance Extender Using P9000 Application Performance Extender involves the following tasks: 1. Identifying applications and hosts. • For application level performance differentiation across applications on an HP UX 11.31 server: • Identify the critical applications running on the host that you want to assign SLOs to • Assign applications on your hosts to different Process Resource Manager (PRM) groups.
Discovering hosts and collecting configuration data P9000 Application Performance Extender interacts with the XP or P9500 disk arrays through hosts which have operating system specific communication agents installed. After the communication agents are installed, the details of the corresponding hosts appear in the List Of Discovered Hosts table. During host discovery, all the hosts registered with the management station are identified. After the hosts are discovered, configuration data is collected.
Item Description APEX Supported Yes — Indicates that the host is supported. No — Indicates that the host is not supported. Displays the status as New, Done, or Fail. Data Collection Status Done — Indicates that configuration data has been successfully collected. New — Indicates that configuration data has not been collected. Fail — Indicates that the configuration collection failed. Hide Offline Hosts Displays only the hosts that are online.
NOTE: • Guest level I/O prioritization using APEX for VMware ESX/ESXi servers can be achieved by configuring NPIV for virtual machines with RDM disk. • On ESX Servers, the default remote CIM Client connection will be disabled. To enable it, perform the following steps : a. vi /etc/sfcb/sfcb.cfg b. Look for httpLocalOnly: true and change this to httpLocalOnly: false c. Execute service sfcbd-watchdog restart or/etc/init.
Figure 11 Discovered hosts table . 2. 3. Click Refresh Host List to view the latest set of discovered hosts. Select a host to collect configuration data. You can also select multiple hosts. Select Select All Hosts to collect configuration data for all the discovered hosts, or Select Hide Offline Hosts to view and collect configuration data only for the online hosts. 4. Click Collect Configuration Data to collect configuration data for the selected hosts.
Figure 13 Controller Settings screen . Item Description Controller(s) And Managed Array(s) Information Displays the controller connected to the selected XP or P9500 disk array. APEX Controller(s) Displays the IP address of the host running the controller. Attach Controller Displays the controllers. Available — Indicates that a controller is available with the host. Command Device Settings Displays the command devices associated to the selected array.
Specifying controller settings To specify controller settings: 1. Select Controller Settings from the Navigation pane. The Controller Settings screen is displayed (see Figure 13). 2. 3. Under Controller(s) And Managed Array(s) Information, select an array from the Select Array list. Select the Controller Active check box to activate the controller. NOTE: If the Controller Active check box is selected, the controller will try to achieve the desired SLO targets as specified in the assigned SLO profile.
Figure 16 Command devices information . 2. 3. Select a command device from the Command Device Settings table to configure the command device of the host running the controller. Click Use Command Devices. NOTE: The controller communicates with the XP and P9500 disk arrays through the command device names stored in the controller. HP recommends that you add more than one command device to enable the controller to use an alternative command device, if required.
NOTE: • The username and password must be the same as specified in Remote Web Console (RWC). More more information, see Appendix A • If the password is incorrectly entered, the command device authentication screen continues to appear until the correct password is entered or Cancel is clicked. 5. Click Next. The DLOM Settings screen is displayed. Alternatively, you can select DLOM Settings from the Navigation pane. For more information on specifying DLOM settings, see “Specifying DLOM settings” on page 59.
Figure 18 DLOM settings screen . Item Description Select a P9500 array Enables you to select a P9500 disk array. Non QoS MPBs Place holder for assigning MP blades to achieve load balancing. QoS MPBs Place holder for assigning MP blades to achieve I/O prioritization and load balancing. Enables you to balance MP blade utilization.
Enabling DLOM settings There are three different modes to enable DLOM: • DLOM only mode (Non QoS MPBs) — In this mode, P9000 Application Performance Extender operates as a load balancer, where MP blade utilization for I/O processing is balanced by changing LDEV ownership across multiple MP blades. This reduces load on overloaded MP blades.
3. 4. 5. 6. 7. 8. 9. Click Submit. Create a profile and define target Service Level Objectives (SLOs) for the workloads identified Assign the profile to an array. Add workloads. Enable the controller. View and monitor workload performance. Modify the defined SLOs to achieve the desired bandwidth or latency, if required. I/O prioritization with load balancing If you want to balance MP blade utilization across all MP blades and also need I/O prioritization, do the following: 1. Select the array. 2.
5. 6. 7. 8. 9. 10. Create a profile and define target Service Level Objectives (SLOs) for the workloads identified Assign the profile to an array. Add workloads. Enable the controller. View and monitor workload performance. Modify the defined SLOs to achieve the desired bandwidth or latency, if required. NOTE: The Submit button is enabled only if the following conditions are met: • If more than one MP blade is present in the Non QoS MPBs compartment.
Figure 19 SLO Settings screen (SLO Profile Management) . Item Description SLO Profile Management Enables you to create, update, and remove SLO profiles. SLO Profile Scheduling Enables you to create, update, and remove SLO profile schedules. Select Profile Enables you to select a profile. Enter New Profile Name Enables you to specify a name to create a new profile. SLO Profile Definition Displays the SLO profile details. Workload Displays the workload numbers (0 to 15).
Item Description Array Sl.No. Displays the array serial number. Default SLO Profile Displays the default SLO profile of the selected array. A default profile is the profile that is manually assigned to the array. Current SLO Profile Displays the current SLO profile of the selected array. Figure 20 SLO Settings screen (SLO Profile Scheduling) . Item Description Schedule Summary Displays all the details of the existing SLO schedules in the system. Schedule Name Displays the name of the schedule.
Item Description Delete Schedule Removes an existing schedule. Creating SLO profiles To create SLO profiles: 1. Select SLO Settings from the Navigation pane. The SLO Settings screen is displayed (see Figure 19). 2. 3. Click the SLO Profile Management tab. Select a profile from the profile list. The workload details of the selected profile is displayed in the SLO Profile Definition table, as shown in Figure 21. Figure 21 SLO profile definition table . NOTE: The value -1 is the Don’tCare SLO value.
Assigning SLO profiles to arrays To assign profiles to arrays: 1. Select a profile from the profile list. 2. Select an array from the Array list. 3. Click Apply Profile To Array. This will assign the profile as the default and the current profile of the selected array. A profile will become the current profile when SLO scheduling is enabled and the associated profile is activated.
Figure 23 Schedule Summary table . 2. Click Create Schedule to create a new schedule. The SLO Schedule Update window is displayed, as shown in Figure 24. Figure 24 Schedule update window . 3. 4. 5. 6. 7. 8. Select a profile from the SLO profile list. Enter a schedule name. Select an array from the array list. Under SLO Effective Time, select the start time and end time to run the schedule. Under Recurrence Pattern, select an appropriate option.
Updating schedules To update SLO schedules: 1. Select a schedule from the Schedule Summary table. 2. Click Update Schedule. The SLO Schedule Update Window is displayed. 3. 4. Modify the schedule settings as required. Click Submit. The selected schedule is updated. The updated details will appear in the Schedule Summary table. Removing schedules To remove SLO schedules: 1. Select a schedule from the Schedule Summary table. 2. Click Delete Schedule. The selected schedule is removed.
Figure 25 Workload settings screen . Item Description Workload Summary Displays the workload details. Host IP Address Displays the IP address of the host. PRM Group/Guest IP Displays the PRM group/ESX Host/VMs the workload belongs to. PRM Groups are applicable only to HP UX. ESX/VM-IP Displays the ESX/VMs associated with the selected ESX server. This is applicable only for VMWare hosts. SLO Value Displays the SLO value. SLO Type Displays the SLO type as bandwidth or latency.
Item Description Workload Number Enables you to select a workload number ranging from 1–15. Create Workload Enables you to create a workload. Update Workload Enables you to update a workload. Remove Workloads Removes a workload. Creating workloads To create workloads: 1. Select Workload Settings from the Navigation pane. The Workload Settings screen is displayed (see Figure 25). The Workload Summary table displays the workload details, as shown in Figure 26. Figure 26 Workload Summary table . 2.
Updating workloads To update workloads: 1. Select a workload from the Workload Summary table. The details of the selected workload will be displayed under Create/Update Workload, as shown in Figure 27. Figure 27 Create/update workload table . 2. 3. Modify the workload details. Click Update Workload. The updated details will appear in the Workload Summary table. Removing workloads To remove workloads: 1. Select a workload from the Workload Summary table. 2. Click Remove Workloads.
Specifying workload settings in a cluster environment P9000 Application Performance Extender is not cluster aware, but it can work with both Active-Active and Active-Standby clusters. Active-Active (multinode) application in a cluster configuration You must map all the hosts (Windows and Linux) and PRM groups (HP-UX) corresponding to the multinode application to the same workload number. This will enable the controller to prioritize the application depending on the SLO specified for that workload number.
Figure 28 MPB graphs screen . Item Description Array Enables you to select a P9500 array. From Date Enables you to select a start date. From Time (HH:MM) Enables you to select a start time. To Date Enables you to select an end date. To Time (HH:MM) Enables you to select an end time. Live Displays live graphs. View History Displays historic graphs. Select MPBs Enables you to select MP blades.
You can select multiple MP blades. d. 3. Click View History. Historic graphs for the specified period are displayed. To generate live graphs: a. Select an array from the Array list. b. Select MP blades c. Select the Live check box. Live utilization graphs of the selected MP blades are displayed. Monitoring workload performance This chapter describes how to use P9000 Application Performance Extender to generate and view performance graphs for the added workloads in your SAN environment.
Item Description Array Enables you to select an array. From Date Enables you to select a start date. From Time (HH:MM) Enables you to select a start time. To Date Enables you to select an end date. To Time (HH:MM) Enables you to select an end time. Live Displays live graphs. View History Displays historic graphs. Select Workloads Enables you to select workloads. Controller Active Switches the controller the monitoring or controlling mode.
c. d. Select the Controller Active check box. Select the Live check box. Live performance graphs of the selected workloads for an array are displayed in the Graph area. To view performance graphs for a different array, select an array from the Array list. NOTE: • In the generated graph, a target line indicating the desired SLO value is displayed based on the SLO types. • HP recommends that you view only four live graphs at a time.
To specify performance data collection interval: 1. Select Other Settings > Performance Collection Settings from the Navigation pane. The Performance Collection Settings screen is displayed. 2. 3. Enter the performance data collection interval in seconds. The minimum performance data collection interval is five seconds. Click Submit. The default performance data collection interval is15 seconds.
Figure 33 Generate report screen . Item Description Report Name Enter a report name. Array Name Select an array. Customer Name Enter your name. Report Type Select the type of report you want to generate. Start Date Select the start date and time. End Date Select the end date and time. Archive Report Select this option to save your report. The generated report is saved at the following location: \Reports Notify Errors To Enter your email ID.
Generating reports To generate reports: 1. Select Generate Report from the Navigation pane. The Generate Report screen is displayed (see Figure 33). 2. Select or enter the following details: • Report Name • Array Name • Customer Name • Report Type • Start Date • End Date • Archive Report • Notify Errors To • Select Below To Include Min. bandwidth Chart(s) In Report • Select Below To Include Latency Chart(s) In the Report 3. 4. Select a workload. You can also select multiple workloads or all workloads.
Figure 34 Schedule Report screen . Item Description Array Displays the array serial number. Schedule Name Displays the name of the schedule. Triggers At Displays the time when the schedule will trigger. Effective Date Displays the start date of the schedule. Stops By Displays the end date of the schedule. Recurs Every Displays the recurrence pattern of the schedule. Create Schedule Enables you to create a schedule. Update Schedule Enables you to update a schedule.
Figure 35 Report schedule update window . 3. Under Report Settings, specify the following details: a. Schedule Name: Enter a name for the schedule. b. Array Name: Select an array from the array list. c. Customer Name: Enter your name. d. Report Type: By default, the report type is set to PDF. Reports can be generated only in the PDF format. e. Email Report To: Enter your email ID. NOTE: • SMTP with authentication is not supported.
b. c. 8. 9. Recurrence Pattern: Select one of the options. The recurrence pattern can be hourly, daily, weekly, or monthly. Range Of Recurrence: Select the recurrence start and end date. You can also select the No End Date option. Click Submit to create a report schedule. Click Close to exit the Report Schedule Update window. A report schedule is created. Updating report schedules To update report schedules: 1. Select a schedule from the Schedule Summary table. 2. Click Update Schedule.
Figure 36 Alarms screen (Alarm Configuration) . Item Description Alarm Configuration Enables you to create, update, and remove alarms. Alarm History Displays the details of the alarm conditions met for the existing alarms in the system. Displays the source of the alarm. The source can be one of the following: • APEX system Source • Communication agent • APEX controller • Management station Source Address Displays the IP address of the alarm source. Displays the event of the alarm.
Item Description Destination Address Displays the email ID to which notifications are dispatched. Active Displays the alarm status as Active or Dormant. Disable Filter Enables you to filter alarms. Create Alarm Enables you to create an alarm. Update Alarm Enables you to update an alarm. Delete Alarm Enables you to remove an alarm. Creating alarms To create alarms: 1. Select Alarms from the Navigation pane. The Alarms screen is displayed (see Figure 36. 2. 3. Click the Alarm Configuration tab.
The Deviation amount field is enabled only if it is applicable to the selected source. 9. Select a severity level from the Severity list. 10. Select a notification type from the Notification Type list. 11. Enter a valid email ID in the Destination field. NOTE: Ensure that you specify the SMTP server address, port number, and the sender's email ID in the settings.ini file. 12. Select the enabled check box. 13. Click Submit. 14. Click Close to exit from the Alarm window. Updating alarms To update alarms: 1.
Figure 38 Alarm History screen . Filtering alarm records You can filter the alarm details based on the following: • Source • Event • Notification • Severity • Status NOTE: Filtering can be toggled on or off by selecting or clearing the Disable Filter check box. To filter alarms: 1. On the Alarm window, do one of the following: a. Select a source from the Source list to filter alarms based on the source of the alarm. b. Select an event from the Event list to filter alarms based on the event type. c.
Using P9000 Application Performance Extender
6 Launching P9000 Application Performance Extender from P9000 Performance Advisor HP StorageWorks P9000 Performance Advisor Software collects, monitors, and displays the performance of your HP StorageWorks XP/P9500 Disk Arrays. P9000 Performance Advisor collects performance data for individual resources such as LDEV, CHIP/CHA, ACP/DKA, and DKC. P9000 Application Performance Extender can be launched from P9000 Performance Advisor.
Figure 39 HP StorageWorks P9000 Application Performance Extender Software screen . The text displayed on the HP StorageWorks P9000 Application Performance Extender Software screen is taken from the AppIntegrations.properties file. So, ensure that the text is not changed in the AppIntegrations.properties file. IMPORTANT: • Only one session of P9000 Application Performance Extender can be active at a time.
7 Troubleshooting P9000 Application Performance Extender This section describes how to troubleshoot problems that can occur while using P9000 Application Performance Extender. It also includes tasks that you can perform for specific scenarios.
Problem/Scenario Recommended actions PRM data is not available during data collection for HP-UX hosts. Check if the PRM groups are configured and the PRM service is enabled on the host. You can verify if the PRM groups are configured by using the following command: /usr/bin/prmconfig Ensure the following: Command devices are not displayed during data collection.
Problem/Scenario Recommended actions Do the following: Email notifications are not dispatched. • Set the SMTP server details and the sender's email ID in the settings.ini file • Verify the email ID provided to receive email notifications. • Verify if the communication agent is running on all the hosts. Hosts are listed as offline. Filtered data is not displayed in the Alarms screen. • Refresh host list to view all the hosts connected to the management station.
Problem/Scenario Recommended actions On Linux hosts, ensure that the driver corresponding to the QLogic HBAs is listed as the first uncommented entry in the /etc/hba.conf file. • For example, on 32 bit Linux hosts, if the /etc/hba.conf file includes the following entries: lpfc /usr/lib/libemsdm.so qla2xxx /usr/lib/libqlsdm.so Change it to the following: qla2xxx /usr/lib/libqlsdm.so lpfc /usr/lib/libemsdm.so Adding/updating workloads fails on Linux hosts. • On 64 bit Linux hosts, if the /etc/hba.
Problem/Scenario Scenario: Manual controller failover procedure Recommended actions 1. On the Controller Settings screen, select the array that was controlled by the controller that rebooted. 2. Remove the controller associated with the array. 3. Select another controller for the same array that is available from the Controller(s) And Managed Array(s) Information table. 4. On the Controller Settings screen, under Command Device Settings, select an array from the Select Array list. 5.
Troubleshooting P9000 Application Performance Extender
8 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
• • • • • • • http://www.hp.com/service_locator http://www.hp.com/support/manuals http://www.hp.com/support/downloads www.hp.com/go/hpuxservermatrix www.hp.com/go/p9000 www.hp.com/go/p9500 www.hp.com/go/p9000software Typographic conventions Table 5 Document conventions Convention Element Blue text: Table 5 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts.
Support and other resources
A Checking for valid user to support command device authentication for APEX in Remote Web Console (RWC) Attributes of the user to support command device authentication for APEX: 1.
Checking for valid user to support command device authentication for APEX in Remote Web Console (RWC)
B Configuring HP Process Resource Manager groups on HP-UX hosts Process Resource Manager (PRM) provides an efficient and flexible way to manage resource allocation at times of peak system load. It gives you the ability to group users or processes together and guarantee each group the minimum amount of the total CPU, real memory, and disk bandwidth available. Installing HP Process Resource Manager PRM is installed using the Software Distribution (SD) utility.
The following configurations must be set: 1. Setup groups based on applications and need. Format for creating groups ########## FSS PRM group record ##################################### # # GROUP:{PRMID | HIER}:SHARES:[MAX]: # # GROUP # FSS PRM group name. For proper display by the ps command, use no # more than 7 characters in the PRM group name. # # PRMID | HIER # Parent nodes in a hierarchy use the HIER keyword, while leaf nodes # use PRM group ID. PRMIDs must be unique and can range from 1 # to 255.
# Full path of the application, starting with a slash (/). # The directory name must be fully qualified, but the file name can # include the shell file name wildcard characters *, ?, [, and ]. # At configuration time, all valid executables matching the expression # without explicit application records of their own will assume the # GROUP of this record. # # GROUP # Name of the application's assigned PRM group. # # ALTERNATE_NAME (optional) # Alternate name the application is assigned when executed.
Configuring HP Process Resource Manager groups on HP-UX hosts
C Deployment scenarios Application level SLOs SAN configuration Two HP-UX 11.31 servers connected to an XP24000 HP disk array through a Fibre Channel fabric • Server 1– HP-UX 11.31 server (hp1) with an instance of Oracle 11g (workload1) configured on the XP24000 array on a Disk Group 1 • Server 2– HP-UX 11.
Three Windows 2003 servers connected to an XP24000 disk array through a Fibre Channel fabric.
D Creating command devices If you are running XP RAID Manager (XP Business Copy and XP Continuous Access), you already have command devices that can be used by XP Application Performance Extender also. If XP RAID Manager is not in use, you must create a command device. To do so, you must use the XP Remote Web Console (RWC) or the Remote Control applications.
Creating a command device using XP RWC for XP24000 and XP20000 disk arrays Complete the following steps to create a command device: 1. Launch the XP RWC with administrator privileges (administrator\administrator). 2. In the XP RWC window, click GO > LUN Manager > LU Path and Security. A list of LDEVs appears. 3. Right-click the LDEV that you want to convert into a command device. 4. Select Enable\Disable from the drop down list. 5.
3. In the Replication Manager GUI, perform the following steps: a. In the Explorer menu, select Resources > Storage Systems. The Storage Systems window appears. b. Expand the object tree, and select the P9500 storage system under Storage Systems. The P9500 storage-system-name window appears. c. Click Open. The Open window appears. d. In the Cmd Devs section, click Add Cmd Devices. The Add Command Devices Wizard begins. e.
Creating command devices
E Procedure to change LDEV ownership using Remote Web Console (RWC) To modify LDEV ownership: 1. 2. 3. 4. 5. 6. Launch P9000 Remote Web Console with administrator privileges. Select Logical devices. Select all the logical devices for which you want to change LDEV ownership. Click Edit LDEVs. Under More Actions, select Assign MP blades. Select the Processor blade to which you want to assign the selected LDEVs 7. 8. Click Finish. Click Apply to confirm.
Procedure to change LDEV ownership using Remote Web Console (RWC)
F Configuring NPIV and RDM disk for VMware ESX Servers Guest level I/O prioritization using APEX for VMware ESX/ESXi servers can be achieved by configuring NPIV for virtual machines with RDM disk Configuring and Troubleshooting N-Port ID Virtualization and using RDM can be found in the following references: • http://www.vmware.com/files/pdf/techpaper/vsp_4_vsp4_41_npivconfig.pdf • http://www.vmware.com/pdf/esx25_rawdevicemapping.
Configuring NPIV and RDM disk for VMware ESX Servers
Glossary This glossary defines terms used in this guide or related to this product and is not a comprehensive glossary of computer terms. APEX P9000 Application Performance Extender. command device A command device is a XP LUN/LDEV mapping in HP-UX, Linux, or Windows that can be used to send management commands to the XP array. controller Is a software that allocates resources to application groups (HP-UX), and hosts (Windows, Linux). It helps applications achieve their Service Level Objectives (SLO).
Raw Device Mapping (RDM) A RDM is a special file in a VMFS volume that acts as a proxy for a raw device. RDM LUN supports direct access (FC or iSCSI only) between the virtual machine and physical storage subsystem. . RMLIB RMLIB is an API library that enables third party software products to directly operate some of the functions on the XP subsystem.
Index installing, 103 setting, 103 A alarms alarm history, 83 creating, 83 filtering, 83 updating, 83 viewing, 83 B bandwidth, 11 G graphs historic, 75 live, 75 H help obtaining, 97 hosts collecting configuration data, 52 discovering, 52 HP technical support, 97 I C communication agent, 11, 25 HP-UX host, 15 Windows host, 15 communication agent, 11, 25 Linux host, 15 contacting HP, 97 controller, 11 conventions document, 98 text symbols, 98 D DLOM I/O prioritization, 59 load balancing, 59 document co
M U management station, 11 Windows, 13 Managing SLOs, 63 workloads, 69 Upgrading communication agent, 21 controller, 21 management station, 21 O overview, 11 P Process Resource Manager using, 103 R related documentation, 97 removing controller, 25 management station, 25 reports generate, 78 schedule, 78 S settings command device, 55 controller, 55 SLO profiles updating, 63 SLO profiles creating, 63 removing, 63 scheduling, 67 Subscriber's Choice, HP, 97 symbols in text, 98 T technical support HP, 97
