HP Insight Capacity Advisor 6.

2 User Guide

HP Part Number: T8670-90019 Published: November 2010 Edition: 2

 Copyright 2006, 2010 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. 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. Acknowledgments HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95 branded products. UNIX is a registered trademark of The Open Group. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Revision history

Document Part Number T8670-90019 T8670-90019

Edition 2 1

Software Version 6.2.0 6.2.0

Supported Operating Systems See the HP Insight Software 6.2 Support Matrix. See the HP Insight Software 6.2 Support Matrix.

Publication Date November 2010 October 2010

Table of Contents
1 Introduction...................................................................................................................11
Setup considerations.............................................................................................................................12 Licensing requirements...................................................................................................................12 Installation.......................................................................................................................................12 Collection methods..........................................................................................................................12 Disk space requirements..................................................................................................................12 Credentials.......................................................................................................................................13 Dependencies...................................................................................................................................13 Upgrades and reinstallation.................................................................................................................13 Upgrading agents on HP-UX or OpenVMS managed systems......................................................13 Navigating within HP SIM, Virtualization Manager, and Capacity Advisor......................................13

2 Features.........................................................................................................................15
Data collection.......................................................................................................................................16 Data collection infrastructure..........................................................................................................16 Supported collection configurations...............................................................................................17 Comparison of agentless and UP data collection............................................................................18 HP PMP data differs from Utilization Provider data......................................................................19 Differences in memory data ......................................................................................................19 Differences in network data ......................................................................................................19 Related topics........................................................................................................................19 Experimentation....................................................................................................................................20 Sizing for service level objectives..........................................................................................................21 Modeling considerations......................................................................................................................22 Capacity Advisor commands...............................................................................................................22

3 Key Capacity Advisor concepts..................................................................................23

Capacity planning goals.......................................................................................................................23 Quality of service ............................................................................................................................23 Utilization monitor, calculator, and simulator.....................................................................................23 Data handling for virtual machines.................................................................................................23 Data normalization..........................................................................................................................24 Resources for which Capacity Advisor collects data............................................................................24 Upper bounds..................................................................................................................................24 Measuring and analyzing resource utilization.....................................................................................25 Peaks and sums................................................................................................................................25 Sampling interval.............................................................................................................................25 Headroom........................................................................................................................................25 Headroom star rating.................................................................................................................26 Interpreting the headroom star rating..................................................................................26 Missing or invalid data....................................................................................................................27 The affect of invalid data on HP Smart Solver solution finding................................................27 Utilization limits .............................................................................................................................27 Specifying utilization limits.......................................................................................................28 Sustained time limits.............................................................................................................28 Percentage of time limits.......................................................................................................28 Understanding utilization limit messages.................................................................................29 Percentage of allocation........................................................................................................29 With sustained limits............................................................................................................29
Table of Contents 3

With percentage of time limits..............................................................................................29 Scope of utilization limits...........................................................................................................29 Adjusting power...................................................................................................................................30 Power cap data.................................................................................................................................30 Automating solution generation: HP Smart Solver..............................................................................31 HP Smart Solver: Types of solutions...............................................................................................31 Determining trends in Capacity Advisor.............................................................................................31 Aggregation of points in business interval bins..............................................................................32 Choosing an appropriate business interval...............................................................................32 Exclusion of data points..................................................................................................................32 Factors that affect data validity..................................................................................................32 Linear regression.............................................................................................................................33 Error analysis...................................................................................................................................33 Forecasting growth...............................................................................................................................33 The forecast model hierarchy..........................................................................................................33 Forecast model attributes................................................................................................................34

4 Planning with Capacity Advisor.................................................................................35

Getting ready........................................................................................................................................35 Task: Understand current resource usage............................................................................................35 Task: Plan server consolidation.............................................................................................................36 Understanding the consolidation task............................................................................................36 Example consolidation: Stacking applications on an existing server........................................36 Step 1: Determine which systems to consolidate..................................................................37 Step 2: Create a scenario.......................................................................................................37 Step 3: Edit the scenario........................................................................................................38 Automating the consolidation task.................................................................................................46 Example consolidation: Automating stacking on a what-if server........................................47 Step 1: Determine which systems to consolidate..................................................................47 Step 2: Create a scenario.......................................................................................................47 Step 3: Edit the scenario........................................................................................................48 Task: Estimating the effect of adding or moving processors................................................................51 Task: Determining where to put a workload using automated solution finding.................................52 Example: Determining where to put a workload............................................................................52

5 Procedures....................................................................................................................55
Accessing Capacity Advisor.................................................................................................................55 Gathering data for Capacity Advisor...................................................................................................55 Impact of data collection on managed system performance...........................................................56 Data collection options....................................................................................................................56 First data collection (or the automated nightly collection).............................................................58 Interpreting task results...................................................................................................................59 Error notification on the standard out tab.................................................................................59 Scheduling a data collection............................................................................................................60 Modifying a collection schedule......................................................................................................61 Removing a collection schedule......................................................................................................61 Updating collected data...................................................................................................................61 Updating collected data on all systems......................................................................................62 Updating collected data on selected systems.............................................................................62 Updating data displayed in a profile viewer.............................................................................62 Collecting data without using an agent..........................................................................................62 Listing systems currently in the configuration file....................................................................62 Setting advanced options in the agentless data collection file...................................................63
4 Table of Contents

Data collection and the HP Insight Capacity Advisor Consolidation software..............................63 Using Capacity Advisor with consolidation software server data............................................64 Viewing the licensed servers in HP SIM....................................................................................64 Importing data for use in Capacity Advisor...................................................................................64 From the Optimize menu Import HP OVPA data.................................................................64 From the Optimize menu Import HP PMP data...................................................................65 From the command line.............................................................................................................66 Ascertaining the data collection availability for a set of servers................................................66 Possible sources of discrepancies in collected data.........................................................................66 No data collected for a managed node......................................................................................66 Data timestamp appears to be incorrect....................................................................................66 Dynamic memory in HP Integrity virtual machines.................................................................67 Producing graphs and reports..............................................................................................................67 Using the Profile Viewer..................................................................................................................67 Using the report wizard..................................................................................................................71 The report wizard.......................................................................................................................71 Creating an historic utilization report........................................................................................72 Creating a scenario utilization report........................................................................................73 Using the report wizard to create a scenario comparison.........................................................74 An example scenario comparison report..............................................................................74 Calculating a virtualization consolidation ratio...................................................................75 Creating a consolidation candidates report...............................................................................76 Creating a cost allocation report................................................................................................76 Creating a peak summary report...............................................................................................76 Creating a population report.....................................................................................................77 Creating a trend report...............................................................................................................77 Creating a power report.............................................................................................................78 Setting utilization limits........................................................................................................................78 Setting global utilization limits.......................................................................................................79 Adding a utilization limit...........................................................................................................79 Removing a utilization limit......................................................................................................79 Setting workload utilization limits..................................................................................................80 Adding a utilization limit...........................................................................................................80 Enabling or disabling the limit...................................................................................................80 Removing a utilization limit......................................................................................................80 Setting scenario-wide utilization limits...........................................................................................80 Adding a utilization limit...........................................................................................................80 Enabling or disabling the limit...................................................................................................81 Removing a utilization limit......................................................................................................81 Setting scenario workload utilization limits....................................................................................81 Adding a utilization limit...........................................................................................................81 Enabling or disabling the limit...................................................................................................81 Removing a utilization limit......................................................................................................82 Forecasting utilization..........................................................................................................................82 Defining forecast models.................................................................................................................82 Accessing the Global Forecast Model........................................................................................82 Defining the Global Forecast Model.....................................................................................83 Accessing the forecast model for a workload or system............................................................83 Defining the forecast model for a workload or system........................................................84 Accessing the forecast model for a scenario..............................................................................84 Accessing the forecast model for a workload within a scenario................................................85 Defining a forecast model..........................................................................................................85 Disabling a forecast model.........................................................................................................85 Enabling a forecast model..........................................................................................................85 Generating forecasts........................................................................................................................85
Table of Contents 5

Viewing forecast data in a profile viewer..................................................................................86 Viewing forecast data in a utilization report.............................................................................86 Working with scenarios........................................................................................................................86 Creating a planning scenario...........................................................................................................86 Editing a scenario............................................................................................................................88 Controlling the data display............................................................................................................88 Change the meter style selection................................................................................................88 Change the data collection period by setting the data range.....................................................88 Change the meter representation...............................................................................................90 Copying a scenario..........................................................................................................................90 Renaming a scenario........................................................................................................................90 Undo/edit/review applied what-if actions in a scenario.................................................................91 To view applied what-if actions.................................................................................................91 To edit applied what-if actions...................................................................................................91 Modifying resource utilization values..................................................................................92 Deleting a scenario..........................................................................................................................92 Working with systems..........................................................................................................................93 Creating a system............................................................................................................................93 Adding an existing system..............................................................................................................94 Editing a system..............................................................................................................................94 Changing VMs to be servers............................................................................................................94 Change VMs to server................................................................................................................95 Changing servers to be VMs (manually).........................................................................................95 Change servers to be VMs..........................................................................................................95 Assigning VM hosts to a VMware DRS cluster in a scenario..........................................................96 Initially converting VM hosts to simulate a VMware DRS cluster............................................96 Adding VM hosts to a converted cluster...................................................................................97 Removing a VM host from a VMware DRS cluster...................................................................97 Removing a VMware DRS cluster from a scenario....................................................................97 Moving a virtual machine...............................................................................................................98 Removing a system..........................................................................................................................99 Editing network and disk I/O capacity...........................................................................................99 Getting there...............................................................................................................................99 Setting the upper bound values.................................................................................................99 Working with workloads....................................................................................................................100 Introduction...................................................................................................................................100 Creating a workload......................................................................................................................100 Editing a workload........................................................................................................................101 Moving a workload........................................................................................................................102 Move considerations.................................................................................................................102 Parking a workload........................................................................................................................104 Deleting a workload......................................................................................................................104 Working with power...........................................................................................................................104 Calibrating power within Virtualization Manager........................................................................105 Calibrating a single system......................................................................................................105 Calibrating multiple systems at once.......................................................................................107 Calibrating power within a scenario.............................................................................................107 Getting there.............................................................................................................................108 Calibrating a single system......................................................................................................108 Calibrating multiple systems at once.......................................................................................109 Automating time-consuming simulations..........................................................................................109 Automated solution finding: System consolidation to VMs.........................................................109 Begin with a scenario................................................................................................................110 Choose the systems to consolidate...........................................................................................110 Step 1 of 3: Define the destination system(s) and attributes....................................................110
6 Table of Contents

Step 2 of 3: Set level of effort for Smart Solver calculation.......................................................111 Step 3 of 3: View Smart Solver solutions..................................................................................111 Results: Automated consolidation to VMs.........................................................................112 Automated solution finding: Load balance of servers or VM hosts .............................................113 Begin with a scenario................................................................................................................113 Choose the VM hosts or servers to load-balance.....................................................................113 Step 1 of 3: Define the solution constraints..............................................................................114 Step 2 of 3: Set level of effort for Smart Solver calculation.......................................................114 Step 3 of 3: View Smart Solver solutions..................................................................................114 Results: Automated load balancing of servers or VM hosts...............................................114 Automated solution finding: Workload stacking..........................................................................115 Begin with a scenario................................................................................................................116 Choose the workloads to stack.................................................................................................116 Step 1 of 3: Stack the specified workloads onto servers...........................................................116 Step 2 of 3: Set level of effort for Smart Solver calculation.......................................................117 Step 3 of 3: View Smart Solver solutions..................................................................................117 Results: Automated workload stacking..............................................................................117 Getting more detail........................................................................................................................118

6 Using Capacity Advisor with HP Serviceguard......................................................119

Using Serviceguard to migrate HP Integrity VM guests....................................................................119 Data collection in a Serviceguard environment..................................................................................120

7 Support and other resources....................................................................................121

Contacting HP.....................................................................................................................................121 New and changed information in this edition....................................................................................121 New and changed information in Edition 1..................................................................................121 Related information............................................................................................................................121 Related technical papers................................................................................................................122

A Calculation assistance..............................................................................................123
Cost calculation...................................................................................................................................123 Cost per kilowatt-hour...................................................................................................................123 Cooling calculation.............................................................................................................................123 Cooling multiplier.........................................................................................................................123 Adjusting for platform changes..........................................................................................................123 Memory multiplier........................................................................................................................124 Adjusting for change in a workload...................................................................................................124 CPU workload multiplier..............................................................................................................124 Memory workload multiplier........................................................................................................125 Network I/O workload multiplier.................................................................................................125 Disk I/O workload multiplier........................................................................................................125 Determining estimated utilization assumptions for a workload..................................................125 Adjusting for virtualization changes..................................................................................................127 CPU Virtualization Overhead %....................................................................................................127 CPU Virtualization Overhead %..............................................................................................128 Hypervisor memory overhead......................................................................................................128 Hypervisor memory overhead.................................................................................................128 Doing the math for hypervisor memory overhead..................................................................128 HP Virtual Machine............................................................................................................128 VMware ESX 3.....................................................................................................................128 VMware vSphere (ESX 4)....................................................................................................129 Microsoft Hyper-V..............................................................................................................129
Table of Contents 7

Power calibration calculations............................................................................................................129 Determining idle/max values for non-Blade servers ....................................................................129 Determining idle/max values for Blade servers............................................................................130 P-class HP Blades and HP Blade system sizer:........................................................................130 C-class HP Blades and HP Blade system sizer:........................................................................131

B Command reference..................................................................................................133
capagentlesscfg (1M)...........................................................................................................................134 capcollect (1M)....................................................................................................................................136 capcustombenchmark(1M).................................................................................................................139 capcustombenchmark (4)....................................................................................................................141 capovpaextract (1M)............................................................................................................................142 capprofile (1M)....................................................................................................................................144 capprofile (4).......................................................................................................................................148 cappmpextract ....................................................................................................................................151

C Units and terminology...............................................................................................153 D Snapshots of Capacity Advisor reports...................................................................157

Consolidation candidate report..........................................................................................................157 Scenario comparison report................................................................................................................157

E Graphed data in Capacity Advisor reports............................................................161 F Example of the Undo/Edit/View Applied What-If Actions screen.......................163 G Troubleshooting in Capacity Advisor ....................................................................165
When there is no connection...............................................................................................................165 Data is not being collected..................................................................................................................166 Data may appear to be old when it is not...........................................................................................167 Data seems to be incorrect or lost.......................................................................................................168 Data cannot be imported.....................................................................................................................170 Out-of-memory errors in the Java heap..............................................................................................170 When working with reports................................................................................................................171 When working in the scenario editor..................................................................................................171 When working with power.................................................................................................................172 Workload and system relationships may not match when comparing Capacity Advisor and Virtualization Manager information...................................................................................................173 Miscellaneous user interface issues....................................................................................................173

H Capacity Advisor messages.....................................................................................175

Command error messages..................................................................................................................175 Command warning messages.............................................................................................................176 HP Smart Solver error messages.........................................................................................................180 When available systems lack sufficient capacity...........................................................................180 When the threshold for invalid data is exceeded..........................................................................181 HP Smart Solver informational messages...........................................................................................182

Glossary.........................................................................................................................183
8 Table of Contents

Index...............................................................................................................................191

Table of Contents

10

1 Introduction
This document describes how to use Capacity Advisor to plan for changes in resource usage in a virtualized server environment. Checklists and examples help you with common planning tasks. This document is for technical professionals working in data center operations, administration, and planning. Some understanding of system administration is assumed. HP Insight Capacity Advisor software is a program that allows you to monitor and evaluate system and workload utilization of CPU cores, memory, network and disk I/O, and power. With this information, you can load your systems to make best use of the available resources. You can monitor and evaluate one or more systems that are connected in a cluster configuration or to a network. A single system can include multi-core or hyper-threaded processors. Capacity Advisor helps you evaluate system consolidations, load balancing, changing system attributes, and varying workloads to decide how to move workloads to improve utilization. The quantitative results from Capacity Advisor can aid the planner in estimating future system workloads and in planning for changes to system configurations. With Capacity Advisor, you can perform the following tasks within an easy-to-navigate, clearly notated graphical user interface: Collect utilization data on CPU cores, memory, network and disk I/O, and power. View historical resource utilization for whole-OS and monitored workloads on HP-UX and OpenVMS systems and whole-OS workload resource utilization on Microsoft Windows and Linux systems. View historical workload resource utilization and aggregate utilization across the partitioning continuum (see the HP Insight Software 6.2 Support Matrix for a complete list of supported platforms). Generate resource utilization reports. Plan workload or system changes, and assess impact on resource utilization. Assess resource utilization impact for proposed changes in workload location or size. Evaluate trends for forecasting resource needs.

Capacity Advisor can be used to simulate changes in system configuration, such as the following: Consolidating several systems into one system Re-sizing a system for an upgrade Re-sizing the demands on a system to reflect a forecast Replacing older, small to mid-sized systems with virtual machines Capacity Advisor can use data collected over time to show the results of these configuration changes in many ways. Graphical views are available so you can see what the effects of the changes are over time. Tables are available that give the percentage of time and the degree to which the system is busy; this information is valuable in comparing resource utilization and quality of service before and after a change. Other tables show how many minutes per month the system is unacceptably busya measure valuable for both quality of service and for estimating TiCAP bills. Because Capacity Advisor works from data traces collected over time, it is much more accurate than using only peak data or average data in understanding your systems and the workloads they support. The significant advantage in using Capacity Advisor, rather than ad hoc processes or guesswork, is that it provides a quantitative basis for examining the usage of current resources. Additionally, it provides the capability to try simulations (what-if scenarios) for moving workloads or other resources before you actually implement a move. Capacity Advisor incorporates numerical values of several components in its analysis and modeling, including:

11

Number of CPU cores CPU benchmark data Memory size Network I/O bandwidth Disk I/O bandwidth Power usage Platform multiplier for memory (see Adjusting for platform changes (page 123)) Virtualization adjustments (see Adjusting for virtualization changes (page 127))

Setup considerations
To prepare to use Capacity Advisor, consider the following: Licensing requirements Installation Upgrade and reinstallation Credentials Dependencies

Licensing requirements
Capacity Advisor is installed when HP Insight Dynamics suite is installed. For specific information about trial and LTU (License To Use) licensing on supported platforms, see the HP Insight Dynamics 6.2 Getting Started Guide at http://www.hp.com/go/insightdynamics/docs. For added information on using the HP Insight Capacity Advisor Consolidation software license, see Data collection and the HP Insight Capacity Advisor Consolidation software (page 63). Capacity Advisor and Capacity Advisor Consolidation Software licenses cannot be used on the same system at the same time.

Installation
Capacity Advisor is installed with other Insight Dynamics components, so no separate installation is required. (See the Insight Dynamics installation guide at http://www.hp.com/go/ insightdynamics/docs appropriate for your operating system.) To use Capacity Advisor, you must have a valid license.

Collection methods
On installation of HP Insight Dynamics suite, the Insight managed system setup wizard automatically configures the mechanism used to collect data from managed servers based on the type of operating system that the managed system is running. (See Supported collection configurations (page 17).) Some problems with data collection can be diagnosed with vseassist. See the HP Insight Dynamics 6.2 Getting Started Guide for additional information.

Disk space requirements

Plan to allot the following amounts of memory for each workload to collect and preserve a maximum of four years of data for use by Capacity Advisor: On a Microsoft Windows CMS: Allot 64.5 MB for each workload on each Windows or Linux managed node to support agentless data collection. Allot 34.7 MB for each workload on each HP-UX managed node. On an HP-UX CMS: Allot 93.1 MB for each workload on each Integrity Linux managed node to support agentless data collection. Allot 34.7 MB for each workload on each Integrity Windows or HP-UX managed node.

12

Introduction

For additional information on disk space requirements, see the Insight Dynamics installation guide appropriate for your operating system at http://www.hp.com/go/insightdynamics/docs .

Credentials
To use Capacity Advisor, to collect data, and to run reports, you must have credentials (a valid user name and password) and appropriate toolbox authorization on systems where you plan to use Capacity Advisor. For specifics about setting up user authorizations, see the HP Insight Dynamics 6.2 Getting Started Guide at http://www.hp.com/go/insightdynamics/docs.

Dependencies
Data collection requires that credentials for each managed server be configured in HP SIM. WBEM/WMI credentials must be configured for all Windows servers, HP-UX servers, and HP Integrity VMs. For agentless data collection on Windows systems, the WBEM/WMI credentials must be set to Administrator level. WBEM certificate authentication is supported for HP-UX servers. SSH credentials (user-based, host-based key, or by certificate) must be configured for all Linux servers. Linux agentless data collection does not require root-level access. HP SIM Privilege elevation is supported on HP-UX and Linux servers using a single user account with sudo or powerbroker with no password required. The Windows or Linux managed node must be configured for agentless data collection by running the Insight managed system setup wizard, or by running Collect Capacity Advisor Data... (capcollect) on the managed server. Administrator or root level permission on the CMS is required to configure agentless collection on the CMS. HP Insight Control virtual machine management (VMM) is required to collect data from ProLiant/x86-based hypervisors and their VMs. Hyper-V VMs also require that WBEM/WMI credentials be configured for Windows VMs and SSH for Linux VMs.

Upgrades and reinstallation

When upgrading or reinstalling software used with Capacity Advisor, there are different considerations and procedures to follow specific to the operating systems underlying the CMS or running on the managed node. Refer to the appropriate installation guide for instructions. Install guides can be downloaded from http://www.hp.com/go/insightdynamics/docs.

Upgrading agents on HP-UX or OpenVMS managed systems

NOTE: This section does not apply to Microsoft Windows or to Linux systems, for which data is collected by leveraging native instrumentation (agentless data collection). When upgrading the Utilization Provider to the latest version on a managed node, any data collected since the last capcollect command execution is lost. To minimize data loss, run the capcollect command on the CMS to collect from the managed node just before upgrading.

Navigating within HP SIM, Virtualization Manager, and Capacity Advisor

Avoid using your browser Back and Forward buttons (except when navigating in the online help). When you use these buttons, the user interface cannot tell that you have changed to a different view. This can cause problems, including incorrectly displaying which objects are selected in the current view, losing information input into screen fields, and cancelling operations. Instead, use the navigation links, buttons, and tabs provided by the user interfaces within the browser screen area.

Upgrades and reinstallation

13

14

2 Features
Capacity Advisor lets you test configuration changes before actually making them in your data center, and helps you to manage existing resources to improve their utilization. For example, Capacity Advisor assists you in answering questions such as the following: Is there room on this system to support additional work? Will this workload fit on this system? Can these servers be consolidated as virtual machines on a single server? What might my resource demand be in six months or a year? What are the estimated power costs for cooling a real or simulated system configuration? What does a comparison of several what-if scenarios reveal about the analyzed alternatives? What is the historic behavior of a system or workload?

Capacity Advisor can display data about the following system resources: CPU cores (number) and speed Memory Network I/O bandwidth Disk I/O bandwidth Power usage Capacity Advisor enables you to collect resource data and create visualization graphs with the following views: Historical utilization and trends Data peaks Peak durations Forecasts with the following utilization limits: amount of acceptable resource usage sustained time percentage of time Capacity Advisor enables you to create scenarios for what-if planning and forecasting, performing tasks such as the following: For systems in scenarios: Create systems based on existing systems or with characteristics that you define Remove systems Edit system attributes Turn systems into virtual machines Move virtual machines For workloads in scenarios: Create workloads based on existing workloads or with characteristics that you define Collect utilization data for workloads Import existing workload profiles Edit workload demands Move workloads between systems Park workloads Delete workloads For scenarios themselves: View and undo/redo scenario changes Use the HP Smart Solver technology to perform:
15

Automated server consolidation to virtual machines Automated load balancing of existing VM hosts or existing servers Automated workload stacking (consolidation)

Create scenario comparison reports

Data collection
Data collection is at the heart of Capacity Advisor and a task is created during configuration to automatically collect utilization data from all resources licensed for Insight Dynamics and discovered by HP Systems Insight Manager software (HP SIM). (See First data collection (or the automated nightly collection) (page 58).) HP recommends that once you have become familiar with using Capacity Advisor, you should review this scheduled task to understand what it is doing and make sure that it fits your needs. This automated data collection task gathers historical data from all your systems so that the data is available when you need it for analysis.

Data collection infrastructure

In the data collection infrastructure, each component plays a role, as shown in Figure 2-1 Capacity Advisor Data Collection Infrastructure. It all begins with data collection. Figure 2-1 Capacity Advisor Data Collection Infrastructure

The Agentless Data Collector Services run on the CMS and collect data from Microsoft Windows and Linux managed systems. Agentless data collected by the Agentless Data Collector Service is made

The Data Collector gathers data from the agentless data files, the Utilization Providers running on the managed nodes, and from VMM. You can import data (HP OVPA and HP PMP) into the historical database for analysis.

11

12

13

Scenario data is stored automatically for continued use in the Scenario Editor. Use the Scenario Editor to manipulate the collected data associated with workloads and systems. Use a Profile Viewer to examine a graphical

16

Features

available to the Capacity Advisor Data Collector. The Utilization Provider enables the operation of the Capacity Advisor Data Collector. HP Insight Control virtual machine management (virtual machine management) data is made available to the Capacity Advisor Data Collector. Characteristics of managed systems are stored in the Insight Dynamics database and used when collecting utilization Data.

9 10

Automatic data conversion occurs when importing data into the Insight Dynamics database. Historical data is stored for use in Capacity Advisor. The Utilization Calculator uses historical utilization data and scales, sums, or converts it to approximate actual or hypothetical system utilization.

14

15

display of the utilization of a specific resource for a specific workload or system. Use the Report Generator to create reports for understanding utilization. Use the web browser to work with Capacity Advisor and exploit its features.

Collecting data for a workload with a HP Serviceguard package

You can associate a monitored workload with a Serviceguard package. This association allowsVirtualization Manager to show workloads moving from one system to another within minutes of a Serviceguard migration. It also allows Capacity Advisor to show an uninterrupted history of utilization data for a workload across migrations. Associating monitored workloads and Serviceguard packages requires that Serviceguard and the corresponding version of the Utilization Provider have been installed on all member systems of the Serviceguard cluster. For specific version information, see the HP Insight Software 6.2 Support Matrix.

Supported collection configurations

Table 2-1 Collection methods by operating system on CMS and managed node types1
Managed node software and/or OS Collector for Microsoft Windows CMS VMM host or guest VMM Hyper-V VM Microsoft Windows on HP Integrity Virtual Machine (HP VM) Linux on HP VM HP-UX on HP VM OpenVMS on HP VM standalone Windows standalone Linux standalone HP-UX standalone OpenVMS VMM VMM and agentless method HP VM Provider and agentless method Collector for HP-UX CMS not supported not supported HP VM Provider and Utilization Provider

HP VM Provider and agentless method

HP VM Provider and agentless method

HP VM Provider and Utilization Provider HP VM Provider and Utilization Provider Utilization Provider agentless method agentless method Utilization Provider Utilization Provider Utilization Provider Utilization Provider (Integrity only) agentless method Utilization Provider Utilization Provider

Data collection

17

Data is obtained from some managed system types using more than one collector. This is done where the data from both collectors provide a broader or more accurate view than can be obtained from using only one collector on that managed system type. For example, where both natively collected data (agentless) and data from the Integrity Virtual Machines Provider are used, the HP VM agent provides info about the VM that allows Capacity Advisor to obtain more accurate CPU data for the VM, and the agentless method provides metrics other than CPU utilization.

NOTE: The supported collection configurations for a managed node are normally set up by the Insight managed system setup wizard. If the capcollect command is run before the wizard is run on a managed node, and agentless data collection is supported for the managed node, the node will be configured for agentless collection at that time. Because no agentless data is yet available, however, the message:
Error: At the time data collection was run, system "system-name" was not configured for agentless data collection. It has been configured and data collection will begin shortly. No utilization data is available now. Try collecting again in 5 minutes.

will appear in the command output. Subsequent collections will retrieve collected data beginning at the time the capcollect command was run on the managed node.

Comparison of agentless and UP data collection

Table 2-2 (page 18) compares the operational characteristics of agentless data collection and that of the Utilization Provider (UP) when used to collect data from systems licensed for Capacity Advisor. Agentless Data Collection. This method leverages native data collection already occurring on the managed server(s). WBEM Utilization Provider. This method uses an agent to gather the data and provide it to the CMS.

Table 2-2 A comparison of agentless data collection and use of Utilization WBEM Provider
Agentless data collection Utilization Provider (UP) Equally useful in data quality and accuracy. Available for Microsoft Windows, Linux, and non-HP systems Available for HP-UX and OpenVMS systems

Provides the basic set of utilization metrics for CPU, Provides the basic set of resource utilization metrics for memory, network I/O, and disk I/O, plus additional CPU, memory, network I/O, and disk I/O. metrics for reporting specific activities in the operating system, disk, and network: CPU queue length, page faults/second, disk I/Os per second, LAN packets/second, number of disks, disk space total, disk space used. Leverages existing data on the system; no additional agent Requires hosting and updating the UP agent hosting or update required Susceptible to network or CMS downtime as data is continuously collected by the CMS across the network from each managed system Small additional load on the CMS CPU and memory resources incurred by the ongoing operation of the agentless data collection service Not susceptible to downtime in the network or the CMS. Collected data is held for a maximum of 30 days by the UP for transfer to the database on the CMS Slight additional load on CMS CPU or memory resources incurred once per day

Slight additional load on managed system resources due Slight additional load on managed system resources, due to remote queries from the collector every 5 minutes to local queries from the UP agent every 5 minutes, and storage/retrieval of historical metrics on the local file system

18

Features

Table 2-2 A comparison of agentless data collection and use of Utilization WBEM Provider (continued)
Agentless data collection Utilization Provider (UP)

Small additional load on the network incurred by the Slight additional load on network incurred once per day ongoing operation of the agentless data collection service Data collection starts within a few minutes of configuring Data collection starts within 24 hours of configuring the the system using Insight managed system setup wizard system using Insight managed system setup wizard. However, if the UP is already running on the managed system, the data collected may cover an interval as long as 30 days previous to configuration in Insight Dynamics.

HP PMP data differs from Utilization Provider data

Differences in data imported from HP Performance Management Pack (HP PMP) affect how you should interpret resulting analysis and scenarios as compared to data collected from the Utilization Provider.

Differences in memory data

Capacity Advisor normally measures memory collected from the Utilization Provider, which returns the sum of memory allocated to the processes on the system. HP PMP collection provides the total memory less the zeroed, free, and standby memory. This means that HP PMP counts memory used by the operating system, whereas the Utilization Provider does not. The memory use reported by HP PMP is about 20% higher than memory use reported by the Utilization Provider. Because Capacity Advisor assumes a different memory amount than HP PMP provides, Capacity Advisor may overestimate the memory needed when using HP PMP data to analyze stacking several application instances in a system running a single instance of an operating system. While either the Utilization Provider data or the HP PMP data can be used to plan memory size in a new configuration, you should not use a mix of HP PMP and Utilization Provider data when looking for a trend in memory utilization.

Differences in network data

HP PMP does not report the correct network I/O when network interface cards (NICs) are being teamed for network fault tolerance (for example, by using HP Network Config utility). That is, for a system with 2 NICs teamed as one single logical NIC, Utilization Provider reports the addition of TX and RX Mbps for the teamed NIC. HP PMP adds the metrics from the 2 NICs, ignoring that they are working as a teamed NIC. For a teamed configuration, the HP PMP network utilization curve will be always twice that of the Utilization Provider data. If you know you have teamed NICs, or if you suspect your imported network data is twice as high as it should be, you will want to instruct Capacity Advisor to ignore the imported data. When logged in as a user authorized to use the Capacity Advisor toolbox on the CMS, you will be able to mark data as invalid. You can do this from a profile viewer, or by using the capprofile(1M) command. Related topics Data handling for virtual machines (page 23) Using the Profile Viewer (page 67) Command reference (page 133)

Data collection

19

Experimentation
You can better understand Capacity Advisor by experimenting considering different configurations and workload placement trying them out in what-if scenarios. A scenario identifies the workload demand profile that creates your experimental simulations. When you do workload analysis in Capacity Advisor, you view graphs and reports that represent CPU or memory utilization by time. For example, Figure 2-2 shows a graph of CPU utilization for a single system over a one-month period. Figure 2-2 CPU utilization for managed system puny03v8

Peak (highest) value.

Similarly, Figure 2-3 shows CPU utilization for a second system over the same period. Figure 2-3 CPU utilization for managed system puny03v7

Peak value.

Comparing these two graphs shows that workload peaks on the two systems do not occur simultaneously, nor do they require the same percentage of the allocated CPU cores for processing. This suggests an opportunity to consider whether you can consolidate both systems together to satisfy the needs of the workloads, while reducing the number of CPU cores (originally each system is allocated 2 cores, for a total of 4 cores available to do work). Figure 2-4 shows the result of using a Capacity Advisor what-if scenario to combine the workloads onto one system.

20

Features

Figure 2-4 Combined what-if CPU utilization for puny03v8 and puny03v7

Peak value.

From the graph, it is evident that the peak of the combined workloads is under 2 CPU cores. Even with utilization limits in place, this system is unlikely to need 4 CPU cores to meet this workload demand.

Sizing for service level objectives

As part of planning configuration changes, you can also consider your service level objectives or quality of service goals. The following utilization graph shows only one month of data; longer periods of data provide an increasingly accurate picture of resource usage. Figure 2-5 CPU utilization with selected percentiles of utilization

In this example, an allocation of three CPU cores is assumed, rather than the four cores initially available in this exercise. Even this reduction may not provide the best fit, as the vast majority of the work (90%) is completed with less than .5 of one core, and 99% of the work is completed with one core. For example, as shown in Figure 2-5 (page 21), CPU utilization has one peak at 1.7 CPU cores, with many lower peaks. If you configure your system to always meet the demand of this single 1.7-CPU peak, and you do not adjust the CPU allocation, a significant fraction of the CPU allocation in this example would go unused most of the time. Depending on your quality of service goals, you may decide that a different configuration can better use the resources available.
Sizing for service level objectives 21

Further experimentation in Capacity Advisor with resource allocations, consolidations, and utilization limits will help you arrive at the best fit for these workloads. With Capacity Advisor's visualization and reporting tools, you can make a considered estimate of server resource utilization using different scenarios and easily refine allocations by tweaking values in the scenarios. Such estimates can help you minimize overspending for capacity you use rarely, and maximize utilization of your systems to ensure that your systems have the capacity needed at the level you require.

Modeling considerations
Capacity Advisor methodology makes certain assumptions in its data analysis. These assumptions include using an automatically determined CPU performance index, with normalization based on benchmark data or benchmark data in combination with CPU clock speed in special cases. Memory is not normalized. Scale factors can be set on the Capacity Advisor Edit Workload and Move Workload screens. SeeAdjusting for platform changes (page 123) for more information. On the Edit Scenario screen, you can select either the System or Workload tab to manipulate the planning scenario and specify which metric representation to view: average, 90th percentile, peak or max 15-min (maximum 15-minute sustained). The Meter Style can be absolute numbers or in percentages. By changing the metrics to view, you can explore multiple options for system and workload deployment. See Controlling the data display (page 88) for more information.

Capacity Advisor commands

In addition to tasks that you can perform from the Capacity Advisor graphical user interface, Capacity Advisor provides several commands that can be run from the command line on an HP-UX or Microsoft Windows CMS. For specific information, see Command reference (page 133).

22

Features

3 Key Capacity Advisor concepts

Capacity planning goals
Capacity planners are driven by multiple, sometimes conflicting, goals: Avoiding surprises Planning for the future Maintaining quality of service (see Quality of service (page 23)) Optimizing resource utilization Meeting internal and external security requirements Reducing costs HP Insight Capacity Advisor software can help lessen the conflicts among goals by buttressing decisions with better information and more robust models. Effective use of Capacity Advisor can help you to double resource utilization in many situations. The most important step in accomplishing capacity planning goals is to clearly understand the goals and the relationship among them. For example, optimizing response time may preclude trying to achieve the most efficient resource utilization, while optimizing resource utilization can compromise certain types of security. It is critical to understand the requirements as well as their priorities to provide best overall quality of service.

Quality of service
Typical aspects of quality of service include (but are not limited to): Availability Accessibility Integrity Performance Reliability Regulatory requirements Security Quality of service is frequently defined in service level agreements between organizations.

Utilization monitor, calculator, and simulator

At a fundamental level, HP Insight Capacity Advisor software collects data from utilization monitoring daemons on systems and workloads. Using this data, Capacity Advisor can report on utilization of memory, core processing units, I/O bandwidth, and power. It can calculate what resource utilization would look like if the load were increased or decreased. Further, it can simulate what resource utilization might look like if loads are combined. This goes beyond simple addition of maximum loads to provide a dynamic addition of components based on the time sequence of utilization measurements taken from the actual loads running on real systems (see Peaks and sums (page 25)).

Data handling for virtual machines

Data collected by Capacity Advisor for use in a profile viewer and historical utilization reports can vary from data reported by tools that run inside a virtual machine. These tools include HP-UX and Linux commands such as top, ps, and sar, and on Microsoft Windows, the task manager or perfmon. This data can vary in a couple of ways. For example: Capacity Advisor usually reports CPU utilization that is greater than what is reported by the VM guest. The operating system inside a virtual machine only knows about the CPU
Capacity planning goals 23

time used by threads that simulate the virtual processors. However, there are also threads that simulate the I/O cards and disks in the virtual system. Capacity Advisor collects data on all of these threads, which can cause the Capacity Advisor data for a specific virtual machines CPU utilization to be greater than the number of virtual CPU cores (vCPUs) associated with the virtual machine. Under certain load conditions, this can result in CPU utilization of more than 100% being reported for a virtual machine. Capacity Advisor data for VM host CPU utilization can be lower than what the guest operating system reports, especially during periods of high utilization. Capacity Advisor records physical CPU utilization, which is the utilization of the actual cores on the VM host; that is, the total utilization reported by Capacity Advisor is based on the CPU time that the VM host allotted to each virtual machine. In contrast, the guest OS records virtual CPU utilization, which includes time when the VM wants to run, but is suspended while another VM is using the resources on the VM host. Because Capacity Advisor corrects for these effects, the collected data has much less noise in it, and better reflects the CPU time that was actually used by any one VM.

Data normalization
Capacity Advisor makes certain assumptions in its data analysis. These assumptions include automatically adjusting for CPU platform differences based on a performance index. (The performance index is constructed by normalizing collected data to selected benchmarks for the source and destination systems). If desired, you can add your own benchmark values to the database for use in calculating the performance index for workload moves among systems with the same or different architectures. (See capcustombenchmark in the Appendix B (page 133) for more information. Memory, network IO, and disk IO usage are not normalized. NOTE: Using benchmarks for data normalization was introduced into the 6.0 release. This change affects workloads defined with static profiles in previous releases because they use clock speed to determine performance. Such workloads that are still used for planning should be redefined or edited in Capacity Advisor 6.x to improve the accuracy of the performance measure.

Resources for which Capacity Advisor collects data

HP Insight Capacity Advisor software collects and analyzes data for utilization of the following resources: CPU cores Memory Network I/O Disk I/O Power

Upper bounds
Upper bounds represent the maximum capacity of a resource for a given system. The maximum capacity is used in Capacity Advisor for items such as the network and disk I/O utilization graphs of systems, the graphs and values shown in a profile viewer, and the Capacity Advisor Smart Solver calculations. CPU capacity The maximum CPU capacity of a system is the product of the number of CPU cores and the clock speed of the system. Memory The maximum capacity of memory is the amount of memory on the system.

24

Key Capacity Advisor concepts

Network I/O The maximum capacity for network I/O defaults to the high-water mark (that is, the maximum observed or collected value) for network I/O. However, to set the upper bound to a value you choose, select ConfigureEdit Network and Disk I/O Capacity... from the Visualization tab in Virtualization Manager. Disk I/O The maximum capacity for disk I/O defaults to the high-water mark (that is, the maximum observed or collected value) for disk I/O. However, to set the upper bound to a value you choose, select ConfigureEdit Network and Disk I/O Capacity... from the Visualization tab in Virtualization Manager. Power Expected maximum and minimum power values for systems and workloads are computed using the CPU and power utilization data collected from HP Insight Control power management (IPM). However, these values can also be set manually from the Virtualization Manager menu bar (select ConfigureCalibrate Power (All Selected Systems)...) for specified systems; or from the Capacity Advisor Edit Scenario: System tab menu bar (select EditCalibrate Power (All Selected Systems)...) for a specific scenario.

Measuring and analyzing resource utilization

In using Capacity Advisor, it is helpful to understand how the tool approaches sampling and data analysis, and the user-provided information that affects these.

Peaks and sums

Measuring utilization of computing resources is more complex than simply determining the maximum memory or processor utilization. Sum of peaks An old standby in capacity planning is to simply take the peak of the two loads and use that to determine the maximum required capacity; this is the sum of peaks. While this will definitely provide a robust solution, it does not take into account the timing of the peak of the loads and may end up planning for more capacity than is actually used. Peak of sums A more efficient planning solution, which is easily accomplished using HP Insight Capacity Advisor software, takes into account the timing of the maximum utilization peaks in the individual loads. By adding together utilization at each measured interval and then taking the maximum of the resulting time sequence, a more accurate measure of the required maximum resource can be determined. This can lead to cost savings when planning the resources required to consolidate loads onto new or existing servers.

Sampling interval
Where used, the Utilization Provider runs on each monitored system to collect information on resource utilization. At the CPU-clock cycle level, a processor is either busy or idle. For Capacity Advisor, the average utilization for each 5-minute (300 seconds) interval is stored. Therefore, peaks lasting less than 5 minutes are not visible. Because each data point is the average of the five preceding minutes of values, this averaging tends to flatten the graphs, particularly when compared with real-time graphs in which each data point is the average of values from the 15 preceding seconds. For data collected using an agentless solution, collection intervals can vary depending on values that you set and the number of machines in the collection.

Headroom
Headroom is the difference between the observed utilization on a system and the maximum available capacity. That is, the headroom of a system is the amount of additional capacity that can be used without violating the utilization limits of the applications running on that system. For example, if you have a system with 4 cores where you never want utilization to exceed 75%, and peak utilization is 1.75 cores, then headroom is 1.25 cores.
Measuring and analyzing resource utilization 25

Optimum headroom varies depending on size of system. While a single processor system might require 50% headroom to preserve reasonable response times, a 16-way system might have reasonable response times when loaded at 80%. Adequate headroom can also depend heavily on the characteristics of the loads; highly interactive systems require much more headroom than those that can tolerate delays in response time; batch systems may get by with very little headroom at all.

Headroom star rating

Various reports and results show headroom star rating. Use the following chart to understand the headroom rating system.
Star image Meaning Not only do all resources fit, but double the resource usage for any single workload could fit. All resources fit, and at least 75% headroom for any single workload is available. All resources fit, and at least 50% headroom for any single workload is available. All resources fit, and at least 25% headroom for any single workload is available. This star arrangement (1 green star) means that all resources fit in the system, but no or little headroom is available. One or more resources do not fit in the system; the utilization limits are violated. Data is not available for this system.

where resources can be CPU cores, memory, network I/O, and disk I/O. In the case of a virtual machine, the number of CPU cores considered are those assigned to the VM, not the total number of cores on the VM host. The VM host clock speed, network capacity, and disk capacity are all inherited by the VM guest when it is moved onto the VM Host. fit means the utilization limits (see Utilization limits (page 27)) are met headroom means room for growth Interpreting the headroom star rating Headroom star ratings for a host are a weighted average of all of the star ratings of the workloads on that host. The weighting tends to give the highest weight to the lowest rating. One low rating can dramatically lower the rating for the entire host. In the case of a VM host, the star ratings account for how well the workloads fit into their virtual machines, as well as how well the virtual machines fit on the VM host. The rating for the VM host will be low if any of the virtual machines are too small for their workloads.
Interpreting the star rating given by the HP Smart Solver

When using the Smart Solver to find a plan to convert physical systems to virtual machines, consider the following factors that can adversely affect the Smart Solver results. The addition of a virtualization overhead multiplier to a VM will often reduce the number of stars for that workload by 1 or 2 stars. The clock speed of the VM host may be slower than the original physical system. Work that was done by 1 core at 2.6 GHz, may require 2 cores when placed on 2.1 GHz VM host.

26

Key Capacity Advisor concepts

You can avoid having the Smart Solver produce inaccurate or useless results by re-sizing your systems before running the Smart Solver. If either of the above conditions exist in your situation, consider increasing the number of cores on your simulated physical systems before running the Smart Solver. (Select What-if ActionsEdit System... on the System tab on the Edit Scenario screen.) If you change the number of cores from 1 to 2 before consolidating, for example, the resulting virtual machines will have enough cores to cover the virtualization overhead or a slower VM host. Re-sizing the virtual machines after running the Smart Solver can be less effort, as you only have to re-size the VMs that have fewer stars than your desired goal. After adding more cores to the VMs for which CPU resources are too tight, you can rerun Smart Solver to balance the load on the VM hosts to improve the solution a bit more. TIP: Use a Scenario comparison report to compare the headroom stars rating for saved scenarios.

Missing or invalid data

Data collected by Capacity Advisor is used in the scenarios you create and manipulate. During an interval when no data was collected, the data is considered missing (data may not have been collected, for example, because a system was down during data collection). Invalidated (or invalid) data is data that you have marked as invalid. For each metric about a system or workload, if a significant amount of data is missing or invalid, the metric is followed by asterisks with the following meaning: [blank] : 91% to 100% of data is valid. * : 51% to 90% of data is valid. ** : 11% to 50% of data is valid. *** : Less than 10% of data is valid. N/A: There is no valid data. Thus, metrics asterisks are considered useful and reliable for analysis. NOTE: In some situations, where time or time zones on a server are incorrect, it may appear that only old data is available in the data collection. For more information on this topic, see the section Handling Old Data in Appendix H (page 175).

The affect of invalid data on HP Smart Solver solution finding

The HP Smart Solver is set to ignore workloads having >25% invalid data; that is, the Solver will not consider these workloads within an automated solution. This percentage can be adjusted, with a corresponding affect on the Solver's ability to include workloads in its solution calculations. For more information on what to do with workloads that violate this limit, see When the threshold for invalid data is exceeded (page 181).

Utilization limits
The default utilization limits used globally across Capacity Advisor in the absence of user-defined limits are the following: CPU utilization cannot exceed 70% of the capacity for more than 15 minutes at a time. (Seventy percent is used as a default for CPU utilization as it provides acceptable performance with a minimum of queuing in jobs.) Memory utilization cannot exceed 100% of the capacity. Typically memory should be set at a value <100% to allow for memory use by the dynamic buffer cache and operating system activity.

Measuring and analyzing resource utilization

27

(For more information on how utilization is calculated for each resource, see Appendix C (page 153) .)

Specifying utilization limits

There are three building blocks to specifying a utilization limit: The limit The maximum percentage or absolute amount of a resource allowed to be used by a workload. For example, a CPU utilization limit might be not above 90% utilization. The resource Utilization limits are applied to specific resources: CPU cores memory network I/O bandwidth disk I/O bandwidth TIP: You can specify more than one utilization limit for a resource Using the Utilization Limits Editor, you can add multiple settings for a resource. For example, you can create multiple different utilization limits for CPU cores by varying percentage and allowed duration for each limit. Multiple limits for CPU cores could look like this: Utilization can exceed 90 percent of assigned cores 0 percent of the time Utilization can exceed 85 percent of assigned cores for a maximum of 5 minutes duration

Not specifying a limit allows HP Smart Solver to over-provision systems To achieve best results with the Smart Solver, it is better to set specific limits, rather than to depend on the default settings for limits to provide the best fit. The time criteria You can specify the time portion of a utilization limit in either of two ways: Sustained (consecutive) time limits Percentage of time limits

Sustained time limits A sustained limit specifies a limit where the resource cannot exceed that utilization limit for X consecutive minutes. For example, if X is 20, this means that the resource cannot exceed the utilization limit for 20 consecutive minutes. Because the Capacity Advisor collects data samples every 5 minutes, the time X for the sustained limit must be a multiple of 5 minutes; the minimum for X is 0 minutes. Percentage of time limits A percentage of time limit specifies that the resource cannot exceed the limit for more than the designated percent of time, where percent of time is related to the percentile utilization ranges in the Capacity Advisor data. Given that there are about 10,000 minutes in a week, 3% of the time is roughly 300 minutes (3% of 10,000). These 300 minutes total to 5 hours per week. Below is a table relating percentages of time to hours per week, which may help you in specifying percent of time utilization limits. Table 3-1 Percent of time conversions
Percent of Time 1 2 28 Key Capacity Advisor concepts Minutes/ Week 100.8 201.6 Hours/ Week 1.68 3.36 Hours/Day (24hour day) .24 .48

Table 3-1 Percent of time conversions (continued)

Percent of Time 3 5 10 15 20 25 30 100 Minutes/ Week 302.4 504.0 1008.0 1512.0 2016.0 2520.0 3,024.0 10080.0 Hours/ Week 5.04 8.40 16.8 25.2 33.6 42.0 50.4 168.00 Hours/Day (24hour day) .72 1.20 2.40 3.60 4.80 6.00 7.20 24.00

Understanding utilization limit messages

Percentage of allocation The utilization limit messages are shown as a percentage of allocation, where allocation is subset of the given hardware for the system the workload is running on. For example, for a 1-core system, the allocation is 1 CPU. The CPU utilization limit of 50% would mean 50% of 1 core, or .5 cores. However, this percentage changes when the hardware (allocation) changes. If 2 additional cores are added (say through dynamic CPU migration with vPars), the CPU utilization limit of 50% would mean 50% of 3 cores, or 1.5 cores. Allocation values for network IO and disk IO are derived from either the highest observed value for that metric over the entire range of data collected, or a user-specified maximum value. The allocation values for network and disk may be updated each time utilization data is collected from the system using the capcollect command. If a new high observed value occurs during the time period collected, the network or disk allocation value for the system is increased to reflect it. This increased value then affects any network or disk utilization limits for workloads on that system. The current allocation values for a system are displayed on the Profile Viewer page under Platform Characteristics. With sustained limits A sustained utilization limit could be set such that CPU utilization cannot exceed 50% of allocation for 20 consecutive minutes, where the allocation of hardware is based upon a 3core system. The utilization limit message would read: CPU utilization may not exceed 50% of allocation or 1.5 cores for more than 20 minutes. With percentage of time limits A percentage of time utilization limit could be set such that CPU utilization cannot exceed 50% of allocation for more 10% of the time, where the allocation is based upon a 3-core system. The utilization limit message would read: CPU utilization may not exceed 50% of allocation or 1.5 cores for more than 10% of the time.

Scope of utilization limits

Utilization limits can be set to apply broadly or narrowly within the Capacity Advisor user interface:

Measuring and analyzing resource utilization

29

Globally. These limits apply to every workload, wherever workloads are analyzed. By Workload. These limits apply to one specific workload, wherever that workload is analyzed. Scenario-wide. These limits apply to every workload within one specific scenario. By Scenario Workload. These limits apply to one specific workload within one specific scenario.

When a workload falls within more than one scope, only the more specific one applies, as shown in the table below. You can disable a more specific scope where you do not want a specific scope to apply. Table 3-2 Scope of utilization limits
Scope More global Limits Description Overrides Nothing

Global Utilization Applies to all workloads for which a more specific Limit utilization limit is not provided. Cannot be disabled Workload Utilization Limit Applies to a specific workload unless a more specific utilization limit is provided. Can be enabled or disabled

Global

Scenario Utilization Limit

Applies to all workloads within a scenario for which a more Global specific utilization limit is not provided. Workload Can be enabled or disabled Applies to a specific workload within a scenario. Can be enabled or disabled Global Workload Scenario

More Local

Scenario Workload Utilization Limit

Adjusting power
With the cost of power increasing, power has become a resource that you may want to measure and manage. Within HP Insight Dynamics suite, power metrics, graphs and reports are displayed for actual systems and for systems within capacity planning scenarios. NOTE: You can calibrate power for physical systems (including virtual partitions), but not for virtual machines. To make the power data as accurate as possible, you are provided with the opportunity to calibrate power usage using data collected from actual systems, or you can supply your own values.

Power cap data

The power cap function on some HP hardware allows you to set a limit in watts for a server, and the server will ensure that its power consumption never exceeds that limit. That, in turn, can reduce power and cooling costs. It can also help to ensure that a data center does not draw more energy from the power grid than it is allocated to use, reducing the likelihood of experiencing unplanned downtime necessary to stay within a power allocation limit. The potential drawback to not setting the power cap high enough is degraded hardware response time, which an administrator can rectify by adjusting the cap -- or accept in exchange for the associated savings. For detailed information on how power caps work in HP hardware, see HP Insight Power Manager. Capacity Advisor gives you insight into the current power cap for HP systems that have these options available and operating. Within Capacity Advisor, you can generate a power report to see historic power usage data that includes power cap settings and estimated enforcement time. The following image shows an example of the power cap data included in a Capacity Advisor power report.

30

Key Capacity Advisor concepts

The power caps settings shown are provided by the administrator who is managing power consumption of servers. Capacity Advisor obtains these settings and the enforcement data for reporting purposes from HP Insight Power Manager. For information on how to generate a Capacity Advisor report that includes power usage data, see Producing graphs and reports (page 67).

Automating solution generation: HP Smart Solver

HP Smart Solver: Types of solutions
These planning scenario simulations can be automated: Consolidation to virtual machines You can simulate the consolidation of existing physical systems into virtualized resources, thereby converting the physical systems into VM guests hosted on VM hosts. To create the simulation, you can use data from existing VM hosts or create template-generated what-if systems based on characteristics that you specify. This feature makes it possible for you simulate a replacement or upgrade of existing legacy systems to fewer systems hosting virtual machines. Workload stacking You can simulate stacking individual workloads onto existing servers and/or onto template-generated what-if systems based on characteristics that you specify. This facility allows you to consolidate existing workloads into as few systems as possible. Load balancing You can simulate balancing system loads across several servers, virtual machines, or virtual machine clusters, such that workloads are distributed evenly across a set of resources, without overloading the subset of the servers. TIP: Use a Scenario comparison report to compare the headroom stars rating for saved scenarios.

Determining trends in Capacity Advisor

Determining trends from collected utilization data can be a challenging task. Accurate trend analysis requires adequate historical data and an understanding of the cyclic nature of the data being analyzed as well as any special events that might be found in the historical data. Trends are frequently small values, on the order of percents or fractions of a percent per month. The cyclic data can easily be orders of magnitude greater than the trend (heavy calculations the day before payroll distribution, floods of users logging on after work on the East coast, and so on). Special events can also be orders of magnitude greater than the trend (seasonal promotions, once per year calculations such as taxes). Any algorithmic analysis must be able to deal with these problems. HP Insight Capacity Advisor software combines aggregation of points based on known business cycles to deal with cyclic patterns with exclusion of points to deal with special events, to provide data for a linear regression.
Automating solution generation: HP Smart Solver 31

Aggregation of points in business interval bins

To reduce the impact of cyclic changes in the historical data, a user-specified business period is used to break the data into time-interval based bins and each bin is then represented by a single point. The point can be the average, the peak, or the 90th percentile of the data (90% of the points are less than the value). A bin will not be used unless the percent of points within the bin that are valid exceeds the threshold you have specified. IMPORTANT: A trend will not be calculated unless at least two bins with an adequate percentage of valid points exist within the range of data being analyzed.

Choosing an appropriate business interval

It is crucial to have a significant amount of data for analysis. Choosing an appropriate business interval with a data collection period that is long enough helps to ensure that you have enough data for a useful analysis. For example, a business interval of 1 week and data collection period of 1 month provides only four aggregate data points. This is insufficient to provide meaningful results. To improve results, for this example, use a business interval of 1 day with a data collection of 1 month to provide 30 data points, or use a business interval of 1 week with a data collection of 6 months to provide 26 data points. Modifying the business interval and/or the data collection period gives you more flexibility in arriving at a significant amount of data for analysis.

Exclusion of data points

You can set the report period to exclude a special event or mark the time period invalid to exclude points collected during that period from a trend analysis.

Factors that affect data validity

Within any data collection period, events can occur in the polled systems that affect the quality of data available during that time period. Capacity Advisor identifies data points that could adversely affect the quality and validity of report results. The following are examples of events that Capacity Advisor can recognize (and disregard) as potential sources of invalid points: System downtime during the collection period. Out of the ordinary activity designated by you. You can manually designate time periods as invalid when you know resource usage has been outside the norm that you want to consider in your capacity planning. Partial collection from a virtual machine or a VM host. When Capacity Advisor is unable to apply a correction that accounts for all activity on a VM host, it marks any partial data collection as invalid.

How this relates to setting a validity threshold The Validity Threshold that you set should reflect your tolerance for obtaining a sufficient amount of valid data in the collection period that you designate. If the reports that you run show that the given threshold is not obtainable for the designated time period, this may indicate that many of the data points in the designated collection period are invalid. In this case, you can choose a lower Validity Threshold with the understanding that the report outcome may be a less reliable indicator of probable resource usage, or you can select a different or longer data collection period to improve the likelihood of obtaining a sufficient percentage of valid points for a good report.

32

Key Capacity Advisor concepts

Linear regression
The linear regression is based on a least squares fit that minimizes the sum of the squares of the vertical offsets between each of the aggregate points and the trend line that describes them. TIP: Regressions performed over small data sets are not always meaningful and can be misleading. Any trend analysis based on less than a dozen aggregate points should be carefully compared with the historical data to see if it "makes sense." The maximum number of data points for the trend analysis is the total time for the report divided by the business interval, because business intervals can be excluded if they do not meet the validity criteria. Because the trend is reported as an annual growth rate, it is best to have more than a year of historical data before trying to analyze trends.

Error analysis
You can choose to include error analysis in the report. The following error value is available: r-squared: r2 is the square of the correlation coefficient (r), and is used in the 'goodness of fit' analysis of trend estimations. r is a value between 0 and +/- 1. where values approaching +/- 1 indicate increasing validity of the data representation.

Forecasting growth
HP Insight Capacity Advisor software forecasting allows you to combine a range of historical data (the forecast data range) with a predicted trend (the annual projected growth rate) to produce a forecast model. The forecast model can be used to provide an estimate of future utilization. Whenever a Capacity Advisor report or profile is generated with an end date later than the current date, the historical utilization data must be projected into the future. The projection is indicated in the utilization graphs by a colored background. This projection is done based on a forecast model. Forecast models can be defined globally, for individual workloads or systems, for a scenario, and for individual workloads within a scenario. Because the process for defining a forecast model is basically the same regardless of where it is in the hierarchy of forecast models, the procedures below are broken into two parts: accessing the forecast model and defining it.

The forecast model hierarchy

The forecast model can be specified at four different levels within Capacity Advisor, with more specific forecast models overriding more general models, as indicated in the following table: Table 3-3 Forecast models
Forecast Global Forecast Description Overrides

Applies to all workloads in Capacity Nothing Advisor for which a more specific forecast is not provided. Applies to a specific workload in Capacity Advisor unless a more specific forecast is provided. Global

Workload Forecast

Scenario Forecast

Applies to all workloads within a Global Capacity Advisor scenario for which Workload a more specific forecast is not provided. Applies to a specific workload within Global a Capacity Advisor scenario. Workload Scenario

Scenario Workload Forecast

Forecasting growth

33

Forecast model attributes

Table 3-4 Forecast model attributes
Field Description Forecast Data Range Selection Description Descriptive text of this model for your use. Defines the set of historical data on which the forecast will be based. If the selected set contains invalid data at the end of the period, the forecast will consider the last valid data to be the end of the period. The forecast data range can be specified as: A fixed interval ending or beginning on a specific date A float interval ending after a specified time period An absolute interval between two selected dates When this feature is checked, automatic adjustment of the specified range is enabled. If the box is checked, and the selected scenario does not have existing data in the specified range, then the range is shifted to use the existing data. If the existing data range is shorter than the specified forecast range, then the forecast range is shortened to fit the available data. Default: on (checked) Removing the check mark from the box prevents a forecast from being generated until a data range is specified that contains an interval of collected data sufficient to fill the forecast period. Example: Assume that you want to view activity one week (7 days) into the future using the most recent week of data. However, in this particular week, only four days of data were collected. With this featured turned on, the future will be tiled with repetitions of the four days of data until the forecast interval is filled. Annual Projected Growth Rate Specified in percent for each utilization resource measured (CPU, memory, network I/O, and disk I/O). Use positive values for increasing utilization, negative values for decreasing utilization, or zero to indicate no change. Default: zero (0) Annual project growth rates in force for a workload within a scenario are displayed in the Scenario Workloads Resource Utilization table on the Edit Scenario Workload tab.

Automatically adjust the specified range to use existing data

NOTE: Combining the data range with the annual growth rate The forecast is applied point-by-point to the historical data within the range specified by the user. It is applied linearly, so that a point 1 year from the starting point of a forecast is the result of the full growth rate being applied to the data. The data within the range provided by the user is used to tile the future by applying the portion of the growth rate appropriate to each point to each point in the data range and repeating the data set until the desired end point is reached.

34

Key Capacity Advisor concepts

4 Planning with Capacity Advisor

Getting ready
In order to get maximum value from the Capacity Advisor tools, it is important to: Be familiar with the Insight Dynamics framework Be familiar with the basic operation of Capacity Advisor Be familiar with Virtualization Manager Have a clear question you are trying to answer Have plenty of utilization data collected for Capacity Advisor Have appropriate access roles on the servers about which you are developing the plan Understand the equipment well enough to know what is physically possible (such as the maximum number of CPU cores) and what is practical (such as when to use 1 GB DIMMs with lots of slots versus when 4 GB DIMMs are more appropriate.) HP software can account for various power saving associated with specific DIMM. In addition, it can be very valuable to collect data on a test system to understand the real utilization characteristics of the applications you are considering.

Task: Understand current resource usage

For specific descriptions of each field shown on the user interface screens, click the software screen. Table 4-1 Checklist Obtaining reports on current resource usage
Task Related procedure(s)

on the

Collect data for a period of time that fully reflects First data collection (or the automated nightly collection) your business cycle(s). (page 58) Modifying a collection schedule (page 61) Ascertaining the data collection availability for a set of servers (page 66) Run utilization reports for selected resources of interest. Estimate current cost allocation for selected resources. The report wizard (page 71) Creating an historic utilization report (page 72) Creating a cost allocation report (page 76)

Getting ready

35

Task: Plan server consolidation

This section starts with a general procedure for consolidating servers (Understanding the consolidation task (page 36)), followed by an example of manual server consolidation (Example consolidation: Stacking applications on an existing server (page 36)). The second half of this section shows how to automate server consolidation using the HP Smart Solver (Automating the consolidation task (page 46)); also followed by an example (Example consolidation: Automating stacking on a what-if server (page 47)).

Understanding the consolidation task

There are three fundamental approaches to consolidating servers: Stacking workloads (representing applications) into standalone servers or nPartitions. Stacking virtual machines onto a single physical system or nPartitions. Stacking nPartitions and virtual partitions into complexes. The task description below is based on stacking server workloads onto one virtual machine and VM host. For other consolidations, the changes made when editing the scenario would differ. Prerequisites You must have already collected data on the systems of interest (see Gathering data for Capacity Advisor (page 55)). You should be familiar with Capacity Advisor operations (see Procedures (page 55)). You must be logged in to Insight Dynamics (see Accessing Capacity Advisor (page 55)). on the

For specific descriptions of each field shown on the user interface screens, click the software screen. Table 4-2 Checklist Consolidating server loads onto a virtual machine manually
Task Related Procedure(s)

Determine which systems to consolidate (both to Creating a consolidation candidates report (page 76) and from). Create a planning scenario. Creating a planning scenario (page 86)

Run reports on the scenario systems. Creating an historic utilization report (page 72) (Include this step if you want to obtain a baseline Creating a cost allocation report (page 76) set of reports to compare your scenario changes against.) See also Task: Understand current resource usage (page 35). Edit the scenario copy: Set up the new VM host system. Modify resources on systems as needed. Make each system to be consolidated become a VM. Modify utilization limits, if desired. Evaluate new quality of service Estimate new cost allocation on the VM host Creating a system (page 93) or Adding an existing system (page 94) Editing a system (page 94) Changing servers to be VMs (manually) (page 95) Setting global utilization limits (page 79) Creating a scenario utilization report (page 73) Creating a cost allocation report (page 76)

Example consolidation: Stacking applications on an existing server

This example demonstrates how Capacity Advisor can be used to simulate converting physical servers to virtual machines, and to then stack those VMs onto one VM host. Assume that you have a set of legacy servers that currently support one application each. There is good data on resource utilization for each of these servers, and it is time to see if converting these application servers into VMs and then consolidating the VMs onto fewer VM hosts can
36 Planning with Capacity Advisor

free up resources for other uses. For purposes of this example, it is assumed that the applications will each run in their own virtual machine. This task requires a profound knowledge about the systems. What are the licensing requirements for the applications? Who owns each of the systems and, if they are owned by different organizations, are they agreeable to the consolidation? What are the security requirements? What are the networking requirements (LAN and WAN)? Are there Storage Area Network (SAN) requirements? How stable are the applications? All of them should be test and development systems or production systems. This list is illustrative; other questions may need to be answered for your particular environment. The steps referenced in the following titles are from the checklist in Table 4-2 (page 36). Step 1: Determine which systems to consolidate From the top menu bar, select ReportsCapacity AdvisorCreate Consolidation Candidates Report... On selecting the systems link, a screen opens listing all discovered servers for which data has been collected (both physical and virtual machines). For the purposes of this exercise, assume that 20 physical servers are selected as targets, and that you are most interested in viewing CPU and memory data for these servers. Once the report is generated, viewing the columns Average CPU Use and Average Memory Use for each of the servers reveals that the applications on all but four servers are using significantly less than the available memory and CPU on each server. (See Consolidation candidate report (page 157) for a snippet of a typical consolidation candidates report.) This report shows that CPU on this set of legacy servers is significantly under-used when average usage is considered. Only four of the servers are using 80 percent or more of available memory on average. Assume that all of the legacy systems: are running applications based on the same database program, which is licensed per CPU use the same LAN use the same SAN have minimal security requirements that are adequately provided by the corporate firewall
Related topic

Creating a consolidation candidates report (page 76)

Step 2: Create a scenario In this step, you want to build a scenario around the systems that you have identified as under-used from the consolidation candidates report. 1. 2. 3. 4. Select ToolsCapacity Advisor from the top menu bar. On the Capacity Advisor tab, select CreatePlanning Scenario.... In the Create Scenario Wizard, name the scenario and describe its purpose. On the Systems screen, click Add to open the list of servers available for use in the scenario. Select the check boxes for the systems that you want to include in the scenario and click Add again. To understand the readiness of a system for use in a scenario, mouse over the status icon for information. A detailed explanation of the status icons, including pointers to troubleshooting information, is available in Capacity Advisor Help online (see Correcting
Task: Plan server consolidation 37

system configuration). The following image shows the mouseover text for a system that has sufficient data collected for meaningful analysis.

NOTE: While the default setting for a scenario is to recommend at least seven days of data to use for analysis, one carefully selected day can be sufficient to simulate your desired conditions; or you may need 30 days or more to reflect your business cycle. For best results, obtain a data set that best reflects the business interval that you want to simulate. 5. 6. Check the Summary and verify that the scenario name and selected systems have been entered correctly. Click Finish.

When finished creating a new scenario, the Edit Scenario screen automatically opens for editing the new scenario (default behavior). TIP: To return to a scenario at a later time... Should you be unable to edit the scenario immediately (or should you want to first make a copy of the scenario to modify), you can find the scenario later by locating the name of the scenario in the list presented on the Capacity Advisor tab screen. Click the scenario name to open the Capacity Advisor - Edit Scenario window for that scenario.
Related topic

Creating a planning scenario (page 86)

Step 3: Edit the scenario The systems included in the scenario are listed on the System tab of the scenario editor. The bar meters in the table show the peak resource utilization from data collected for the current week (the default setting). The following image shows three systems and their workloads.

38

Planning with Capacity Advisor

Figure 4-1 Example of bar meters on a System tab in the scenario editor

The weekly data is representative of recent utilization and can be calculated quickly, but doesn't always give a comprehensive picture. For a more comprehensive picture, look at a month of data. Change the data range to a month by clicking Edit Interval and selecting Month from the first drop-down list, and then OK. Once the screen has refreshed, new information about resource utilization is available. In this case, you can see that some of the utilization peaks have increased.

Scrolling or paging through the list of servers, you can see that some of the servers have peak usage that is at 100% of the resource, an insight you were not able to glean from the consolidation candidates report. The following image shows a server in this situation (legacy08).

The red bars in the CPU utilization column indicate that the utilization limits assumed for this scenario have been exceeded, though the available resource capacity has not. Mousing over the

Task: Plan server consolidation

39

legacy08 CPU utilization bar, you can see a pop-up message indicating the CPU utilization limit that is exceeded:

More information about the utilization limits can be obtained by mousing over the workload name (legacy08_wl), as in this image:

Now look at a few profiles for CPU usage. Click the legacy08 CPU utilization bar. A profile viewer for the selected resource and system opens, showing this information:

40

Planning with Capacity Advisor

Looking at the legacy08 graph, you can see that processing frequently requires 100% of available CPU in a month-long period. Also, it appears that the activity on this system exceeds 70% of the utilization resource for 15 sustained minutes, the utilization limit found earlier for this system. By studying the Interval Metric Summary table, you can see that 90% of the application processing was measured at using .47 core or less. Less that 10% of processing measured on this server required more than .5 core. Now open the profile viewer for CPU utilization on legacy03. The blue bar meter for this server (on the System tab) indicates that activity on this server does not exceed utilization limits.

Task: Plan server consolidation

41

The application on legacy03 has a 2-core processing capacity. A significant gap exists between Average use (.35 cores) and Peak use (1.63 cores), as can be seen in the Interval Metric Summary. Comparing CPU core usage at the 90th Percentile (90% of usage measures fall below this value 0.69 cores) with the Peak usage (1.63 cores), you can see that almost 1 core is required to support 10 percent of CPU use on this server.
Adding a VM host to the scenario

As of yet, this scenario does not include a VM host on which the virtual machines can be put once you create them. Click EditAdd Existing System... on the System tab. A list of discovered systems displays on the Add Existing Systems screen. Select two or three VM hosts that seem likely to be able to host the additional VMs. Click OK to include them in the scenario. The System tab screen now displays the VM hosts in addition to the initially selected systems: NOTE: This example has been intentionally constructed to exercise a number of Capacity Advisor screens. Careful study of the utilization meters on the System tab can help you anticipate changes that you will need to make in resource provision or allocation before you try to consolidate systems.
Related topics

Adding an existing system (page 94)

Making servers become virtual machines

Select the check boxes for servers that are to become virtual machines, and then select What-If ActionChange Servers to be VMsManually Change Servers to be VMs... For this example, 10 legacy servers were selected 4 of which exceeded utilization limits assumed by Capacity Advisor.

42

Planning with Capacity Advisor

The Manually Change Servers to be VMs... screen opens, and by scrolling down, you can see an evaluation of the current fitness of the selected VM hosts in relation to the proposed addition of the legacy servers:

By studying this table and the key, you may have already concluded: None of the servers meet an acceptable level of fitness as described by the headroom rating. Two servers (tornado and orthus) would require additional CPU and additional memory to host all ten of the legacy servers. One server (vse02) might have enough memory, but would require more CPU. Also, the demands on network and disk I/O would exceed resource capacity. The remaining server (hypv2) could have more memory and CPU added, but would still be short on network and disk I/O. The ten selected legacy servers will not fit on any one of the hosts present in the scenario. Add another existing system having more memory and CPU and small use of network and disk I/O to the scenario. Create a what-if system in the scenario that is sized to accommodate the ten legacy servers. Put fewer legacy servers on one of the systems already in the scenario.

At this point, you could do one of several things:

This example will continue with the third option putting fewer legacy servers on one of the systems already in the scenario. By cancelling the Manually Change Servers to be VMs operation, you can return to the scenario editor System tab to try this operation again; this time selecting 5 of the legacy servers, with this result:

Task: Plan server consolidation

43

This time, vse02 looks like the best VM host candidate in this scenario, as long as additional CPU are added to it to handle the additional processing load.
Adding processor cores

A look at the peak usage data shows that the usage of the CPU core allocation varies among the five servers, but usage still appears to be within the bounds of a server having no more than 8 cores. However, Capacity Advisor will expect to calculate CPU processing overhead for running each of the virtual machines. Eight cores may not be enough when CPU virtualization overhead is accounted for, but for now add 4 cores to vse02 for a total of 8 cores. NOTE: You can refine this estimate further by changing utilization limits or by forecasting future growth. Also, the longer the period of data analyzed, the better the analysis of resource utilization. From the System tab, select the vse02 check box, and then What-If ActionEdit System.... Change the number of CPU cores from 4 to 8 and click OK. Other attributes such as memory size, processor speed, and bandwidth can be adjusted at the same time on the Edit System screen. Thus, you can tweak the resource allocations on this screen as you refine the fit through additional changes.
Related topic

Editing a system (page 94)

Continuation: Making servers become VMs

Once again, select the five servers that are to become virtual machines and then select What-If ActionChange Servers to be VMsManually Change Servers to be VMs... When the screen repaints, you first see the selected legacy servers listed. In the CPU Virtualization Overhead column, you have the opportunity to designate the percentage of overhead that you anticipate each virtual machine will require for operation. After referring to Adjusting for virtualization changes (page 127), add a CPU virtualization overhead of 20% for each of the legacy servers. You must click Refresh (which is down and to the right of the Systems to be

44

Planning with Capacity Advisor

modified table) in order to update the To: (Selected VM host) table to include virtualization overhead in the utilization calculations.

Leave the default setting for headroom calculations as it is exclude guest fitness results (no fitness rating will be considered for individual VMs in the calculation, only for the VM hosts as a whole). Study the To: (Selected VM Host) table and make adjustments if needed. For purposes of this example, the utilization limit will be changed. Click OK to complete the conversion of servers to virtual machines.
Related topic

Changing servers to be VMs (manually) (page 95)

Changing the utilization limit for the scenario

Assume that it will be sufficient to limit CPU utilization to 80% of capacity and that memory utilization limits do not need to change. Select EditScenario-wide Utilization Limits on the scenario editor menu bar. Add a new CPU utilization limit of 80% for 15 sustained minutes, and remove the previous limit of 70% for 15 sustained minutes. The screen looks like this when these changes have been made:

Task: Plan server consolidation

45

Click OK to save and apply the changes.

Related topics

Utilization limits (page 27) Setting scenario-wide utilization limits (page 80)

Automating the consolidation task

The preceding sections demonstrated a basic progression through Capacity Advisor screens where each step required manual evaluation and adjustment. The time this takes is not too laborious for a few machines, but you may need to evaluate possibilities among hundreds of machines. This section shows you how the HP Smart Solver simplifies evaluating a large number of opportunities for consolidation. The task description below is based on stacking server workloads onto virtual machines and VM hosts. For other consolidations, the changes made when editing the scenario would differ. Prerequisites You should be familiar with Capacity Advisor operations (see Procedures (page 55)). You must be logged in to Insight Dynamics (see Accessing Capacity Advisor (page 55)). You must have already collected data on the systems of interest (see Gathering data for Capacity Advisor (page 55)). on the

For specific descriptions of each field shown on the user interface screens, click the software screen.

46

Planning with Capacity Advisor

Table 4-3 Checklist Consolidating server loads onto a virtual machine using automated solution finding (HP Smart Solver)
Task Related Procedure(s)

Determine which systems to consolidate (both to Creating a consolidation candidates report (page 76) and from). Create a planning scenario. Creating a planning scenario (page 86)

Run reports on the scenario systems. Creating an historic utilization report (page 72) (Include this step if you want to obtain a baseline Creating a cost allocation report (page 76) set of reports to compare your scenario changes against.) See also Task: Understand current resource usage (page 35). Edit the scenario copy: Set up the new VM host system(s). Automated solution finding: System consolidation to VMs (page 109) Make each system to be consolidated become a VM. Evaluate new quality of service Estimate new cost allocation on the VM host Creating a scenario utilization report (page 73) Creating a cost allocation report (page 76)

Example consolidation: Automating stacking on a what-if server

Assume that you have a collection of legacy servers for which you are uncertain of historic resource usage. You have collected enough resource utilization data for each of these servers to provide good insights, and it is time to see if converting these application servers into VMs on fewer VM hosts is a cost-effective choice that will use your resource pool more efficiently. You also want to do the simulation with a virtualization technology and server model that you are thinking of purchasing in the near future. The steps referenced in the following titles are from the checklist in Checklist Consolidating server loads onto a virtual machine using automated solution finding (HP Smart Solver) (page 47). Step 1: Determine which systems to consolidate From the top menu bar, select ReportsCapacity AdvisorCreate Consolidation Candidates Report... This is the same process discussed in Step 1: Determine which systems to consolidate (page 37) of the manual consolidation example.
Related topic

Creating a consolidation candidates report (page 76)

Step 2: Create a scenario This is the same process discussed in Step 2: Create a scenario (page 37) of the manual consolidation example. When finished creating a new scenario, the Edit Scenario screen automatically opens for editing the new scenario.

Task: Plan server consolidation

47

Related topic

Creating a planning scenario (page 86)

Step 3: Edit the scenario The systems included in the scenario are listed on the System tab of the scenario editor. The bar meters in the table show the peak resource utilization from data collected for the current week (the default setting).
Making servers become virtual machines using automated solution finding

Select ten legacy servers from the manual consolidation example to become virtual machines, and then select What-If ActionChange Servers to be VMsAutomated Consolidation of Servers to VMs...
Screen 1 of 3

Modify the data range, if desired. Define the destination VM host(s). This example demonstrates the selection Use both existing hardware for workload placement and host templates for overflow. Here is the template definition for a what-if system:

Next, set the constraints for the solver:

CPU virtualization is set to 20%, as in the manual consolidation example. The default settings for load balancing and maximum allowed invalid data are not changed. Click Next to proceed to the next step.

48

Planning with Capacity Advisor

Screen 2 of 2

This screen gives you the opportunity to review the settings you have made thus far and to select the level of effort for the Solver to operate within. The default setting is for maximum effort that the Solver should expend to find the best solution. Click OK to start the calculation.
Screen 3 of 3

This screen shows the results of this Solver run:

Based on the information given in the solution, you might choose to do the following: Run the Solver again, and define the template host to have 5 GB of memory to allow for more headroom in the systems and to obtain a solution that includes legacy03.

Rather than starting over, click Return to Step 1. The user interface remembers the values that you entered previously, so just change the value for system memory from 4 GB to 5 GB and proceed through the screens again, running the Solver with the new value.

Task: Plan server consolidation

49

Related topics

Automating solution generation: HP Smart Solver (page 31) Automated solution finding: System consolidation to VMs (page 109) Results: Automated consolidation to VMs (page 112)

50

Planning with Capacity Advisor

Task: Estimating the effect of adding or moving processors

It is frequently desirable to move processors among servers or add processors to balance resources, adjust headroom, deal with existing problems, or prevent anticipated ones. With HP Insight Capacity Advisor software, you can make more informed decisions about re-configuring your servers to improve the quality of service or maintain it with a more efficient configuration. Capacity Advisor allows you to size your system with more precision. This sizing is not based on a simple peak utilization value, but on knowing the answers to questions such as whether your system is more than 70% busy for an unacceptable percentage of the time. For specific descriptions of each field shown on the user interface screens, click the software screen. Table 4-4 Checklist Estimating the effect of adding processors
Task Related Procedure(s)

on the

Determine the current quality of service for a desired Creating an historic utilization report (page 72) metric for systems under consideration. (See also Task: Understand current resource usage (page 35).) Create a planning scenario that includes the systems to Creating a planning scenario (page 86) which you would like to add processors. Simulate adding processors on selected systems. Evaluate new quality of service Editing a system (page 94) Creating a scenario utilization report (page 73)

Table 4-5 Checklist Estimating the effect of moving processors

Task Related Procedure(s)

Determine the current quality of service for a desired Creating an historic utilization report (page 72) metric for systems under consideration. (See also Task: Understand current resource usage (page 35).) Create a planning scenario that includes the systems that Creating a planning scenario (page 86) could exchange processors. Simulate moving processors from donor systems to receiver systems. Evaluate new quality of service Editing a system (page 94) Creating a scenario utilization report (page 73)

Task: Estimating the effect of adding or moving processors

51

Task: Determining where to put a workload using automated solution finding

Adding a new application or set of applications to an existing server environment requires careful planning. Deciding where to add the new workload can be challenging; can it be placed on an existing server, or is a new system required? With HP Insight Capacity Advisor software, the planning can be based on real data and realistic modeling of the results of adding a new workload to the current environment. Prerequisites You should be familiar with Capacity Advisor operations (see Procedures (page 55)). You must be logged in to Insight Dynamics. (See Accessing Capacity Advisor (page 55).) You must have already collected data on the systems of interest (see Gathering data for Capacity Advisor (page 55)). on the

For specific descriptions of each field shown on the user interface screens, click the software screen.

Table 4-6 Checklist Determining where to put a workload using automated solution finding (HP Smart Solver)
Task Related Procedure(s)

Determine which workload(s) to move. See also Creating a consolidation candidates report (page 76) Task: Understand current resource usage (page 35). Create a planning scenario. Creating a planning scenario (page 86)

Edit the scenario: Modify the workload(s) as desired. Editing a workload (page 101) Modify potential host systems as desired Editing a system (page 94) Move the workloads using automated solution Automated solution finding: Workload stacking finding (page 115) Evaluate new quality of service Estimate new cost allocation on the VM host Creating a scenario utilization report (page 73) Creating a cost allocation report (page 76)

Example: Determining where to put a workload

1. Obtain data from a test machine The most accurate models are based on real data, collected over a long enough period of time to capture the variations in load due to periodic peaks in usage (such as events happening late Thursday night or the first and 15th of the month). Collect data for at least a week, and preferably for long enough to capture any periodic variations. If you cannot collect data from a test machine and have data from a similar application running on an existing system, you can create a new workload based on the existing data and scale it to provide a best guess model of the new application's resource utilization. 2. Create a scenario Follow the procedure in Creating a planning scenario (page 86) to create a scenario with the test system running the new application and all the candidate host systems. 3. Edit the workload Follow the procedure in Editing a workload (page 101) to make any modifications to the data collected on the workload necessary to reflect estimated future production loads. This might include increasing the processor load and/or memory usage.

52

Planning with Capacity Advisor

4.

Move the workload Follow the procedure in Automated solution finding: Workload stacking (page 115)to move the workload from the test machine it has been running on to one of the potential host machines. The bar graphs on the screen provide a rough estimate of the effect of moving the workload to each of the candidate hosts.

5.

Estimate the new quality of service a. Follow the procedure in Using the Profile Viewer (page 67) to obtain a quick overview of the resource utilization of the system with the added workload. b. Follow the procedure in Using the report wizard (page 71) to generate a detailed report on the new configuration. In addition to the quantitative measures of the goodness of a system, it is important to use your knowledge of such things as how the system will be used, system ownership, and future constraints. This is an area where your knowledge of the context the application will be run in can be as important as the estimated resource utilization.

Task: Determining where to put a workload using automated solution finding

53

54

5 Procedures
This chapter provides information on procedures you are likely to use with Capacity Advisor. Note that all procedures are indexed by their names.

Accessing Capacity Advisor

Before you can use HP Insight Capacity Advisor software, you must access it. IMPORTANT: For specific descriptions of each field or summary table on the user interface screens, click the help topic link on the software screen for the task. This procedure assumes the following: You are familiar with HP Systems Insight Manager software (HP SIM). For information on HP SIM, select HelpFor HP Systems Insight Manager from the top menu bar to access the HP Systems Insight Manager 6.2 online help. You have appropriate licenses to use Capacity Advisor on the Central Management Server (CMS) and the systems you wish to monitor with HP Insight Capacity Advisor software (see HP Insight Dynamics 6.2 Getting Started Guide). Procedure 5-1 Accessing Capacity Advisor 1. 2. Open a Web browser. Enter the following in the Address field (it is not always labeled in browsers): http://CMS-Host:280/ where CMS-Host is the server running the CMS for Insight Dynamics. 3. 4. 5. 6. Press Enter. A login screen is displayed (if security dialogs are presented first, respond appropriately). Fill in the User name and Password fields. Click Sign In or press Enter. If the VSE Management: Capacity Advisor screen is not displayed, select ToolsCapacity Advisor from the top menu to open the Capacity Advisor home tab. Alternatively, you can select OptimizeCapacity AdvisorView Scenarios ... from the top menu bar. The Optimize menu provides several options for accessing Capacity Advisor features. The VSE Management: Capacity Advisor screen is displayed, with a list of the scenarios that have already been created.

Gathering data for Capacity Advisor

HP Insight Capacity Advisor software works best when using generous amounts of data to generate reports and create meaningful simulation scenarios. Though it is most efficient and effective to collect data on a regular schedule, you can also start an up-to-date data collection for reports and profile generation at any time. Data collected by the Utilization Provider is kept on a managed system for 30 days. Data captured through agentless means are transferred at 5-minute intervals. Any data transferred to the database on the CMS is kept for four years.

Accessing Capacity Advisor

55

TIP: When you want to keep less than four years of data Change the property file vseprefs.props in one of the following locations: Program Files\HP\Virtual Server Environment\vseprefs.props (on Windows CMS) /etc/opt/vse/vseprefs.props (on HP-UX CMS) Look for this text, and change to the desired number of days:
# # The default number of days to retain capacity planning profile data. # This limit is enforced by the capcollect command. # PROFILE_RETAIN_DAYS=1460 #

To create a meaningful simulation scenario or to view the historical resource utilization of a workload, you must collect data from representative systems or the systems for which you want to monitor resource utilization. Once you have collected the data, you can create simulation scenarios or experiment with different configurations and workloads to evaluate your system capacities. You can use Capacity Advisor to plan for the future. You can collect data for the following: A selected set of licensed systems All licensed systems NOTE: Use only one CMS to manage each node used with Capacity Advisor.

To collect data on any system managed using Insight Dynamics, you must have the following configured on the CMS: Authorization in the Central Management Server (CMS) to run the Capacity Advisor toolbox on the managed system WBEM credentials in the CMS to access WBEM on the managed system

Impact of data collection on managed system performance

The data collection process is purposely designed to consume few resources on the managed systems from which data is being collected. This means you can feel free to collect data whenever you want. Note, however, that when there is a large number of managed systems, the data collector (running capcollect on the CMS) can take a relatively long time to obtain all the collected data for storage on the CMS . For a diagram of the Capacity Advisor data collection infrastructure, see Figure 2-1 (page 16) .

Data collection options

When preparing to collect data for use in scenarios or for obtaining historical activity reports, consider the following:

56

Procedures

the list of servers from which you want to collect data the collection agency in operation on the servers (Capacity Advisor can collect data by way of the Utilization Provider, by way of agentless means, or by import from other HP data collection methods) For discussions of various collection agencies, see Comparison of agentless and UP data collection (page 18) and HP PMP data differs from Utilization Provider data (page 19).

whether you need to collect data for the first time, update a data collection, or update a data collection schedule.

Deciding from which servers to collect Data collection via Capacity Advisor is limited to those systems recognized as servers within HP SIM. The list of all possible servers can be viewed by opening the All Systems view or the All Servers view in the Systems and Event Collections area on the left. The list of all possible servers that are licensed with Insight Dynamics can be viewed by opening the All VSE Resources view in this same area, or by opening HP Insight Virtualization Manager software (ToolsVirtualization Manager... from the top menu bar). You may also have servers in mind where data collection has been accomplished using software other than the Utilization Provider. This can be done by collecting data from licensed systems for which Capacity Advisor has agentless data collection capability or by importing data collected by other agents, such as HP Performance Agent (formerly HP OpenView Performance Agent OVPA) or HP Performance Management Pack. How to collect data using Capacity Advisor Data collection functions are accessible from multiple locations: the Configure, Optimize, and Tasks & Logs menus on the top menu bar the Virtualization Manager Visualization tab (Tools menu) the Capacity Advisor tab using capcollect, capagentlesscfg, capovpaextract, or cappmpextract on the command line.(see Command reference (page 133)) TIP: For lists of all menu options for Capacity Advisor features, see Menus & tabs in Capacity Advisor Help. NOTE: Licensing and data collection Typically, servers from which data are collected are licensed for Capacity Advisor and Insight Dynamics. However, it is possible that not all servers in a data center or network are licensed to run HP Insight Dynamics suite. For information on installing the Utilization Provider, see HP VSE Managed Node Software Update. For general information about licensing systems, see the HP Insight Dynamics 6.2 Getting Started Guide . For discussion of using the HP Insight Capacity Advisor Consolidation software to collect data for a systems consolidation effort, see Data collection and the HP Insight Capacity Advisor Consolidation software (page 63). When to collect data Data collection via Capacity Advisor can be controlled to occur at different times by doing one or more of the following actions: use the automated nightly collection schedule a collection to occur periodically or one time only launch an immediate collection

Gathering data for Capacity Advisor

57

NOTE: Performance for a virtual machine is usually calculated using the performance index calculated for its VM host. However, when a virtual machine is moved from one VM host to multiple other VM hosts within a short period of time (between one capcollect operation and the next capcollect), as might occur when simulating virtual machines within a cluster, performance is calculated using the ratio of the clock speeds multiplied by the performance index of the current VM host. If all the nodes of your cluster (for example) are nearly identical, then this clock speed scaling will not introduce any error. However, if the original and destination hosts are different, you can reduce any error caused by this clock speed scaling in the following ways: Collect data just before moving a VM. Schedule capcollect to run more often on your VMs, particularly the ones using VMware DRS.

Once you have determined the method and location for data collection, updating the data stored in the Capacity Advisor database operates the same regardless of how the data was collected. IMPORTANT: For specific descriptions of each field or summary table on the user interface screens, click the help topic link on the software screen for the task.

First data collection (or the automated nightly collection)

In general, the procedures for collecting data are similar: you must select the target system or systems, schedule the collection task for a later run or to run now, and start the task. Upon installation of HP Insight Dynamics suite (and Capacity Advisor in particular), Capacity Advisor is set to automatically collect data from all managed nodes discovered by HP SIM that are licensed to run Capacity Advisor, beginning at midnight on the CMS time clock. This is called the nightly data collection. It occurs automatically at this time unless and until it is disabled or rescheduled to a different time. Prerequisites You must be logged in to Insight Dynamics as a privileged administrator user or root. (see Accessing Capacity Advisor (page 55)). Select Tasks & LogsView All Scheduled Tasks... from the top menu bar. From the list of current tasks, select Collect ALL Capacity Advisor Data Nightly.... If you would like to modify the timing, click Edit. The Task Confirmation screen is displayed. 4. 5. 6. 7. Click Schedule. Select Periodically from the list labeled When would you like this task to run?. In the area labeled Refine Schedule:, set the time of your choice. Click Done. The Task Results screen is displayed. The data collection will start when the system clock reaches the time that you have set. 8. Or, if you would like to turn off the nightly collection, click the Disable this task check box and Done. If you now want to schedule a regular data collection for one or more blocks of machines, see Scheduling a data collection (page 60).

Procedure 5-2 To alter the automated nightly data collection 1. 2. 3.

58

Procedures

To return to a planning checklist: Obtaining reports on current resource usage [p. 35]

Interpreting task results

The Task Results screen shows a Running check box with a Start time: until the task completes. When data collection finishes, you see an End time: displayed, with standard out (stdout) and standard error (stderr) information on the data collection. Once the Status field shows Complete, the collection task is complete, and the screen provides a summary of pertinent information for this task, including the name of the task, completion status, and the command line options used to run this task. The results of the task are presented in the Stdout and Stderr tab windows. The messages on the Stdout tab include indications of any errors that occur. Be sure to click both tabs for a complete understanding of what happened. An Exit code of 0 means complete success. Positive values indicate partial or complete failure. In addition, you will see iconic indicators in the table Status column: When a task concludes successfully, you see this symbol: . When a task concludes with a global or system-specific error, you see either of these symbols in the status column, respectively: or .

Error notification on the standard out tab

While error messages are sent to the Stderr tab, the fact that errors have occurred is indicated on the Stdout tab. The types of messages sent to the Stdout tab are explained below.
All physical CPU utilization data collected for Integrity VM "vm-name" from Integrity VM Host "host-name". All corrected physical CPU utilization data collected for HyperV VM "vm-name". All utilization data collected for "system-name"

Data collection succeeded. No need to check the Stderr tab if this is the only type of notification.
Some utilization data collected for "system-name"

Although data collection was not entirely successful, some utilization data was collected. Check the Stderr tab for details of the problem.
Warning: message text.

A condition was detected while collecting that may affect the usefulness of the data collected. Check the Stderr tab for details of the problem.
NN Warnings issued.

Appears at the end of output on the Stdout tab. Warnings were issued. Check the Stderr tab for details.
Collection failed on NN systems.

Appears at the end of output on the Stdout tab. No data was collected from one or more systems. Check the Stderr tab. For each of the failed systems, there will be one or more messages, including the host name. See also Appendix G (page 165)and Capacity Advisor messages (page 175) for additional information to help you troubleshoot data collection errors. As you review and analyze the resulting data collection, you may notice discrepancies. See Possible sources of discrepancies in collected data (page 66)for information.
Gathering data for Capacity Advisor 59

Scheduling a data collection

As conditions evolve over time or to manage data collection for large numbers of servers, you can schedule one or more periodic data collections in addition to, or in place of, the automated nightly collection. At the scheduled time, Capacity Advisor will pull data collected by the Utilization Provider or via the agentless configuration file into the database on the CMS for storage. Prerequisites To create a collection schedule: You must be logged in to HP SIM (see Accessing Capacity Advisor (page 55)). Select OptimizeCapacity AdvisorCollect Capacity Advisor Data... from the top menu bar. The Collect Capacity Advisor Data wizard starts. 2. Click the word - select - in the drop-down list below the title Add targets by selecting from:. A list of filters is presented. 3. Select an appropriate filter from the list. All Systems will list all the available systems, while other choices will constrain the selection list to subclasses of systems. The choice All VSE Resources restricts the list to those likely to be licensed for data collection. Click the check boxes beside the systems for which you wish to collect data. If needed, expand the plus sign controls beside classes of systems to display specific systems. (For additional help on selecting targets, see the HP Systems Insight Manager 6.2 online help on Creating a Task.) Click Apply. The Verify Target Systems screen of the wizard displays the resulting list of target systems. 6. 7. If you wish to collect data on more targets, click Add Targets and repeat the preceding two steps. If you wish to remove any targets from the list: a. Click the check boxes by the targets you wish to remove. Check marks appear in the check boxes. b. 8. 9. 10. 11. 12. 13. 14. Click Remove Targets. The targets with check marks in the check boxes disappear from the list. Once the list has the correct set of targets, click Next. The Task Confirmation screen of the wizard is displayed. To start a one-time collection immediately, click Run Now. The Task Results screen is displayed. See Interpreting task results (page 59). To schedule the timing for a periodic collection, click Schedule. The Schedule Task screen is displayed. Select Periodically from the list labeled When would you like this task to run?. In the area labeled Refine Schedule:, set the time of your choice. Click Done. The Task Results screen is displayed. The data collection will start when the system clock reaches the time that you have set. See Interpreting task results (page 59) for more information about the Task Results screen.
60 Procedures

Procedure 5-3 To collect data on selected systems 1.

4.

5.

Modifying a collection schedule

As collection needs change over time, you can modify an existing schedule for better results. Prerequisites You must be logged in to Insight Dynamics. (see Accessing Capacity Advisor (page 55)). You must be the creator of the collection schedule that you want to modify, or a privileged administrator user. Select Tasks & LogsView All Scheduled Tasks... from the top menu bar. The All Scheduled Tasks screen displays a list of the tasks that have been associated with your current user ID. 2. 3. 4. 5. 6. Click the radio button beside the task you wish to reschedule. Click Edit. The Task Confirmation screen of the Collect Capacity Advisor All wizard displays. Click Schedule. The Schedule Task screen of the wizard displays. Modify the Schedule Task screen of the Collect Capacity Advisor Data All wizard. Click Done. The All Scheduled Tasks screen displays. To return to a planning checklist: Obtaining reports on current resource usage [p. 35]

Procedure 5-4 To modify a collection schedule 1.

Removing a collection schedule

As your collection needs change over time, you might need to remove a collection schedule. Prerequisites You must be logged in to Insight Dynamics. (see Accessing Capacity Advisor (page 55)). You must be the creator of the collection schedule that you want to modify, or a privileged administrator user. Select Tasks & LogsView All Scheduled Tasks... from the top menu bar. The All Scheduled Tasks screen displays a list of the tasks associated with your current user ID. 2. 3. 4. Click the radio button beside the task that you wish to delete. Click Delete. A confirmation screen displays. Click OK on the confirmation screen. The task is removed from the list. If this is the last task in the list, the message There are no available tasks to display. replaces the list of tasks.

Procedure 5-5 To remove a collection schedule 1.

Updating collected data

At times, such as when you are generating reports and developing or refining scenarios, you may want to trigger data collection so that your work is based on the most up-to-date data. You may want to do one of the following actions:

Gathering data for Capacity Advisor

61

Update the collected data on all available systems ( see Updating collected data on all systems (page 62)). Update the collected data from some systems (see Updating collected data on selected systems (page 62)). Update the collected data presented in a Profile Viewer report (see Updating data displayed in a profile viewer (page 62)).

Updating collected data on all systems

You may want to update data for all systems at one time. Prerequisites To update collected data on all systems: You must be logged in to Insight Dynamics (see Accessing Capacity Advisor). Procedure 5-6 To update collected data on all systems 1. Select OptimizeCapacity AdvisorCollect Capacity Advisor Data ALL... from the top menu bar. This starts the wizard for collecting data from all systems licensed for Capacity Advisor. 2. Click Run Now. See Interpreting task results (page 59) for more information about the Task Results screen.

Updating collected data on selected systems

At times, you might want to collect data on selected systems. In this case, follow the same procedure as for Scheduling a data collection (page 60), steps 19.

Updating data displayed in a profile viewer

To update the data in a profile viewer: You must be in a profile viewer (see Using the Profile Viewer (page 67)). Click the Collect Capacity Advisor Data... link. A busy indicator appears over the grayed out screen. When the busy indicator disappears, you can see the refreshed data display. NOTE: If the data collection fails, the output from stdout and stderr of the command are shown at the top of the screen. Procedure 5-7 To update data that a profile viewer is displaying

Collecting data without using an agent

Agentless data collection is currently available for systems that run supported versions of Microsoft Windows and Linux operating systems and that are licensed for Capacity Advisor. These managed systems will be automatically configured for agentless data collection, either using the Insight managed system setup wizard or the first time capcollect is run for those systems (whichever comes first).

Listing systems currently in the configuration file

This section describes the procedure for determining the current settings for agentless data configuration on a CMS, particularly the list of systems from which to collect data using this method.

62

Procedures

Prerequisite 1. 2. 3. You must be logged in to HP Systems Insight Manager software with any level of access permissions. From the Capacity Advisor tab, select ConfigureAgentless Data CollectionList Selected Systems.... The Task Confirmation screen opens. Click Run Now. The Task Results screen opens. When the command completes successfully, the current contents of the configuration file are listed on the Stdout tab. If you suspect an error, check the Stderr tab for more information.

Setting advanced options in the agentless data collection file

This section describes the procedure to use when defining advanced options to be included in the agentless data collection configuration file. (See Advanced agentless options screens in Capacity Advisor online help for reasons why it can be advantageous to alter the default values using the Advanced Agentless Options screen.) Prerequisite 1. 2. 3. 4. 5. 6. You must be logged in to Insight Dynamics with VSE All Tools or Capacity Advisor tools permissions. From the Capacity Advisor tab, select ConfigureAgentless Data CollectionAdvanced Agentless Options.... The Specify Parameters screen opens. Optionally, change the polling interval. Optionally, change the number of collector threads to assign to the task of collecting this data. When satisfied with changes, click Run Now. The Task Results screen opens. When the command completes successfully, the current contents of the configuration file are listed on the Stdout tab. If you suspect an error, check the Stderr tab for more information. Related topics capagentlesscfg in the Appendix B (page 133)

Data collection and the HP Insight Capacity Advisor Consolidation software

HP provides the HP Insight Capacity Advisor Consolidation software specifically to address the need to understand resource utilization on servers that are targeted for consolidation onto other systems. Such servers often will not be running Insight Dynamics. Yet, being able to use Capacity Advisor's planning facilities can greatly reduce the amount of time needed to plan a consolidation effort. The HP Insight Capacity Advisor Consolidation software provides you with a limited license to obtain data for use in Capacity Advisor scenarios. For six months from the time the license is locked into its assignment to a server, you can collect data to use in your consolidation planning scenarios within Capacity Advisor.

Gathering data for Capacity Advisor

63

Using Capacity Advisor with consolidation software server data

Because servers using the HP Insight Capacity Advisor Consolidation software are not licensed for Insight Dynamics, you must use HP SIM Optimize menu options for Capacity Advisor to collect and manipulate this data. The available Optimize menu options allow you to do the following actions: view a utilization profile collect data import data view and create scenarios create various reports

Viewing the licensed servers in HP SIM

Another implication of this limited license is that servers with this license are not visible in the Visualization tab of Virtualization Manager. To see these servers in a list, look for All Servers selections and links within HP SIM task screens and a few Capacity Advisor screens. The All Servers list allows you to view and select servers licensed with the HP Insight Capacity Advisor Consolidation software for inclusion in scenarios or for creating reports.

Importing data for use in Capacity Advisor

To import system utilization data, the system must be discovered by HP SIM. For systems that you know are running HP Performance Agent (OVPA), you can verify discovery by clicking All Systems or All Servers in the HP SIM left navigation bar. If the system has not been discovered, you can add it manually. (From the top menu bar, select OptionsDiscovery.... You must be a privileged administrator user or root to see this option.) For help on adding a system manually, see the Discovery and Identification topic in the HP Systems Insight Manager 6.2 online help. After you add a system, verify that the system appears in All Systems view. For systems running HP Performance Management Pack (PMP), select OptimizeCapacity AdvisorList PMP Systems to see the list of discovered servers running PMP. Once you verify that the system of interest has been discovered by HP Systems Insight Manager software, you can import system utilization data into Capacity Advisor. IMPORTANT: Avoid importing PMP or OVPA data that overlaps time intervals where agentless data collection has already occurred. Mixing the two data sets can produce confusing reports, because the agentless collector obtains more metrics than the PMP or OVPA collectors, and the imported data will overwrite only the metrics that both collectors obtain. This is primarily an issue when the imported data has invalid data points and the agentless set does not. Instead, determine if there are time periods where data was not collected using the agentless method. Import data only for those time periods. Capacity Advisor will behave as though all the data collected is one contiguous set, and reports will better reflect the actual resource usage. See Ascertaining the data collection availability for a set of servers (page 66) for instructions.

From the Optimize menu Import HP OVPA data

Prerequisites 1. You must be logged in to Insight Dynamics (see Accessing Capacity Advisor (page 55)). The system(s) must be discovered by HP SIM. Click OptimizeCapacity AdvisorImport OVPA System Data....

Procedure 5-10 Import HP OVPA data into Capacity Advisor

64

Procedures

2. 3.

Select the target system(s). The Verify Targets screen displays. Verify the target system(s). You have the opportunity to add or remove systems here. When done, click Next. The Specify Parameters screen displays.

4.

Specify the begin and end dates desired to define the extent of the collection to import. For example: [-b 20071101 -e 20071231] If no date range is given, all data up to 30 days is imported.

5. 6.

Optionally, specify [-p] if the import is for a non-Insight Dynamics workload. Click Run Now. After a short time, the Task Results screen displays.

For tasks where you select Run Now, a few moments will pass and then you see the Task Results screen. For general help on interpreting the information in this screen, see the HP Systems Insight Manager 6.2 online help on Viewing Task Results. The Task Results screen shows a Running check box with a Start time: until the task completes. When data import finishes, you see an End time: displayed, with standard out (stdout) and standard error (stderr) information displayed on tabbed panes in this screen. Check both tabs for relevant information.

From the Optimize menu Import HP PMP data

Prerequisites 1. 2. 3. You must be logged in to Insight Dynamics (see Accessing Capacity Advisor (page 55)). The system(s) must be discovered by HP SIM. Click OptimizeCapacity AdvisorImport PMP System Data.... Select the target system(s). The Verify Targets screen displays. Verify the target system(s). You have the opportunity to add or remove systems here. When done, click Next. The Specify Parameters screen displays. 4. Specify the begin and end dates desired to define the extent of the collection to import. For example: [-b 20071101 -e 20071231] If no date range is given, all available data is imported. 5. 6. 7. Optionally, specify [-p] when the import is for a non-Insight Dynamics workload. Optionally, specify [-o] when you want the new data to overwrite existing data for the system within the Capacity Advisor database. Click Run Now. After a short time, the Task Results screen displays. For tasks where you select Run Now, a few moments will pass and then you see the Task Results screen. For general help on interpreting the information in this screen, see the HP Systems Insight Manager 6.2 online help on Viewing Task Results.
Gathering data for Capacity Advisor 65

Procedure 5-1 1 Import HP PMP data into Capacity Advisor

The Task Results screen shows a Running check box with a Start time: until the task completes. When data import finishes, you see an End time: displayed, with standard out (stdout) and standard error (stderr) information displayed on tabbed panes in this screen. Check both tabs for relevant information.

From the command line

Add user login information to the SSH settings for your specific system on the System Protocol Settings screen (OptionsProtocol SettingsSystem Protocol Settings). From the command line on the CMS, and logged in as rootor Administrator, execute the capopvaextract or cappmpextract command, giving the fully qualified host name as the first argument. (See the corresponding command reference pages in Appendix B (page 133) for more information.) For example: # capovpaextract node12.company.com

Ascertaining the data collection availability for a set of servers

From within a scenario, or from the Visualization tab of Virtualization Manager, you can see the data collection period for systems included in a scenario or for individual managed systems, respectively. This procedure describes how to create a list of selected (or all) licensed servers and their data collection periods, and is for use when you want to quickly see the data collection periods for a set of servers without creating or accessing a scenario to do so. Prerequisites You must have command-line access to the CMS managing the systems of interest. The systems of interest must be licensed for Capacity Advisor. Type
capprofile -lv

Procedure 5-12 From the command line

to see a list showing the name of each licensed system managed by this CMS, dates for which data has been collected, and the percent of data considered valid by Capacity Advisor. For other options, see capprofile in Appendix B (page 133). To return to a planning checklist: Obtaining reports on current resource usage [p. 35]

Possible sources of discrepancies in collected data

Several possibilities exist to explain discrepancies that may appear in the data or that may affect data collection. Check these possibilities to understand what actions you can take to correct the discrepancy.

No data collected for a managed node

If you do not obtain data on systems from which you expect to collect data, it is possible that the system has not been licensed for use with Capacity Advisor, either through Insight Dynamics or through HP Insight Capacity Advisor Consolidation software.

Data timestamp appears to be incorrect

For best accuracy in providing simulation solutions and historic reporting of actual system resource use, it is assumed that the time clocks of managed nodes are synchronized with the time clock of the central management server. If, on gathering or collecting data, the date stamp on your data is not current, the time or time zone on a managed node may be set incorrectly in relation to the CMS.
66 Procedures

Dynamic memory in HP Integrity virtual machines

A dynamic memory feature is available in HP Integrity virtual machines. This allows the memory allocated to each virtual machine to be changed without rebooting the virtual machine. Capacity Advisor is aware of this feature and records both the memory allocated to each virtual machine, as well as how much of this memory is in use for each five-minute interval. Both of these values are correct when the virtual machines are using the dynamic memory feature. When a virtual machine is running HP-UX 11.23, most built-in commands such as top and sar will not be aware of the dynamic memory feature and can show memory sizes that are different from what is recorded by Capacity Advisor. For example, if a virtual machine is initially booted with 16 GB of memory, and is then re-sized to 4 GB, the built-in commands will not know about the change and will show 16 GB for physical RAM. Capacity Advisor, however, will show that the available memory for the VM is 4 GB. Also, when a virtual machine is sized less than its maximum size, some built-in commands will show the kernel using more memory than it is actually using.

Producing graphs and reports

HP Insight Capacity Advisor software can generate both graphical and tabular data for presentation in either a report format or within an adjustable profile viewer.

Using the Profile Viewer

A profile viewer provides a quick summary of historical resource utilization, presenting data graphically as well as in tabular summaries. See also Profile Viewer Screen in Capacity Advisor Help for specific descriptions of the screen functions. A profile viewer can be accessed from the system meters on the Visualization tab, the HP SIM Optimize menu, or from the meters or menu selections on the Edit Scenario tabs in Capacity Advisor. A profile viewer opened from the Visualization tab generally displays the actual resource utilization data collected from the selected node. However, for non-OS node types such as an enclosure, a complex, or a vpar monitor, which do not have an operating system (OS) or hypervisor from which to collect actual resource utilization data, a profile viewer calculates the utilization profile by aggregating the actual data from all of the associated child nodes (blades, nPartitions, or vPartitions, respectively). A profile viewer opened from the scenario editor, on the other hand, always aggregates data from all of the workloads on a system or from all of the virtual machines (VM) running on a VM host when the VMs are included in the scenario. This is true even when there is actual data collected for the operating system or hypervisor. Aggregation is done to account for the modifications that can be made to a scenario, such as adding, removing, or moving workloads, changing the actual profile data, or changing the resource allocations within the modeled hardware. Due to the malleability of a scenario, it is possible that a scenario profile of a node could differ from profile viewed from the Visualization tab in Virtualization Managerfor the real node. This is particularly true of physical nodes that contain virtual nodes, such as a VM host. Additionally, for ESX VM hosts, Microsoft Virtual Server, and Hyper-V hosts, data for non-guest workloads is not collected for use in the 4.1 release of Capacity Advisor. Therefore, profile views accessed from the scenario editor do not account for utilization by workloads that are not VM guests. IMPORTANT: For specific descriptions of each field or summary table on the user interface screens, click the help topic link on the software screen for the task. The following sections describe how to access a profile viewer from various locations within HP SIM.
Producing graphs and reports 67

Prerequisites You must be logged in to Insight Dynamics (see Accessing Capacity Advisor (page 55)). You must have collected data on the systems of interest (see Gathering data for Capacity Advisor (page 55)).

Some functions of a profile viewer require Capacity Advisor Tools permissions to be seen and used. Procedure 5-13 To access a profile viewer from the HP SIM Optimize menu This procedure gives you access to view historic resource utilization on a real system in your network. 1. 2. 3. Select OptimizeView Profile... The target selection wizard opens. Select one system to view and click Apply. (For information on a typical task progression in HP SIM, see Creating a Task in the HP Systems Insight Manager 6.2 online help. Verify the target system and click Run Now. The profile viewer opens. NOTE: When no data has been collected If no data exists in the Capacity Advisor database for the selected system, and the system is licensed to work with Capacity Advisor, you are presented the opportunity to collect data immediately, calibrate power settings, and edit I/O capacity. At minimum, you will need to collect data prior to continuing this task. Procedure 5-14 To access a profile viewer from the Virtualization Manager Visualization tab This procedure gives you access to view historic resource utilization on a real system in your network. 1. 2. Select ToolsVirtualization Manager... The Visualization tab displays systems discovered by HP SIM. Find a system to view and click the desired meter icon to open a profile viewer for that utilization metric on that system. (For information on meters appearing on the Visualization tab, see Utilization metrics in Virtualization Manager Help.) NOTE: When no data has been collected If no data exists in the Capacity Advisor database for the selected system, and the system is licensed to work with Capacity Advisor, you are presented the opportunity to collect data immediately, calibrate power settings, and edit I/O capacity. At minimum, you will need to collect data prior to continuing this task. Procedure 5-15 To access a profile viewer when editing a scenario This procedure gives you access to view simulated resource utilization on a simulated system. This procedure assumes that you are starting from the Capacity Advisor Edit Scenario screen in the System tab view. For information on getting to this location, see Editing a scenario (page 88).

68

Procedures

1.

If you want to view the profile of a system: Click any of the horizontal utilization meters in the system table that represent current utilization of a resource. Profile views are available for all of the current resource types for which data is available (CPU, memory, network and I/O bandwidth, and power usage). The Capacity Advisor Profile Viewer opens and displays the data for the selected resource type and system.

2.

If you want to view the profile of a workload: a. Click the Workload tab. The Workload tab opens. b. When bar graphics are displayed in the workload table: Click any of the horizontal bar graphics representing current utilization of a resource. Profile views are available for all of the current resource types for which data is available for workloads (CPU, memory, and network and I/O disk bandwidth usage). The Capacity Advisor Profile Viewer screen displays opens and displays the data for the selected resource type and workload. c. If no bar graphics are displayed: i. Click the check box preceding the workload for which you want to see a profile. The row that is checked is highlighted to indicate selection. ii. Select ViewWorkload Profile... from the menu bar. The Profile Viewer screen displays.

Procedure 5-16 To change the view within the system hierarchy 1. 2. Find the Hierarchy near the top of the screen Click a link or select an item from the drop-down list to view a related profile. The new profile displays in the viewer screen. Procedure 5-17 To modify data presentation in a profile viewer You can change select settings that control modeling limits, and then view the resulting changes in the data when the new settings are applied. 1. 2. Locate the set of links that appear below and to the right of the profile identification summary information and above the data range selector. For each setting that you would like to modify, click the appropriate link. NOTE: Available settings When editing a scenario, you can edit the forecast model, edit the power settings, and edit utilization limits. When viewing profiles from the HP SIM Optimize menu, you can also edit I/O capacity and/or immediately collect data. The editor for the setting opens.

Producing graphs and reports

69

3.

Click OK to save the changes for each setting that you edit, and return to the Profile Viewer. NOTE: Viewing a VM guest on a VM host or viewing a complex In certain situations (such as when you are viewing the profile for a system or complex), navigational controls are presented to the right of the Hierarchy label near the top of the screen, such as links and drop-down lists , that allow you to view parents and siblings of the current resource profile. Click a link or select an item from the drop-down list to view a related profile. For details, access the help by clicking the ? button.

Procedure 5-18 To change the time and data range displayed in the profile viewer Optionally, you can adjust the time frame and interval. The default display, a Fixed Interval, shows the most recent seven days of activity. 1. You can select a different Fixed Interval in the drop down selector, or you can change to an Absolute Interval by clicking the radio button to the left of this interval selection. The user interface pauses momentarily to reset the screen fields. 2. 3. Set the beginning and end dates for the interval that you want to view. Click OK to apply the new interval to the graph and table data. The screen displays the new interval and data. Procedure 5-19 To manipulate the graphic display of utilization data 1. Optionally, use the pan right (> or >>) and pan left (< or << ) buttons to view earlier historic data (pan left) or forecast activity (pan right beyond the current date). The screen repaints with the new date interval resulting from the pan action. A pale blue background in the graph indicates the area in the graph where activity is forecast based on historic data and user-selected settings. 2. Optionally, turn off the bandwidth capacity indicator by deselecting the Show Capacity radio button. (Visible on network and disk I/O utilization metric viewers.) The screen repaints with the dashed blue capacity indicator line removed. 3. Optionally, turn off the resource allocation indicator by deselecting the Show Allocation radio button. (Visible on CPU and memory utilization metric viewers.) The screen repaints with the dashed blue allocation indicator line removed. 4. 5. 6. 7. Optionally, turn on the Show Invalid Data selection to see the points that have been dropped from the display and analysis (if any). Optionally, turn on the Show Observed Data selection to see actual observed activity collected from a real system. Optionally, turn on the Show Simulated Data selection to see representational activity based on data collected from a real system. Optionally, use the Profile Editor to set the data time frame and click Validate or Invalidate to set the status of the date range. Changes made here will be reflected in the graphic and Interval Metric Summary table. 8. When finished viewing the graph and table data for a scenario system or workload, click the Go back to .... link to return to your original starting point in the Edit Scenario screens.

For information on accessing special editors from a profile viewer, seeAccessing the forecast model for a workload or system (page 83).

70

Procedures

Procedure 5-20 To switch to alternate utilization resource metrics You can cause a profile viewer to display any of the utilization resource metrics provided by Capacity Advisor. Click the radio button to the left of the metric that you want to view. The user interface pauses momentarily to reset the screen display to the new metric, updating both the utilization graphic and the Interval Metric Summary table.

Using the report wizard

Capacity Advisor reports provide valuable summaries and details from data collected from managed systems. Reports can be generated that describe: resource utilization for CPU, memory, network I/O, disk I/O, and power consumption for real systems (historic usage) and for systems within a scenario (simulated usage), and including trends in usage over a period of time. candidates for system consolidation cost allocation by resource summary of peak values for CPU and memory (historic or simulated) system populations (by OS type, processor type, cores per socket, and total cores per socket) comparisons among scenarios

The report wizard

This general description of the report wizard applies to all reports, though options vary within the wizard depending on the report type and other options selected. For specific descriptions of each field on the report wizard screens, click the help link on the software screen. IMPORTANT: For specific descriptions of each field or summary table on the user interface screens, click the help topic link on the software screen for the task. Getting there The report wizard can be accessed from the following locations: the HP SIM Optimize and Reports menus the Virtualization Manager Report menu on the Visualization tab the Report menu on the Capacity Advisor tab TIP: For lists of all menu options for Capacity Advisor features, see Menus & tabs in Capacity Advisor Help. Prerequisites You must be logged in to Insight Dynamics. (See Accessing Capacity Advisor (page 55).) You must have collected data for the systems of interest (see Gathering data for Capacity Advisor (page 55)). You must be authorized and licensed on all systems to be included in the report (see HP Insight Dynamics 6.2 Getting Started Guide ).

Procedure 5-21 Select targets and set date range For specific descriptions of each field on the user interface screens, click the help link on the software screen for the task.

Producing graphs and reports

71

1.

Click one of the visible links to select a scenario, one or more collections, one or more complexes, one or more systems, or one or more workloads to appear in the report. (The availability of selections depends on the report type selected.) A new screen opens with an appropriate list of known scenarios, collections, complexes, systems, or workloads.

2. 3.

Click the check box to the left of each object's name that is to appear in the report. Click OK. The Select Report Targets screen reopens with an updated list of targets and a date range selector visible.

4. 5.

6. 7.

Check that the selected targets are correct. Note the available date range of all collected data, which appears above the date range selector, and the default date range (at most, 1 month prior to the current day, when that amount of data is available). If the default date range is acceptable, click Next. If a different data set is desired, change the date and time, then click Next. The Select Details screen opens.

Select details specific to report type This step in the report wizard is different for each report. See the specific report procedures and Capacity Advisor online help for information. Confirm selections for the report Some reports give you the opportunity to confirm selections before you actually run the report. Download or browse the report For help in interpreting the report, click the help button provided on the browser-viewable and downloadable reports. To return to a planning checklist: Obtaining reports on current resource usage [p. 35]

Creating an historic utilization report

1. 2. Select ReportsCapacity AdvisorCreate Utilization Reports... on the top menu bar. The Report Wizard opens on the Select Report Content screen. Select the check box(es) for a utilization summary or a summary and details and click Next. NOTE: You can also select to run a trend report and a power report at the same time that you run a utilization report. The Select Report Targets screen opens. 3. Select the collection, complex, or systems for which you want the report, and select the data range. See Select targets and set date range for more information. 4. Select details specific to report type. 1. Select one or more types of resources for which you want to see data from among CPU, memory, network I/O, disk I/O, and power. 2. Select the type of scale for data presentation: percentage of allocated resource, absolute numbers, or both.

72

Procedures

3.

Check the default graph size. The default size fits just within a letter-size page for printing. If you prefer dimensions smaller or larger, use the drop-down to change width (in pixels). If you prefer a different width-to-height proportion, use the Aspect Ratio drop down.

4. 5.

Click Finish. The Report Created screen opens.

Click the appropriate link to browse the report in a web browser or to save the report to the location that you designate.

To return to a planning checklist: Obtaining reports on current resource usage [p. 35] Consolidating server loads onto a virtual machine manually [p. 36] Consolidating server loads onto a virtual machine using automated solution finding [p. 47] Estimating the effect of adding processors [p. 51] Estimating the effect of moving processors [p. 51]

Creating a scenario utilization report

1. 2. Select ReportsCapacity AdvisorCreate Utilization Reports... on the top menu bar. The Report Wizard opens on the Select Report Content screen. Select the check box(es) for a utilization summary or a summary and details and click Next. The Select Report Targets screen opens. 3. 4. Select the scenario for which you want the report, and select the data range. See Select targets and set date range for more information. Select details specific to report type. 1. Select one or more types of resources for which you want to see data from among CPU, memory, network I/O, disk I/O, and power. 2. Select the type of scale for data presentation: percentage of allocated resource, absolute numbers, or both. 3. Check the default graph size. The default size fits just within a letter-size page for printing. If you prefer dimensions smaller or larger, use the drop-down to change width (in pixels). If you prefer a different width-to-height proportion, use the Aspect Ratio drop down. 4. 5. Click Finish. The Report Created screen opens. Click the appropriate link to browse the report in a web browser or to save the report to the location that you designate.

To return to a planning checklist: Consolidating server loads onto a virtual machine manually [p. 36] Consolidating server loads onto a virtual machine using automated solution finding [p. 47] Estimating the effect of adding processors [p. 51] Estimating the effect of moving processors [p. 51] Determining where to put a workload using automated solution finding

Producing graphs and reports

73

Using the report wizard to create a scenario comparison

The Scenario Comparison Report allows you to compare two to four scenarios in a tabular and graphical side-by-side comparison report. Procedure 5-26 Selecting scenarios and setting the data range 1. 2. From the Capacity Advisor tab, select ReportCreate Scenario Comparison Reports... . If you have pre-selected the scenarios (on the Capacity Advisor tab) that you want to compare, review the information displayed on this screen. If it is satisfactory, go to step 5 to set the date range. If you need to select scenarios to compare, continue with step 2. Want to compare more than four scenarios?: One way to do this is to run and save multiple reports, and then print them out to compare them side-by-side. For example, to compare six scenarios, run one report with four scenarios and one report with two scenarios. Lay the printouts side-by-side to compare various aspects of the scenarios. 3. 4. 5. Select Edit Scenario Selection. A new screen appears showing the possible scenarios to include in the comparison report. Check the box to the left of the scenarios to include. Choose one of the following actions: Press OK to accept the selections and return to the Select Report Targets screen. A Date Selection area appears in the screen. Press Cancel to end the report creation and return to your originating screen. To set the date range, look at the default provided (the full range of data collected). Decide if you want to modify this value. If so, select the beginning and ending date/time. Click Next to continue to the Select Report Options screen.

6. 7.

Procedure 5-27 Selecting report details in a scenario comparison All resource metric options are available in a scenario comparison. All selectable fields are combined into one section called General Report Options. 1. 2. Put a check in the box(es) next to the resource types that you want to compare. If you selected the Power resource type, fill in the Currency, Cost per kWh, and Cooling Cost Multiplier values. For detailed discussion of the available power options, see Power Report Options. Choose the scale (absolute utilization numbers, percent of allocated resources used, or both). Select Finish to create and complete the report.

3. 4.

An example scenario comparison report The following image illustrates one small part of a scenario comparison report.

74

Procedures

Figure 5-1 Comparison of three scenarios in a Capacity Advisor report

This report includes two consolidation solutions provided by the Smart Solver (ServerConsolidationResult-SmallSystem and ServerConsolidationResults-BigSystem) and the original pre-consolidation set of physical servers (ServerConsolidationScenario). For more snapshots from this same report, see Scenario comparison report (page 157). Calculating a virtualization consolidation ratio It can be useful to look at the resulting ratio of virtual machines to physical servers after running a system or workload consolidation simulation to help in evaluating the return on investment for a particular configuration of machines. Currently, Capacity Advisor does not supply this ratio in its reports, but you can easily calculate ratios for a set of scenarios that you wish to compare. Prerequisites You must be logged in to Insight Dynamics (see Accessing Capacity Advisor (page 55)). You must have created a planning scenario that represents the system configuration that you want to consolidate. (See Creating a planning scenario (page 86) and Editing a scenario (page 88).) You must have consolidated the systems in the initial planning scenario onto the VM host(s) of your choice. For purposes of comparison, you may want to save two to three different consolidation simulations. (See Automated solution finding: System consolidation to VMs (page 109).) You must have run a scenario comparison report that includes your initial planning scenario and your consolidated scenario results. (See Using the report wizard to create a scenario comparison (page 74).)

Procedure 5-28 Calculate virtualization consolidation ratios using data from a scenario comparison report 1. 2. Examine the scenario comparison report. (As an example, see Figure 5-1 (page 75).) For the systems scenario in the report, subtract the Number of VM Hosts in that scenario from the Number of Physical Servers Including VM Hosts. This value represents the number of physical servers that are to be consolidated into virtual machines. For each consolidation solution scenario, calculate the virtualization consolidation ratio: number_of_physical_servers/number_of_VM_hosts For example, using the data in Figure 5-1 (page 75), you can determine that the number of physical servers to be consolidated is 20. The ratio for the small system consolidation is 20/6, and the ratio for the big system consolidation is 20/3 meaning that the 20 physical servers can fit on 6 small VM hosts or 3 larger VM hosts.
Producing graphs and reports 75

3.

Creating a consolidation candidates report

1. 2. Select ReportsCapacity AdvisorCreate Consolidation Candidate Reports... The Report Wizard opens on the Select Report Targets screen. Select the collection, complex, scenario, or systems for which you want the report, and select the data range. See Select targets and set date range for more information. 3. Select details specific to report type. 1. Select one or more types of resources for which you want to see data from among CPU, memory, network I/O, and disk I/O. 2. Decide whether or not to alter the default settings for the Table Threshold Settings. (See Details: Consolidation Candidates Report in Capacity Advisor Help for more information. 3. Click Next to view a confirmation page showing the report selections. 4. Click Finish to run the report. Click the appropriate link to browse the report in a web browser or to save the report to the location that you designate.

4.

To return to a planning checklist: Consolidating server loads onto a virtual machine manually [p. 36] Consolidating server loads onto a virtual machine using automated solution finding [p. 47] Determining where to put a workload using automated solution finding

Creating a cost allocation report

1. 2. Select ReportsCapacity AdvisorCreate VM Host Cost Allocation Reports... or ReportsCapacity AdvisorCreate Workload Cost Allocation Reports... The Report Wizard opens on the Select Report Targets screen. Select the collection, complex, scenario, or systems for which you want the report, and select the data range. See Select targets and set date range for more information. 3. Select details specific to report type. 1. Select one or more types of resources for which you want to see data from among CPU, memory, network I/O, and disk I/O. 2. Supply the weighted average that you want the calculation to use for each selected resource. 3. Click Next to view a confirmation page showing the report selections. 4. Click Finish to run the report. Click the appropriate link to browse the report in a web browser or to save the report to the location that you designate.

4.

To return to a planning checklist: Obtaining reports on current resource usage [p. 35] Consolidating server loads onto a virtual machine manually [p. 36] Consolidating server loads onto a virtual machine using automated solution finding [p. 47] Determining where to put a workload using automated solution finding

Creating a peak summary report

1. Select ReportsCapacity AdvisorCreate Peak Summary Reports....

76

Procedures

2.

The Report Wizard opens on the Select Report Targets screen. Select the systems, scenario, or collection for which you want the report, and select the data range. See Select targets and set date range for more information.

3.

Select details specific to report type. 1. Select one or more types of resources for which you want to see data from among CPU, memory, network I/O, and disk I/O. 2. Select whether to include a Full Table of all available metrics or a subset (Short Table) of the available metrics. See Details: Peak summary report in Capacity Advisor Help for more information. 3. Select the graphs that you want to include in the report. 4. Provide the hours during which you expect peak activity to occur in your typical business day. 5. Optional. Select a different graph size. 6. Click Next to view a confirmation page showing the report selections. 7. Click Finish to run the report. Click the appropriate link to browse the report in a web browser or to save the report to the location that you designate.

4.

Creating a population report

1. 2. Select ReportsCapacity AdvisorCreate Population Reports.... The Report Wizard opens on the Select Report Targets screen. Select the systems, scenario, or collection for which you want the report, and select the data range. See Select targets and set date range for more information. 3. Select details specific to report type. 1. Optional. Select the operating system detail to be displayed in the report. 2. Optional. Select the processor information to be displayed in the report. 3. Optional. Select the cores per socket information to be displayed in the report. 4. Optional. Select the total cores per server information to be displayed in the report. 5. Optional. Select a different scale or graph size. 6. Click Next to view a confirmation page showing the report selections. 7. Click Finish to run the report. Click the appropriate link to browse the report in a web browser or to save the report to the location that you designate.

4.

Creating a trend report

1. 2. Select ReportsCapacity AdvisorCreate Utilization Reports.... The Report Wizard opens on the Select Report Content screen. Select the check box(es) for a trend report summary or a summary and details and click Next. The Select Report Targets screen opens. 3. Select the collection, complex, systems, scenario, or workloads for which you want the report, and select the data range. See Select targets and set date range for more information.

Producing graphs and reports

77

4.

Select details specific to report type. a. Select one or more types of resources for which you want to see data from among CPU, memory, network I/O, and disk I/O. (Power is not available when reporting trends only.) b. Check the default graph size. The default size fits just within a letter-size page for printing. If you prefer dimensions smaller or larger, use the drop-down to change width (in pixels). If you prefer a different width-to-height proportion, use the Aspect Ratio drop down. If you chose trend report details: i. Select the Business Interval (default: 1 week). Requiring higher percentages of valid points can make the business intervals analyzed more meaningful, but can also reduce the number of business intervals available for the analysis, making the overall analysis less useful. ii. Select the minimum percentage of valid data points that must be present within the period (default: 95%), called the Valid Threshold. iii. Choose the data aggregation type (default: average), called Compute Trending of. iv. Optional. Check the box to include error analysis. c. Click Finish.

5.

Click the appropriate link to browse the report in a web browser or to save the report to the location that you designate.

Related topics Determining trends in Capacity Advisor (page 31)

Creating a power report

1. 2. Select ReportsCapacity AdvisorCreate Utilization Reports.... The Report Wizard opens on the Select Report Content screen. Select the check box(es) for a power summary or a summary and details and click Next. The Select Report Targets screen opens. 3. Select the scenario, complex(es), or systems for which you want the report, and select the data range. See Select targets and set date range for more information. 4. If you chose power report details: a. Designate the currency label to use in power report tables. b. Designate a typical cost for power per kilowatt-hour (see Cost per kilowatt-hour (page 123)). c. Optionally, designate a cooling cost multiplier (see Cooling multiplier (page 123)). d. Designate a time interval for display of results (default: by day). e. Click Finish. Click the appropriate link to browse the report in a web browser or to save the report to the location that you designate.

5.

Setting utilization limits

Utilization limits allow you to set service level objectives for workloads based on overall system utilization. For any given workload, you can specify one or more service level objectives. Global
78 Procedures

utilization limits are applied to real workloads recognized by Virtualization Manager and to workloads within scenarios to enable analysis of collected data (actual utilization) as it relates to desired resource utilization. Within a scenario, when a service level objective cannot be met for a workload, a visual indicator along with a warning message will be displayed when moving a workload in a scenario. When making automated changes, such as the automated system consolidation, these utilization limits are enforced in determining a solution. For more discussion about utilization limits, see Utilization limits (page 27). IMPORTANT: For specific descriptions of each field or summary table on the user interface screens, click the help topic link on the software screen for the task.

Getting there
Screens for modifying utilization limits can be accessed from the following locations: the Virtualization Manager Configure menu on the Visualization tab the Modify menu on the Capacity Advisor tab the Edit menu on either the System or Workload tab of the Edit Scenario screen TIP: For lists of all menu options for Capacity Advisor features, see Menus & tabs in Capacity Advisor Help.

Setting global utilization limits

The default global utilization limits, which are applied in the absence of more specific limits, are: CPU utilization may not exceed 70% of allocation for more than 0 minutes. Memory utilization may not exceed 100% of allocation more than 0% of the time.

Adding a utilization limit

1. 2. From the Visualization tab, select Configure Global Utilization Limits... For each metric for which you wish to add a utilization limit: a. Select the type of limit you wish to place, the utilization metric the limit applies to and the utilization value above which the limit applies. For a Percent of Time Limit, enter the percent of time the utilization value may be exceeded and a comment describing the limit. For a Sustained Minutes limit, enter the duration in minutes the utilization may be exceeded, and a comment describing the limit. b. Click Add. To see the current global utilization settings, click Revert. To cancel your changes, click Cancel. To accept your changes, click OK. To return to a planning checklist: Consolidating server loads onto a virtual machine manually [p. 36]

3.

Removing a utilization limit

1. For each utilization limit you wish to delete: a. Check the box next to the utilization limit. b. Click Remove.

Setting utilization limits

79

2.

To see the current global utilization settings, click Revert. To cancel your changes, click Cancel. To accept your changes, click OK.

Setting workload utilization limits

Utilization limits allow you to set service level objectives for workloads based on overall system utilization. For any given workload, you can specify one or more service level objectives. The limit acts as an indicator for what the desired maximum usage would be. This limit can be applied to selected workloads on existing systems viewable from the Virtualization Manager Visualization tab. The workload utilization limits apply only to the selected workload(s).

Adding a utilization limit

1. 2. From the Capacity Advisor tab, select ConfigureWorkload Utilization Limits... For each metric for which you wish to add a utilization limit: a. Select the type of limit you wish to place, the utilization metric the limit applies to, and the utilization value above which the limit applies. For a Percent of Time Limit, enter the percent of time the utilization value may be exceeded and a comment describing the limit. For a Sustained Minutes limit, enter the duration in minutes the utilization may be exceeded, and a comment describing the limit. b. Click Add. To see the current utilization settings, click Revert. To cancel your changes, click Cancel. To accept your changes, click OK.

3.

Enabling or disabling the limit

To enable or disable the application of the current utilization limit: Select either Enabled or Disabled.

Removing a utilization limit

1. For each utilization limit you wish to delete: a. Check the box next to the utilization limit. b. Click Remove. To see the current global utilization settings, click Revert. To cancel your changes, click Cancel. To accept your changes, click OK.

2.

Setting scenario-wide utilization limits

The scenario utilization limits apply to all workloads within the selected scenario.

Adding a utilization limit

1. 2. From the Capacity Advisor tab, select a scenario from the list of scenarios. Select ConfigureScenario-wide Utilization Limits.

80

Procedures

3.

For each utilization limit you wish to add: a. Select the type of limit you wish to place, the utilization metric the limit applies to and the utilization value above which the limit applies. For a Percent of Time Limit, enter the percent of time the utilization value may be exceeded and a comment describing the limit. For a Sustained Minutes limit, enter the duration in minutes the utilization may be exceeded, and a comment describing the limit. b. Click Add. To see the current utilization settings, click Revert. To cancel your changes, click Cancel. To accept your changes, click OK.

4.

Enabling or disabling the limit

To enable or disable the application of the current utilization limit on the scenario: Select either Enabled or Disabled.

Removing a utilization limit

1. For each utilization limit you wish to delete: a. Check the box next to the utilization limit. b. Click Remove. To see the current global utilization settings, click Revert. To cancel your changes, click Cancel. To accept your changes, click OK.

2.

Setting scenario workload utilization limits

The scenario workload utilization limits apply to the selected workload(s) within the selected scenario.

Adding a utilization limit

1. 2. 3. 4. From the Capacity Advisor tab, open a scenario. Click the Workload tab. Select EditScenario-wide Workload Utilization Limits. For each metric for which you wish to add a utilization limit: a. Select the type of limit you wish to place, the utilization metric the limit applies to and the utilization value above which the limit applies. For a Percent of Time Limit, enter the percent of time the utilization value may be exceeded and a comment describing the limit. For a Sustained Minutes limit, enter the duration in minutes the utilization may be exceeded, and a comment describing the limit. b. Click Add. To see the current utilization settings, click Revert. To cancel your changes, click Cancel. To accept your changes, click OK.

5.

Enabling or disabling the limit

To enable or disable the application of the current utilization limit: Select either Enabled or Disabled.

Setting utilization limits

81

Removing a utilization limit

1. For each utilization limit you wish to delete: a. Check the box next to the utilization limit. b. Click Remove. To see the current global utilization settings, click Revert. To cancel your changes, click Cancel. To accept your changes, click OK. To return to a planning checklist: Consolidating server loads onto a virtual machine manually [p. 36]

2.

Forecasting utilization
HP Insight Capacity Advisor software provides multiple levels of forecast models to allow precise control of forecasting future utilization. IMPORTANT: For specific descriptions of each field or summary table on the user interface screens, click the help topic link on the software screen for the task.

Defining forecast models

Whenever a Capacity Advisor report or profile is generated with an end date later than the current date, the historical utilization data is projected into the future. The projection is indicated in the utilization graphs by a light blue colored background next to the usual white background. This projection is done based on a forecast model. Forecast models can be defined globally, for individual workloads or systems, for a scenario, and for individual workloads within a scenario. Because the process for defining a forecast model is basically the same regardless of where it is in the hierarchy of forecast models, the procedures below are broken into two parts: accessing the forecast model and defining it. NOTE: Although forecast models cannot be deleted, all but the global forecast model can be disabled and enabled. Follow the appropriate procedure for accessing the forecast model and then follow the procedure for disabling or enabling it.

Accessing the Global Forecast Model

The annual growth rates for the global forecast model are frequently based on an organization's planned growth rate. The global forecast model applies to all reports generated on systems and complexes. Reports on workloads or scenarios without a forecast model also use the global forecast model. Prerequisites 1. You must be logged in to Insight Dynamics. (See Accessing Capacity Advisor (page 55).) You must have sufficient authorization to define the global forecast model. If you are not on the Capacity Advisor tab: If the Capacity Advisor tab is visible, click the Capacity Advisor tab. If the Capacity Advisor tab is not visible, select OptimizeCapacity AdvisorView Scenarios... from the top menu bar. The Capacity Advisor tab opens with a list of scenarios. 2. From the Capacity Advisor menu bar, select ConfigureGlobal Forecast... The Forecast Editor - Global Forecast Model screen displays.
82 Procedures

Procedure 5-50 To access the Global Forecast Model

Defining the Global Forecast Model The settings that you define here are applied globally in the absence of other specifically targeted forecast models. This procedure assumes that you have opened the Global Forecast Model screen (see Accessing the Global Forecast Model (page 82).) . 1. 2. 3. Provide a brief description of the forecast model in the Description field. Choose a time frame to use in tiling the data into the future (default: fixed interval). The time interval (date range) field adjusts according to your time frame selection. Select the date range for defining the period of data collection to use as the basis for the forecast. a. For a fixed interval: select the calendar interval, Beginning or Ending, and the date (MM-DD-YYYY) b. For a ranged interval: select the beginning and ending dates and times. c. For a float interval: select the calendar interval, Beginning or Ending, and general date indicator (default: Last Full Day) Provide Annual Projected Growth Rates for each resource: CPU, Memory, Network I/O, and Disk I/O. Use positive values for increasing utilization, negative values for decreasing utilization, and zero for no change). The default is 1% projected annual growth for every resource. TIP: You can estimate projected annual growth by including trend calculations in utilization reports derived by analyzing historical data. (See Determining trends in Capacity Advisor (page 31) and The report wizard (page 71).) 5. Click the OK button to save and apply a new definition for global forecasting. TIP: Undoing changes to the global forecast model If you change your mind about values while editing this screen, use the Revert button to replace newly set values with the values that were there when you started. The Revert button does not return default values, so if you have edited the global forecast values once before, and then decide that you prefer the default values, you will have to set the values to 0 (zero) for each resource and click OK to have the original default values in operation.

4.

Accessing the forecast model for a workload or system

When the resource utilization of an individual workload or system is expected to differ from that predicted by the global forecast model, a workload- or system-specific forecast model can be created. Forecasting for workloads or systems is done from within a profile viewer associated with the workload or system. See Using the Profile Viewer (page 67) for information on how to access the viewer from the HP SIM Optimize menu or from a scenario.

Forecasting utilization

83

IMPORTANT: The forecast model for a system is not inherited by any monitored workloads. If a system with monitored workloads is included in a scenario, the forecast model will not be used within the scenario. Prerequisites You must be logged in to Insight Dynamics. (See Accessing Capacity Advisor (page 55).) You must have sufficient authorization to define the forecast model for a workload or a system.

Defining the forecast model for a workload or system The following procedure assumes that a profile viewer is open (see Using the Profile Viewer (page 67).) 1. If you are not on the Virtualization Manager screen, from the top menu, select ToolsVirtualization Manager.... The Virtualization Manager Visualization tab screen is displayed. 2. To define the forecast model for a system, start on the Visualization tab. To define the forecast model for a workload, click the Workload tab. The Workload tab opens, displaying the licensed workloads. 3. Open a profile viewer by clicking a utilization meter for a particular system on the Visualization tab or by clicking a utilization link for a particular workload on the Workload tab. The Profile Viewer screen is displayed for the system or workload. 4. 5. Click the Edit Forecast Model... link on the profile viewer. The Forecast Editor: Workload Forecast Model screen displays. To define the forecast model, follow the procedure Defining a forecast model. To disable the forecast model, follow the procedure Disabling a forecast model To enable the forecast model, follow the procedure Enabling a forecast model.

The default state of the new forecast definition is Enabled.

Accessing the forecast model for a scenario

Defining a separate forecast for a scenario allows you to provide estimates of utilization based on differing growth projections. Prerequisites 1. You must be logged in to Insight Dynamics (see Accessing Capacity Advisor). You must have created the scenario (see Creating a planning scenario (page 86)). If you are not on the Capacity Advisor tab: If the Capacity Advisor tab is visible, click the Capacity Advisor tab. If the Capacity Advisor tab is not visible, select OptimizeCapacity AdvisorView Scenarios... from the top menu bar. The Capacity Advisor tab opens, with a list of scenarios. 2. 3. The names of scenarios for which you have authorization to define a forecast model are displayed as links. Click the link to open the scenario editor. From the System tab, select EditScenario-wide Forecast... The Forecast Editor: Scenario-wide Forecast Model screen is displayed.
84 Procedures

Procedure 5-53 To access the forecast model for a scenario

4.

To define the forecast model, follow the procedure Defining a forecast model. To disable the forecast model, follow the procedure Disabling a forecast model To enable the forecast model, follow the procedure Enabling a forecast model.

Accessing the forecast model for a workload within a scenario

If the resource utilization of an individual workload within a scenario is expected to change differently from the scenario forecast model, a different forecast model can be provided for the workload. Prerequisites 1. 2. 3. 4. You must be editing a scenario (see Editing a scenario (page 88)). If you are not viewing the workloads, click the Workload tab. The Workload tab opens, revealing a list of the workloads in the scenario. Click the check box preceding a single workload. Select EditScenario Workload Forecast... from the menu bar. The Forecast Editor: Scenario Workload Forecast Model screen is displayed. To define the forecast model, follow the procedure Defining a forecast model. To disable the forecast model, follow the procedure Disabling a forecast model To enable the forecast model, follow the procedure Enabling a forecast model.

Defining a forecast model

Once you have accessed a forecast model, use the following procedure to define it. For descriptions of each of the fields noted in this procedure, see the screen description for the model with which you are working in the Capacity Advisor online help reference. See The forecast model hierarchy (page 33)for a list of the model screen descriptions. 1. Provide a brief description of the forecast model in the Description field 2. Specify an appropriate range of data to base the forecast on in the Forecast Data Range Selection fields. 3. Provide Annual Projected Growth Rates for each of the utilization resources (CPU, memory, network I/O, disk I/O). You may want to use trend data derived from analyzing historical data to help you estimate future growth (see Forecasting growth (page 33)). 4. Click the OK button.

Disabling a forecast model

While it is not possible to delete a forecast model, forecast models at all levels below the global forecast model can be disabled by accessing the appropriate forecast model and using the following procedure. 1. Click the Disable radio button. 2. Click the OK button.

Enabling a forecast model

If you have previously disabled a forecast model, you can re-enable it by accessing the appropriate forecast model and using the following procedure. 1. 2. Click the Enable radio button. Click the OK button.

Generating forecasts
Once you have defined one or more forecast models, you can view the results of the forecast models two ways:
Forecasting utilization 85

For a quick view, Viewing forecast data in a profile viewer For a more thorough report, Viewing forecast data in a utilization report (page 86)

Viewing forecast data in a profile viewer

A profile viewer provides a quick view of resource utilization for a system, complex, or workload. Once the profile viewer is posted, you can view the forecast by extending the date range into the future. Prerequisites: You must be in a profile viewer. (See Using the Profile Viewer (page 67).) Change the Time Frame and/or Interval and/or Beginning and/or Ending for the profile to include future dates and/or times. If necessary, click the Refresh button. The graph will be updated. Historical utilization data will be plotted on a white background and forecast data will be plotted on a light blue background.

Viewing forecast data in a utilization report

Use the procedure specified in Creating an historic utilization report (page 72) and specify Ending (and possibly Beginning) times under Date Selection to include future times. Historical utilization data will be plotted on a white background and forecast data will be plotted on a light blue background.

Working with scenarios

Scenarios are collections of systems and workloads, both real and what-if creations. While scenarios are based on real data, you can modify parameters to model changes to the environment and the configuration of systems and workloads without affecting the real systems that the scenario is based upon. IMPORTANT: For specific descriptions of each field or summary table on the user interface screens, click the help topic link on the software screen for the task. TIP: For lists of all menu options for Capacity Advisor features, see Menus & tabs in Capacity Advisor Help.

Creating a planning scenario

Scenarios are used to model system behavior by performing what-if operations based on collected data. The first step in using scenarios is creating one. Prerequisites You must be logged in to Insight Dynamics. (See Accessing Capacity Advisor (page 55).) You must have already collected data on the systems of interest (see Gathering data for Capacity Advisor (page 55)). The systems you want to include in the scenario must be licensed for Capacity Advisor and you must be authorized on all of them (see HP Insight Dynamics 6.2 Getting Started Guide). Select OptimizeCapacity AdvisorCreate Scenario... from the top menu bar. The Create Scenario wizard opens to an Introduction screen containing explanatory information on how to interpret the icons that are used to indicate progress through the wizard and how to navigate the wizard.

Procedure 5-59 Starting a scenario

86

Procedures

Procedure 5-60 Identifying the scenario 1. 2. 3. Click Scenario Name in the left navigation column to open the Enter Scenario Name and Description screen. Required. Type a unique Name. Type a short description in the Description field. TIP: As the number of scenarios grows, the description field can help you to differentiate similarly named scenarios. 4. Optional. You can de-select the check box for opening a scenario editing session after completing scenario creation. When you un-check this box, you will return to the scenario list page upon completing the scenario creation. The Edit Scenario window on Mozilla Firefox: In the case where the Edit Scenario window is already open, but hidden beneath other windows when you create a new scenario, it is not obvious that the window has refreshed with your new scenario information. This can occur when using Mozilla Firefox with multiple windows open on your display. To more easily access the refreshed window, set Firefox to allow Javascript to raise or lower windows. Then, when you create a new scenario, the pre-existing Edit Scenario window will rise to the forefront of the display. 5. Click Next to proceed to the Add Systems to Analyze screen, or click Systems in the left navigation column. From the Add Systems to Analyze, click Add. A new window opens that provides controls for filtering and selecting discovered systems to include in the scenario. 2. In the new window, select existing systems that you want to include in the scenario and click Add. (See Adding systems in Capacity Advisor online help for information on using the controls in this window.) With each addition, the list of systems on the primary Systems screen lengthens. 3. 1. 2. Click Next to view a summary of all actions taken in the wizard. Verify that the summary information is what you expect. When satisfied, click Finish to save the scenario and exit the Create Scenario wizard. By default, the scenario editor will open, showing utilization data for your new scenario. The default data range used to calculate the utilization in the meters is set to one week back from the current date. (See Controlling the data display (page 88) in the Scenario Editor to change this value.) If you have not selected to open a scenario editing session, the main window refreshes with the list of scenarios (on the Capacity Advisor tab), including your new scenario. To return to a planning checklist: Consolidating server loads onto a virtual machine manually [p. 36] Consolidating server loads onto a virtual machine using automated solution finding [p. 47] Estimating the effect of adding processors [p. 51] Estimating the effect of moving processors [p. 51] Determining where to put a workload using automated solution finding Procedure 5-62 Reviewing a summary of the scenario settings

Procedure 5-61 Selecting systems to simulate 1.

Working with scenarios

87

Editing a scenario
Editing a scenario allows you to modify the systems and workloads in a scenario. This can be done immediately after initial creation or to tune a scenario to represent planned changes. Edit only one scenario at a time : Opening a new edit scenario session when another editing session is already open causes the loss of any unsaved changes in the previously opened session. If you were running an automated solution in your previous session, the automated calculations are immediately halted and no settings or results are saved. Prerequisites 1. You must be logged in to Insight Dynamics. (See Accessing Capacity Advisor (page 55).) You must have created the scenario. (See Creating a planning scenario (page 86).) If you are not on the Capacity Advisor tab: If the Capacity Advisor tab is visible, click the Capacity Advisor tab. If the Capacity Advisor tab is not visible, select OptimizeCapacity AdvisorView Scenarios... from the top menu bar. The Capacity Advisor tab will open, with a list of scenarios. 2. Any scenarios you have authorization to edit will be presented as links. Click the name of the scenario you want to edit. The Capacity Advisor - Edit Scenario screen will be displayed.

Controlling the data display

The default values for the data range and the Metric View Selection may not accurately represent the interval of interest and the preferred metric. These are easily adjusted.

Change the meter style selection

Prerequisites: You must be editing a scenario (see Editing a scenario (page 88)). Click the Absolute or Percent radio button. The meter bars in the scenario resource utilization table display the data as absolute numbers or as percentages, according to your selection.

Change the data collection period by setting the data range

Set the interval within a data collection period that you want to use as the foundation for a simulation or to view a specific historic period.

88

Procedures

Prerequisites: You must be editing a scenario (see Editing a scenario (page 88)) Changes to the data collection period persist across sessions.

NOTE: 1.

Click Edit Interval within the Set Data Range box.

The fields are enabled as shown in the following image.

2.

Click the first drop-down arrow to the left to see the choices for the duration of the data collection period that you want to use. Choose one to view in the display. The choices are as follow: Day Week (default) Month Quarter Half Year

3.

Click the next drop-down arrow to the right to see the choices for selecting what relationship the interval shall have to the selected date. Choose one to view in the display. The choices are as follow: Ending (the simulation shall end at the selected date default) Beginning (the simulation shall begin at the selected date)

4. 5. 6.

Change the date, if needed, to work well with your other Data Range selections Click OK to refresh the scenario resource utilization table with data collected during the defined interval. Click Cancel Edit Interval to return to the previous data range for this scenario.

Working with scenarios

89

Change the meter representation

Prerequisites: You must be editing a scenario (see Editing a scenario (page 88)).

NOTE: Changes to the Meters Represent: options are applied to the current scenario editing session, but options return to the default values at the beginning of any new session. Click the drop-down arrow to select a type of calculation to be represented in the meter bars in the resource utilization table. The choices are as follow: average 90th percentile peak (default) max 15 minute sustained

The scenario resource utilization table displays the new values for each resource, including violations of utilization limits set for each resource.

Copying a scenario
It is frequently desirable to use an existing scenario as the starting point for developing a new scenario. Copying a scenario provides an easy way to accomplish this. Prerequisites You must be logged in to Insight Dynamics. (See Accessing Capacity Advisor (page 55).) You must be authorized on all systems in the scenario (see HP Insight Dynamics 6.2 Getting Started Guide). If you are not on the Capacity Advisor tab: If the Capacity Advisor tab is visible, click the Capacity Advisor tab. If the Capacity Advisor tab is not visible, select OptimizeCapacity AdvisorView Scenarios... from the top menu bar. The Capacity Advisor tab opens with a list of existing scenarios that you are authorized to view. 2. 3. 4. 5. Click the check box preceding the scenario that you want to copy. Select CreateCopy Planning Scenario.... The Copy Scenario screen displays. Modify the Name and Description fields as appropriate. Click OK. You are returned to the Capacity Advisor tab, and the copied scenario appears in the scenario list. To return to a planning checklist: Consolidating server loads onto a virtual machine manually [p. 36]

Procedure 5-67 To Copy a Scenario 1.

Renaming a scenario
Over time, more appropriate names for scenarios may become apparent, and you may want to change the scenario name. Prerequisites To rename a scenario: You must be logged in to Insight Dynamics (see Accessing Capacity Advisor). You must have created the scenario (see Creating a planning scenario (page 86)).
90 Procedures

Getting there
If you are not on the Capacity Advisor tab: If the Capacity Advisor tab is visible, click the Capacity Advisor tab. If the Capacity Advisor tab is not visible, select OptimizeCapacity AdvisorView Scenarios... from the top menu bar. Procedure 5-68 To rename a scenario The Capacity Advisor tab opens with a list of existing scenarios that you are authorized to view. 1. 2. 3. 4. Click the check box preceding the scenario that you want to rename. Select ModifyRename Planning Scenario... from the menu bar. The Rename Scenario screen displays. Modify the Name and Description fields as desired. Click OK. You are returned to the Capacity Advisor tab, and the renamed scenario appears in the scenario list.

Undo/edit/review applied what-if actions in a scenario

As you work on a scenario, you can review, delete, or disable/enable selected system changes. Select What-If ActionUndo/Edit/View Applied What-If Actions from either the System or Workload tab. The screen displays a list of changes made to the scenario. Check boxes precede each action, with the earliest changes at the top of the list. IMPORTANT: Disabling or enabling what-if actions can cause subsequent and dependent what-if actions to fail. If this occurs, return to this screen to evaluate the dependencies and decide what might be done to eliminate the errors. Remember that deletions permanently remove the action from the record (and the scenario).

To view applied what-if actions

If you only wanted to review the changes, click Close once you are done reviewing. You will be returned to the Capacity Advisor - Edit Scenario screen.

To edit applied what-if actions

If you wish to disable changes, click the check boxes preceding the changes you want to disable. You can check either one step or a range of steps that have been grouped together. Then, click Disable. If you want to re-enable changes, click in the check boxes preceding the changes you want to re-enable. You can check either one step or a range of steps that have been grouped together. Then, click Enable. If you want to delete changes, click the check boxes preceding the changes that you want to delete. You can check either one step or a range of steps that have been grouped together. Then, click Delete. This will completely remove the selected actions from the scenario record.

Working with scenarios

91

IMPORTANT: Keep the change record clear of conflicting instructions and errors because errors prevent the scenario from evaluating any further change. Note that changes made to this screen are not applied until you Close the screen. This means that error messages resulting from conflicts introduced on the Undo/Edit screen are displayed on the Edit Scenario screen. Modifying resource utilization values For rows where this feature is available, you can change the scaling factors (multipliers) associated with a change. 1. 2. 3. Click the check box to the left of the row where you want to change the value. Change the value using the field in the column labeled Modifiable Values. Click Modify.

When you are done, click Close. You can come back to the this screen as many times as needed. You will be returned to the Capacity Advisor - Edit Scenario screen. The changes you disabled or deleted will no longer be in effect and those you re-enabled will be in effect again. You should be able to see the resulting modifications reflected in the data presented on the Edit Scenario System or Workload tab screens.
Related topic

Appendix F (page 163)

Deleting a scenario
Over time, as scenarios become irrelevant, removing them will reduce the list you have to search to find your scenarios. Prerequisites You must be logged in to Insight Dynamics. (See Accessing Capacity Advisor (page 55).) You must have created the scenario (see Creating a planning scenario (page 86).) or be the HP SIM administrator (see the HP SIM help by selecting HelpFor HP Systems Insight Manager from the top menu bar). If you are not on the Capacity Advisor tab: If the Capacity Advisor tab is visible, click the Capacity Advisor tab. If the Capacity Advisor tab is not visible, select OptimizeCapacity AdvisorView Scenarios... from the upper, top menu bar. The Capacity Advisor tab will open, with a list of scenarios. 2. The names of any scenarios you created, and thus can delete, will be displayed as links. If you are the administrator, you can delete any scenario. Click the radio button preceding the scenario you wish to delete. The row containing the scenario will be highlighted and the radio button will be filled in to indicate selection. 3. Select DeletePlanning Scenario from the Capacity Advisor tab menu bar. The Delete Scenario confirmation screen will be displayed, with the name of the scenario that will be deleted. 4. Confirm that this is the scenario you want to delete, then click the OK button. You will be returned to the VSE Management: Capacity Advisor screen.

1.

92

Procedures

Working with systems

Systems can represent physical hardware, Virtual Machines (VM), or Virtual Machine Hosts. They can be real systems from your current environment or What-If creations to represent new systems you are planning. You can also modify a system based on an existing system to represent planned configuration changes. IMPORTANT: For specific descriptions of each field or summary table on the user interface screens, click the help topic link on the software screen for the task. Most of the procedures described in this section are accessed from the System tab menus in the scenario editor. From the Capacity Advisor tab, double-click the scenario that you want to modify to open the editor. TIP: For lists of all menu options for Capacity Advisor features, see Menus & tabs in Capacity Advisor Help.

Creating a system
When developing a scenario to model future configurations, you can create one or more systems to represent system types that you are considering adding to the configuration. 1. On the System tab of the scenario editor, select What-If ActionCreate Systems... from the menu bar. The Edit Scenario - Create System screen displays. 2. Fill in the System Name with a unique name. You cannot change the name once the system is created. NOTE: You can add one or more system names at a time by separating each name with a comma (,) within the System Name field. IMPORTANT: While Capacity Advisor will inform you when the system name that you have designated is not unique (a system with the same name has been discovered by HP SIM), it cannot check names of systems that have not yet been discovered or created. Use names that you believe will not be used in the future (during the useful life of the scenario). 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Select the appropriate System Model and Hardware Processor Family in the System Hardware section. Select the appropriate server type. The screen repaints with the options appropriate to the selected server type. If you selected Standard Server in step 5, now select the appropriate operating system. If you selected VM Guest in step 5, now select a VM host. If you selected VM Host in step 5, now select a VM host platform. Modify the CPU Resources as appropriate. Modify the Memory Size as appropriate. Modify the network and disk I/O Capacity as appropriate. Optional. Modify Power Calibration. Click Apply to save the system definition and stay on the Create System screen to create more systems, or click OK to save the system definition and return to the Edit Scenario screen.

Working with systems

93

To return to a planning checklist: Consolidating server loads onto a virtual machine manually [p. 36]

Adding an existing system

As your environment changes, you may want to add an existing system to a scenario. 1. From the System tab of the scenario editor, select EditAdd Existing Systems... from the menu bar. The Edit Scenario - Add Existing Systems screen will be displayed. The systems with available data will be displayed in a list with check boxes beside them. Any systems licensed for Capacity Advisor will be named below the list. 2. If any of the systems you want to add to the scenario are not displayed on this page, you need to license them for Capacity Advisor (see the section Adding and applying licenses in HP Insight Dynamics 6.2 Getting Started Guide) and collect data on them (see Gathering data for Capacity Advisor (page 55)). If the systems you wish to add to the scenario are in the list of licensed systems without available Capacity Advisor data, collect data on them (see Gathering data for Capacity Advisor (page 55)) and continue with the next step. Click in the check boxes beside the systems you want to add to the scenario to select them. Click the OK button. The System tab of the Capacity Advisor - Edit Scenario screen will open. To return to a planning checklist: Consolidating server loads onto a virtual machine manually [p. 36]

3.

4. 5.

Editing a system
When constructing a scenario, it is frequently necessary to modify the characteristics of a system to reflect future changes to existing hardware or to reflect the characteristics of a planned system. 1. From the System tab of the scenario editor, select What-If ActionEdit System... from the menu bar. The Edit Scenario: Edit System screen displays in a new window. 2. Modify the system attributes as desired. These attributes can be changed: 3. System Hardware CPU Resources Memory Size I/O Capacity

Click the OK button. The System tab of the Capacity Advisor Edit Scenario screen displays.

To return to a planning checklist: Consolidating server loads onto a virtual machine manually [p. 36] Estimating the effect of adding processors [p. 51] Estimating the effect of moving processors [p. 51] Determining where to put a workload using automated solution finding

Changing VMs to be servers

This screen allows you to convert existing virtual machines to individual servers.

94

Procedures

Change VMs to server

1. 2. 3. 4. From the System tab of the scenario editor, select one or more VMs. Select What-If ActionChange VMs to be Servers from the menu bar. The Edit Scenario: Change VMs to be Servers screen displays. Change the Meter Scale, if desired. Change the Data Range if a different size of data collection is desired, and click OK to refresh the table display. TIP: A longer data collection period provides a better picture of activity on the system over time than shorter periods do. 5. 6. Change the Meter Representation if a different calculation is desired . Examine the table titled Systems to be modified:. If you wish to modify the CPU utilization to account for any change in virtualization overhead, you can enter a percentage under CPU virtualization overhead %. The default is 0% to represent no change. 7. Click OK to accept these changes. After clicking OK, you see an updated Edit Scenario page. The modified virtual machines now appear as Server under the System Type heading.

Changing servers to be VMs (manually)

This option provides a quick way to change a physical server into a virtual machine so that you can later simulate the movement of virtual machines among VM hosts.

Change servers to be VMs

For specific descriptions of each field on this screen, click the help topic link on the software screen for this task. 1. 2. 3. 4. From the System tab of the scenario editor, select one or more servers. Select What-If ActionChange Servers to be VMs from the menu bar. The Edit Scenario: Change Servers to be VMs screen displays. Change the Meter Scale, if desired. Change the Data Range if a different size of data collection is desired, and click OK to refresh the table display. TIP: A longer data collection period provides a better picture of activity on the system over time than shorter periods do. 5. 6. Change the Meter Representation if a different calculation is desired . Examine the table titled Systems to be modified:. If you want to modify the CPU utilization to account for any change in virtualization overhead, you can enter a percentage under CPU virtualization overhead %. The default is 0% to represent no change. On entering a new value for CPU virtualization overhead, you must click Refresh to update the table titled To: (Selected VM Host) with the new values. 7. Optional. Change the headroom calculation. You must click Refresh to update the server destination table with the new values.

Working with systems

95

8.

Within the table titled To: (Selected VM Host), select a destination VM host for the previously selected systems. Server presentation: The table entries are ordered by headroom fitness as determined by Capacity Advisor, and Capacity Advisor selects the top selection by default. Examine the headroom rating and the utilization meters for each prospective host to determine which host best fits your goals for headroom fitness and optimal utilization. (See Headroom (page 25) for a discussion of this concept.)

9.

Click OK to accept these changes. Unknowingly accepting unseen values: This can happen if you modify the CPU virtualization overhead % or headroom calculation after selecting the destination server, but then click OK without refreshing the destination table with the new values. The resulting change to the utilization values shown in the System tab view will differ from those seen in the previously shown destination table because the System tab will reflect the modified values. When modifying CPU virtualization overhead % or headroom, remember to click Refresh, and check the updated values shown in the utilization meters in the destination table. Once you have refreshed this table, select a server based on the new values. If you want the same server that you selected before changing the values, you must re-select that server to enable the OK button.

After clicking OK, you see an updated Edit Scenario page. The modified system(s) now appear with the VM guest type listed under System Type (for example, 'Integrity VM'). Additionally, the modified system(s) is/are listed under the selected destination server. To return to a planning checklist: Consolidating server loads onto a virtual machine manually [p. 36]

Assigning VM hosts to a VMware DRS cluster in a scenario

You can use Capacity Advisor to simulate the behavior of workloads and VMs that are members of a VMware Distributed Resource Scheduler (DRS) cluster. This conversion is meant to let you simulate VM hosts running VMware ESX servers. Once you have created one of these what-if cluster scenarios, you are able to do any of the following actions in this scenario: add other VM hosts to the cluster consolidate or load balance VMs in a cluster

In addition, you can run reports on clusters defined within a scenario.

Initially converting VM hosts to simulate a VMware DRS cluster

1. From the System tab of the scenario editor, click the check boxes for two or more ESX VM hosts that you want to convert to a DRS cluster. IMPORTANT: If you want to see power metrics for the cluster, make sure that all VM hosts that you select have been calibrated (either automatically or manually) before adding them to a cluster. 2. Select What-If ActionConvert/Add to VMware DRS Cluster.... The Convert/Add to VMware DRS Cluster screen opens.

96

Procedures

3.

Type a unique name for identifying the cluster (required). IMPORTANT: While Capacity Advisor will inform you when the cluster name that you have designated is not unique (a cluster with the same name has been discovered by HP SIM), it cannot check names of clusters that have not yet been discovered or created. Use names that you believe will not be used in the future (during the useful life of the scenario).

4. 5.

Optional. Select HA (High Availability) Cluster. Click OK to save the cluster definition. The System tab screen refreshes. The previously selected VM hosts and their guests are now identified as members of a VMware DRS cluster in the system list.

Adding VM hosts to a converted cluster

1. From the System tab of the scenario editor, click the check boxes for one or more ESX VM hosts that you want to add to an existing DRS cluster AND click the existing DRS cluster or one VM host that is already a member of the desired cluster. IMPORTANT: If you want to see power metrics for the cluster, make sure that all VM hosts that you select have been calibrated (either automatically or manually) before adding them to a cluster. 2. 3. Select What-If ActionConvert/Add to VMware DRS Cluster.... The Convert/Add to VMware DRS Cluster screen opens. Confirm that all of the systems that you wanted to add to the cluster appear in the System Name(s) list. TIP: The System Name(s) field cannot be edited when adding systems to a cluster. If an error is made, Cancel out of the screen, and try again with your system selection. 4. 5. Optional. Select HA (High Availability) Cluster. Click OK to save the modified cluster definition. The System tab screen refreshes. The newly selected VM hosts and their guests are now identified as members of a VMware DRS cluster.

Removing a VM host from a VMware DRS cluster

1. 2. Select What-If ActionUndo/Edit/View Applied What-If Actions . Disable or Delete the row(s) containing the record of making the VM host(s) a member of a cluster. (See Undo/edit/review applied what-if actions in a scenario (page 91) for more information on using this screen.) Close the Undo/Edit/View Applied What-If Actions window to return to the updated System tab.

3.

Removing a VMware DRS cluster from a scenario

1. 2. Select What-If ActionUndo/Edit/View Applied What-If Actions . Disable or Delete the row(s) containing the record of creating the cluster and any rows that record making the VM host(s) and the VM guests members of the cluster. (See Undo/edit/review applied what-if actions in a scenario (page 91) for more information on using this screen.) Close the Undo/Edit/View Applied What-If Actions window to return to the updated System tab.
Working with systems 97

3.

Moving a virtual machine

Moving Virtual Machines (VMs) among VM hosts allows you to redistribute virtual equivalents of existing systems across physical servers. Capacity Advisor automatically takes into account use of dynamic memory by a virtual machine. NOTE: Performance for a virtual machine is usually calculated using the performance index calculated for its VM host. However, when a virtual machine is moved from one VM host to another having a different clock speed, performance is calculated using a combination of clock speed and the performance index of the destination host. To get the best possible measure, collect the desired amount of data from a VM before moving it to host of a differing CPU clock speed. 1. 2. 3. 4. From the System tab in the scenario editor, click the check box preceding the virtual system(s) that you want to move. Select What-if ActionMove Virtual Machines... from the menu bar. The Edit Scenario: Move Virtual Machines screen displays. Change the Meter Scale, if desired. Change the Data Range if a different size of data collection is desired, and click OK to refresh the table display. TIP: A longer data collection period provides a better picture of activity on the system over time than shorter periods do. 5. 6. 7. 8. Change the Meter Representation if a different calculation is desired . The first table presents the virtual machines selected for the move. Optional. Change the headroom calculation. You must click Refresh to update the server destination table with the new values. Within the table titled To: (Selected VM Host), select a destination VM host for the previously selected systems. The OK button becomes enabled for use. Server presentation: The table entries are ordered by headroom fitness as determined by Capacity Advisor, and Capacity Advisor selects the top selection by default. Examine the headroom rating and the utilization meters for each prospective host to determine which host best fits your goals for headroom fitness and optimal utilization. 9. Click OK to accept these changes. Unknowingly accepting unseen values: This can happen if you modify the headroom calculation after selecting the destination server, but then click OK without refreshing the destination table with the new values. The resulting change to the utilization values shown in the System tab view will differ from those seen in the previously shown destination table because the System tab will reflect the modified values. When modifying headroom, remember to click Refresh, and check the updated values shown in the utilization meters in the destination table. Once you have refreshed this table, select a server based on the new values. If you want the same server that you selected before changing the values, you must re-select that server to enable the OK button. The System tab of the Edit Scenario screen opens showing the new virtual machine relationships.
98 Procedures

Removing a system
As your scenarios evolve, you might need to remove systems from a scenario to represent planned or actual changes. 1. 2. 3. From the System tab of the scenario editor, click in the check boxes beside the systems that you want to remove from the scenario. Select EditRemove Systems... from the menu bar. A confirmation screen listing the systems you are removing will be presented. Click the OK button. You will be returned to the Capacity Advisor - Edit Scenario screen with the systems you selected removed.

Editing network and disk I/O capacity

Use the Edit Network and Disk I/O Capacity page to set the upper bound value of network and disk I/O capacity for the selected set of systems. Setting this upper bound creates the maximum capacity value for such items as the network and disk I/O utilization graphs shown for the systems, the graphs and values shown in a profile viewer, and the HP Smart Solver calculations. Further, when using Capacity Advisor, the currently set upper bound values here are propagated as the upper bound values for the systems when a scenario containing the systems are created.

Getting there
1. From the Virtualization Manager Visualization view, select a compartment or sub-compartment for a system for which you want to edit its network I/O and disk I/O capacity. From the Virtualization Manager Configure menu, select Edit Network and Disk I/O Capacity....

2.

The Edit Network and Disk I/O Capacity screen displays. TIP: This feature can also be accessed from profile viewers opened from the Visualization view.

Setting the upper bound values

1. Select to use the maximum observed network and disk I/O readings Or Manually specify the network and disk I/O capacity values a. b. Enter a value for network I/O in Mb/s. Enter a value for disk I/O in MB/s. NOTE: If desired, you can set the manual maximum value to be greater than the observed maximum. The designated values are used to populate the Selected Systems table and are applied elsewhere by Capacity Advisor. 2. Select Apply or OK to apply and preserve your changes, respectively.

Working with systems

99

Working with workloads

Introduction
Workloads represent applications running on systems. IMPORTANT: For specific descriptions of each field or summary table on the user interface screens, click the help topic link on the software screen for the task. All of the procedures described in this section can be accessed from the Workload tab menus in the scenario editor. From the Capacity Advisor tab, double-click the scenario that you want to modify to open the editor. TIP: For lists of all menu options for Capacity Advisor features, see Menus & tabs in Capacity Advisor Help.

Creating a workload
When you are modeling future configurations, you can create new workloads to represent applications that will be added. The workload can be based on either a static baseline or profile data from an existing workload. 1. To preselect the system on which to run the workload: From the System tab in the scenario editor, click the check box preceding the system on which you want to run the workload(s). Select What-If ActionCreate Workloads... from the menu bar. The Edit Scenario: Create Workloads screen opens. 3. Fill in the Workload Name(s) with a unique name. IMPORTANT: While Capacity Advisor will inform you when the workload name that you have designated is not unique (a workload with the same name has been discovered by HP SIM), it cannot check names of workloads that have not yet been discovered or created. Use names that you believe will not be used in the future (during the useful life of the scenario). 4. 5. Optionally, add a detailed description of the workload(s) in the Workload Description field. a. If you intend to park the workload(s), confirm that the check box labeled Park/Unassign Workload is checked. Skip to step 7. b. If you previously selected a system, review the associated information given for that system. Then skip to step 7. c. If you want to select a system, uncheck the Park/Unassign Workload check box, if needed, to enable system selection.

2.

100

Procedures

6.

Select a system on which to run the workload(s). NOTE: You can move the workload(s) later as needed.

7.

a.

b.

If you want to use collected data from a real workload in your computing environment to serve as the baseline information for the new workload(s), select Copy Profile. Copy Profile is enabled whether or not the workload is parked. If you want to supply static values, select Static Profile. Static Profile is disabled when a workload is parked. NOTE: Static values remain the same throughout scenario simulations unless modified by editing the workload attributes . Copied profile values can change with changes to the date range selected for the scenario because the data range determines the set of collected data to be used in a data-based scenario.

8.

Modify the values for each attribute in the selected profile, as desired. See Determining estimated utilization assumptions for a workload (page 125) for information about each requested attribute.

9.

Click the OK button to save the new workload(s) and return to the System or Workload tab where you started. The new workload(s) will be listed on the Workload tab or in association with the selected server on the System tab.

Editing a workload
When constructing a scenario, it is frequently necessary to modify the characteristics of a workload to reflect future changes in the application or in the users of the application. Use the Edit Workloads screen to make modifications to workload characteristics. There are two types of workloads: those that reflect current workloads on the system and those that are created for a scenario. While both can be edited, the characteristics that can be edited are different for each. Edit only one scenario at a time : Opening a new edit scenario session when another editing session is already open causes the loss of any unsaved changes in the previously opened session. If you were running an automated solution in your previous session, the automated calculations are immediately halted and no settings or results are saved. Procedure 5-84 To edit a workload 1. 2. 3. 4. If you are not on the Workload tab, click the Workload tab. The Workload tab will open, listing the workloads in the scenario. Click the check box preceding the name of the workload that you wish to edit. Select What-If ActionEdit Workloads... from the menu bar. The Edit Scenario: Edit Workload screen displays. If you are editing a workload that uses profile data, or you want to change the workload so that it will use profile data, modify those fields as appropriate. See Determining estimated utilization assumptions for a workload (page 125) for more information about the Copy Profile fields. If you are editing a workload that uses a static profile created for this scenario, or you want to change the workload that it will use static information, modify those fields as appropriate.
Working with workloads 101

5.

6.

See Determining estimated utilization assumptions for a workload (page 125) for more information about the Static Profile fields. Click OK to save changes. The Workload tab of the Capacity Advisor: Edit Scenario screen opens.

To return to a planning checklist: Consolidating server loads onto a virtual machine manually [p. 36] Determining where to put a workload using automated solution finding

Moving a workload
Moving workloads allows you to redistribute workloads, including virtual equivalents of existing systems, across physical servers. While moving workloads, you can compensate for differences among systems by adjusting platform multiplier values. These values can be determined by running applications on systems representing the hardware and software configurations being used.

Move considerations
In considering where to move a workload, think about the following aspects of a move: architecture is the workload moving from one architecture to a system with the same architecture? If the workload may move to a system with a different architecture, what are the implications of architectural differences? operating system is the workload moving from one operating system to a system with the same OS? If the workload may move to a system with a different OS, what are the implications? CPU speed is the workload moving to a system with the same or faster CPU speed? CPU utilization what is the current CPU utilization of the workload? what is the projected growth rate of the workload available memory is the available memory on the new system the same or greater than that on the system where the workload currently resides? TIP: To obtain the most meaningful feedback about the proposed move of workloads, it is important to size the VM guest where the workload resides so that it is appropriate to the size of the workload. This should be done prior to using the Move Workload menu option. NOTE: When measuring CPU utilization of virtual machines, it is possible for the reported utilization to be greater than the number of virtual CPU cores (vCPU cores) associated with the virtual machine. While the number of virtual machine host threads allocated to the process for the virtual machine is restricted to the number of virtual CPU cores, the virtual machine host threads used to implement virtual hardware, such as I/O cards, are not restricted. Under certain load conditions, this can result in CPU utilization of more than 100% being reported for a virtual machine. Procedure 5-85 To move a workload 1. 2. 3. 4. If you are not on the Workload tab, click the Workload tab. Click the check box preceding the workload(s) that you wish to move. Select What-if ActionMove Workloads... from the menu bar. The Edit Scenario: Move Workloads screen displays. Change the Meter Scale, if desired.

102

Procedures

5.

Change the Data Range if a different size of data collection is desired, and click OK to refresh the table display. TIP: A longer data collection period provides a better picture of activity on the system over time than shorter periods do.

6. 7. 8.

Change the Meter Representation if a different calculation is desired . The first table presents the workloads selected for the move. If the original system that the workload resided on differs significantly from the intended destination system on which you intend to run the workload, use the memory platform multiplier to adjust for differences between the two systems. On entering a new value for the memory platform multiplier, you must click Refresh to update the table titled Select Destination System: with the new values. 9. Optional. Change the headroom calculation. You must click Refresh to update the server destination table with the new values. 10. In the next table, labeled Select Destination System, take a few moments to mouse over various entries in the table and analyze the information presented. This table lists the possible destination systems available in this scenario, their current resource utilization information, and their headroom rating. 11. Select a system to be the new host for the workload. The OK button becomes enabled for use. Server presentation: The table entries are ordered by headroom fitness as determined by Capacity Advisor, and Capacity Advisor selects the top selection by default. Examine the headroom rating and the utilization meters for each prospective host to determine which host best fits your goals for headroom fitness and optimal utilization. Not seeing a host that you expect to be in the destination list?: Capacity Advisor allows only one workload to be assigned to a VM host in a scenario. Therefore, VM hosts that already have a workload do not appear as destination candidates in this screen. 12. Click OK to accept these changes. Unknowingly accepting unseen values: This can happen if you modify the memory platform multiplier after selecting the destination server, but then click OK without refreshing the destination table with the new values. The resulting change to the utilization values shown in the Workload tab view will differ from those seen in the previously shown destination table because the Workload tab will reflect the modified values. When modifying the memory platform multiplier, remember to click Refresh, and check the updated values shown in the utilization meters in the destination table. Once you have refreshed this table, select a server based on the new values. If you want the same server that you selected before changing the values, you must re-select that server to enable the OK button. The Workload tab of the Edit Scenario screen opens showing the new workload relationships.

Working with workloads

103

Parking a workload
When constructing a scenario, it can be desirable to temporarily remove the effects of workloads to reflect potential changes, without permanently removing the workloads. This is referred to as parking the workloads. 1. 2. If you are not on the Workload tab, click the Workload tab. Click the check boxes preceding the names of the workloads you wish to park. Check marks will appear in the check boxes and the rows containing the workloads will be highlighted, to indicate selection. 3. 4. 5. Select What-If ActionPark Workloads... from the menu bar. The Edit Scenario - Park Workloads screen will be displayed. Confirm that the workloads listed under Workload Name hosted on the systems listed under Contained In are the workloads you wish to park. Click the OK button. The Workload tab of the Capacity Advisor - Edit Scenario screen will open.

Deleting a workload
When working with a scenario, it is sometimes desirable to remove workloads to reflect potential changes. 1. 2. If you are not on the Workload tab, click the Workload tab. Click the check boxes preceding the names of the workloads you wish to remove. Check marks will appear in the check boxes and the rows containing the workloads will be highlighted to indicate selection. 3. 4. 5. Select What-If ActionDelete Workloads... from the menu bar. The Edit Scenario - Delete Workloads screen will be displayed. Confirm that the workloads listed under Workload Name hosted on the systems listed under Contained In are the workloads you wish to delete. Click the OK button. The Workload tab of the Capacity Advisor - Edit Scenario screen will open.

Working with power

When you are calibrating power data settings, you specify the following: how power metrics should be displayed for graphs, meters, and reports how the power estimation should be calibrated: manually (you specify idle/maximum watt usage) automatically (using power and CPU data obtained from HP Insight Control power management (IPM) and HP Integrated Lights-Out (iLO) none (no power metrics are displayed) Power settings can be calibrated for actual systems from within HP Insight Virtualization Manager software and for simulated systems from within a Capacity Advisor scenario. These two areas are discussed in the sections below.

104

Procedures

TIP: The various power calibration screens look similar to one another, but you can tell that you are within a scenario rather than interacting with the actual system when the screen title includes the words Edit Scenario:. IMPORTANT: For specific descriptions of each field or summary table on the user interface screens, click the help topic link on the software screen for the task. TIP: For lists of all menu options for Capacity Advisor features, see Menus & tabs in Capacity Advisor Help.

Calibrating power within Virtualization Manager

This screen allows you to directly calibrate the power settings for managed systems. You can specify the source data for the power metrics that are stored on the system and displayed in the profile viewers available from the power meter displays in Virtualization Manager. Collected power data is also viewable in historic resource utilization reports. All power calibration options (manual, automatic, none) are available from Virtualization Manager. The resulting calculated metrics are viewable in the power measurements and graphs in Virtualization Manager. HP Insight Control power management and iLO If you choose to use power data from IPM , you will be interacting with IPM and iLO on the system itself. Therefore, you will need appropriate authorizations for the target systems. For more information on IPM and iLO, see following Internet locations: IPM (HP Insight Control power management) iLO (HP Integrated Lights-Out)

Prerequisites
You will need VSE All Tools permissions on the managed systems where you want to calibrate power. (See Accessing Capacity Advisor (page 55).) Procedure 5-88 Open the Visualization tab in Virtualization Manager 1. 2. Start Virtualization Manager. (ToolsVirtualization Manager...) The Visualization tab opens. View the list of systems in the display.

Calibrating a single system

There are multiple paths to edit the power settings for a single system: On the Visualization tab, select the check box to the left of the desired physical system, and select ConfigureCalibrate Power (All Selected Systems) on the Virtualization Manager menu bar. From the profile viewer for a specific system, click the Calibrate Power link. TIP: Click the power meter on a physical system shown on the Visualization tab to view its power information and to access the power profile viewer for that system. Procedure 5-89 Selecting a calibration option for a single system 1. 2. Review the current configuration shown in the summary area. Click the radio button to the left of the desired calibration option.
Working with power 105

3.

Supply values for idle and maximum power usage when manual calibration is selected. (See Power calibration calculations (page 129) for assistance in determining valid values for particular systems.) Click the Calibrate link. Results are posted in the Last Attempted Auto-Calibration table. If an error is indicated, read the Troubleshooting and Notes column for help on fixing the error.

Procedure 5-90 Calibrating HP Insight Control power management (IPM)

Procedure 5-91 Clearing current power management calibration values Click the Clear Calibration Data link. Calibration values are deleted. Results are posted in the Last Attempted Auto-Calibration table. If an error is indicated, read the Troubleshooting and Notes column for help on fixing the error. Procedure 5-92 Updating iLO data and calibration Click the Collect iLO Data link. The latest power usage data for this system is obtained and used to update the calibration for this system. Results are posted in the Last Attempted Auto-Calibration table. If an error is indicated, read the Troubleshooting and Notes column for help on fixing the error. Procedure 5-93 Configuring power management 1. 2. Examine the Power Management Plug-in Configuration table. In order of presentation, configure or correct each step listed in the table, as needed. a. Look at the icon in the Status column. If the status icon shows , then the step is working correctly. , then this step is not working correctly. , indicates waiting for a previous step to complete successfully. b. Fix errors in the order that they appear in the table. Use the information in the Notes column to determine what you need to do. Use the links in the Help column to resolve the problem(s) for that step.

3.

When all the icons show a green status, select Apply or OK to complete the power calibration for the selected system .

106

Procedures

Known problem: Collecting an iLO license: One of the steps in the checklist is to collect the iLO license. The following are known issues with this step: You must be able to ping the iLO from the CMS using only the system name (not the fully qualified domain name). The HP SIM License Manager uses the system name, not the fully qualified domain name, regardless of system settings. Systems in the same DNS zone as the CMS will work fine. Systems in a different DNS zone will need to have the DNS suffix for the managed nodes iLO added to the IP configuration of the CMS. You must be able to access the iLO via SSH from the CMS. The License Manager collects iLO licenses via SSH. There is a maximum of 2 concurrent SSH sessions for iLO. iLO SSH sessions may be abandoned and not reclaimed. This causes the iLO SSH to deny new connections, and the License Manager iLO license collection to fail. If this occurs, reset the iLO (that is, use the reset button at the bottom of the iLO diagnostics page in the iLO web GUI).

Calibrating multiple systems at once

On the Visualization tab, select the check boxes to the left of the desired systems, and select ConfigureCalibrate Power (All Selected Systems) on the Virtualization Manager menu bar. Procedure 5-94 Selecting a calibration option for multiple systems 1. 2. Click the radio button to the left of the desired calibration option. Supply values for idle and maximum power usage when manual calibration is selected. (See Power calibration calculations (page 129) for assistance in determining valid values for particular systems.) Review the list of systems in the Selected Systems table. Optional: Click the remove link to delete a system from the table and remove it from the calibration operation. Select Apply or OK to set the new calibration value for all systems remaining in the table .

Procedure 5-95 Confirming system selection 1. 2. 3.

Want to calibrate a single system at a time?: For each system in the Selected Systems table that you want to calibrate individually, click the details link to open the Calibrate Power (Single System) screen for that system. TIP: If you elect to individually calibrate some of the systems in a multiple listing, but not all, first calibrate the individual systems, and then remove them from the Selected Systems table. The systems remaining in the table list are those to which you can apply a different set of values at once using the control buttons on this screen.

Calibrating power within a scenario

This screen allows you to define the power calibration parameters for simulated systems in a scenario. These power settings specify whether or not to calibrate power, and if so, which settings to use for the calibration.

Working with power

107

This section describes the procedures for calibrating power for a single or for multiple systems within a planning scenario. Automatic power calibration options are not available from within scenarios as you are not interacting with real systems. You can choose to have no calibration in effect, or you can manually supply values. By calibrating power in a scenario, you can view estimated effect on power usage and costs due to changes that you make in the scenario. The resulting calculated metrics are viewable in Capacity Advisor reports and the profile viewer. NOTE: When a scenario is created, the initial idle and maximum power values of any real system that is being simulated in the scenario are taken from current measurements in HP Insight Virtualization Manager software. These values remain constant once the scenario is created, unless you manually change them using this screen. A later re-calibration performed in Virtualization Manager does not modify the power calibration of existing scenarios. What-if systems (for example, systems created by the Smart Solver that do not physically exist) can only be manually calibrated. For overview information, see Adjusting power (page 30).

Getting there
Power settings apply only within a selected scenario. Prerequisites You will need Capacity Advisor tool box permissions on the CMS or VSE All Tools permissions on the managed systems where you want to calibrate power. (See Access & authorizations.) Procedure 5-96 Open an existing scenario 1. 2. View the list of scenarios. (OptimizeCapacity AdvisorView Scenarios) Select a scenario to edit by double-clicking on the scenario name (or check the check box next to the desired scenario and select ModifyEdit Planning Scenario). The scenario opens on the Edit Scenario: System tab Choose physical systems only: Power settings can only be adjusted for entire physical systems.

Calibrating a single system

There are multiple paths to edit the power settings for a single system: On the System tab, click a Calibrate Power link in the Power Utilization column on the Edit Scenario system list table (This link appears when CPU information is available, but power has not yet been calibrated.) Also on the System tab, you can select the check box to the left of the desired system, and select EditCalibrate Power (All Selected Systems) on the Capacity Advisor menu bar. From the profile viewer for a specific system, click the Calibrate Power link. Procedure 5-97 Selecting a calibration option for a single system 1. 2. Review the current configuration shown in the summary area. Click the radio button to the left of the desired calibration option.

108

Procedures

3.

4.

Supply values for idle and maximum power usage when manual calibration is selected. (See Power calibration calculations (page 129) for assistance in determining valid values for particular systems.) Select Apply or OK .

Calibrating multiple systems at once

On the System tab, select the check boxes to the left of the desired systems, and select EditCalibrate Power (All Selected Systems) on the Capacity Advisor menu bar. Procedure 5-98 Selecting a calibration option for multiple systems 1. 2. Click the radio button to the left of the desired calibration option. Supply values for idle and maximum power usage when manual calibration is selected. (See for assistance in determining valid values for particular systems.) Review the list of systems in the Selected Systems table. Optional: Click the remove link to delete a system from the table and remove it from the calibration operation. Select Apply or OK to set the new calibration value for all systems remaining in the table .

Procedure 5-99 Confirming system selection 1. 2. 3.

Want to calibrate a single system at a time?: For each system in the Selected Systems table that you want to calibrate individually, click the details link to open the Calibrate Power (Single System) screen for that system. TIP: If you elect to individually calibrate some of the systems in a multiple listing, but not all, first calibrate the individual systems, and then remove them from the Selected Systems table. The systems remaining in the table list are those to which you can apply a different set of values at once using the control buttons on this screen.

Automating time-consuming simulations

The Smart Solver calculates where to place workloads among the pool of available servers to reduce the number of servers used or to balance workloads across the servers. The Smart Solver technology uses workload traces to quantify the demands placed by the workloads on the servers and uses the workload traces to calculate viable placement solutions subject to user-defined constraints, such as workload utilization limits and the specific resources that may be used. IMPORTANT: For specific descriptions of each field or summary table on the user interface screens, click the help topic link on the software screen for the task. TIP: For lists of all menu options for Capacity Advisor features, see Menus & tabs in Capacity Advisor Help.

Automated solution finding: System consolidation to VMs

This section describes the procedure for performing an automated system consolidation to virtual machines.

Automating time-consuming simulations

109

NOTE: A consolidation adheres to the existing utilization limits. For information on utilization limits, see Utilization limits (page 27).

Begin with a scenario

From the list of Capacity Advisor scenarios , select an existing scenario to edit by either: clicking the linked name of an existing scenario that includes the workloads and servers you wish to modify, or checking the box next to an existing scenario that includes the workloads and servers you wish to modify. Then, from the menu select ModifyEdit Planning Scenario A new window opens to display the Edit Scenario: System tab screen. (If you have not yet created a suitable scenario, you will need to do so (see Creating a planning scenario (page 86)).)

Choose the systems to consolidate

Take the following actions on the Edit Scenario System tab. 1. Using the check boxes, select the systems that you plan to consolidate. NOTE: Though the HP Smart Solver is now aware of what-if VMware DRS clusters, solutions can be presented that do not account for other cluster relationships (such as a Serviceguard cluster). To preserve these cluster relationships in a simulation, create a scenario that includes all members (hosts and guests) from the cluster that you want to represent in the scenario. TIP: Before running the HP Smart Solver automation, ensure that your source systems do not violate any of the utilization limits set for those systems. (See (and mouse over) the utilization meters on the System tab of the scenario editor to check this information.) When systems violate utilization limits, the Smart Solver solutions are unlikely to be useful. Understanding the consolidation task (page 36) illustrates this situation. 2. Select What-If ActionAutomated System Consolidation to VM....

The window displays step 1 of 3 for Automated System Consolidation to VMs.

Step 1 of 3: Define the destination system(s) and attributes

1. 2. Change the Meter Style, if desired. Change the Data Range if a different selection of data is desired, and click OK to refresh the table display. TIP: Longer intervals provide a better picture of activity on the system over time than shorter intervals do. 3. 4. Change the Meter Representation if a different calculation is desired . Select a destination host option.

110

Procedures

5.

Depending on your host destination type, you will need to do one or both of the following steps. View the list of potential hosts included in the scenario in the Select the existing hardware... table. Check the box(es) for the system(s) to be used as the VM host(s). TIP: You may need to expand the gray bar to view the table entries.

If you select to use a host template, a template editor will open. Fill in the fields as desired. (See Host Template Fields in Capacity Advisor Help for attribute descriptions.) Any new host systems will use this configuration.

6.

Change solution constraints, if desired. NOTE: Solution constraints include whether or not to load balance a solution, provide a virtualization CPU overhead percentage, or change the maximum invalid data percentage allowed.

7.

Click OK. Step 2 of 3 displays.

Step 2 of 3: Set level of effort for Smart Solver calculation

1. Select a level of effort. Higher levels of effort require more time and often produce better results. NOTE: A message appearing near the control buttons at the bottom of the screen informs you of the amount of memory needed to generate the solution and the amount of memory available. If the memory available is insufficient to generate the solution, you will need to correct this situation before continuing to run the Smart Solver. 2. Check the Smart Solver Configuration Values and Scenario Contents Summary Information to confirm that they match your expectations. To change values, click Previous to return to the screen where the simulation values are set (step 1 of 3). 3. Once you are satisfied with the simulation values, click OK to begin the calculations. The Smart Solver runs for a time, and then the results display.

Step 3 of 3: View Smart Solver solutions

1. 2. Review the proposed solution(s). Given these results, you can Press Cancel to prevent these changes from being saved. Press Save to write these changes to the scenario with which you started the consolidation. Press Save As... to save these changes under a new scenario name. Press Return to Step 1 to edit the consolidation attributes and constraints prior to running the Smart Solver again.

Automating time-consuming simulations

111

Insufficient resources on the VM host: Smart Solver informs you when the destination VM host has insufficient resources to host all of the consolidated systems. This can happen when the selected systems do not have enough resource capacity to place all of the workloads or when workloads cannot be placed on any of the selected systems. The Smart Solver will try to place as many workloads as will fit, giving you a partial solution. When this occurs, you can click Return to Step 1 to adjust the attributes and constraints for the VM host, or Cancel and return to the scenario editor. From there, adjust the resources on your destination VM host or add another VM host to the automated consolidation simulation. For more information on this behavior, see When available systems lack sufficient capacity (page 180). Results: Automated consolidation to VMs
Expected results

The solutions show the systems converted to VM guests on VM hosts. These VM hosts are either existing VM hosts, what-if generated template VM hosts, or a combination, depending on what destinations you selected. When a combination of VM hosts are chosen, the placement of VM guests goes first to existing VM hosts, and then to the template VM hosts. Further, as part of the input parameters, you can select to load balance the resulting VM hosts. This load balancing occurs after and only amongst the target VM hosts that are required for the consolidation solution. In other words, if the consolidation solution results in any VM hosts being unused (and therefore, not required in the solution), the unused systems will not be involved in the load balancing. Only the required systems in the solution are involved in the load balancing. The resulting solution is the configuration requiring the fewest number of systems with the minimal requirement for headroom, while taking into consideration resource utilization and utilization limits. Resources The placement of VM guests takes into consideration CPU, memory, network I/O, and disk I/O capacity, and utilization limits. If load balancing (balancing resource utilization across the resulting systems) was selected, the VM guests were load balanced across the systems that had 1 or more VM guests. Resource capacity. Workloads that specify utilization limits for a metric (for example, memory or disk I/O) can only be placed on resources that define a capacity for the corresponding metric. In other words, if you specified that a workload never exceed 100% memory utilization, that workload can only be placed on a system for which total memory capacity is known. Utilization limits. Every workload selected must have at least one utilization limit applied before using the Smart Solver. This can be any type of utilization limit, including the default global utilization limit. Headroom rating The headroom ranking shows the amount of available resource above the existing resource utilization that will exist for the resulting solution in the simulation. Among the solutions that require the same target systems, the solution with the tightest fit is shown.
Possible anomalies in the results

Fewer systems shown. The Smart Solver solution can contain fewer VM host targets than were originally selected. This occurs when the workloads fit on fewer systems than originally selected. For example, if systems A, B, and C are selected as target VM hosts, but all the workloads can fit into VM hosts A and B, then only VM hosts A and B are shown in the solution. Systems involved in load balancing. When load balancing is performed, the loads are balanced only across the resulting systems in the solution. For example, if only VM hosts A and B are used (and VM host C is not), then load balancing is performed only across VM hosts A and B. VM host C is not included for the load balancing calculation.
112 Procedures

Headroom rating shows zero (0) stars. The headroom rating shows zero stars even though it appears that there is sufficient room on the VM host for the workloads. This happens whenever one or more of the original servers violates a utilization limit prior to the Smart Solver being run. Before running the Smart Solver, ensure that your source systems are not already violating a utilization limit. To return to a planning checklist: Consolidating server loads onto a virtual machine using automated solution finding [p. 47]

Automated solution finding: Load balance of servers or VM hosts

This section describes the procedure for automating the search for an optimal load-balanced set of servers. NOTE: The solution will adhere to the existing utilization limits. For information on utilization limits, see Utilization limits (page 27).

Begin with a scenario

From the list of Capacity Advisor scenarios , select an existing scenario to edit by either: clicking the linked name of an existing scenario that includes the workloads and servers you wish to modify, or checking the box next to an existing scenario that includes the workloads and servers you wish to modify. Then, from the menu select ModifyEdit Planning Scenario . A new window opens to display the Edit Scenario: System tab screen. (If you have not yet created a suitable scenario, you will need to do so (see Creating a planning scenario (page 86)).)

Choose the VM hosts or servers to load-balance

Take the following actions on the Edit Scenario System Tab. 1. Using the check boxes, select the VM hosts or servers that you plan to load-balance. NOTE: Though the HP Smart Solver is now aware of what-if VMware DRS clusters, solutions can be presented that do not account for other cluster relationships (such as a Serviceguard cluster). To preserve these cluster relationships in a simulation, create a scenario that includes all members (hosts and guests) from the cluster that you want to represent in the scenario. TIP: Before running the HP Smart Solver automation, ensure that your source systems do not violate any of the utilization limits set for those systems. (See (and mouse over) the utilization meters on the System tab of the scenario editor to check this information.) When systems violate utilization limits, the Smart Solver solutions are unlikely to be useful. Understanding the consolidation task (page 36) illustrates this situation. 2. Select What-If ActionAutomated Load Balance of VM Hosts....

The window displays step 1 of 3 for Automated Load Balance of VM Hosts.... If you want to load-balance servers, select What-If ActionAutomated Load Balance of Servers...

Automating time-consuming simulations

113

Step 1 of 3: Define the solution constraints

1. 2. Change the Meter Style, if desired. Change the Data Range if a different interval is desired, and click OK to refresh the table display. TIP: Longer intervals provide a better picture of activity on the system over time than shorter intervals do. 3. 4. Change the Meter Representation if a different calculation is desired . Change solution constraints, if desired. NOTE: 5. The solution constraint is to change the maximum invalid data percentage allowed.

Click OK. Step 2 of 3 displays.

Step 2 of 3: Set level of effort for Smart Solver calculation

1. Select a level of effort. Higher levels of effort require more time and often produce better results. NOTE: A message appearing near the control buttons at the bottom of the screen informs you of the amount of memory needed to generate the solution and the amount of memory available. If the memory available is insufficient to generate the solution, you will need to correct this situation before continuing to run the Smart Solver. 2. Check the Smart Solver Configuration Values and Scenario Contents Summary Information to confirm that they match your expectations. To change values, click Previous to return to the screen where the simulation values are set (step 1 of 3). 3. Once you are satisfied with the simulation values, click OK to begin the calculations. The Smart Solver runs for a time, and then the results display.

Step 3 of 3: View Smart Solver solutions

1. 2. Review the proposed solution(s). Given these results, you can Press Cancel to prevent these changes from being saved. Press Save to write these changes to the scenario with which you started the load balancing. Press Save As... to save these changes under a new scenario name. Press Return to Step 1 to edit the constraints prior to running the Smart Solver again.

Results: Automated load balancing of servers or VM hosts

Expected results

The solutions show workloads that are balanced across the selected existing servers or VM hosts. Load balancing is based upon CPU, memory, network I/O, and disk I/O capacity, utilization limits, and headroom, where the goal is to distribute workloads so that each system has comparable headroom and therefore, similar headroom rating.

114

Procedures

Resource capacity. Workloads that specify utilization limits for a metric (for example, memory or disk I/O) can only be placed on resources that define a capacity for the corresponding metric. In other words, if you specified that a workload never exceed 100% memory utilization, that workload can only be placed on a system for which total memory capacity is known. Utilization limits. Every workload selected must have at least one utilization limit applied before using the Smart Solver. This can be any type of utilization limit, including the default global utilization limit. Headroom rating The headroom rating shows the amount of available resource above the existing resource utilization that will exist for the resulting solution in the simulation. Among the solutions that require the same target systems, the solution with the tightest fit is shown.
Possible anomalies in the results

The load balanced results appear unbalanced. The solution may not look balanced because smaller systems generally are assigned a smaller percentage of usage than larger systems, and very small systems may end up with no workloads at all. For example, a large 16 GB system at 87% memory usage has 2 GB of headroom, and a smaller 4 GB system at 87% has only 500 MB of headroom. Aiming for 87% usage on both systems would not yield a balanced solution. Instead, a balanced solution is to fill the larger system to 87% and fill the smaller system to only 50%. With this placement, workloads placed on either system will have the same amount of headroom to grow (2 GB). No apparent change from original configuration. The solution may be the same as the original scenario, and it looks as though no computation was performed. Actually, with the current attributes and constraints, the Smart Solver could not find a better solution than the current configuration of systems. This means that the current configuration is the current best solution. A message displayed in BLUE text indicates that the results are not an error (errors are displayed in RED text). No apparent change on one or more systems. The solution may show no change on one or more destination systems. Thus, it may appear that the Smart Solver did not include the server in its computations. In actuality, the Smart Solver determined that as part of the best solution, it was best to leave these target systems with their original configurations. Fewer systems shown. The Smart Solver solution can contain fewer destination servers than were originally selected. This occurs when the workloads fit on fewer servers than originally selected. For example, if servers A, B, and C are selected as destinations, but all the workloads can fit onto servers A and B, then only servers A and B are shown in the solution. Smaller systems appear unused. The solution may not display smaller systems, making it appear as if the smaller systems were not included in the Smart Solver computations. In actuality, when the Smart Solver attempts to place the workloads on target systems, it accounts for the robustness of those systems. If the workloads fit on larger, more robust systems and the smaller systems go unused, the solution will display only the larger, used systems. For example, if there are two large systems and two small systems, the solution may show only the two large systems, and load balancing will occur only on those two systems.

Automated solution finding: Workload stacking

HP Insight Capacity Advisor software can automate a workload stacking solution, where you set which servers (existing or newly created) you want the workloads to be on and set optimization parameters. HP Insight Capacity Advisor software then calculates and displays the best results for moving the workloads based upon the parameters that you provided. This allows you to see the predicted results of moving existing workloads onto selected physical systems. This section describes the procedures for automating workload stacking.

Automating time-consuming simulations

115

NOTE: Workload stacking adheres to existing utilization limits. For information on utilization limits, see Utilization limits (page 27).

Begin with a scenario

From the list of Capacity Advisor scenarios , select an existing scenario to edit by either: clicking the linked name of an existing scenario that includes the workloads and servers you wish to modify, or checking the box next to an existing scenario that includes the workloads and servers you wish to modify. Then, from the menu select ModifyEdit Planning Scenario A new window opens to display the Edit Scenario: Systems tab screen. Click the Workload tab to reveal the appropriate menus for editing workloads in a scenario. (If you have not yet created a suitable scenario, you will need to do so (see Creating a planning scenario (page 86)).)

Choose the workloads to stack

Take the following actions on the Edit Scenario Workload tab. The window will display the Capacity Advisor: Automated Workload Stacking screen with the selected workloads that you chose. 1. Using the check boxes, select the workloads that you plan to stack. NOTE: Though the HP Smart Solver is now aware of what-if VMware DRS clusters, solutions can be presented that do not account for other cluster relationships (such as a Serviceguard cluster). To preserve these cluster relationships in a simulation, create a scenario that includes all members (hosts and guests) from the cluster that you want to represent in the scenario. 2. From the Workload tab, select What-If ActionAutomated Workload Stacking.... Step 1 of 3 displays.

Step 1 of 3: Stack the specified workloads onto servers

1. 2. Change the Meter Style, if desired. Change the Data Range if a different interval is desired, and click OK to refresh the table display. TIP: Longer intervals provide a better picture of activity on the system over time than shorter intervals do. 3. 4. Change the Meter Representation if a different calculation is desired . Select a destination host option.

116

Procedures

5.

Depending on your host destination type, you will need to do one or both of the following steps. View the list of potential hosts included in the scenario in the Select the existing hardware... table. Check the box(es) for the system(s) to be used as the destination server(s). TIP: You may need to expand the gray bar to view the table entries.

If you select to use a host template, a template editor will open. Fill in the fields as desired. (See Host Template Fields in Capacity Advisor Help for attribute descriptions.) Any new host systems will use this configuration.

6.

Change solution constraints, if desired. NOTE: Solution constraints include whether or not to load balance a solution or change the maximum invalid data percentage allowed.

7.

Click OK. Step 2 of 3 displays.

Step 2 of 3: Set level of effort for Smart Solver calculation

1. Select a level of effort. Higher levels of effort require more time and often produce better results. NOTE: A message appearing near the control buttons at the bottom of the screen informs you of the amount of memory needed to generate the solution and the amount of memory available. If the memory available is insufficient to generate the solution, you will need to correct this situation before continuing to run the Smart Solver. 2. Check the Smart Solver Configuration Values and Scenario Contents Summary Information to confirm that they match your expectations. To change values, click Previous to return to the screen where the simulation values are set (step 1 of 3). 3. Once you are satisfied with the simulation values, click OK to begin the calculations. The Smart Solver runs for a time, and then the results display.

Step 3 of 3: View Smart Solver solutions

1. 2. Review the proposed solution(s). Given these results, you can Press Cancel to prevent these changes from being saved. Press Save to write these changes to the scenario with which you started the consolidation. Press Save As... to save these changes under a new scenario name. Press Return to Step 1 to edit the solution attributes and constraints prior to running the Smart Solver again.

Results: Automated workload stacking

Expected results

The solutions show the target systems with the selected workloads placed to require as few of the target systems as possible. The target systems are either existing servers, what-if servers
Automating time-consuming simulations 117

generated by template, or a combination, depending on what targets you selected. When a combination of servers are chosen, the placement of workloads goes first to existing servers and then to template-generated what-if servers Resource capacity. Workloads that specify utilization limits for a metric (for example, memory or disk I/O) can only be placed on resources that define a capacity for the corresponding metric. In other words, if you specified that a workload never exceed 100% memory utilization, that workload can only be placed on a system for which total memory capacity is known. Utilization limits. Every workload selected must have at least one utilization limit applied before using the Smart Solver. This can be any type of utilization limit, including the default global utilization limit. Headroom rating The headroom rating shows the amount of available resource above the existing resource utilization that will exist for the resulting solution in the simulation. Among the solutions that require the same target systems, the solution with the tightest fit is shown.
Possible anomalies in the results

Fewer systems shown. The Smart Solver solution can contain fewer destination servers than were originally selected. This occurs when the workloads fit on fewer servers than originally selected. For example, if servers A, B, and C are selected as destinations, but all the workloads can fit onto servers A and B, then only servers A and B are shown in the solution. Systems involved in load balancing. When load balancing is performed, the loads are balanced only across the resulting systems in the solution. For example, if only servers A and B are used (and server C is not), then load balancing is performed only across servers A and B. Server C is not included for the load balancing calculation. Return to a planning checklist: Determining where to put a workload using automated solution finding

Getting more detail

In addition to the solutions shown, you can do the following with the solution: 1. Expand the sections using the + box on the right-hand side of the desired section. 2. Mouse over the headroom ratings (the stars) to obtain more rating detail. 3. Save the solution under a different scenario name and then use the Scenario Comparison Report feature to compare the scenario differences.

118

Procedures

6 Using Capacity Advisor with HP Serviceguard

You are likely to use both Capacity Advisor and HP Serviceguard together in your data center. Serviceguard organizes systems or nodes into Serviceguard clusters, called SG Members in Capacity Advisor screens such as the scenario editor and profile viewers. In a Serviceguard environment, applications, services, and other entities are organized as packages that can move from one cluster node to another. TIP: In the HP SIM Version C.05.00 environment, Serviceguard clusters must have unique names. To avoid issues with duplicate names in your configuration, do one the following: Upgrade HP SIM Rename the clusters so they have unique names, deleting and recreating the Serviceguard packages Insight Dynamics components organize applications into workloads. Capacity Advisor collects utilization data for both systems and workloads. As a package fails over from one system to another, one of the workloads that Capacity Advisor is tracking might also move from one system to another. Capacity Advisor continues to monitor the workload on the old system until the workload is updated or edited to change the host name to that of the new host. Serviceguard packages and Capacity Advisor workloads are defined independently but can overlap. A Serviceguard workload is associated with one Serviceguard package in the Virtualization Manager and Capacity Advisor environment. With the latest release of Virtualization Manager, certain sub-operating system workloads are associated with Serviceguard packages. With this change, the capcollect command automatically concatenates the utilization of these Serviceguard-package workloads as they move from one cluster node to another. This significantly simplifies the use of Capacity Advisor in a Serviceguard environment. NOTE: Capacity Advisor assumes that Serviceguard-package workloads have been correctly defined so that there is a reasonably close 1:1 relationship between a Capacity Advisor workload and the Serviceguard-package workload. If multiple workloads are associated with the same Serviceguard package, Capacity Advisor results might be difficult to interpret. The first Serviceguard-package workload created on a system also has an OTHER workload associated with it for the system where it is running (for example, such a workload would have a name such as system_name.OTHER). The OTHER workload for systems with Serviceguard-package workloads in a Serviceguard cluster is associated with the system, not with the Serviceguard-package workloads. It does not move as the Serviceguard package running on the system moves to another system in the cluster. If all the Serviceguard-package workloads on a cluster member move to other nodes in the cluster, the OTHER workload for that system disappears from the display, and its utilization data becomes inaccessible until a Serviceguard-package workload is run on that system. For additional information about this capability, see the Virtualization Manager documentation; for more information about workloads, including the OTHER workload, see the Workloads topic in Virtualization Manager Help online.

Using Serviceguard to migrate HP Integrity VM guests

When Serviceguard manages a configuration that contains Integrity VM, failover of a virtual machine changes the UUID of the virtual machine. Several components of Insight Dynamics use the UUID as a search key, and they treat the single virtual machine as two distinct virtual machines, one with the previous UUID and one with the later UUID. Capacity Advisor treats this as two or more different system traces for a failed-over virtual machine. By default, these system workloads are named domainname, domainname.2, domainname.3, and so on. Each system
Using Serviceguard to migrate HP Integrity VM guests 119

workload has data for only when the virtual machine was running on a particular virtual machine host, and when the virtual machine fails over, the workload and its utilization data gathered from the previous host becomes inaccessible. Collecting utilization data from the virtual machine will gather utilization data for the newly created workload. This process affects only the system workload for the virtual machine. If monitored workloads are defined inside the virtual machine, their data is tracked correctly even when the virtual machine fails over to a new host. It is a good idea to create a workload inside any virtual machine that you intend to fail over using Serviceguard to ensure that the utilization data of the virtual machine is kept whole. TIP: Prevent data loss To prevent the loss of utilization data when migrating HP Integrity VM guests using Serviceguard, create a monitored workload for the processes of interest on the virtual machine. If there is no monitored workload, then utilization data for the failed-over system is split across two or more workloads. To prevent this, use the following procedure to treat these multiple workloads as a single workload: 1. Create a scenario and include the current virtual machine host. 2. Within that scenario, create a new workload and import data from the unrepresented workload. (Create two or three workloads, if needed.) 3. Place these new workloads in the current virtual machine. 4. When you edit or move one of these workloads, do the same with the others. The virtual machine containing the multiple workloads can be moved within the scenario and can give a complete picture of past utilization. The collection of these multiple workloads gives you a nearly uninterrupted view of the historical utilization for the virtual machine. Virtual machines that are moved between hosts using the hpvmmigrate command preserve their UUIDs and are not seen as two virtual machines.

Data collection in a Serviceguard environment

When you collect data from a virtual machine, capcollect is aware of the guest/host relationship and collects data from the virtual machine host as well as from the virtual machine. However, capcollect does not have knowledge of Serviceguard cluster membership, so when you collect data when viewing a Serviceguard workload, capcollect collects data only from the system you are viewing but not from any other systems in the Serviceguard cluster. If the workload has executed on any cluster members other than the one you are viewing since the last time data was collected on all the systems in the cluster, there will be gaps in the data profile for the Serviceguard workload for those times when the workload was executing on another cluster member. To fill these gaps, collect data manually from all nodes in the cluster.

120

Using Capacity Advisor with HP Serviceguard

7 Support and other resources

The following resources are available to help you learn how to best use HP Insight Capacity Advisor software or to help you if you encounter difficulties.

Contacting HP
Your comments and suggestions regarding product features will help us develop future versions of Capacity Advisor and the Insight Dynamics. Use the following e-mail address to send feedback directly to the Insight Dynamics development team: vse@hpuxweb.fc.hp.com NOTE: HP cannot provide product support through this e-mail address. To obtain product support, contact your HP Support Representative, your HP Services Representative, or your authorized HP reseller. For more information about support services, visit http://www.hp.com/ go/support. For other ways to contact HP, visit http://welcome.hp.com/country/us/en/ contact_us.html. We encourage your comments concerning this document. We are committed to providing documentation that meets your needs. Include the document title, manufacturing part number, and any comment, error found, or suggestion for improvement you have concerning this document. Also, please let us know what we did right so we can incorporate it into other documents.

New and changed information in this edition

A pointer to HP Integrity power calculators was incorrect in Appendix A of Edition 1. This is now corrected in Determining idle/max values for non-Blade servers [p. 129].

New and changed information in Edition 1

The following chapters and appendices have changed: Introduction Dependencies information updated. Procedures A few procedures have been updated to reflect changes in the user interface. These include Creating a consolidation candidates report (page 76) and Creating a peak summary report (page 76). A few procedures have been rewritten to provide improved clarity, including Creating a population report (page 77) and Moving a virtual machine (page 98). Units and Terminology Definition of how and when Capacity Advisor uses clock-speed added. Graphed data in Capacity Advisor reports (page 161) (new) Troubleshooting in Capacity Advisor Updates added to these sections: Data seems to be incorrect or lost, Data cannot be imported, When working with power

Related information
The latest versions of manuals, white papers, and the Support Matrix for HP Insight Dynamics suite can be downloaded from the HP Web at http://www.hp.com/go/insightdynamics/docs . For translations of these documents, see the HP Business Support Center (http:// h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp).
Contacting HP 121

Additional related information can be found in the following web sites: The HP VSE Managed Node Software Update web site (http://vsemgmt.external.hp.com/) HP Insight Dynamics VSE for Integrity servers (http://www.hp.com/go/vse) Reference Architectures for Application Deployment in Virtualized Environments (http:// www.hp.com/go/vsera) HP Systems Insight Manager software (http://www.hp.com/go/hpsim). Follow the Information Library link for access to white papers and other documents. The following book can be ordered from InformIT Network (http://www.informit.com/store/ product.aspx?isbn=0131855220): The HP Virtual Server Environment: Making the Adaptive Enterprise Vision a Reality in Your Datacenter, by Dan Herington and Bryan Jacquot, Prentice Hall, 2006.

Related technical papers

Greenberg, S., E. Mills, B. Tschudi, P. Rumsey, and B. Myatt. 2006. Best Practices for Data Centers: Results from Benchmarking 22 Data Centers, Proceedings of the 2006 ACEEE Summer Study on Energy Efficiency in Buildings. Hewlett-Packard Development Company, L.P.; 2010. Backing up and restoring HP Insight Software v6.00 Central Management System (Windows) at http://www.hp.com/go/ insightdynamics/docs. Hewlett-Packard Development Company, L.P.; April 2009. Exploring the Technology Behind Key Use Cases for HP Virtual Server Environment for Integrity Servers (PDF). Hewlett-Packard Development Company, L.P.; January 2009. HP Insight Capacity Advisor: a look under the hood (PDF). Hewlett-Packard Development Company, L.P.; April 2008. HP Insight Power Manager (PDF). Hewlett-Packard Development Company, LP; 2007. Hardware Consolidation with Integrity Virtual Machines (PDF). Hewlett-Packard Development Company, LP; 2007. HP Power Calculator Utility: a tool for estimating power requirements for HP ProLiant rack-mounted systems (PDF). Microsoft Corporation, 20072008. Performance Tuning Guidelines for Windows Server 2008. Microsoft Corporation, 2008. System Requirements for Virtual Server. VMware, Inc, 20062007. Resource Management Guide: ESX Server 3.0.1 and VirtualCenter 2.0.1.

122

Support and other resources

A Calculation assistance
See Related technical papers (page 122) for additional information.

Cost calculation
When creating utilization reports, Capacity Advisor gives you the ability to provide a value for calculating the cost per kilowatt-hour for selected servers in relation to the resource usage on those servers.

Cost per kilowatt-hour

Meaning This field represents the effective cost per kilowatt-hour that is paid for powering a server in a data center. It is a single value that assumes all servers under consideration are in the same data center and subject to the same charge. Default value None Where you might use this multiplier to create a power utilization report to create a scenario comparison report Example Assuming a server uses up to 20 kilowatts of power in a 1-hour period, and the cost charged to the data center per kilowatt-hour is 0.03, the cost of powering this one server for one hour would be 0.6. (You select the currency type relevant to the data center location.

Cooling calculation
The following section describes the multiplier that you can use to more accurately report in cooling costs within your data center.

Cooling multiplier
Meaning The ratio of the energy consumed by the air conditioning system to remove heat from the machine room to the energy consumed by the computers in that room. This ratio varies depending on the climate and the type of air conditioner used. It is generally a value between 0.3 and 1.6. Default Value .6 Where you might use this multiplier to create a power utilization report Example A value entered of 0.9 would mean that for every 10 kilowatt-hours of energy used by the computers, another 9 kilowatt-hours of energy are needed to cool the machine room.

Adjusting for platform changes

Capacity Advisor gives you the ability to provide a compensating factor, a scaling multiplier, to help Capacity Advisor to adjust memory when analyzing various scenario changes. The following are situations that you will want to adjust for when modifying a scenario because they can change resource utilization: A move from one system architecture to another system architecture can increase or decrease resource utilization. A move from a two-way to a one-way system can decrease resource utilization. A change in the application can increase or decrease resource utilization. (For information on how utilization is calculated for each resource, see Appendix C (page 153).)

Cost calculation

123

Memory multiplier
Meaning The ratio of change in memory utilization due to using a different platform (PA-RISC, Itanium, or Xeon, for example) to host workloads in the scenario than the platform originally assumed. If changes made in a scenario assume using the same platform, use the default multiplier. Default The default value is 1.0 (0% change) Where you might use this multiplier when moving workloads from one system architecture to another different system architecture in a scenario. Simple examples If you are moving from: PA-RISC to PA-RISC: keep the value as 1.0 (no change). PA-RISC to Itanium: because Itanium has 64-bit addressing, you may expect a decrease in memory utilization. Use .5 to arrive at a 50% decrease in utilization. Detailed example Assume that you benchmark your current application on a test machine that is similar to one that is currently running a production application. Assume that the test machine is a two-way 550 MHz PA-RISC system with a benchmark of 400 CPU seconds to complete, using 400 MB of RAM. Next, assume that you want to run a newer version of the application on a one-way, 1.6 GHz, HP Integrity Virtual Machine. Your new benchmark for this application is 100 CPU seconds to complete, using 600 MB of RAM. To compute the Memory Multiplier, calculate the ratio of the memory used for the new and the old platform: 600/400 = 1.5 The multiplier of 1.5 represents a 50% increase in memory utilization. This change is affected primarily by the move to Integrity and by getting a new version of the software application. In the case of memory utilization, factors like the number of CPU cores and the use of virtual machines have no effect unless the application tests for these factors and changes its behavior accordingly. To return to a planning checklist: Obtaining reports on current resource usage [p. 35]

Adjusting for change in a workload

The following sections describe the multipliers that you can use when you create new workloads. The multipliers help you to more accurately simulate changes in resource demand that are anticipated for workloads in a new data center configuration. TIP: These workload multipliers are also available to use when editing a simulation that represents a real workload in your data center. However, in this situation, you will achieve more accurate predictive results if you use forecasting growth rates to model anticipated change in an existing workload.

CPU workload multiplier

Meaning The relative change in CPU utilization desired when sizing an existing workload to better simulate a new workload in a scenario. CPU utilization by the new workload that you are creating can be made smaller, the same, or larger than that of the workload chosen as the baseline value. TIP: You do not need to account for different CPU clock speeds in this multiplier. Capacity Advisor will do this automatically. Default
124

The default value is 1.0 (no change).

Calculation assistance

Where you might use this multiplier when creating a workload or editing its attributes Examples To increase the CPU utilization of a new workload by 10% of the chosen baseline workload, enter a multiplier of 1.1. To decrease the CPU utilization of a new workload by 10% of the chosen baseline workload, enter a multiplier of .9.

Memory workload multiplier

Meaning The relative change in memory utilization when you are sizing a workload to simulate a new workload in a scenario. Memory utilization by the new workload that you are creating can be made smaller, the same, or larger than that of the workload chosen as the baseline value. TIP: To account for differences in platforms, use the Memory Multiplier.

Default The default value is 1.0. Where you might use this multiplier when creating a workload or editing its attributes Example To increase the memory utilization of a new workload by 20% of the chosen baseline workload, enter a multiplier of 1.2.

Network I/O workload multiplier

Meaning The relative change in network I/O utilization desired when sizing an existing workload to better simulate a new workload in a scenario. Network I/O can be made smaller, the same, or larger than that available for the workload chosen as the baseline value. Default The default value is 1.0 (no change). Where you might use this multiplier when creating a workload or editing its attributes Example To decrease the network I/O available to a new workload by 5% of that available to the chosen baseline workload, enter a multiplier of .95.

Disk I/O workload multiplier

Meaning The relative change in disk I/O utilization desired when sizing an existing workload to better simulate a new workload in a scenario. Disk I/O can be made smaller, the same, or larger than that available for the workload chosen as the baseline value. Default The default value is 1.0 (no change). Where you might use this multiplier when creating a workload or editing its attributes Example To increase the disk I/O available to a new workload by 10% of that available to the chosen baseline workload, enter a multiplier of 1.1.

Determining estimated utilization assumptions for a workload

Use these fields to set parameters for the workload's utilization of resources. When you use an existing workload profile (Copy Profile), you leverage data that already exists for a workload to examine alternatives. When you use a static workload profile (Static Profile), you create a profile based on independent values.

Adjusting for change in a workload

125

Table A-1 Modify existing profile settings to guide Estimated Utilization assumptions for workload
Area Copy Profile Attribute Select Workload Description Drop-down list of previously defined workloads from which to copy attributes for the new workload. Default: 1.0 See CPU workload multiplier (page 124) for more information. Memory Workload Multiplier Default: 1.0 See Memory workload multiplier (page 125) for more information. Network I/O Workload Multiplier Default: 1.0 See Network I/O workload multiplier (page 125) for more information. Disk I/O Workload Multiplier Default: 1.0 See Disk I/O workload multiplier (page 125) for more information. Offset Hours A positive or negative integer used to move an occurrence of peak activity to an alternate desired time. For example, suppose that peak activity in the profile data set occurred at 12:00 PM, but the desired peak time to be simulated is 9:00 AM. Setting the Offset Hours to 3 will move the peak time in the simulation from 12:00 PM to 9:00 AM. Default: 0

CPU Workload Multiplier

126

Calculation assistance

Table A-2 Define static estimates settings to guide Estimated Utilization assumptions for workload
Area Static Profile Attribute or action CPU Core Utilization Description Fractional or whole number of cores assumed to be used by the new workload on the assigned system. Default: 0.0 Memory assumed to be used by the new workload. Default: 0.0 Network bandwidth assumed to be used by the new workload. Default: 0.0 Disk bandwidth assumed to be used by the new workload. Default: 0.0 Clicking this button automatically fills in the following values from the Assigned System selection: System Model Model number for simulated system. Default: None Hardware Processor Family Processor name. Default: Itanium CPU Core Count Total number of cores on the simulated system. Default: 0 CPU Speed (GHz) Typical speed of the selected processor. Default: 0.0 These fields can also be filled in manually using values that you choose for the workload.

Memory Utilization (GB) Network I/O Utilization (Mb/s) Disk I/O Utilization (MB/s) Import from Assigned System

TIP: Providing estimates for a static profile The baseline that you enter should represent your best guess as to the load the particular application or workload will place on the system where you assign it. For example, if you have an application that you plan to assign to a 4-core system, and it typically uses two cores, you would enter 2.0 for CPU utilization. In the same way, you would enter a processor speed based on the system the workload originally ran on, and the amount of memory usually consumed by the workload on its previous system. Once you have a baseline workload that represents current behavior, you can create additional workloads with different values to experiment with variations in the CPU speed, available memory, and variable utilization limits to discover the behavior and performance of the workload in different scenarios.

Adjusting for virtualization changes

Capacity Advisor gives you the ability to provide compensating factors to help Capacity Advisor adjust needed resources when analyzing moving workloads from a physical system to a virtual machine on a VM host or from a virtual machine to a physical system. (For information on how utilization is calculated for each resource, see Appendix C (page 153).)

CPU Virtualization Overhead %

The following section presents the scaling factor that you can use to more accurately simulate the impact of changing a standalone system to a virtual machine, or a virtual machine into a standalone system. In these situations, CPU utilization can increase or decrease due to the overhead required for the virtual machine software. The CPU Virtualization Overhead % helps you to account for this in a scenario.

Adjusting for virtualization changes

127

CPU Virtualization Overhead %

Meaning The percent change in CPU utilization due to the overhead (or the absence of overhead) incurred by running an application in a virtual machine. When using virtual machines, the CPUs on the VM host do some of the work normally done by I/O cards. This work is the virtualization overhead accrued by running an application in a virtual machine. You can expect that applications that require significant I/O may experience a CPU virtualization overhead of 20%, and applications that do lots of calculations, but that require little I/O, would have an overhead of about 10%. When in doubt about I/O usage, use 15%. If your measured values in growth of CPU usage due to virtualization are greater than 20% for a particular workload or set of workloads, virtualization may not be the appropriate solution for that server. Default The default value is 0% (0% change). Where you might use this multiplier when changing a virtual machine to a server when changing a server to a virtual machine Example: Making a server become a virtual machine If your virtualization software would cause a 10% increase in CPU utilization due to the overhead for virtualization software, enter 10 for the CPU Virtualization Overhead % to account for the additional demand on the CPU core(s) when changing a server to a virtual machine. Example: Making a virtual machine become a server If your virtualization software requires a 10% increase in CPU utilization due to the overhead for virtualization software in the virtual machine, enter -10 for the CPU Virtualization Overhead % to account for the gain in CPU availability when changing a virtual machine to a server.

Hypervisor memory overhead

The following section presents the scaling factor that you can use to more accurately simulate the impact of including a hypervisor in your scenario. With the addition of a hypervisor, memory utilization increases due to the operation of the hypervisor. The Hypervisor Memory Overhead helps you to account for this in a scenario.

Hypervisor memory overhead

Meaning The amount of memory used by the virtualization platform to host virtual machines. The size of the memory overhead varies for each virtualization platform. Default Capacity Advisor calculates the value for you. Where you might use this percentage adjustment when moving workloads from one system platform to another different system platform in a scenario, where one or both system platforms are VM hosts.

Doing the math for hypervisor memory overhead

When you encounter this adjustment factor in altering a scenario, you have a choice to supply your own values. To help you with this, the following calculation examples are provided. HP Virtual Machine To compute the memory overhead of the hypervisor, use the following formula: 750 MB (.73 GB) + 7.5% of (Total Physical Memory 1 GB) Example: For a host with 32 GB of physical memory, the Hypervisor Memory Overhead will be: 750 MB (.73 GB) + 7.5% of 31 GB = .73 GB + 2.24 GB = 2.97 GB Source: Hardware Consolidation with Integrity Virtual Machines VMware ESX 3 To compute the memory overhead of the hypervisor, use the following formula:
128 Calculation assistance

Total Physical Memory (Total Physical Memory 284 MB)/1.078 This formula is derived from a least squares fit of observed values in test systems running VMware ESX. VMware documentation provides tables that outline how much memory overhead to expect based on the number of virtual CPUs and the amount of memory allocated to guests. For more information: Resource Management Guide on the VMware web site. VMware vSphere (ESX 4) To compute a conservative estimate of the memory overhead of the hypervisor, use a value from column 3 (2 VCPUS) in the table at this location: Overhead Memory on Virtual Machines For more information: vSphere Resource Management Guide on the VMware web site. Microsoft Hyper-V Microsoft recommends at least 512 MB (.5 GB) of physical memory be available for basic hypervisor features. In addition, for each guest, plan on 32 MB of overhead for the first GB of RAM allocated to a guest, and 8 MB for each additional GB of RAM allocated to a guest. To compute the memory overhead introduced by the hypervisor, use the following formula: 512 MB + (Number of Guests x (32 MB for first GB of guest RAM + 8 MB per additional GB of guest RAM)) Example: For a system hosting 2 guests with 2 GB of RAM, and 2 guests with 1 GB of RAM, the Hypervisor Memory Overhead is as follows: 512 MB + (32 MB + 8 MB) + (32 MB + 8MB) + 32 MB + 32 MB = 512 MB + 40 MB + 40 MB + 32 MB + 32 MB = 656 MB (.64 GB) Capacity Advisor assumes that a host will be filled with 1 GB guests when estimating the memory overhead for Hyper-V. This provides a generous estimate of memory overhead, as this configuration will maximize the size of the memory overhead. As a result, allowing Capacity Advisor to estimate the Hypervisor Memory Overhead for Hyper-V will leave extra headroom on Hyper-V hosts. Source: Performance Tuning Guidelines for Windows Server 2008 on the Windows Hardware Developer Central web site.

Power calibration calculations

Manual calibration uses CPU utilization data to estimate power utilization. Power utilization can be estimated by looking at CPU utilization because power utilization is closely related to CPU utilization. Further, the greater the CPU usage, the more power that is required to run and cool the system. Within the power calibration screens, you can specify the idle and maximum power usage values that you want to use for power usage calculations. The values can be determined by checking model and hardware configuration information. For your convenience, HP provides power calculators to aid you in this process (noted below). Each power calculator allows for different hardware configurations, such as amount of processors and memory, in order to yield the most accurate results. IMPORTANT: Values given by these power calculators are only estimates. Actual results can vary depending on application load, ambient temperature, and other factors.

Determining idle/max values for non-Blade servers

1. Locate the appropriate power calculator for a given model number.

Power calibration calculations

129

a.

Download the power calculators in spreadsheet form for older HP Proliant DL/ML/PL servers: http://h30099.www3.hp.com/configurator/powercalcs.asp. For newer Proliant systems...: Use the HP Power Advisor described at this web site: HP ProLiant Energy Efficient Solutions.

b.

Download the power calculators in spreadsheet form for HP Integrity servers (rx* and Superdome) by visiting HP Thermal Logic for Integrity servers web page: http://h20341.www2.hp.com/integrity/w1/en/ integrity-servers-thermal-logic.html#calculators

2. 3.

Configure the power calculator to match your desired hardware configuration. Determine idle/max values for manual calibration by locating the Total System Input Power Requirement. This value is always in Watts unless otherwise indicated. a. If a system utilization slider bar is present, the user can determine both the max and idle power requirements by adjusting the slider bar. 1) The idle power value is determined by adjusting the system utilization slider bar to 0% usage, and reading the value of Total System Input Power Requirement. 2) The max power value is determined by adjusting the system utilization slider bar to 100% usage, and reading the value of Total System Input Power Requirement. b. If no slider bar is present, then only the maximum power value can be determined. 1) Use the indicated Total System Input Power Requirement as the Max power requirement in the power calibration screen. 2) Leave the Idle power requirement blank in the power calibration screen. Capacity Advisor will automatically use 80% of the provided Max power requirement as the assumed idle value.

Determining idle/max values for Blade servers

An HP Blade System has a distributed power architecture, which makes it difficult to determine idle/max values for an individual blade. A single blades power usage depends on rack configuration and the power consumption of other blades within an enclosure. For HP Blades with iLO, it is recommended not to use Manual Calibration. Auto Calibration using actual observed power consumption of an individual blade (from HP Insight Control power management) is more accurate than manual calibration in this situation. However, manual idle/max values can still be determined by using the HP Blade System Sizer that can be downloaded from http://h71019.www7.hp.com/ActiveAnswers/cache/ 347628-0-0-0-121.html.

P-class HP Blades and HP Blade system sizer:

1. 2. 3. 4. Go to the HP Blade System Sizer, and start with an empty configuration. Specify the Rack and Power configuration. Select enclosure1, and specify the appropriate enclosure type. Select CTO if you are configuring for Integrity blades. Calculate idle value for a single blade: a. Configure a single bay with a blade matching your desired configuration. b. Specify utilization to 1%. c. Select Update Calculation and record the Total System Input Power as idleSingle. Calculate the max value for single blade:

5.

130

Calculation assistance

a. b. c. 6.

7.

8.

Configure a single bay with a blade matching your desired configuration. Specify utilization to 100%. Select Update Calculation and record the Total System Input Power Requirement as maxSingle. Calculate idle value for two blades: a. Configure two bays with blades matching your desired configuration. b. Specify utilization to 1%. c. Select Update Calculation, and record the Total System Input Power Requirement as idleMultiple. Calculate max value for two blades: a. Configure two bays with blades matching your desired configuration. b. Specify utilization to 100%. c. Select Update Calculation, and record the Total System Input Power Requirement as maxMultiple. Calculate the idle/max power values to use: a. Idle power requirement will be: idleMultiple idleSingle. b. Max power requirement will be: maxMultiple maxSingle.

C-class HP Blades and HP Blade system sizer:

1. 2. 3. Go to the HP Blade System Sizer, and start with an empty configuration. Specify Rack and Power configuration. Select enclosure1 and specify the appropriate enclosure type. Select CTO if you are configuring for Integrity blades. a. Configure a single bay with a blade matching your desired configuration . b. Specify utilization to 100%. Select enclosure2 and specify the appropriate enclosure type a. Configure two bays with blades matching your desired configuration. b. Specify utilization to 100%. Select Update Calculation. Calculate idle power values to use: a. Locate enclosure1 table, and record the input power @ idle as enc1Idle. b. Locate enclosure2 table, and record the input power @ idle as enc2Idle. c. Idle power requirement will be: enc2Idle enc1Idle. Calculate max power values to use: a. Locate enclosure1 table and record the input power @ 100% as enc1Max. b. Locate enclosure2 table and record the input power @ 100% as enc2Max. c. Max power requirement will be: enc2Max enc1Max.

4.

5. 6.

7.

Power calibration calculations

131

132

B Command reference
This reference section contains detailed descriptions of the Capacity Advisor commands. Commands Available on HP-UX and Microsoft Windows Operating Systems The command information included here is specific to HP-UX, though these commands are also available to run on Windows. TIP: For options and examples that are specific to using these commands on Microsoft Windows, see the Command Reference in Capacity Advisor Help. capagentlesscfg capagentlesscfg command controls advanced settings for agentless data collection, and lists the systems currently configured for agentless collection. Agentless data collection gathers data from Microsoft Windows and Linux systems without requiring the installation and configuration of an agent. Data from this collection method is picked up by capcollect for storage in the Insight Dynamics database for use in capacity planning. capcollect(1M) The capcollect(1M) command collects Capacity Advisor data from systems and stores data on the CMS. The data is used in capacity planning scenarios. capcustombenchmark(1M) The capcustombenchmark(1M) command configures Capacity Advisor benchmark CPU scaling to normalize collected data. capcustombenchmark(4) The capcustombenchmark(4) command provides information on formatting Capacity Advisor custom benchmark database files. capovpaextract(1M) The capovpaextract(1M) command exports OVPA system data from a specified managed node and imports the data into Capacity Advisor. capprofile(1M) The capprofile(1M) command imports, exports, displays, invalidates and removes Capacity Advisor data for workloads or systems. capprofile(4) The capprofile(4) command defines the format of Capacity Advisor data files for import and export.

Commands Available on Microsoft Windows Only cappmpextract(1M) The cappmpextract(1M) command exports HP PMP system data from the specified managed system and imports the data into Capacity Advisor.

133

capagentlesscfg (1M)
NAME
capagentlesscfg -- Set advanced options for Capacity Advisor agentless data collection, and view a list of systems configured for agentless data collection. Agentless Data Collection is available from these CMS types: 1) Microsoft Windows for managed servers running Windows and Linux , and 2) HP-UX for managed servers running Linux. For options and examples that are specific to using this command on Microsoft Windows, see the Command Reference in Capacity Advisor Help online.

SYNOPSIS
Default path: /opt/vse/bin/ capagentlesscfg -l capagentlesscfg -Lnnumber_of_collectors -Lmminimum_interval

DESCRIPTION
capagentlesscfg creates a list of systems licensed for Capacity Advisor that have been configured for agentless data collection, and sets the number of collecting threads and the minimum time interval to occur between data collections. Configuring the number of collector threads can be useful when a large number of systems have been configured for agentless data collection and you suspect that the agentless collectors are consuming a large amount of CPU on the CMS. Configuring the minimum collection interval can also reduce the amount of CPU used by the agentless collectors on the CMS, and can also be used to provide more accurate data. The user must be logged in as root on HP-UX to use this command.

Options
-h Display the capagentlesscfg command usage -l List the current configuration for agentless data collection. -Lmminimum_interval Optional. Define the minimum time (in seconds) that must pass before the next collection can start. Default value: 300 seconds (5 minutes). To restore the default value after an alternative value has been specified, use 0 (zero) for the value of minimum_interval. 14,400 [seconds] is the maximum value allowed; 30 [seconds] is the minimum interval recommended. The first letter indicates that the change applies specifically to the Linux (L) collector. -Lnnumber_of_collectors Optional. Define the number of collectors (threads) to be used to do the collection. Default value: Computed considering the number of hosts and the minimum interval between collections. To restore the default value after an alternative value has been specified, use 0 (zero) for the value of number_of_collectors. 250 [threads] is the maximum value allowed; 1 [thread] is the minimum value. The first letter indicates that the change applies specifically to the Linux (L) collector.

RETURN VALUES
Exit values are: 0 Successful execution. 1 An error was encountered.

EXAMPLES
For the configured Linux nodes, specify a 1-minute interval between data collections using two collector threads.
134 Command reference

# capagentlesscfg -L -m60 -n2

List all nodes configured for agentless data collection by this CMS:
# capagentlesscfg -l

AUTHORS
capagentlesscfg was developed by Hewlett-Packard Company.

DOCUMENT LAST UPDATED

January 2010

SEE ALSO
capcollect(1M)

135

capcollect (1M)
NAME
capcollect -- Collect Capacity Advisor data from systems to examine workload scenarios, do capacity planning, and store the data on the CMS. For options and examples that are specific to using this command on Microsoft Windows, see the Command Reference in Capacity Advisor Help online.

SYNOPSIS
Path on CMS: /opt/vse/bin capcollect [-c] [hostname1, hostname2, ...hostnameN] capcollect [-f] [-i] [hostname1, hostname2, ...hostnameN] capcollect [-z] [hostname1, hostname2, ...hostnameN]

DESCRIPTION
The capcollect command enables the user to collect historical utilization data from systems licensed for Capacity Advisor for analysis on the Central Management Server (CMS). Utilization data is gathered from systems specified using Web-Based Enterprise Management (WBEM). WBEM credentials for the systems are used as set up in HP Systems Insight Manager software. The data gathered is stored on the CMS in files. During a run, capcollect attempts to gather all WBEM utilization data stored on the managed system that is not already present on the CMS. Configuring capcollect to be run daily allows the last 24 hours of data to be gathered on each run. If a system is inaccessible when capcollect runs, an attempt is made to gather the missing data during the next run. Previously collected data on the CMS older than four years is removed. HP recommends that collection be configured to occur daily. capcollect also supports calibration of power data based on information obtained from HP Insight Control power management (IPM). The default behavior of capcollect is to collect utilization data and perform IPM calibration where available. NOTE: An automatic discovery task and automatic capcollect task start the 90-day trial license for Insight Dynamics for each discovered managed node.

Options
-c Checks the suitability of each system for data collection by verifying its attributes in HP SIM and the ability to retrieve utilization data from the data source or sources used for collection. Error or warning messages are issued for problems that would prevent successful collection. No utilization data is gathered and no previously collected data is removed. Force IPM to refresh data from the iLO interface. This can take up to one minute for each managed node. Perform IPM calibration only; do not collect utilization data. Collect utilization data only; do not perform IPM calibration.

-f -i -z

Operands
hostname Specifies the names of the systems from which to collect utilization data. By default, data is collected from all systems licensed for Capacity Advisor. Note that Capacity Advisor does not consider a complex to be a system. You cannot use the following special characters as part of a hostname: grave accent (`), semi-colon (;), ampersand (&), vertical bar (|), left parenthesis ( ( ), hash mark (#), greater-than sign (>), less-than sign (<), and the new-line character (ASCII 012).

136

Command reference

The disk space needed for data storage on the CMS depends on the method employed to collect data. Consult the latest version of the Capacity Advisor user guide for recommended disk space amounts per workload.

RETURN VALUES
Exit values are: 0 Successful completion. 3 An error was encountered when creating a new workload in the database or reading an existing workload from the database. 8 An invalid option was specified on the command line. 11 An error occurred accessing HP SIM, or an unhandled exception occurred during collection. 12 A system specified on the command line is not licensed for Capacity Advisor, or an error occurred when determining whether or not a system is licensed. 13 No WBEM credentials were available from HP SIM for a node. 14 An exception or other error prevents collection from one or more nodes. 15 An error was encountered accessing the WBEM server on a managed system. 16 Name specified on command line cannot be resolved by HP SIM as a node name, host name or IP address. 17 The operating system type for a system specified on the command line has not been discovered by HP SIM or it is not a type supported for collection. This can be caused, for example, by a "bare metal" blade added through HP SIM horizontal discovery. 18 A system specified on the command line has a system type of Unknown or Unmanaged in HP SIM, it is disabled in HP SIM, or it is a vpar monitor.

EXAMPLES
Collect Capacity Advisor data from the systems prod05 and sap_1.
capcollect prod05 sap_1

Force a refresh of IPM data and calibrate.

capcollect f i system6

WARNINGS
Write access to profile data using the capprofile(1M) command may be delayed while the capcollect command is running. If you receive the following message: "Unable to contact the WBEM server. See the capcollect(1M) manual page", a network or system problem is preventing contact with the WBEM server. To determine the cause of the problem, use the RETRY AND VERIFY PROCESS described next.

RETRY AND VERIFY PROCESS

1. 2. 3. 4. Retry the operation to see if the same error occurs. Verify that the system is connected to the network. Verify that the WBEM server process is running on the system. Use the /opt/wbem/bin/cimprovider -ls command on the managed node to verify that the provider is responding to requests.

DEPENDENCIES
You must run the capcollect command on the HP SIM CMS. For agentless data collection to occur, the system must have been configured for agentless collection for at least 10 minutes. For collection from VMWare, and Hyper-V virtual machines, the host must be registered with the VM Manager.

137

EXTERNAL INFLUENCES
By default, capcollect waits as long as 60 seconds for a response from a WBEM request. It waits an additional 4 minutes beyond this for a response from a WMI mapper WBEM request. These values can be changed by setting WBEMTimeOut, a HP SIM global setting, to a different value. For example, running the command
mxglobalsettings -s WBEMTimeOut=120

changes the time-out for WBEM requests to 2 minutes, or 4 + 2 minutes for a Microsoft Windows system accessed via WMI mapper. These time-out values only affect capcollect's use of WBEM. They do not affect agentless data collection or data collection on systems managed by HP Insight Control virtual machine management.

FILES
/var/opt/vse/profile/bin Root directory for storing collected data.

AUTHORS
capcollect(1M) was developed by Hewlett-Packard Company.

DOCUMENT LAST UPDATED

January 2010

SEE ALSO
capprofile(1M), capprofile(4)

138

Command reference

capcustombenchmark(1M)
NAME
capcustombenchmark -- Configure Capacity Advisor benchmark CPU scaling to normalize collected data.

SYNOPSIS
Path on CMS: /opt/vse/bin capcustombenchmark {-c | -customOnly} {{ -f | -inputFile } benchmark-file} capcustombenchmark {-b | -bothCustomAndBuiltIn} {{ -f | -inputFile } benchmark-file} capcustombenchmark {-B | -builtInOnly}

DESCRIPTION
The capcustombenchmark command allows you to configure the Capacity Advisor benchmark database for scaling CPU utilization data when modeling the move of workloads from one system to another. With capcustombenchmark, you can set the benchmark configuration to use only custom benchmark data that you supply, use custom benchmark data first and fall back to benchmark data provided by Capacity Advisor, or use only Capacity Advisor benchmark data. By default, Capacity Advisor is configured to use only its own benchmark data. This command is for use on servers running a CMS on HP-UX or Microsoft Windows.

Options
-c | -customOnly Specifies that Capacity Advisor should use only benchmark data that you supply. You must include {-f | -inputFile} with this option. Specifies that Capacity Advisor should preferentially use benchmark data that you supply, then use Capacity Advisor benchmark data when custom data does not contain data for the system(s) in question. You must include {-f | -inputFile} with this option. Specifies that Capacity Advisor should use only its own benchmark data. Specifies that Capacity Advisor should use benchmark-file as input for normalization calculations.

-b | -bothCustomAndBuiltIn

-B | -builtInOnly -f | -inputFile

LOGGING
Performance index results are calculated in the web application and by the capcollect command. To enable logging of performance index results, add the following line to the /etc/opt/vse/vseprefs.props file: benchmark.db.logresults=true The results are logged to file: /var/opt/vse/logs/perfIndex.resultLog In this file, you can see one line for each system for which a performance index has been calculated. The format of each line is: hostname=attribute:value,attribute:value,.... For example,
hostname1=result:1.0 +- 1.0 : CLOCK_SPEED (1000.0),processor:,model:ia64 hp superdome server SD32A,Core count:4,Database:BASELINE hostname2=result:1.0 +- 1.0 : CLOCK_SPEED (1000.0),processor:Intel(R) Itanium(R) 2 ,model:,Core count:16,Database:BASELINE

The attributes displayed are:

139

result: value +/- std_dev : type

value is the performance index result. +/- std_dev is the standard deviation for the type. type is the method used to compute the index and can be CLOCK_SPEED, AVERAGE, EXACT_MATCH, or NORMAL. CLOCK_SPEED is the CPU clock speed for the container. From the example: value is 1.0 +/- std_dev is +/- 1.0 type is CLOCK_SPEED

processor:

The processor information gathered from HP Systems Insight Manager software. From the example: processor: ia64 The model information gathered from HP Systems Insight Manager software. From the example: model: hp superdome server SD32A The number of CPU cores for the system. From the example: Core count:4 The performance database from which the result was derived; either BASELINE or CUSTOM. BASELINE is supplied by Capacity Advisor. From the example: Database:BASELINE

model:

Core count:

Database:

FILES ON CMS
/etc/opt/vse/vseprefs.props Used to enable or disable performance index logging. /var/opt/vse/logs/perfIndex.resultLog Used to log information about performance index determinations.

AUTHORS
capcustombenchmark(1M) was developed by Hewlett-Packard Company.

DOCUMENT LAST UPDATED

January 2010

SEE ALSO
capcustombenchmark(4), capcollect(1M)

140

Command reference

capcustombenchmark (4)
NAME
capcustombenchmark -- Format of Capacity Advisor custom benchmark database files.

DESCRIPTION
Defines the file format to use when creating custom benchmark data to be used by Capacity Advisor for scaling of CPU utilization values when moving workloads and/or virtual machines. Custom benchmark data can be defined as single line entries in a text file with each line containing the following data as a comma-separated list defining benchmark data for a single system type: system description: String Description of the system (model) as it appears after discovery in HP Systems Insight Manager software. number of configured cores: The number of CPU cores in the system. Integer Description of the processor (processor family) as it appears processor description: after discovery in HP SIM. String The speed of the processor in MHz for which the custom processor speed: Integer benchmark data was determined. benchmark performance index The custom value to use as the benchmark performance index for the system described. value: Float

EXAMPLE
A line of benchmark data would look like the following in a custom file:
ProLiant BL460c G1, 2, Intel Xeon, 2700, 2807.5809

where ProLiant BL460c G1 is the system description 2 is the number of configured cores Intel Xeon is the processor description 2700 is the processor speed 2807.5809 is the benchmark performance index value

CONVERSIONS
To convert from some publicly available benchmark values to a Capacity Advisor performance index value, the following conversion formulas have been provided. Spec2006: Performance index = specInt2006rate * 209 / coreCount

AUTHORS
capcustombenchmark(4) was developed by Hewlett-Packard Company.

DOCUMENT LAST UPDATED

January 2010

SEE ALSO
capcustombenchmark(1M), capcollect(1M)

141

capovpaextract (1M)
NAME
capovpaextract -- Export Performance Agent (OVPA) system data from the specified managed node and import the data into Capacity Advisor.

SYNOPSIS
Path on CMS: /opt/vse/bin/ capovpaextract [ -b begin-time -e end-time capovpaextract -h ] [ -p ] managed_node

DESCRIPTION
capovpaextract exports OVPA (MeasureWare data) system utilization information from the specified managed node and imports the information into Capacity Advisor. The data returned from managed_node overwrites any existing data for the managed node. The user must have root privileges to run this command. capovpaextract allows importing data from non-Insight Dynamics (non-ID) systems, such as older HP-UX systems or Solaris systems so long as those systems are running a supported OVPA version. Supported OVPA versions are listed in the Dependencies section of this command reference page.

OPTIONS
-b start-time -e end-time Specifies the beginning (start-time) and ending (end-time) dates of data in MM/DD/YY (month/day/year) format. If no start or end time is given, 30 days of data are imported. -p Indicates that the workload whose data is being imported is a non-Insight Dynamics workload. This provides an alternative to importing OVPA data from non-licensed systems to use in Capacity Advisor scenarios. If a non-ID workload already exists in the Capacity Advisor data, an error message appears. Non-ID workloads are not associated with any licensed nodes and are not visible on the Insight Dynamics Workload tab. To import non-Insight Dynamics workload data, use the following GUI action sequence starting from the Capacity Advisor tab: Modify -> Edit Planning Scenario -> What-If Action -> Create Workloads. Activate the radio button Use profile data from workload and choose a non-ID workload from the Import Profile Values workload list. You must know ahead of time the name of the non-ID workload. -h Displays command usage.

Dependencies
This command uses the remote execution facilities provided by HP Systems Insight Manager software, and therefore requires the configuration of SSH authentication within HP SIM for the specified managed_node. Capacity Advisor supports the following versions of OVPA :

142

Command reference

HP-UX C.03.35 or later SOLARIS C.03.75 or later LINUX C.04.00 or later

EXAMPLES
Extract OVPA data and import the data to an existing system, test.company.com.
# capovpaextract test.company.com

Extract OVPA data for a specific time interval.

# capovpaextract -b 01/01/06 -e 06/31/06 test.company.com

Extract OVPA data for a specific time interval and import it as a non-Insight Dynamics workload to test.company.com.
# capovpaextract -b 01/01/06 -e 06/31/06 -p test.company.com

AUTHORS
capovpaextract(1M) was developed by Hewlett-Packard Company.

DOCUMENT LAST UPDATED

January 2010

SEE ALSO
capcollect (1M)

143

capprofile (1M)
NAME
capprofile -- Import, export, display, invalidate and remove Capacity Advisor data collected for workloads or systems.

SYNOPSIS
Path on CMS: /opt/vse/bin capprofile -c [ -b begin-time ] [ -e end-time ] [ -y delimiter ] profileID capprofile -i [ -p|-S ] [ -b begin-time ] [ -e end-time ] [ -o ] [ -y delimiter ] profileID capprofile -l [n|t|v] [-p] [ -b begin-time ] [ -e end-time ] [profileID ...] capprofile -m [i|v] [ -b begin-time ] [ -e end-time ] profileID ... capprofile -r profileID capprofile -x [ -p ] [ -b begin-time ] [ -e end-time ] [ -t ] [ -y delimiter ] profileID ...

DESCRIPTION
The capprofile command manages utilization data collected on the Systems Insight Manager Central Management Server (CMS) for Capacity Advisor. With capprofile, you can export profile data, either as a file formatted for further processing, or as a table with headings; you can also import data. With the capprofile command, you can display the names of systems or workloads that have sufficient utilization data for Capacity Advisor to analyze and, for a particular system or workload, you can display those time intervals that have valid data. The capprofile command also lets you mark utilization data for specified time intervals as invalid. Refer to the capprofile command reference pages for information on capprofile file formats. The capprofile command compensates for certain imperfections in imported data. If profile data is missing for a sample time, the data is assumed to be unavailable. No data for these samples is shown in the profile viewer and the samples do not affect utilization aggregation. A warning is issued for each group of consecutive missing samples when importing. Duplicate entries may appear for a sample time. Only the values from the last sample in the file for that time are used. A warning is issued for each duplicated sample. You can also import data from non-Insight Dynamics (non-ID) workloads, such as data from nodes without Capacity Advisor licenses. During a transition to Daylight Savings Time, sample times may decrease by an hour and then increment again as usual. After such a transition, samples are ignored until the time reaches the next expected sample time. Sample times may differ from times aligned to the hour (the usual case) as long as they are 5 minutes apart. Each sample time is modified to the nearest 5-minute multiple from the hour. For example, if the first sample time is 18 minutes after the hour, the time for the data sample is imported with a time of 20 minutes after the hour. The next sample time must be 23 minutes after the hour, and it is imported with a time of 25 minutes after the hour, and so on. A warning is issued when a file with non-aligned sample times is imported. The following cases cause imported data to be ignored or converted and a warning message issued: A sample line with missing or extra metrics, as compared to the labels in the file header; the sample line is ignored. A sample with negative values for one or more metrics. Negative values are converted to Not A Number floating point values. A sample with invalidly formatted floating point numbers for the value of a metric; these sample lines are ignored.

144

Command reference

Options
-b begin-time -c Specifies the time to begin using profile data. If omitted, the first available profile time is used. Checks an import file without importing its data. This checks for duplicate sample times, sample times not aligned to hours, improperly formatted samples, samples with negative values, and missing samples. A message is issued for each inconsistency noted. Specifies the time to stop using profile data. If omitted, the last available profile time is used. Begin-time and end-time are defined as YYYYMM[DD[hh[mm]]] as follows:
Units YYYY MM DD hh mm Meaning Year (for example, 2005) Month of the year (01-12) Day of the month (01-31) Hour of the day (00-23) Minute of the hour (00-59)

-e end-time

If a day, hour or minute field is omitted, its value defaults to zero. -h -i Displays command usage. Imports utilization data for a workload or system. The capprofile command reference pages describe the format of the text representation of the imported data. The imported text is read from standard-in (stdin). If any data already exists for the workload or system, the -o option must be specified as well. Also see the -o and -S options. Lists profile summaries. By default, this is a list of the systems and workloads that have any profile data. Use -ln to list the profileIDs (the name or unique identification of the profile). Use -lt (the default) to list profileIDs and available history. Use -lv to list profileIDs, available history, and percent valid. Marks utilization data as valid (v) or invalid (i) for a specified system or a group of systems or workloads. When a data range is specified, only data within that range will be affected. If no date range is specified, all data is marked. Specify the utilization data to be marked by date range. Marking data by a date range marks every sample in the specified range. Marking utilization data invalid does not remove or alter it; Capacity Advisor just ignores it. Marking utilization data invalid excludes all utilization values (CPU, memory, disk or network I/O, and power) from consideration. You cannot, for example, mark invalid only the CPU utilization portion of a sample. Use -m i to mark data for a specified interval and profileID as invalid; use -m v to mark data as valid. When used with the -i option, overwrites existing data where there is an overlap in the date range of the import data and the date range of the existing data. If there is no overlap, no overwrite occurs, though the user will see a message informing of the possibility of an overwrite occurring. Indicates that the workload whose data is being imported is a non-Insight Dynamics workload. This provides an alternative to importing OVPA data from non-licensed systems to use in Capacity Advisor scenarios. If a non-ID
145

-l

-m

-o

-p

workload already exists in the Capacity Advisor data, an error message appears. Non-ID workloads are not associated with any licensed nodes and are not visible on the Insight Dynamics Workload tab. To import non-Insight Dynamics workload data, use the following GUI action sequence starting from the Capacity Advisor tab: Modify -> Edit Planning Scenario. The Edit Scenario window opens. Then select What-If Action -> Create Workloads from the menu. Activate the radio button Copy Profile and choose a non-ID workload from the Import Profile Values workload list. You must know ahead of time the name of the non-ID workload. -r profile_ID Removes all profile data for a specified workload or system from the CMS. This can be used, for example, to release disk space when a workload is retired and its performance data is no longer needed. The profileID names a specific workload. All system name profiles are fully qualified. Saves the import-compartment attributes. Used in conjunction with -i to import data. Saves the container attributes specified in the import header as attributes for the target profile. Exports data as a table. Exports utilization data for the specified profile as a sequence of lines. Each line contains utilization values for a five-minute period. The format is specified in the capprofile(4) manpage. The exported text is sent to standard-out (stdout). Specifies the delimiter character used to separate values in imported and exported data. The default delimiter is the comma. Valid delimiters, with or without double quotes, are: comma (,), slash (/), semicolon (;), colon (:) and vertical bar (|); some of these delimiters may need to be quoted or escaped.

-S

-t -x

-y delimiter

RETURN VALUES
Exit values are: 0 Successful completion. 3 An error was encountered accessing the database.. 8 An invalid command-line option was specified. 9 An invalid argument was specified to an option. 10 An invalid combination of options was specified. 11 An error occurred accessing HP SIM, or an unhandled exception occurred during collection. 32 The beginning of the sample date range occurs after the end date.

EXAMPLES
Export profile data from December 14, 2005 at midnight to midnight December 31, 2005 for the workload with profileID billing3 to the file billing3.txt in the /tmp directory.
capprofile -x -b 20051215 -e 200512312359 billing3 > /tmp/billing3.txt

Import profile data from the file /tmp/billing3.txt for the profile with profileID billing3.
capprofile -i -o billing3 < /tmp/billing3.txt

Mark a range of utilization data as invalid for the workload with profileID prod05_wkld. All samples between December 15 2005 at 11 a.m. and December 16 2005 at 12 p.m. (inclusive) are marked invalid.
capprofile -m i -b 2005121511 -e 2005121612 prod05_wkld

List profileID, available history, and percent valid. (Note that a Percent Valid value of less than 100% can occur when there is invalid or uncollected data. For example, there may be one or two uncollected data samples on a node right after it reboots.)
capprofile -lv
146 Command reference

Name node01.co.com node02.com billing3 node03.com.OTHER cimserver

Available History 01/17/06 05:30 pm 12/18/05 05:00 pm 12/10/05 05:00 pm 01/15/06 03:05 pm 01/17/06 05:30 pm

01/19/06 01/20/06 01/20/06 01/18/06 01/19/06

10:10 01:05 01:05 12:55 10:10

am pm pm pm am

Percent Valid 100.00% 99.96% 100.00% 82.83% 99.78%

Import profile data from the file /tmp/nonIDWorkloadFile.txt for the profile with profileID nonIDWorkload.
capprofile -i -p nonIDWorkload < /tmp/nonIDWorkloadFile.txt

List profile summaries for non-Insight Dynamics workloads:

# capprofile -l -p Non-ID-Workloads-Name externalBilling2 accounting1 monitoring

WARNINGS
While the capcollect(1M) command is running, write access to profile data using the capprofile(1M) command may be delayed.

FILES ON CMS
/var/opt/vse/profile/bin Root directory for storing collected data for both capcollect and capprofile. Note that the format of these data files may change without notice from release to release. The file system where these files are stored needs to be sized to hold all the daily utilization profile data, which for each system, is about 32K per day per workload, taking into account minimum block size of 4K. For example, with a CMS monitoring 100 systems, each with an average of 3 workloads, with a need to keep historical data for one year, the file system where the profile resides must have space for (100 systems + 300 workloads) * 365 days * 32K = 4.45 Gigabytes. With a file system that allocates storage in blocks greater than 24K, then use the larger block size.

AUTHORS
capprofile(1M) was developed by Hewlett-Packard Company.

DOCUMENT LAST UPDATED

January 2010

SEE ALSO
capprofile(4), capcollect(1M), capovpaextract(1M), vseinitconfig(1M)

147

capprofile (4)
NAME
capprofile -- Format of Capacity Advisor import and export files.

DESCRIPTION
Defines the file format used when importing and exporting data for Capacity Advisor. The data for the specified profile is imported and exported as a series of lines containing the following: profile headers, including date and metric labels utilization values The collection period is 5 minutes. The collection occurs at the end of the 5-minute period. Each data line is called a sample. The first nine lines of the import file are format headers that define the profile characteristics. This information is used to normalize the utilization data when it is saved in the Capacity Advisor database. The last line gives the date and time format and the list of metrics to be included. The format header is: #Profile: name #Host: hostname #CPU: CPU_count@CPU_speedGHz #Memory: MEM_sizeMB #OS: platform #Model: model #ProcessorString: processor_string #ProcessorFamily: processor_family #Version: version_number [YYYYMMDDhhmm,] UTIS, metric [, metric, ...] The English characters shown above always appear in the field names and units specified in the header, even when the locale causes messages to display in a different language. The fields of the profile header format are the following: name: Name of the profile. hostname: Fully-qualified name of the system. For example, node05.company.com. CPU_count: Number of CPUs for which data is gathered in the file. For example, 1 means data was gathered for 1 CPU. Only integer values are valid. Note that CPU_count includes iCAP processors that are not enabled. This reflects the number of cores when dual-core processors are in use. The number of hardware threads when hyperthreaded processors are in use are NOT counted in CPU_count. CPU_speed: Speed in GHz (gigahertz); all CPUs are assumed to have the same speed. MEM_size: Memory size in MB (megabytes). platform: Name of operating system, HP-UX or Linux. model: The string representing the model of hostname as output by the model command. processor_string: A complete identification of the processor that includes the maker, the name of the processor, the processor speed, and specific details about the processor model. processor_family: The maker and name of the processor. version_number: Capacity Advisor version number. The last header line contains the comma-separated list of labels for the date and gathered metrics.

148

Command reference

metric: One or more of the following metrics: CPU_UTIL, MEM_UTIL, NET_UTIL, DISK_UTIL, CPU_ALLOC, MEM_ALLOC, PHYS_CPUS, PHYS_MEM, CPU_QUEUE, PAGES_PER_SEC, IOS_PER_SEC, PKT_PER_SEC, DISK_USED. The command only outputs a result when there is data for the given metric during the provided period of time. If the metric data covers some of the time range, but does not encompass all of the time range, the column is padded with NaN values. You cannot import a file containing only metrics you must include the UTIS with any metrics that you select. The fields that appear on this line are defined as: YYYYMMDDhhmm: Timestamp in local time, given in units of YYYY (year), MM (month, as 01 to 12), DD (day, as 01 to 31), hh (hours, as 00 to 23), and mm (minutes, as 00 to 59). This format is also used to specify the begin and end times for the capprofile(1m) command. This field is optional when importing data. UTIS: Universal Time (GMT) in seconds (standard UNIX time in seconds since 1 January 1970) (Required) CPU_UTIL: CPU utilization expressed as the number of CPUs used (5 minute average). MEM_UTIL: Memory utilization or amount of memory used in gigabytes (at end of interval reading). NET_UTIL: Network bandwidth utilization, in Mb/s (10^6 bits, megabits per second) (5 minute average). DISK_UTIL: Disk bandwidth utilization in MB/s (10^6 bytes, megabytes per second) (5 minute average). CPU_ALLOC: Number of CPUs allocated (active CPUs only; cores or hardware threads on multicore). Hyperthreaded processors are not counted in CPU_ALLOC. MEM_ALLOC: Memory allocation in GB (gigabytes). PHYS_CPUS: Number of physical CPUs (at end of interval reading). PHYS_MEM: Physical memory available, in GB (gigabytes). CPU_QUEUE: The average depth of the CPU run queue. PAGES_PER_SEC: The peak pages input and output per second. IOS_PER_SEC: The number of disk I/O operations executed per second. PKT_PER_SEC: The number of network packets either sent or received per second. DISK_USED: The disk space used on local disks, expressed in 1024-byte blocks.. The last line of the import file header must include at least one metric column label and may have any combination of the metric column labels, in any order. It must have the UTIS timestamp column label in position 1 or, if the YYYYMMDDhhmm column label is present, in position 2. A metric label can appear only once in the header. UTIS timestamps must increment in a consistent order for each row; YYYYMMDDhhmm values are provided for readability. To import a subset of metrics, specify only those metrics in the header. For example, to import only the CPU_UTIL metric, the last header line should contain YYYYMMDDhhmm, UTIS, CPU_UTIL or UTIS, CPU_UTIL. Each subsequent line after the header contains utilization values for a specified moment in time. Each data line, called a sample, has a timestamp followed by the values as designated in the header. Utilization values for a sample are separated by a specified delimiter character or by a comma (default). The UTIL seconds must be in 5-minute intervals (increments of 300 seconds). NOTE: In some of the following examples, UTIS values are truncated to omit following zeroes.

EXAMPLES
The following example shows utilization data in compressed format created using the following command: # capprofile -x -b20090824 -e20090825 node05.company.com

149

#Profile:node05 #Host:node05.company.com #CPU:4 @ 1.866GHz #Memory:4093MB #OS:WINNT #Model:ProLiant DL380 G5 #ProcessorString:Intel(R) Xeon(TM) Processor 1.866 GHz (x86 Family 6 Model 15 Stepping 7) #ProcessorFamily:Intel Xeon #Version:A.03.00.00 YYYYMMDDhhmm,UTIS,CPU_UTIL,MEM_UTIL,NET_UTIL,DISK_UTIL,CPU_ALLOC,MEM_ALLOC,PHYS_CPUS,PHYS_MEM 200908241200,1251136800,0.34790,2.12109,0.04915,0.66662,4.00000,3.99707,4.00000,3.99707 200908241205,1251137100,1.42610,1.93066,0.02458,1.41005,4.00000,3.99707,4.00000,3.99707 200908241210,1251137400,0.20913,2.19043,0.06554,0.09114,4.00000,3.99707,4.00000,3.99707 200908241215,1251137700,0.92060,2.26855,1.02400,0.17613,4.00000,3.99707,4.00000,3.99707 200908241220,1251138000,0.98760,2.48145,1.93331,0.26010,4.00000,3.99707,4.00000,3.99707 200908241225,1251138300,0.61837,2.56836,1.49914,0.33485,4.00000,3.99707,4.00000,3.99707

The following example shows utilization data in a tabular format, aligned in columns. # capprofile -t node05.company.com
#Host: node05 HP-UX B.11.23 #CPU: 1 @ 1.0 GHz #Version:A.02.50.00 YYYYMMDDhhmm, UTIS, CPU_ALLOC, CPU_UTIL, DISK_UTIL, MEM_ALLOC, MEM_UTIL, NET_UTIL, PHYS_CPUS, PHYS_MEM 200509120020, 11264196, 0.01, 2.14, 0.003, 0.02, 4.0, 3.98, 4.0, 200509120025, 11264199, 0.03, 2.13, 0.005, 0.01, 4.0, 3.98, 4.0, 200509120030, 11264202, 0.02, 2.15, 0.003, 0.01, 4.0, 3.98, 4.0, 200509120035, 11264205, 0.02, 2.15, 0.004, 0.01, 4.0, 3.98, 4.0, 200509120040, 11264208, 0.01, 2.13, 0.004, 0.01, 4.0, 3.98, 4.0, 200509120045, 11264211, 0.02, 2.14, 0.003, 0.01, 4.0, 3.98, 4.0, 200509120050, 11264214, 0.02, 2.14, 0.003, 0.02, 4.0, 3.98, 4.0,

3.98 3.98 3.98 3.98 3.98 3.98 3.98

The following example shows data gathered only for CPU allocation and utilization.
YYYYMMDDhhmm, 200605250020, 200605250025, 200605250030, 200605250035, 200605250040, 200605250045, 200605250050, UTIS, CPU_ALLOC, CPU_UTIL 11264196, 0.01854, 2.14 11264199, 0.03128, 2.13 11264202, 0.02075, 2.15 11264205, 0.02101, 2.15 11264208, 0.01960, 2.13 11264211, 0.02391, 2.14 11264214, 0.02387, 2.14

AUTHORS
capprofile(4) was developed by Hewlett-Packard Company.

DOCUMENT LAST UPDATED

January 2010

SEE ALSO
capprofile(1M), capcollect(1M)

150

Command reference

cappmpextract
NAME
cappmpextract -- Export HP Performance Management Pack (PMP) system data from the specified managed node and import the data into Capacity Advisor. List PMP-managed nodes from where data can be extracted from or imported into Capacity Advisor.

SYNOPSIS
Path: install_dir\bin C:\Program Files\HP\Virtual Server Environment\ cappmpextract -l capovpaextract -h cappmpextract -x managed_node [ -b begin_time ] [ -e end_time ] cappmpextract -i managed_node [ -o ][ -p ] [ -b begin_time ] [ -e end_time ] -S

DESCRIPTION
The main functionality of cappmpextract is to export PMP system utilization data for the specified managed node and import into Capacity Advisor. The user must have administrator privileges to run this command. Because PMP is only available on a Windows CMS, this command will only work on a Windows CMS. The cappmpextract command also provides ways of (1) listing PMP managed nodes which contains system utilization data; and (2) exporting utilization from data PMP in a capprofile (4) format. cappmpextract also allows the user to import data from non-Insight Dynamics (non-ID) managed nodes (non-licensed nodes), so long as those nodes are being monitored by a supported PMP version. Supported PMP versions are listed in the Dependencies section of this command reference page.

OPTIONS
-b start-time -e end-time Specifies the beginning (start-time) and ending (end-time) dates of data in YYYYMMDD format, where YYYY is the year MM is the month DD is the day If no beginning and ending dates are provided, cappmpextract extracts all available data. The user can not provide only beginning or ending dates. Displays command usage. Imports utilization data for a system into Capacity Advisor database. Also see the o option. Lists all PMP managed nodes, including available data interval and percent of valid data for each system. Any node listed by the -l option is a valid node to have its PMP data imported into Capacity Advisor with the -i option. Used with the -i option. This allows cappmpextract to overwrite existing data. Indicates that the workload whose data is being imported is a non-Insight Dynamics workload. This provides an alternative to importing PMP data from non-ID licensed systems to use in Capacity Advisor scenarios. Non-ID

-h -i -l

-o -p

151

workloads are not associated with any licensed nodes and are not visible on the Insight Dynamics Workload tab. To import non-Insight Dynamics workload data, use the following GUI action sequence starting from the Capacity Advisor tab: Modify -> Edit Planning Scenario. This will open the scenario that you selected. Then click What-If Action -> Create Workloads from the Edit Scenario menu. Activate the radio button Use profile data from workload and choose a non-ID workload from the Import Profile Values workload list. You must know ahead of time the name of the non-ID workload. -x Exports utilization data for the specified system from PMP to standard-out (stdout). The utilization data is exported in the same CSV format used by capprofile. The format is specified in the capprofile (4) command reference page Saves the import-compartment attributes. Used in conjunction with -i to import data. Saves the container attributes specified in the import header as attributes for the target profile.

-S

Dependencies
The command requires an installed and configured PMP. This command does not support PMP configured with remote database. Capacity Advisor supports the following version(s) of PMP : 4.7

EXAMPLES
Extract PMP data and import it into Capacity Advisor database for system test.company.com.
# cappmpextract -i test.company.com

Extract PMP data for a specific time interval and redirecting output to out.txt file.
# cappmpextract x -b 20060101 -e 20060631 test.company.com > out.txt

Extract PMP data for a specific time interval and import it as a non-ID workload to test.company.com.
# cappmpextract i -b 20060101 -e 20060631 -p test.company.com

Lists all available PMP managed nodes from where data can be extracted from or imported into Capacity Advisor:
# cappmpextract Name SystemA SystemB l Available History 12/17/07 05:30 pm - 12/18/07 05:05 pm 12/17/07 05:35 pm - 12/18/07 05:05 pm

AUTHORS
cappmpextract was developed by Hewlett-Packard Company.

DOCUMENT LAST UPDATED

January 2010

SEE ALSO
capcollect(1M), capprofile (1M), capprofile (4)

152

Command reference

C Units and terminology

The units and terms listed in the following table are used within Capacity Advisor. For an expanded list of terminology used within Capacity Advisor and VSE Management Software, see the Glossaryat the end of this guide. Table C-1 Units and Terminology
Unit or Key Word clock speed Meaning Some newer processors are capable of short bursts of speed above the base speed of the processor. When Capacity Advisor shows the clock speed of a system, it reports the base speed. Some other applications (such as the Onboard Administrator) may report the maximum clock speed. Integrated Lights Out software reports both the base and accelerated (maximum) clock speed. Processors are also able to run at slower clock speeds to save power. These different power/performance states are called P-states, with the fastest P-state called P0. When Capacity Advisor shows the clock speed of a system, it gives the P0 clock speed, as opposed to the current clock speed. core Active data-processing unit within a processor; a processor (CPU) can contain one or more cores. Multiple cores on the same physical unit provides the capability for multiprocessing within the same CPU. Central Processing Unit. The computer chip that executes most programming instructions; can be composed of one or more cores. The number or percentage of CPU cores in use. Each Capacity Advisor data sample represents a 5-minute average of CPU cores used over that period of time. These measurements are calculated by tracking CPU usage within the kernel at each polling interval in the following manner:

CPU CPU utilization

Table C-2 Data collection for CPU utilization by platform

Platform HP-UX Calculation Total used CPU ticks during the interval divided by the total available CPU ticks during the interval Total used CPU ticks during the interval divided by the total available CPU ticks during the interval Collected From pstat()

Linux

/proc/stat

Microsoft Windows Proliant VM Host and VMs OpenVMS

Percent busy since the start of the interval CPU PDH counter Imported as is HP Virtual Machine Management Pack (VMM)

Total used CPU ticks during the interval CPU database CPU divided by total available CPU ticks during tick counters the interval.

When monitoring user-defined workloads, CPU and memory utilization for short-lived, "user-owned" processes may be missed. Short-lived processes are those lasting less than 5 minutes that span less than two sample periods. Any "missed" utilization is attributed to system processes.

153

Table C-1 Units and Terminology (continued)

disk I/O bandwidth utilization Measured in MB/s (10^6 bytes, megabytes per second). Each sample represents an average reading over the past 5 minutes. These measurements are obtained and calculated in the following manner:

Table C-3 Data collection for disk I/O bandwidth utilization by platform
Platform HP-UX Linux Microsoft Windows Proliant VM Host and VMs OpenVMS Calculation Total bytes transferred during the interval Total bytes transferred during the interval Collected from pstat() /proc/diskstats

Total bytes transferred out during the interval PDH disk counters Imported as is HP Virtual Machine Management Pack (VMM) sys$getdvi system service DVI$_OPCNT)

Total bytes transferred during the interval

GBs GHz

Gigabytes. Unit used for memory: (10^9 bytes) Gigahertz. In Capacity Advisor, CPU capacity is defined in terms of clock speed expressed in megahertz (10^6 hertz) or gigahertz (10^9 hertz). Clock speed refers to the rate at which a computer performs its most basic operations such as adding two numbers. The difference between the average resource utilization on a system and the maximum available capacity. See Headroom (page 25)for an explanation of headroom rating (stars), and information on interpreting the star ratings shown in automated solutions. Capability of some Intel processors to create an additional virtual core that provides additional processing efficiencies. Note that Capacity Advisor does not count Hyper-Thread virtual cores separately. In Capacity Advisor, the hypervisor includes not only the virtualization platform, but also all functions performed by the host OS, as well as all virtual machine monitoring processes (everything on the VM host that is not a VM guest).

headroom

Hyper-Threading

hypervisor

hypervisor memory Capacity Advisor estimates hypervisor memory overhead by adding together all memory overhead used in support of running guests. This overhead can be estimated by adding together the memory use of the following: the host operating system that the hypervisor is running on (HP-UX, Linux, Windows) the hypervisor process that manages and enables the execution of guests An overhead constant per guest that can either be a standard value for each guest on the host, or a function of the amount of RAM allocated to a guest depending on the virtualization platform. Except in the case of HP Virtual Machine, Capacity Advisor assumes a worst case scenario where all guests are allocated 1GB of memory, as this will maximize the hypervisor memory overhead. Mb/s MB/s Megabits (10^6 bits) per second. Unit used for networking throughput. Megabytes per second (10^6 bytes per second). Unit used for storage media throughput.

154

Units and terminology

Table C-1 Units and Terminology (continued)

memory utilization The amount of memory used in gigabytes (2^30 bytes). Each sample represents an actual reading at the time the sample was taken. These measurements are obtained and calculated in the following manner:

Table C-4 Data collection for memory utilization by platform

Platform HP-UX Linux Calculation Memory used by the users Memory used by the users Collected From pstat() /proc/stat

Microsoft Windows Memory used by the users + memory used by the system + cache memory Proliant VM Host and VMs OpenVMS Imported as is HP Virtual Machine Management Pack (VMM)

Total memory used by user and system sys$getrmi system service processes. (RMI$_USERPAGES) and Sys$getsyi (syi$_PhysicalPages)

multithreading network I/O bandwidth utilization

The ability of an application and operating system to split processing between processors or cores, thereby enabling parallel computing. Measured in Mb/s (10^6 bits, megabits per second). Each sample represents an average reading over the past 5 minutes. These measurements are obtained and calculated in the following manner:

Table C-5 Data collection for network I/O bandwidth utilization by platform
Platform HP-UX Linux Microsoft Windows Proliant VM Host and VMs OpenVMS Calculation Collected from

Total bytes transferred during the interval MIB system Total bytes transferred during the interval proc/net/dev Total bytes transferred out during the interval Imported as is PDH counters HP Virtual Machine Management Pack (VMM)

Total bytes transferred during the interval. sys$qio system service (GETSTATS)

Counters are sampled at the start and end of each interval. OTHER workload The system-name.OTHER workload is used to account for all processes on a system that do not match any user-defined workloads. For more information, see Workloadsin Virtualization Manager Help. On some Capacity Advisor displays, data is not available for this .OTHER workload. Component that plugs into a processor socket. A processor can contain more than one core. The packaging of one or more processors in a unit that connects to a single socket on the system bus. The system board socket to which a processor is attached. A compensating factor that Capacity Advisor uses to adjust needed resources when analyzing a move from one platform to another.

processor processor module processor socket scaling multiplier

155

156

D Snapshots of Capacity Advisor reports

Consolidation candidate report
The following image illustrates a portion of data shown in a consolidation candidate report when CPU and memory resource utilization data are selected for inclusion. You can also select to see data on network I/O and disk I/O in this report. Other data that would appear in this report: average paging (pages/second). Note that the data can be downloaded to a CSV file for import into a spreadsheet. Use the spreadsheet to sort the data according to the attributes that you are most interested in.

Scenario comparison report

The following images provide clips from a report that compares three scenarios: one a collection of physical servers and two consolidation solutions that illustrate changes that would occur after moving the physical servers to VM hosts. These images are provided to illustrate some of the types of information that the report contains for each scenario included in a scenario comparison report.

Consolidation candidate report

157

Workload Detail

158

Snapshots of Capacity Advisor reports

Scenario Inventory

Scenario comparison report

159

160

E Graphed data in Capacity Advisor reports

To access Capacity Advisor reports, select ReportsCapacity Advisor . Table E-1 Data graphs available in Capacity Advisor reports.
Graph title Report type

Accumulated hourly peak CPU utilization for all servers Peak summary report and for individual server Number of servers at peak use by hour for all servers and Peak summary report for individual server Number of servers by CPU use for all servers and for individual server Peak summary report

Operating system, processor type, cores/socket, and total Population report cores/server in server population Peak CPU use by week for all servers and for individual Peak summary report server Percent of allocation for CPU, memory, disk I/O, and network I/O for individual server and for individual workload Utilization report Utilization options

Resource utilization trend for CPU, memory, disk I/O, Utilization report Trend options and network I/O for individual server and for individual workload Utilization of CPU, memory, disk I/O, network I/O for individual server and individual workload Utilization report Utilization options

161

162

F Example of the Undo/Edit/View Applied What-If Actions screen

This screen illustrates some actions taken in Capacity Advisor to produce examples in this guide.

163

164

G Troubleshooting in Capacity Advisor

Behaviors that you might see when working within the Capacity Advisor user interface that may not have error or warning messages associated with them are explained in this appendix.

When there is no connection

Within an interdependent product like Insight Dynamics, there are conditions that can create errors in connection that make it difficult or impossible for some functions to complete in Capacity Advisor. Errors in CMS or managed node configuration Insight Dynamics provides a tool called vseassist that you can use to identify and troubleshoot system configuration errors that may be preventing data collection or other use of Capacity Advisor. For full information on the vseassist tool, see HP Insight Dynamics 6.2 Getting Started Guide. Internet Explorer times out before report generation completes In the case where you request a report using data from many managed systems (>100), Microsoft Internet Explorer may end the session connection before the report is complete. This ends the report creation; no report is generated for viewing or download. Suggested action: One way to address this behavior is to create a registry key on your local Microsoft Windows system to extend the amount of time that Internet Explorer will wait before closing the connection, as follows:
Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings] "MaxConnectionsPer1_0Server"=dword:00000005 "MaxConnectionsPerServer"=dword:00000005 "ReceiveTimeout"=dword:5265C0

These settings cause the following to occur: MaxConnectionsPer1_0Server and MaxConnectionsPerServer increase the maximum number of connections that can be used to handle the traffic from the browser. (Normally, the value is 2 connections per server; this example shows 5 connections per server.) ReceiveTimeout extends the timeout boundary of the browser. (Use hexadecimal values to adjust the time to the desired number of hours, with 24 hours being the maximum time that will work successfully.) Other alternatives include: reducing the number of systems included in a single report to <100. running large reports in Mozilla Firefox browser, where this behavior does not seem to occur. capprofile hangs when exporting non-contiguous data into Capacity Advisor for profiling capprofile may hang when exporting large amounts of non-contiguous data (data set containing significant periods when data was not collected interspersed with periods of data collection). Suggested action: Export contiguous chunks of data. Licensing - general To collect data from a managed node, that node must be licensed to fully use Capacity Advisor or must have a limited license (the HP Insight Capacity Advisor Consolidation software) for data collection only. For information on licensing, see the Licenses management chapter in HP Insight Dynamics 6.2 Getting Started Guide and Data collection and the HP Insight Capacity Advisor Consolidation software (page 63). License check fails The licensing check conducted by Capacity Advisor will fail in the case where a duration license has been assigned or locked prior to HP SIM discovering the serial number of the system. Suggested action: Confirm that a system has been fully discovered in HP SIM before assigning a duration license to it. For systems for which HP SIM does not attempt to discover Unique Identifiers (UUIDs), this problem does not occur. (For a definition of a duration license, see About Licenses in the HP Systems Insight Manager 6.2 online help.)

When there is no connection

165

User authorization Some operations in Capacity Advisor require Administrator or root permissions. As needed, check that you are logged in with the appropriate role or permissions for the operation you are trying to do. For information on user authorizations, see the Licenses management chapter in HP Insight Dynamics 6.2 Getting Started Guide. Create Scenario Wizard not working requires Adobe Flash Player The Adobe Flash Player is delivered with HP Systems Insight Manager software, and assistance is provided to help you install this plug-in into your browser. If you find that you need more information, please consult the HP Systems Insight Manager 6.2 User Guide, available from http://www.hp.com/go/hpsim. Follow the Information Library link for access to the guide and other documents.

Data is not being collected

Numerous circumstances can contribute to failure in collecting data. Data collection not configured and/or agent not installed Suggested action: For standalone systems, use the Insight managed system setup wizard to configure the system. The managed system setup wizard will automatically select the supported data collection method for the CMS/managed node communication. For VM hosts and guests, this can mean making sure that the host is licensed for HP Insight Control virtual machine management (or Insight Control), and making sure that the host is registered in VMM. Nothing needs to be done for most VM guests, but Microsoft Hyper-V VM guests must have SSH access set up in HP SIM. Again, use the Insight managed system setup wizard to set up the VM host or to make sure there are no configuration errors. TIP: How to tell whether or not agentless data collection is working View the utilization meters on the Visualization tab of the CMS. When meters display data and no errors, then data collection is configured correctly and working for those systems. Utilization pop-up text from icons to the right of the meters provide details on errors or warnings encountered. You can also run capcollect (or OptimizeCapacity AdvisorCollect Capacity Advisor Data...) and look for any errors or warnings in the output. Note that it takes up to 10 minutes after configuring systems for agentless data collection before data is visible in Capacity Advisor or Virtualization Manager. (See Supported collection configurations (page 17) to learn which configurations will have agentless data collection.) No network connectivity between the CMS and the managed node This is often a source of errors, once a system has been configured and data collection is initially working, but subsequently fails. Suggested action: Check that the following situations have not occurred: Is the host shutdown? Is the host hung, or otherwise not responding? Has the NIC or NIC driver on the host failed? Is a network cable unplugged from the host or switch? Are there other physical issues (for example, a port on a switch failing)? Are DNS and DHCP working correctly? (the system's IP address is not in use by another host, for example) Is a firewall blocking connectivity? Incorrect credentials for the managed node Suggested action: Confirm that system credentials are appropriate for the data collection method and the operating system or hypervisor software. See the HP Insight Dynamics 6.2 Getting Started Guide for information on system credentials. Unsupported data collection method for the managed node This situation is less likely with Insight Dynamics 6.0 release. Suggested action: Make sure the OS is supported for use with Insight Dynamics. Collection agents or services are either not running or are hung on the managed system or CMS Suggested action: For systems using agentless and virtual machine management data collection, make sure the corresponding services are running on the CMS and are not hung. If it is suspected

166

Troubleshooting in Capacity Advisor

that they are hung, (because all the above situations are fine, but still no data), first try restarting the individual services: For a Windows CMS, restart: HP Agentless Data Collector Service (the agentless collector service for Windows systems) HP Agentless Collection for Linux Systems (the agentless collector service for Linux systems) HP Insight Control virtual machine management (the VMM service) For an HPUX CMS, type from the command line:
# /sbin/init.d/hp_capad_service stop Stopping HP Agentless Collection for Linux Systems... Waiting for HP Agentless Collection for Linux Systems to exit... Stopped HP Agentless Collection for Linux Systems. # /sbin/init.d/hp_capad_service start Starting HP Agentless Collection for Linux Systems... Started HP Agentless Collection for Linux Systems.

If restarting the service(s) does not work, try rebooting the CMS. Other possibilities For suspected WMI issues on Microsoft Windows nodes (applies to agentless collection on Windows and virtual machine management/Hyper-V data collection), if nothing else works, try running the following command on the managed system to re-register WMI performance classes that may have become un-registered, causing data collection errors:
wmiadap /f

For agentless collection on Linux, make sure that SSH (sshd) is running on the managed system.

Data may appear to be old when it is not

When time or time zone on a managed node is set incorrectly (that is, it is not synchronized with the clock time on the CMS), the user may collect data and see only old dates for data collected. Suggested action: You must complete the following tasks (the process is different for each operating system): 1. Correct the time or time zone on your managed node. 2. Stop and restart the Utilization Provider daemon where the UP is in use. Brief instructions for these tasks are provided here.

Setting the time or time zone

On an HP-UX or Linux managed node, use the date(1) command to set the correct time. On an HP-UX system, the source of the time zone varies depending on the local configuration. See the setting for the TZ variable in the files /etc/profile or /etc/TIMEZONE or the file /etc/ defaults/tz, if the TZ variable is not set. (For more information, see the manual pages for ctime(3C) and environ(5). On SuSE Linux, see the file /etc/sysconf/clock. For other versions of Linux, consult the operating system documentation. On Microsoft Windows, right-click on the time displayed at the right end of the task bar and select Adjust Data/Time. Select the Time Zone tab on the dialog box and select the correct time zone from the drop-down list at the top. Click OK to close the dialog box and use the new time zone.

Stopping and restarting the Utilization Provider daemon

On HP-UX and Linux, use the following command: kill `ps -ef | grep utild | grep -v grep | awk '{ print $2 }'` On Windows 2003 Server: StartManage Your ServerTools and UpdatesAdministrative ToolsServices. Look for HP UtilProvider Data Collector in the Name column. Right click on the row and select Stop. Wait for it to stop and then right-click on it again and select Start. Close the Services window, the Administrative Tools window and the Manage Your Server window.
Data may appear to be old when it is not 167

Data seems to be incorrect or lost

VM guest resource utilization appears to exceed the resource utilization of its VM host When viewing historical resource utilization data in a profile viewer, it can appear that the utilization of a resource by a given VM guest exceeds the utilization of that resource by its VM host at a given instance of time. (For example, you might see the I/O usage occasionally exceed the VM host's high-water mark value (the dashed blue line in a profile viewer graph). In reality, it should never be possible for a VM guest's resource utilization to exceed that of its host, since the utilization shown for a VM host is the aggregation of a resource's utilization for all VM guests running on that host. Yet this does occur on rare occasions due to differences in how the data was collected, interpolated, and averaged into the 5minute intervals that Capacity Advisor stores in its database. Such anomalies become insignificant when the data is averaged over sample intervals greater than 5 minutes. Note that this situation typically occurs only when a single guest is running on the host and is creating a very large load on the host. Peak utilization in a scenario is greater than 100% Though this situation is rare when you first create a scenario, it can occur in the following situations: When virtual machines are modeled to be using a lot of I/O bandwidth, because some hypervisors will give the VM more CPU time than seems possible given the virtual processors assigned to the VM. When forecasting growth of workloads into the future. Over time, the forecast model will show workloads growing beyond the size of their hosts. When a real system simulated in a scenario is down-sized during the useful life of a scenario. The scenario will retain the original description of the system, but will be plotting data captured from the smaller real system. As you begin to edit the systems in the scenario, you can easily edit attributes in a way that will cause the simulated data to exceed 100% utilization. Use the data displays in the scenario editor to help you check the validity of the simulation you have constructed, and watch out for the following situations: When editing simulation system attributes, or when importing data using capprofile, be aware of discrepancies in clock speed or memory between the real system and the simulated system. To associate the characteristics of the real system from which data is being imported to the simulation system, use the -o -S options with the capprofile command. When converting standalone servers to VMs, be sure to include an appropriate virtualization overhead in the utilization calculation for the new VMs. (See CPU Virtualization Overhead % for more information on this calculation.) Socket count is missing or seems incomplete in population report Socket information is not always available due to limitations in data collection from some platforms or when leveraging data collection techniques that do not include socket count in their collection. There is no remedy in these situations. Workload performance seems inaccurate Using benchmarks for data normalization is new with the 6.0 release. This change affects workloads defined with static profiles in previous releases because they use clock speed to determine performance. Suggested action: Such workloads that are still used for planning should be redefined or edited in Capacity Advisor 6.0 to improve the accuracy of the performance measure. See Creating a workload (page 100) and Editing a workload (page 101). CPU utilization seems high on managed nodes running Microsoft Windows 2003 Server Agentless data collection might not be accurate on hyper-threaded systems. Suggested action: Update Microsoft Windows 2003 Server so that it correctly reports the number of physical hyperthreading-enabled processors or the number of physical multi-core processors. See Microsoft Support for this issue. Socket and core count seem off on Microsoft Windows 2003 and HP-UX 1 1 v2 (IA and PA) systems Windows 2003 and HP-UX 11 v2 (IA and PA platforms) operating systems may not correctly
168 Troubleshooting in Capacity Advisor

report the number of processor sockets in a multicore/hyperthreading environment. Suggested action: The following patches are required to correct this issue. For Windows 2003, apply the KB932370 patch. For more information, see http:// support.microsoft.com/kb/932370/. For HP-UX 11 v2, apply the PHKL_37803 patch. You can download this patch from ftp:// us-ffs.external.hp.com/hp-ux_patches/s700_800/11.X/PHKL_37803. After downloading, execute the command sh PHKL_37803, and install the depot file that is generated. No patch is necessary for Windows 2008 or HP-UX 11 v3. This information does not apply to HP-UX 11 v1. Data seems to have disappeared The profileID that Capacity Advisor uses to store whole-OS performance data (profiles) is based on a system's network name, as currently discovered in HP SIM (as seen in the System Page for the managed node).* If a system is later re-identified, but with a different network name, any data collected under the old name will no longer be associated with the managed system under its new network name. The data may still exist in the database, but because it is no longer identified with the managed system from which it was collected, it cannot be viewed or used for capacity planning. The following are some examples of how this can occur: An VMware ESX VM guest is initially discovered by HP SIM horizontally only, with no IP address or host name (only the ESX host is explicitly discovered in HP SIM, and VMware Tools are not installed/running on the guest). Later, the guest is discovered with a valid host name/IP address (that is, VMware Tools are subsequently installed on the guest). (Horizontal discovery can also find Microsoft Hyper-V hosts with a similar effect if the guests are later rediscovered with valid host name or IP address.) If a system is multi-homed and its multiple IP addresses or network names are discovered in HP SIM, only one "system node" is recorded in HP SIM to represent that server (the Primary IP Address). This node will contain the list of IP addresses and network names for that system. HP SIM randomly selects which IP address and network name pair becomes the default Primary IP Address used for the node's short name. If you edit the System Properties and change the "Primary IP Address", any data associated with the previous workload name reference will be lost. A system is initially discovered by IP address ONLY (for example, in a non-DNS environment). Later the system is identified in HP SIM by its fully-qualified host name (when DNS is subsequently enabled in the environment). Also in a non-DNS environment, a Windows system may be initially discovered by its NetBIOS name. If DNS is later enabled in the environment, that system may be subsequently identified by its fully-qualified host name. Suggested prevention: Make sure that all managed systems are identified the way you expect in HP SIM as soon as possible, and that they will remain identified that way during the period that you intend to collect data for those systems. For example: For VMware ESX VMs, if you ever plan to install VMware Tools on the VM guests, install the tools on all the guests OR enter the host name or IP address of all guests in the HP SIM discovery task, rather than depend on horizontal discovery. (This latter option should be applied to Hyper-V hosts also.) For multi-homed systems, discover only one IP address, or set the Primary IP Address immediately after discovery to insure that you have set the final name that you want the node to have before running Insight managed system setup wizard and data collection. If you are using DNS (or are planning to use DNS), make sure all systems are correctly discovered with a fully-qualified host name in HP SIM. Recovering system profile data lost due to a network name change: 1. Determine the name that the system was previously identified as. If not sure what the "old" name was, run capprofile to list the available profiles in Capacity Advisor. 2. Export the data from the old profile to a CSV file using capprofile -x.
Data seems to be incorrect or lost 169

3. Import the exported profile into the "new" profile using capprofile -i. For other issues where data seems to be incorrect, see: Data for node appears to differ from one profile viewer to another (page 173) A configuration change is not immediately visible in all Insight Dynamics products (page 173) Data may appear to be old when it is not (page 167) I reused a previously removed server name or IP address, and Capacity Advisor is showing an error. This situation can occur because workload definitions are currently associated with an OS instance using the fully qualified domain name (FQDN) and/or an IP address as the unique identifier for tracking the relationship between an OS instance, a workload, and the data collected for the workload and server. Keeping a record of this association allows Capacity Advisor to track an OS instance when it is moved onto new hardware and to retain the data association. As a result of keeping the workload association, when you remove a managed server from discovery by HP SIM, Capacity Advisor still retains a record of the workload, but it assumes the workload is parked, rather than deleted. Suggested resolution: Remove the parked workload(s) immediately after you remove a managed server when you know that you do not want to retain the associated workload utilization data. It is best to do this before reusing the FQDN or IP address. To remove a parked workload, click the Virtualization Manager Workload tab and select the parked workload for deletion. If you have already reused the FQDN or IP address, open the Virtualization Manager Workload tab, and check to see if the workload in question is associated with a different hostname. Remove the workload from this location. If the workload is not referenced on the Workload tab, you can delete the workload with the following command from the CLI: gwlm delete --workload=workload_name This will remove the association between the workload and its collected data. The next scheduled data collection (usually done nightly) will delete any non-referenced profile data. Capacity Advisor should correctly recognize the new server association from this point on.

Data cannot be imported

Cannot import PMP data This can occur in the case where a server, for which you already have PMP data collected, is discovered by HP SIM using WBEM instead of SNMP. Suggested resolution: Rediscover the server using SNMP and turn on PMP monitoring. This populates the PMP database with the values that Capacity Advisor needs in order to import the data associated with this server. Then import the existing data into Capacity Advisor. Thereafter, if you want to rediscover the system using WBEM, you may do so; PMP data collection should work properly at this point.

Out-of-memory errors in the Java heap

A few situations can cause the Java heap to run out of memory. Spiking the mxdomainmgr server process When capcollect is executed, its initial invocation causes a temporary spike in memory use of the server process named "mxdomainmgr". If the HP SIM server is currently managing a large number of systems, there is a small chance that this spike in memory could cause the server process to reach its maximum configured memory allocation. Suggested action: See the Insight Dynamics install guide specific to your OS platform for more information on tuning configuration parameters . Editing a scenario containing a large number of systems and/or workloads When using an "Edit Scenario" screen in Capacity Advisor, the number of workloads included in the scenario and the selected data range to use for analysis will affect how much memory is used in the HP SIM server process to read and analyze the scenario. Initially editing the scenario will invoke the action to
170 Troubleshooting in Capacity Advisor

read and analyze the utilization data of all systems and workloads defined in the scenario. The greater the number of systems and the longer the date range, the more memory and time is consumed to read and analyze the utilization data. Suggested action: Experiment with different combinations of systems, workloads, and data ranges to arrive at a manageable, but still useful scenario. Multiple users running simultaneous automated what-if actions Executing an automated what-if action will cause an increased use of memory and CPU time for the length time required to provide a solution. With multiple users running automated what-if actions simultaneously, the server process can reach its maximum configured memory allocation. Suggested action: See the Insight Dynamics install guide specific to your OS platform for more information on tuning configuration parameters. Running reports with very large data sets or when CMS is busy During the execution of Capacity Advisor reports, consumed memory is monitored. Should consumed memory reach a given threshold (85% of total JVM memory) the report execution stops and informs you that there is insufficient memory to complete the report(s ) Users trying to create more modest or even small reports could see this message if the rest of the system is busy. Remedies: Increase heap memory size allocated to the JVM and/or reduce memory pressure on the CMS. Try to generate the report again. Exporting four years or 3 MB of data into Capacity Advisor for profiling capprofile aborts with data sets of this size. Suggested action: Export multiple, smaller chunks of data.

When working with reports

This section discusses problems that you may encounter when creating or printing reports. HTML report format is too wide for available printer Though the width of reports is restricted as much as possible to work with standard printer paper sizes, in some reports, data might be cut-off in a printed copy of the HTML report. Suggested action: Export the report CSV file to a spreadsheet, and print the wide tables from that format.

When working in the scenario editor

This section discusses behaviors of the scenario editor that may cause confusion. Edit Scenario window not visible A couple situations can cause you to lose the Edit Scenario window. The window can be blocked by a browser pop-up blocker when you initially try to open it. Suggested action: Check that you have pop-up blockers turned off in the browser that you use to control Capacity Advisor functions. In the case where the Edit Scenario window is already open in Mozilla Firefox, but is hidden beneath other windows when you create a new scenario, it is not obvious that the window has refreshed with your new scenario information. Suggested action: set Firefox to allow Javascript to raise or lower windows. Then, when you create a new scenario, the pre-existing Edit Scenario window will rise to the forefront of the display. Systems in scenario are not available due to licensing or authorization issues When a scenario is first created, some systems may not yet be licensed; or over time, licensing on an existing system may be removed or may have expired, making it impossible for Capacity Advisor to access data or continue to use the system in a scenario. Suggested action: When this occurs, the Edit Scenario screen will show a message that allows you to remove the system from the scenario so that you can continue using the scenario without that system. You can either have your system administrator apply a license to a system to make it usable in the scenario, or click the links provided in the message to remove all systems having the problem (or to remove each system individually). In situations where you decide to remove the systems from the scenario, you will also want to check the change record for any entries related to the system (What-If ActionUndo/Edit/View Applied What-If Actions). Delete any related entries to completely clean up the scenario so that other errors will not be triggered by the unlicensed or unauthorized system entries in the change record.
When working with reports 171

TIP: When a scenario is newly created, it is unlikely that any changes will be recorded for unlicensed or unauthorized systems in the change record. A lack of user authorization on systems in a scenario can also affect the usefulness of the scenario for planning. As above, you can obtain authorization to use the systems or remove them from the scenario. Systems in scenario no longer available scenario seems corrupted Because names for what-if systems must be unique (they do not match names for existing systems on a real network), it is possible that real systems can be discovered with matching names after a scenario is created with systems having imagined names. When this occurs, the scenario change record (Undo/Edit/View screen) indicates an error; the scenario is corrupted and cannot be repaired. Suggested action: Create a new scenario, replacing the no-longer-unique what-if systems with new, uniquely named systems. Delete the corrupted scenario. Note that this naming corruption can also occur when using what-if workloads or what-if VMware DRS clusters in a scenario. The problem and remedy are the same in each case. I want to reuse a system name, but I'm seeing a name duplication error Name duplication errors can occur in these situations: when trying to create a what-if system using the same name as an existing system. You cannot reuse an existing system name. when trying to create a what-if system using the same name as a what-if system already in use in the same scenario. Suggested action: Edit the system attributes of the original what-if system (What-If ActionEdit System...) This remedy will not be sufficient if you have defined the original what-if system to have no power calibration, and then decide that you want the system to have power calibration. The Edit System screen does not provide the opportunity to edit power settings. Where it is important to reuse the system name and add power calibration, do the following: Select the original what-if system and remove it from scenario. (EditRemove Systems) Delete both the create system and remove system actions from the scenario change record. (What-If ActionUndo/Edit/View Applied What-If Actions) Re-create the system using the same name, but with new attributes, including power calibration. (What-If ActionCreate Systems...)

Workloads no longer available in a scenario With the 6.0 release, monitored workloads on Linux are no longer supported or recognized by Insight Dynamics components. This means that scenarios containing representative Linux systems that once had monitored workloads will be broken. Suggested action: Remove these systems from the scenario (EditRemove Systems...), and then re-add them EditAdd Existing Systems...). A profile viewer has error message and no profile graph The error message that you would see in this situation:
Unable to write the following file: I/O error writing PNG file!

This occurs when a profile viewer is unable to write temporary files to the CMS storage space. Suggested action: Check that permissions are correct for writing to the storage space, and check to see if the storage space is full.

When working with power

Data collection method for Linux systems affects access to automatic power management Utilization data for Linux systems are obtained using an agentless data collection method that is automatically assigned to managed Linux systems by the Insight managed system setup wizard.

172

Troubleshooting in Capacity Advisor

Automatic power calibration can be done on managed Proliant Linux systems with no additional agents or providers. Automatic power calibration is supported for Integrity Linux systems when, in addition to the agentless data collection, the Utilization Provider (UP) is configured on managed nodes running supported Linux distributions. However, to obtain the UP, you must install it as part of the Integrity Linux distribution or from a separate web download. NOTE: The Utilization Provider does not support Integrity SUSE 11 or RHEL 5.5; these Integrity Linux systems must be manually calibrated.

No power metrics appear for simulated VMware DRS cluster This situation occurs when VM hosts that have not yet been calibrated for power are added to a VMware DRS cluster in a scenario. Suggested action: 1. Open the scenario change record (What-If ActionUndo/Edit/View Applied What-If Actions) and delete from the cluster all VM hosts that were not previously calibrated. (See Undo/edit/review applied what-if actions in a scenario (page 91) .) 2. From the scenario editor Systems tab, select the VM hosts that you want to calibrate, and then select EditCalibrate Power (All Selected Systems). Calibrate the systems. (See Calibrating multiple systems at once (page 109) .) 3. Add the calibrated VM hosts to the cluster by selecting What-If ActionConvert/Add to VMware DRS Cluster. (See Assigning VM hosts to a VMware DRS cluster in a scenario (page 96). )

Workload and system relationships may not match when comparing Capacity Advisor and Virtualization Manager information
A configuration change is not immediately visible in all Insight Dynamics products This information is updated every 5 minutes, but there still can be a period of time when the information that you can see in the Insight Dynamics Visualization tab may differ from that presented in Capacity Advisor. Suggested action: Click to the Workload tab in the Virtualization Manager and then click the "Refresh Data" link on the far right corner of the screen above the table that lists workloads discovered by HP SIM. HP SIM identification of a VM host and its virtual machines inconsistent If you open the Capacity Advisor "Edit Scenario" screen and see this message:
Error generating screen. Attempting to create second instance of (Scenario_systemLayout_nameHeader_system_name_popupContent*)

this means that the HP SIM identification of a VM host is inconsistent with the identification of the virtual machines associated with it. Suggested action: Re-identify the VM host and its virtual machines to correct this issue. See the HP Systems Insight Manager 6.2 online help to learn how to identify or discover systems from the top menu bar or from the command line. You need to be a privileged administrator user or root to do this action. You may then want to click the "Refresh Data" link on the Virtualization Manager Workload tab to ensure the information is also up-to-date for Capacity Advisor. If this problem persists, you may need to run vseassist on the VM host to determine why HP SIM is not correctly identifying the VM host and its constituents. Data for node appears to differ from one profile viewer to another Though a profile viewer looks the same and behaves similarly from whichever location it is accessed, the data displayed for a node may indeed differ it may be actual historic data or an aggregation of data, depending on the location from which the viewer is accessed or the type of system being viewed. For a discussion of data handling in a profile viewer, see Using the Profile Viewer (page 67).

Miscellaneous user interface issues

Menu fly-out forces scrolling in Microsoft Internet Explorer browser This occurs with some IE browser security settings. When you mouse over the menu picks, the menu looks compressed,
Workload and system relationships may not match when comparing Capacity Advisor and Virtualization Manager information 173

showing one entry and a scrolling mechanism for the other menu choices. HP SIM checks for this setting on entry and shows this message to help you correct the situation:
Your browser's zone security settings are not compatible with the HP SIM popup menu. The following setting must be enabled in your current zone: Internet Options | Security | Custom Level | Miscellaneous | Allow script-initiated windows without size or position constraints (This setting is enabled by default for the "medium-low" security level, such as the "local intranet" zone.)

174

Troubleshooting in Capacity Advisor

H Capacity Advisor messages

Certain messages that you might see when working within the Capacity Advisor user interface or that are about data collected for use in Capacity Advisor are explained in this section. Messages appearing in the user interface that are self-explanatory are not included here.

Command error messages

Within the messages sections, messages appear in alphabetical order. Messages that start with system_name are placed at s in a list. During data import using the capprofile command, sample_time is the timestamp in local time if the import profile includes it (YYYYMMDDhhmm), or the time in UTIS, if not. NOTE: A message such as the following may precede other messages: system_name: System information is not available to the WBEM provider. Collection from this system cannot proceed until this situation is corrected. detailed_message where system_name is the name of an HP-SIM managed node from the names specified on the command line, and detailed_message is one of the Capacity Advisor data collection messages. For additional information, refer to the Command reference (page 133) in this guide, as well as the HP Systems Insight Manager 6.2 online help. Table H-1 Error Messages and Their Correction
Message Collection failed on 1 system or Collection failed on n systems. Possible cause Appears at the end of output if data collection failed on any system. To correct Examine the output. If information there seems insufficient, run vseassist to troubleshoot connection errors. You can also check the configuration of the system(s) in the Insight managed system setup wizard. Use mxstart to start HP SIM on the central management server.

Could not access the HP SIM instance on HP SIM is not running. this system; nested exception is: java.net.ConnectException: Connection refused. Error collecting utilization data for whole-OS workload "system-name" no data collected. The Utilization Provider may be missing or incorrectly configured on the managed node. or The system may not be Error collecting utilization data for licensed for Capacity Advisor workload "workloadname" on data collection. "system-name" - no data collected. The workload may have been or moved since the last automatic update in Capacity Advisor Error collecting physical CPU utilization (update occurs every 5 data for HPVM "vm-host" from HPVM minutes). Host "vm-name" - no data collected.

Check that the Utilization Provider is running on the system. Check that the system is licensed for Capacity Advisor. Check that the workload is still associated with the same system (is Capacity Advisor information up-to-date). Run vseassist to troubleshoot connection errors.

Command error messages

175

Table H-1 Error Messages and Their Correction (continued)

Message Error collecting utilization data for whole-OS workload "system-name" some data collected. or Error collecting utilization data for workload "workloadname" on "system-name" - some data collected. or Error collecting physical CPU utilization data for HPVM "vm-host" from HPVM Host "vm-name" - some data collected. Error: Missing Capacity Advisor authorization for node: system_name Permissions for this node are not Ensure that the node is licensed, and in place. that appropriate permissions for the node are set. Run vseassist to troubleshoot connection errors. You can also check the configuration of the system(s) in the Insight managed system setup wizard. Ensure that the system where the workload is running has appropriate authorization or credentials, then collect data on that system again. Run vseassist to troubleshoot connection errors. You can also check the configuration of the system(s) in the Insight managed system setup wizard. Check access and process activity. Run vseassist to troubleshoot connection errors. Possible cause To correct

A system may have been down Check that the server is up, and during the collection period. start a new collection. The workload may have been Check that the workload is still moved since the last automatic associated with the same system (is update in Capacity Advisor Capacity Advisor information (update occurs every 5 up-to-date). minutes). Run vseassist to troubleshoot connection errors.

Error: No data has been collected for the Missing authorization or specified workload. credentials for a system.

system_name: Another HP SIM Central See message text. Management Server may be accessing this system. CIM_ERR_NOT_FOUND: The requested object could not be found: Instance not found for RpID: FSS_3 and datetime: date_time, GUID: n. system_name: Error attempting to access See message text. the WBEM server; CIM_ERR_NOT_FOUND: The requested object could not be found: Instance not found for RpID: rpid and datetime: 2006...,GUID: n. system_name: Error creating object. The system specified by system_name during data collection is running Version 2.00.09 of HP-UX WBEM Services without required patches.

Run vseassist to troubleshoot connection errors.

For systems running HP-UX 11.11, apply patch PHSS_34428; for systems running HP-UX 11.23, apply patch PHSS_34429.

Command warning messages

Within the messages sections, messages appear in alphabetical order. Messages that start with system_name are placed at s in a list. These messages alert you to specific conditions present in the user interface or data collection. Follow-up actions may or may not be necessary. For additional information, refer to Command reference (page 133) in this guide, as well as the HP Systems Insight Manager Technical Reference Guide available at http://h18013.www1.hp.com/ products/servers/management/hpsim/infolibrary.html.

176

Capacity Advisor messages

Table H-2 Warning Messages in Capacity Advisor

Message 1 warning issued or n warnings issued A series of overlapping samples begins Samples imported with Overlapping samples are automatically at time sample_time. The overlapping capprofile that overlap in time ignored or invalidated in Capacity samples starting at this time are ignored. cannot be interpreted. Advisor. Import the data again, taking care to designate date ranges that do not overlap. Collection from system_name is not supported on an HP-UX CMS. Collection from VMware and MSVS Virtual Machines is only supported from a Windows HP SIM CMS. A sample line in the file imported with capprofile contains values that are improperly formatted. Discover the system from an HP SIM CMS running on a Microsoft Windows system and collect data from there. The improperly formatted values will be automatically marked as invalid, and will not be included in Capacity Advisor reports. Some formatting errors can be manually corrected. See the capprofile(1M) command reference page for format examples. Use a profile viewer to determine if the sample contains a sufficient number of valid data points to provide a meaningful report. Java Heap Space. Please see the HP See Out-of-memory errors in the See Out-of-memory errors in the Java Capacity Advisor User's Guide for more Java heap (page 170). heap (page 170). information on this issue and possible solutions. Missing sample for 1 time interval at time Samples imported with The missing samples will be sample_time. capprofile are missing for one automatically marked as invalid and will not be included in Capacity or more sample intervals. or Advisor reports. Use a profile viewer Missing samples for n time intervals at to determine if the sample contains a time sample_time. sufficient number of valid data points to provide a meaningful report. Negative sample value at time sample_time has been ignored. A sample imported with capprofile contained a negative value for the value of a metric. The negative samples will be automatically marked as invalid and will not be included in Capacity Advisor reports. Use a profile viewer to determine if the sample contains a sufficient number of valid data points to provide a meaningful report. Ensure that the CMS has access to WBEM. Run vseassist to troubleshoot connection errors. Add the required credentials to the systems where you plan to run Capacity Advisor, or run the cimserver process. You can also run vseassist to troubleshoot connection errors. Probable cause Appears at the end of output if any warnings were issued. To correct Check for advisements and take corrective action if desired.

Improperly formatted sample values at time sample_time have been ignored.

No systems are available from HP SIM in the HPVSE collection. No WBEM credentials are available for system "system_name. Please verify that a valid WBEM account and password for this system are configured in HP SIM (Options->Protocol Settings->Global Protocol Settings).

CMS access to WBEM, using Bastille, ipf, or other means, has been shut down. Either no WBEM credentials have been entered in HP SIM or HP SIM could not successfully use the credentials entered. The latter can happen when acimserver process is not running on the system.

Command warning messages

177

Table H-2 Warning Messages in Capacity Advisor (continued)

Message Sample time sample_time is not aligned to hour intervals. Probable cause To correct

Capacity Advisor cannot analyze Synchronize the managed node clock utilization across multiple to the CMS system clock. systems or servers when system clocks (and therefore, data timestamps) are not synchronized.

Skipping system_name collection from The system or server is running the some_operating_system operating an operating system unsupported system is not supported. by VSE. System system_name has incomplete HP SIM has not discovered system information. Check the system's enough information about this status in HP SIM. system for capcollect to be able to collect data from the system. capcollect requires that the System Type attribute has the value server to collect from a system. system_name: HP SIM requires trusted See message text. certificates for managed systems but no trusted certificate exists for this system. system_name: The Utilization WBEM Provider is not installed. See message text. From the HP SIM All Systems page, click the system name to go to the HP SIM System Page. On the identify tab, click the + next to Product Description to expand it. If the System Type is unknown or unmanaged, capcollect cannot collect data from that system. Change the System Type to server. Set up the trusted certificate by manually installing the system's certificate into the HP SIM Trusted System Certificate List. Install the WBEM utilization provider on the system. Correct the global or system protocol settings for the affected system in HP SIM. You may need to rerun discovery to have the settings take effect.

system_name: The WBEM credentials The capcollect command provided by HP SIM were not accepted cannot use the WBEM credentials by the WBEM server. provided by HP SIM, perhaps because of recent changes to the user ID or password. system_name: The WBEM server is not running and should be restarted. system_name: Upgrade the Utilization Provider on this system to version A.01.06.00.00 or later.

The WBEM provider on the On the managed system, execute the system is not running and should command be restarted. /opt/wbem/sbin/cimserver See message text. See message text.

system_name: Unable to contact the A network or system problem Run vseassist to troubleshoot WBEM server. See the capcollect(1M) prevents contact with the WBEM connection issues. server. manual page. system_name: System information is not available from the WBEM provider. Collection from this system cannot proceed until this situation is corrected. The Name Resolution Service could not See message text. resolve localhost on the CMS. To correct this, make sure that either the name localhost can be resolved on the CMS or change the CMS_HOSTNAME setting in /etc/opt/vse/vseprefs.props to a hostname for the CMS that can be resolved. See the hosts(4) and nsswitch.conf(4) manual pages. Run vseassist to troubleshoot connection issues.

If you prefer not to use the method described in the message, change the value for the CMS_HOSTNAME property in the vseprefs.props file from localhost to some other name that resolves to the IP address of the CMS.

178

Capacity Advisor messages

Table H-2 Warning Messages in Capacity Advisor (continued)

Message The system attribute "attribute-name" is not available from HP SIM for the workload-name workload. Either run "Identify" on the system in HP SIM and export the profile again, or correct these fields in the header of the exported profile before importing it. Probable cause To correct

If HP SIM has not correctly See message text. discovered all of the system attributes (operating system type, model, CPU count/speed, and memory size) some of the attributes needed to export the profile using the capprofile command are not available. If the profile data originated from a capprofile export, re-export the data after running OptionsIdentify Systems...on the system in HP SIM, or manually correct the values in the header. See the capprofile(1M) command reference page for an example of a correctly formatted file. Install the HP VM WBEM provider (vmProvider) on the virtual machine or correct the configuration problem. For help with using vseassist, see the HP Insight Dynamics 6.2 Getting Started Guide.

The system attribute "attribute-name" When importing a file using must be specified before this profile can capprofile, the input file be imported. header must contain correct values for the system from which the profile data was gathered. If one or more attributes have the value <UNKNOWN>, the profile cannot be imported. The system "system_name" has no workload defined. Make sure to select ToolsVSE Management...in HP SIM before running this command for the first time. For HPVM Guests, please be sure that the HPVM WBEM provider is properly configured. If problems persist, run VSE Assist to further diagnose errors. The system system_name was not found in the HP SIM database. An HP virtual machine may be discovered by HP SIM and labeled as a standalone server if the system does not have a properly configured WBEM provider for HP VMs. Such a system cannot be collected from until it is discovered by HP SIM correctly.

The system name specified on the Verify that the name is spelled command line is not known to HP correctly or add the system to HP SIM. SIM. Set authorizations as needed. For information on user authorizations in VSE, see HP Insight Dynamics 6.2 Getting Started Guide. Make sure that: 1. Your user name has been added to HP Systems Insight Manager. 2. Your user name and password, if specified, are spelled correctly. 3. HP Systems Insight Manager is running. 4. You used '--' for any long options and double quotes if your user name contains a domain, for example, commandname user mydomain\myusername pass mypassword If the system is booted, go to the System page in HP SIM and resume monitoring using the link on the Tools & Links tab, then run Discovery on the system. If the system remains disabled, delete the system from HP SIM and rediscover it. Run vseassist to help locate the problem.

The user has none of the required toolbox See message text. authorizations on node cms_name, where cms_name is the name of the CMS where the command was run. There was a problem connecting to the HP SIM server.

Unable to collect from system The system may be an unbooted "system-name" because it is disabled in VM or an un-initialized blade. HP SIM.

Unable to contact the WBEM server. See A network or system problem is preventing contact with the the capcollect(1M) manual page. WBEM server.

Command warning messages

179

Table H-2 Warning Messages in Capacity Advisor (continued)

Message Values at duplicate sample time sample_time replace previous values for this time. Warning: Ignoring unknown workload workload_name on system_name Probable cause More than one sample imported with capprofile has the same time stamp. Workload on the utilization provider on system_name is not known to VSE. No utilization data is collected for this unknown workload. To correct The most recent sample is kept.

On the CMS managing system_name, open the HP SIM All Systems list, click the system name to go to the HP SIM System Page.

Warning: Overlapping workload definitions detected on system_name. Warning: the system clock on system_name is ~60 minutes, ss seconds ahead of the system clock on the CMS; this may render the utilization data unusable for planning purposes. If the time on the managed node is correct, the node's version of 'HP WBEM Services for HP-UX' may be older than the minimum, A.02.00.08.

The sum of workload utilizations Redefine the workloads so that their exceeds system utilization. utilization limits fall within the resource allocation for the system. capcollect relies on WBEM to Install a version of the WBEM Services report the local time on a system, Core Product that is 2.00.08 or later. but Version 2.00.07 of the WBEM Services Core Product for HP-UX reports the local time incorrectly. Messages that do not indicate a time difference of about an hour and for which actual times on the servers are not an hour apart, are not likely to be caused by the wrong WBEM version. When systems are used together Ensure that clocks on systems in the in a scenario, Capacity Advisor scenario are synchronized to the clock assumes that the time axis of the on the CMS system. utilization graphs for all systems is the same. The time axis is obtained from the system clock on the system where the utilization data is gathered. If the system clock is not synchronized with the other systems and with the CMS, the Capacity Advisor summed utilization traces may not be correct. This error message is issued if the time difference between the system for which data is collected and the CMS is more than 15 minutes.

Warning: the time difference of nnn seconds between the system clock on system_name and the system clock on the CMS may render the utilization data gathered unusable for planning purposes.

HP Smart Solver error messages

In situations where the Smart Solver is unable to produce a solution, one or more error messages are displayed. Solver error messages are shown in red text on the user interface screen and describe the issues that prevent a solution from being found.

When available systems lack sufficient capacity

When workloads cannot be placed on any system because the available systems lack sufficient capacity in one or more resources, the workloads are excluded from the computation and listed in the Smart Solver Excluded Systems table. A summary line is included that reports the minimum system capacity required to place the workload(s).

180

Capacity Advisor messages

Figure H-1 Example of Smart Solver Excluded Systems table, part of the a Smart Solver Results screen

Remember that the Smart Solver includes utilization limits set for the workload, system, or scenario-wide when calculating desired capacity for the solution. Therefore, one way to correct the resource insufficiency could be to raise the utilization limits for the specified metrics. Another way is to select or add additional systems having at least the minimum required capacity. In the next example, the Smart Solver is unable to arrange the workloads such that they can all be placed on available systems, even though the systems have sufficient resources to place at least one workload per system. Figure H-2 Solver error messages when too few systems are available for the calculated required capacity needed

Here every workload can be placed on at least one system. However, the Smart Solver has concluded that there is simply insufficient total capacity across all systems to place all the workloads. In this case, the Smart Solver cannot derive a singular estimate of additional required capacity for a resource because an estimate depends on whether the remaining workloads will all be placed on a single system (thereby using the most restrictive utilization limits), or spread across multiple systems. As a result, a range of estimates is displayed: the first value specifies the total aggregate demand if all workloads were placed together, while the second value is the summed demand for each workload if it were placed separately. The workload(s) used in the estimation are named. It is possible that different combinations of the same workloads and systems can result in failures on different metrics. The Smart Solver results might state that the failure to arrive at a solution is due to memory shortfalls, which occurred 100% of the time. Given the same workloads and systems but an alternate solution, the Smart Solver may identify that 80% of the failures were due to CPU overages while 20% were due to memory shortfalls.

When the threshold for invalid data is exceeded

The Smart Solver tracks placement attempts that were abandoned because the attempted aggregation of workloads would have exceeded the percentage of invalid data allowed for each system. (The invalid data threshold for each system is currently configured to be equal to the invalid data threshold specified by users for each workload.) In this situation, you would see a message similar to this:
Some placement attempts failed because workloads exceeded the 16% per-system invalid data threshold -Per-attribute exceedances: 15% CPU, 0% memory, 0% disk I/O, 0% network I/O

The above message indicates that, while trying to place workloads, 15% of the placement attempts failed because the resulting set of workloads would have exceeded the invalid data threshold for CPU allowed for each system. As a result, the returned solution was less than ideal because the Smart Solver had to rearrange workloads to keep those having significant invalid data in
HP Smart Solver error messages 181

non-aligned samples from being placed together on a system. The degree to which these solutions are less than ideal increases as the invalid data threshold is pushed to allow higher tolerances because there is no way to determine the true utilization for invalidated sample intervals. To resolve this issue, use a combination of the following options: Adjust the Maximum Invalid Data percentage allowed by the Solver. Adjust the Data Range in the automated task such that all workloads have sufficient valid data. Collect or import additional valid data to improve the data validity percentage. Adjust the workload forecast model data range selection to exclude invalid periods. If these steps are insufficient or cannot be done, remove the workloads from the scenario that have higher percentages of invalid data, and run the Solver on the remaining workloads to obtain the best placement for those workloads.

HP Smart Solver informational messages

While working on a solution, the Smart Solver notes any non-critical issues that it encounters. These issues are presented on the Solution Results screen in the "Smart Solver Solution Information" box. For example, in the following consolidation and load balance job: Figure H-3 Example 3. Solver information messages when workload requirements exceed available capacity

Here the Smart Solver reported that during the consolidation phase, workloads "metallica03" and "metallica04" were removed from consideration because their workload data exceeded the user-specified 5% threshold on the specified metrics. Any workload removed from consideration remained on its original system. Additionally, after the load-balance phase had completed, the Smart Solver noted that both new template systems were over capacity with respect to network I/O because the workloads placed there had no utilization limits specified for that metric.

182

Capacity Advisor messages

Glossary
90th percentile activate That utilization value in the selected time interval which 10% of the utilization values fall above, and 90% fall below or are equal to. When referring to a logical server, activate means to make a logical server definition available to be deployed into the computing environment. An active logical server is one that is currently operating within the computing environment. An inactive logical server is one that has been defined but is not currently operating within the computing environment. A core that has been turned on by the HP Instant Capacity (iCAP) software or during installation. Cores are activated with the icapmodify command (or the vparmodify command in an HP-UX virtual partition) while HP-UX is running. A logical server that has been bound to both an HP SIM node and a Insight Dynamics workload, and is bound to specific storage. Active logical servers can be in one of two states: powered on or powered off. See also inactive logical server, logical server. A program with a well-defined task that runs in the background and that is used to capture information or do processing tasks. The collection of inventory and performance data from managed systems without requiring installation or configuration of agents on the managed systems. The rate at which utilization of a resource is projected to change. 1. In HP Systems Insight Manager software (HP SIM), an association is created by discovery and identification of HP SIM system objects that are then associated with other objects. One type of association is containment. For example, clusters contain members, complexes contain nPartitions, and OS images contain resource partitions. In HP Insight Global Workload Manager software for Integrity (gWLM), a policy-workload association tells gWLM which policy to use to manage that workload's resource allocation.

activated core

active logical server

agent agentless data collection annual projected growth rate association

2. available resources average baseline business period Capacity Advisor capacity planning capacity-planning simulation central management server CLI cluster

Cells and I/O chassis that are not assigned to an nPartition; or cores, memory, and I/O resources that are not assigned to a virtual partition. These resources are available to be used in new partitions or can be added to existing partitions. The sum of all the utilization values divided by the number of data points for the selected time interval. A timeless demand profile used to generate demand profiles in forecasting. A meaningful time interval (a day or a week) for which to create an HP Insight Capacity Advisor software report. HP Insight Capacity Advisor software. The HP Insight Dynamics application that performs analysis and planning of workloads on a system or across a set of systems. The analysis of and planning for resource usage by workloads on a system or across a set of systems. The process of combining workload demand profiles, as prescribed by a scenario, to estimate the demand profiles of the systems that contain the workloads. Statistics gathered from the simulation can be summarized in reports. See CMS.

Command line interface. An operating system shell for direct entry of commands by the user. See also GUI. A set of two or more systems configured together to host workloads, such that users are unaware that more than one system is hosting the workload.

183

CMS

Central management server. A system in the management domain that executes the HP Systems Insight Manager software software. All central operations within HP SIM are initiated from this system. See CLI. A complex includes one or more cabinets that are cabled together and all of the hardware resources that they contain. A complex has a single Service Processor. See also server, system. Resource allocation restrictions imposed by either the customer (for example, workload placement restrictions), or the HP Insight Dynamics suite. See also policy. The actual data-processing engine within a processor. A single processor might have multiple cores, and a core might support multiple execution threads. See also processor. A set of resource-demand readings made at regular intervals for some period of time. The demand profile of a workload, system, or complex is used when doing capacity planning. Demand profiles can be based on historical data or computed as part of a forecast. 1. 1. In HP Systems Insight Manager software, to implement one or more components such as software, drivers, or licenses, rendering them under control of HP SIM. In system management applications, the process of finding and identifying network objects. In HP Systems Insight Manager software, discovery finds and identifies all the HP systems within a specified network.

command line interface complex

constraints

core

demand profile

deploy discovery

failover forecast forecast data range forecast model Global Workload Manager guest guest OS GUI

The operation that takes place when a primary service (network, storage, or CPU) fails, and the application continues operation on a secondary unit. A prediction of system utilization and workload demand profiles for some future time. A time interval specifying the set of historical data to use for generating a forecast. A combination of a forecast data range and a set of annual projected growth rates that are used to estimate future utilization. See gWLM. See virtual machine. The operating system that is running on a virtual machine. Graphical User Interface. A visually-oriented user interface in which components and actions can be selected by clicking on objects and menus instead of typing command lines. See also CLI. HP Insight Global Workload Manager software for Integrity. The HP Insight Dynamics application that allows you to centrally define resource-sharing policies that you can use across multiple HP servers. These policies increase system utilization and facilitate controlled sharing of system resources. gWLM's monitoring abilities provide both real-time and historical monitoring of the resource allocation. High availability. The ability of a server or partition to continue operating despite the failure of one or more components. High availability requires redundant resources, such as CPU resources and memory, in specific combinations.

gWLM

HA

184

Glossary

The high-availability status of a device group is usually indicated by the following notation.
N+ N The device group can experience a device failure and still function normally. The device group has just enough good devices to function normally. Subsequent failure of a device in the group can cause the cabinet to shut down. The device group does not have enough good components to function normally. If a cabinet is running and goes into an N- cooling state, then the cabinet is automatically shut down. If a cabinet has an N- power state, then devices in the group cannot be powered on. This means that if the cabinet is running, it continues running, but no additional devices can be powered on. If the cabinet is off and comes up in the N- power state, then none of its devices can be powered on.

N-

headroom

In general, the amount of a computing resource that is available on a system after all requirements for applications on the system are accounted for. In HP Insight Capacity Advisor software, requirements for applications include the utilization limits set for each application. See also relative headroom.

high availability host host name host OS HP Insight Control power management HP SIM

See HA. 1. A system or partition that is running an instance of an operating system. The name of a system or partition that is running an OS instance. The operating system that is running on the host machine. IPM

HP Systems Insight Manager software (HP SIM). HP SIM provides simplified, centralized management of multiple servers and platforms through a web-based, unified interface. HP SIM provides the platform and framework on which the VSE Management Software products are deployed. HP SIM provides administrators single sign-on access to HP SMH on managed servers (standalone or partitioned) from a central console. HP System Management Homepage. HP SMH is a web-based interface that consolidates and simplifies the management of a single HP-UX server. HP SMH is also available for Linux and Microsoft Windows systems. HP SMH integrates with HP Systems Insight Manager, the strategic platform for multisystem management. Intel Hyper-Threading Technology. The ability of certain processors to create a second virtual core that allows additional efficiencies of processing. This is not a true multi-core processor, but it adds performance benefits. True multi-core processors typically deliver much greater performance than equivalent hyper-threading technology. HP Instant Capacity. The HP Utility Pricing Solutions product that allows you to purchase and install additional processing power through the use of a two-step purchase model. Initially, you purchase system components (cores, cell boards, memory) at a fraction of the regular price because the usage rights are not included. These Instant Capacity components are inactive but installed and ready for use. When extra capacity is needed, you pay the remainder of the regular price for the usage rights to activate the components. If the regular price for the component is reduced by the time the usage rights are purchased, the remainder price is proportionally reduced, providing additional savings. Earlier versions of iCAP were referred to as Instant Capacity on Demand, or iCOD.

HP SMH

hyper-threading

iCAP

iCAP core

Also referred to as a core without usage rights, a core that is physically installed in an HP Instant Capacity (iCAP) system but does not have usage rights and is not activated. After obtaining
185

usage rights, iCAP cores can be turned on by the iCAP software or during installation. Cores with usage rights are activated with the icapmodify command (or the vparmodify command in a virtual partition) while HP-UX is running. iLO inactive logical server HP Integrated Lights-Out. An application that allows you to remotely configure, update, and operate server blades and standalone systems. A logical server that contains metadata but is not currently bound to a specific physical server or system. Inactive logical servers that have never been activated might or might not be bound to storage. See also active logical server, logical server. See iCAP. See iLO. See Integrity VM. HP Integrity Virtual Machines. A soft partitioning virtualization product that allows you to install and run multiple systems (virtual machines) on the same physical host system (Integrity server or nPartition). The Integrity server or nPartition acts as a VM Host for the virtual machines (also referred to as guests). The virtual machines share a single set of physical hardware resources, yet each virtual machine is a complete environment in itself and runs its own instance of an operating system (referred to as a guest OS). See also virtual machine, VM Host. In HP Insight Capacity Advisor software, data that could potentially skew reporting results and lead to inaccurate or misleading conclusions when capacity planning. Examples of events that Capacity Advisor can recognize as potential sources of invalid points include the following: System downtime during a data collection period Data manually marked by the user as invalid Partial collection from a virtual machine or a VM host See also missing data, valid data. HP Insight Control power management. An integrated power monitoring and management application that provides centralized control of server power consumption and thermal output at the level of the data center. It extends the capacity of data centers by enabling you to reduce the amount of power and cooling required for ProLiant and Integrity servers. Systems built on any version of the Intel Itanium architecture. A feature provided by HP Insight Virtualization Manager software, a logical server is a set of configuration and metadata that you create, activate, and assign to operate within a physical or virtual machine. An active logical server can be moved from one location to another, and its characteristics can be modified. This feature allows you to populate an enclosure, load balance servers, and evacuate servers in case of disaster; it allows you to provision resources only when needed and increase utilization of limited compute resources. See also active logical server, inactive logical server. License to use. One of the three main components of HP Insight Global Workload Manager software for Integrity (gWLM): CMS, agents, and LTU for each agent. The CMS allows you to control and monitor gWLM. The agents run on the systems where you are managing workloads. You install an LTU on each system that runs an agent in order to continue full agent functionality beyond the initial trial period. A resource that can be allocated and controlled by HP Insight Virtualization Manager software. Managed resources include: cores, memory, disks, and I/O bandwidth. A server or other system that can be managed by HP Systems Insight Manager software from a CMS . A managed system can be managed by more than one CMS. A workload that is managed by HP Insight Global Workload Manager software for Integrity (gWLM).

Instant Capacity Integrated Lights-Out Integrity Virtual Machines Integrity VM

invalid data

IPM

Itanium-based systems logical server

LTU

managed resource managed system managed workload

186

Glossary

management domain max 15-min

A CMS and its managed systems. Maximum 15-minute sustained: data given in the Utilization Metric Summary screen of the HP Insight Capacity Advisor software Profile Viewer, the highest value in the selected time interval that was sustained for at least 15 minutes. A specific measurement that defines a performance characteristic. In HP Insight Capacity Advisor software, a combination of the statistical model (such as peak or average) used to calculate the metric and whether it is to be presented as a percentage or an absolute value. Data that was not collected by HP Insight Capacity Advisor software, perhaps because a monitored system was down during data collection. Such data is not used in analysis, though the collection gap may be shown in the Profile Viewer. See also invalid data, valid data. A workload that can be monitored by HP Insight Virtualization Manager software on HP-UX and OpenVMS managed nodes, but which has no policy associated with it. Monitored workloads are not managed by HP Insight Global Workload Manager software for Integrity (gWLM). The ability of an application and operating system to allow parallel computing by dividing processing between multiple processors or cores. See system. A partition in a cell-based server that consists of one or more cells , and one or more I/O chassis. Each nPartition operates independently of other nPartitions and either runs a single instance of an operating system or is further divided into virtual partitions. See also virtual partition. Operating system. A package groups application services (individual HP-UX processes) together. See also Serviceguard package. A workload that is not currently associated with a system. A workload becomes parked if its system is set to none when it is created or later modified. A parked workload that was previously associated with a system may have historical data associated with it from HP Insight Capacity Advisor software or HP Insight Global Workload Manager software for Integrity (gWLM). As with any workload, the historical data will be lost if the workload is deleted. When migrating a workload from one system to another, it may be useful to park the workload (removing the association with the original system) until the new system becomes available. This preserves the historical data for the workload across the migration.

metric metric view selection missing data

monitored workload multithreading node nPartition

OS package parked workload

partition

1.

A subset of server hardware that includes core, memory, and I/O resources on which an operating system (OS) can be run. This type of partitioning allows a single server to run an OS independently in each partition with isolation from other partitions. See also nPartition, virtual partition. The highest utilization value in the selected time interval. A collection of rules and settings that control workload resources managed by HP Insight Global Workload Manager software for Integrity (gWLM). For example, a policy can indicate the minimum and maximum amount of CPU resources allowed for a workload, and a target to be achieved. A single policy can be associated with multiple workloads.

peak policy

PRM

Process Resource Manager. An HP product used to dynamically divide resource utilization among different applications and users PRM controls the amount of resources that processes use during peak system load. See PRM. The hardware component that plugs into a processor socket. Processors can contain more than one core. See also core.

Process Resource Manager processor

187

processor module

The packaging of one or more processors to connect into a single socket on the system bus. Examples include the Intel Xeon FC-mPGA package, the HP mx2 dual-processor module, and the IBM Power 5 MCM. Provides a visual display of historical utilization data collected by HP Insight Capacity Advisor software, along with additional information that you have provided. A profile viewer enables you to examine different time intervals and different categories of data. A function that makes a component operational. Provisioning might include installing, upgrading, loading, and configuring a software or hardware component. Provisioning a server includes loading the appropriate software (operating system and applications), customizing and configuring the system, and starting the server and its newly-loaded software. This makes the system ready for operation. A combination of qualitative and quantitative factors such as up time, response time, and available bandwidth, that collectively to describe how well a system performs. The Quality of Service is frequently embodied in a Service Level Agreement or in a set of Service Level Objectives between or among organizations. The percentage by which the demand on a resource can grow before the utilization limits set for the resource are exceeded. For example, in the case of a system running several workloads, the relative headroom for any one workload is the percentage by which one workload can grow without exceeding the utilization limits set for itself and without causing any of the other workloads on the system to exceed their limits. See also headroom.

Profile Viewer

provision

Quality of Service

relative headroom

resource partition scenario

A subset of the resources available to an operating system instance, isolated for use by specific processes. A resource partition has its own process scheduler. A possible configuration of systems and workloads under consideration when doing capacity planning. See also what-if scenario. 1. Physical server: Hardware that can run one or more operating systems, including a partitionable complex. Also, hardware that can run an instance of the vPars monitor. Server hardware includes one or more cabinets containing all the available processing cores, memory, I/O, and power and cooling components. HP Integrity servers include two types of server hardware: standalone servers and cell-based servers. Virtual server: A software-based virtual environment that can run an operating system. A virtual server includes a subset of the server hardware resources, including cores, memory, and I/O. Virtual servers may be virtual partitions under vPars or virtual machines under Integrity VM.

server

2.

3.

HP Systems Insight Manager software uses the term server for any standalone server, nPartition, or virtual server that is running an instance of an operating system or an instance of the vPars monitor. See also system. Service Processor An independent support processor for HP servers that support nPartitions. The Service Processor provides a menu of service-level commands, plus commands to reset and reboot nPartitions and configure various parameters. The Service Processor in HP servers is sometimes called the Management Processor (MP) or the Guardian Service Processor (GSP). Serviceguard Specialized software for protecting mission-critical applications from a wide variety of hardware and software failures. With Serviceguard, multiple servers (nodes) and/or server partitions are organized into an enterprise cluster that delivers highly available application services to LAN-attached clients. HP Serviceguard monitors the health of each node and rapidly responds to failures in a way that minimizes or eliminates application downtime. A Serviceguard cluster is a networked grouping of HP 9000 or HP Integrity servers (host systems known as nodes) having sufficient redundancy of software and hardware that a single point of failure will not significantly disrupt service.

Serviceguard cluster

188

Glossary

Serviceguard package Serviceguard workload simulation SMH standalone server system

Packages are the means by which Serviceguard starts and halts configured applications. A package is a collection of services, disk volumes and IP addresses that are managed by Serviceguard to ensure they are available. A monitored workload associated with a Serviceguard cluster and a particular package within the cluster. The workload (and the utilization data reported) follows the package it is associated with as it moves between the nodes of the cluster. A mock situation (scenario) that allows you to experiment with various capacity-planning solutions. See HP SMH. Hardware that can run one or more operating systems but does not support dividing hardware resources into nPartitions. 1. A server, nPartition, virtual partition, or virtual machine that is running an instance of an operating system. 2. Entities on the network that communicate through TCP/IP or IPX. To manage a system, some type of management protocol (for example, SNMP, DMI, or WBEM) must be present on the system. Examples of systems include servers, workstations, desktops, portables, routers, switches, hubs, and gateways. See also server. See headroom. See HP SMH.

system headroom System Management Homepage Systems Insight Manager unbound core

See HP SIM. For vPars versions prior to A.04xx, an unbound core is one that can be migrated between virtual partitions while those partitions are running. Unbound cores cannot handle I/O interrupts. Unbound cores are sometimes referred to as floater processors. The distinction between bound and unbound cores does not apply to vPars version 4.0 or later.

utilization limits

The limits set on the usage of system resources such as CPU, memory, or network I/O by an application. Utilization limits are expressed as a percent of the system capacity and the amount of time an application is allowed to exceed this limit. The time that a limit is exceeded can be expressed as a percentage of time or as a maximum duration of time. See also max 15-min. The WBEM services provider for real-time utilization data from managed systems. In HP Insight Capacity Advisor software, data that meaningfully contributes to the user's ability to understand actual past resource usage and that provides reliable information for accurately forecasting current and future capacity needs. See also invalid data, missing data. HP Virtual Connect. A set of interconnect modules and embedded software for HP BladeSystem c-Class enclosures that simplifies the setup and administration of server connections, thereby enabling administrators to add, replace, and recover server resources dynamically. Virtual CPU. A single-core virtual processor in a virtual machine. See also core, processor. An emulation of a physical device. This emulation, used as a device by an Integrity VM virtual machine, effectively maps a virtual device to an entity (for example, backing store) on the VM Host. A software entity provided by HP Integrity Virtual Machines, VMware ESX, VMware ESXi, or Microsoft Hyper-V. This technology allows a single server or (with Integrity Virtual machines) nPartition to act as a VM Host for multiple individual virtual machines, each running its own instance of an operating system (referred to as a guest OS). Virtual machines are managed systems in the HP Virtual Server Environment (VSE).

Utilization Provider valid data

VC

vCPU virtual device

virtual machine

189

virtual machine host virtual partition

See VM Host. A software partition of a server, or of a single nPartition, where each virtual partition can run its own instance of an operating system. A virtual partition cannot span an nPartition boundary. See also nPartition, virtual machine. HP Insight Virtualization Manager software. Provides hierarchical visualization of servers and workloads, with seamless access to the management tools of the VSE technologies. See virtual machine. A server running HP Integrity Virtual Machines, VMware ESX, VMware ESXi, or Microsoft Hyper-V, that provides multiple virtual machines, each running its own instance of an operating system. Integrity Virtual Machines Manager. The HP Insight Dynamics application that allows you to manage and configure Integrity VM. An HP software product that provides virtual partitions. See also virtual machine. The program that manages the assignment of resources to virtual partitions in a vPars-enabled system. To enable virtual partitions, the vPars monitor must be booted in place of a normal HP-UX kernel. Each virtual partition running under the monitor then boots its own HP-UX kernel. The vPars monitor reads and updates the vPars partition database, boots virtual partitions and their kernels, and emulates certain firmware calls. See also VM Host.

Virtualization Manager VM VM Host

VM Manager vPars vPars monitor

WBEM

Web-Based Enterprise Management. A set of web-based information services standards developed by the Distributed Management Task Force, Inc.A WBEM provider offers access to a resource. WBEM clients send requests to providers to get information about and access to the registered resources. See also Utilization Provider. See WBEM.

Web-Based Enterprise Management what-if scenario

A configuration of systems and workloads that is different from the current configuration. Capacity-planning simulations are run using what-if scenarios as experiments before making any actual configuration changes. The entire OS instance is considered a workload for recognition by Insight Dynamics components. A sequential series of pages that transforms a complex task into simple steps and guides you though them. The wizard makes sure that you provide all of the required information and do not skip any steps. At each step, a page is presented that allows you to specify the information needed to complete that step. Help is available at each step and you always have the option of going back to continue the wizard from a previous step. The collection of processes in a standalone server, nPartition compartment, virtual partition compartment, or virtual machine compartment. See also managed workload, monitored workload, Serviceguard workload.

whole-OS workload wizard

workload

190

Glossary

Index
A
absolute interval, 70 agentless data collection for Capacity Advisor viewing configuration, 62 annual growth rate, 34 and data range combined, 34 assistance, 121 automated consolidation to VMs expected results, 112 possible anomalies, 112 automated load balancing expected results for servers or VM hosts, 114 possible anomalies, 115 automated solutions, 31 automated workload stacking expected results, 117 possible anomalies, 118 create, 58 command capcollect, 120 hpvmmigrate, 120 comparison report selecting details in Capacity Advisor, 74 complex viewing in profile viewer, 70 configuration, 11 conversion data, 17 conversion table percent of time limit to minutes, hours, 28 cooling multiplier, 123 Copy Profile parameters for workload in Capacity Advisor scenario, 125 core, 153 cost calculating for power usage, 123 CPU, 153 utilization, 153 CPU capacity, 24 CPU Core Utilization, 125 CPU speed, 125 CPU utilization as measured for virtual machines, 23 CPU Virtualization Overhead %, 128 default value, 128 CPU Workload Multiplier, 124, 125 default value, 124 examples, 125 credentials, 13

B
back button problem with use in Capacity Advisor, 13 business interval, 32

C
calculator, 23 capacity determining resource maximum, 24 Capacity Advisor scenario modify parameters, 88 parameters, modify, 88 capacity planning goals, 23 capcollect command, 120 change record disabling, 91 editng, 91 checklist consolidating server loads onto a virtual machine manually, 36 consolidating server loads onto a virtual machine using automated solution finding, 47 determining where to put a workload using automated solution finding, 52 estimating the effect of adding processors, 51 estimating the effect of moving processors, 51 understanding current resource usage, 35 clock setting on HP-UX, 167 setting on Linux, 167 setting on Windows, 167 unsynchronized, 167 clock speed, 153 cluster, 11 cluster node Serviceguard, 119 collection schedule

D
data accuracy, 23 as measured for CPU capacity, 24 as measured for disk I/O, 25 as measured for memory, 24 as measured for network I/O, 25 as measured for power usage, 25 Capacity Advisor update, 61 collect for Capacity Advisor, 55 first time, 58 collect in Serviceguard cluster, 120 collect nightly automatically, 58 considerations in measuring resource utilization, 25 conversion, 17 export, 133 gap, 120 historical, 17 import, 133 incorrect, 168 invalid, 27
191

invalidating, 133 linear regression to calculate trend line, 33 measurement interval, 25 missing, 27, 120 old, 167 OVPA, 133 peaks, 15 PMP, 133 power caps and HP hardware, 30 utilization, 11 data collection, 16 agentless, 12, 18 and licensing, 57 automatic, 16 differences between HP PMP and Utilization Provider, 19 first time, 58 HP Serviceguard, 17 infrastructure, 16 interpreting task results, 59 menu options, 56 method comparison, 18 server resources, 24 supported configurations, 17 timing options, 56 Utilization Provider, 12, 18 data collection, Capacity Advisor impact on system performance, 56 data collection, importing OVPA information, 57 data collection, importing PMP information, 57 data collection, records not current, 66 data discrepancy in Capacity Advisor, 66 data handling for virtual machines, 23 data import view results for HP OVPA system, 65 view results for HP PMP system, 65 data normalization, 24 data range changing in Profile Viewer, 70 modify for Capacity Advisor, 88 delay in refresh of system and workload configuration data associated issues in Capacity Advisor, 173 dependency SSH and agentless data collection, 13 VMM and data collection, 13 WBEMcredentials and agentless data collection, 13 WMI and agentless data collection, 13 disk I/O bandwidth utilization, 154 edit capacity in Capacity Advisor, 99 disk I/O capacity, 25 Disk I/O Utilization, 125 Disk I/O Workload Multiplier, 125 default value, 125 example, 125 documentation, 121
192 Index

dynamic memory, and data collection in Capacity Advisor, 67

E
Edit Scenario accessing Capacity Advisor Profile Viewer, 68 error difference in workload associations to systems, 173 message explanation, 175 time synchronization, 167 when reusing a server name or IP address, 170 error analysis, 33 error, connecting to systems, 165 example adding a VM host to a scenario, 42 adding processor cores, 44 changing a utilization limit for a scenario, 45 consolidation candidate report, 157 creating a scenario, 37 determining which systems to consolidate, 37 editing a scenario, 38 making servers become virtual machines with automated solution finding, 48 making servers become VMs manually, 42, 44 scenario comparison report, 74, 157 server consolidation, planning, 36, 47 Undo/edit change record screen, 163 exported data, 133

F
fixed interval, 70 forecast viewing in an historic utilization report, 86 forecast model attributes defined, 34 editing in Profile Viewer, 69 precedence table, 33

G
gap data, 120 goals capacity planning, 23 growth rate forecasting, 124

H
headroom, 154 defined, 25 stars definitions, 26 historical data, 17 historical utilization, 15 host name, 119 HP Performance Agent, importing data into Capacity Advisor, 57 HP Performance Management Pack data collection, 19 HP SIM documentation, 121

HP Smart Solver, 31 HP Virtual Machine calculating Hypervisor Memory Overhead for Capacity Advisor, 128 hpvmmigrate command, 120 Hyper-Threading, 154 hypervisor, 154 memory overhead, 154 Hypervisor Memory Overhead calculating for HP Virtual Machine, 128 calculating for Microsoft Hyper-V, 129 calculating for VMware ESX, 128 calculating for VMware vSphere, 129 default setting, 128 definition, 128 examples, 128 where used, 128

I
iLO collecting license for power calibration, 107 imported data, 133 incorrect data, 168 infrastructure data collection, 16 Insight Dynamics documentation, 121 Insight managed system setup wizard, 12 installation, 12 Integrity VM, 119 interval business, 32 sampling, 25 invalid data affect in Smart Solver, 27 excluding data points, 32

Memory Utilization, 125 Memory Workload Multiplier, 125 default value, 125 example, 125 memory, dynamic, 67 menu options for HP Insight Capacity Advisor Consolidation software server data, 64 method data collection, 12 metric view modify for Capacity Advisor, 88 Microsoft Hyper-V calculating Hypervisor Memory Overhead for Capacity Advisor, 129 missing data, 120 modeling predictive, 11 multiplier scaling, 155 multiplier, used in Capacity Advisor cooling, 123 CPU Virtualization Overhead %, 128 Disk I/O Workload Multiplier, 125 Hypervisor Memory Overhead, 128 memory , 124 Memory Workload Multiplier, 125 Network I/O Workload Multiplier, 125 multipliers, used in Capacity Advisor cost/kWh, 123 multithreading, 155

N
network data, 19 network I/O bandwidth utlization, 155 edit capacity in Capacity Advisor, 99 network I/O capacity, 25 Network I/O Utilization, 125 Network I/O Workload Multiplier, 125 default value, 125 example, 125 no data for managed node, 66

L
license requirements, 12 licenses, checking status, 66 load balance automated solutions, 31

M
machine virtual, 120 managed node, importance of time and time zone settings for data collection accuracy in Capacity Advisor, 66 member SG, 119 memory modeling, 22 utilization, 155 memory capacity, 24 memory data, 19 Memory Multiplier, 124 default value, 124 examples, 124

O
Offset Hours, 125 old data, 167 old dates, 167 operations overview Capacity Advisor scenarios, 86 Capacity Advisor systems, 93 OTHER workload, 155 out-of-memory, 170 overview Capacity Advisor procedures, 55 OVPA data, 16 importing, 64

193

P
peak data, 15 peak width, 15 peaks and sums, 25 percent of time limit example, 29 percentage of allocation defined, 29 performance calculating for a virtual machine in a cluster, 58 planning determining where to put a workload using automated solution finding, 52 estimating the effect of adding or moving processors, 51 server consolidation, 36 with Capacity Advisor, 35 PMP, importing data into Capacity Advisor, 57 point aggregation for trend calculation, 32 power adjusting calibration, 30 calibrating for multiple systems in Capacity Advisor scenario, 109 calibrating for multiple systems in Virtualization Manager, 107 calibrating for single system in Capacity Advisor scenario, 108 calibrating for single system in Virtualization Manager, 105 calibrating one system at a time, 109 calibration options in Capacity Advisor scenario, 105, 107, 108, 109 initial calibration, 108 power cap data in Capacity Advisor, 30 power consumption, 25 power settings editing in Profile Viewer, 69 procedure access Capacity Advisor Profile Viewer from HP SIM Optimize menu, 68 access Capacity Advisor Profile Viewer from Visualization menu, 68 access Capacity Advisor Profile Viewer when editing a scenario, 68 accessing a scenario forecast model, 84 accessing Capacity Advisor, 55 accessing global forecast model, 82 add global utilization limits in Capacity Advisor, 79 add scenario-wide utilization limits in Capacity Advisor, 80 add scenario-wide workload utilization limits in Capacity Advisor, 81 add workload utilization limits in Capacity Advisor, 80 adding an existing system, 94 adding existing systems to a scenario, 94
194 Index

adding VM hosts to an existing cluster, 97 altering the automated nightly data collection, 58 ascertaining data collection period for set of servers, 66 assigning VM hosts to a VMware DRS cluster in a scenario, 96 automated consolidation to VMs choose destination systems, 110 choose systems to consolidate, 110 set level of effort, 111 view solutions, 111 automated load balance of servers view solutions, 114 automated load balance of VM hosts choose VM hosts to load-balance, 113 view solutions, 114 automated load-balance of servers define constraints, 114 automated load-balance of VM hosts define constraints, 114 set level of effort, 114 automated workload stacking choose workloads to stack, 116 open scenario, 116 set level of effort, 117 stack workloads, 116 view solutions, 117 automating finding solution for workload stacking, 115 automating finding solutions for system consolidation to VMs, 109 calculating a virtualization consolidation ratio, 75 calibrating power for a single system in Virtualization Manager, 105 calibrating power in Virtualization Manager, 107 calibrating power within a scenario, 107, 108 change the data range in Capacity Advisor, 89 change the meter bar calculation in a scenario, 90 change the meter scale of a scenario display, 88 change time and data range in profile viewer, 70 change view of system hierarchy in profile viewer, 69 collect Capacity Advisor data, 55 controlling Capacity Advisor data presentation, 88 copying a scenario, 90 creating a collection schedule, 60 creating a consolidation candidates report, 76 creating a cost allocation report, 76 creating a peak summary report, 76 creating a planning scenario, 86 creating a population report, 77 creating a power report, 78 creating a scenario comparison report, 74 creating a scenario report, 73 creating a system, 93 creating a trend report, 77 creating a workload in a scenario, 100 creating an historic utilization report, 72 defining a forecast model, 85 defining a forecast model for a workload or system, 84

defining global forecast model, 83 deleting a scenario, 92 determining idle/max power values for non-Blade servers, 129 determining idle/max values for Blade servers, 130 disabling a forecast model, 85 edit Capacity Advisor workload, 101 edit I/O capacity in Capacity Advisor scenarios, 99 editing a scenario, 88 editing a system in a scenario, 94 editing a workload in a scenario, 101 enabling a forecast model, 85 enabling or disabling a utilization limit, 80 gathering data the first time, 58 generate Capacity Advisor report, 71 importing HP OVPA data, 64 importing HP PMP data, 65 listing systems currently in agentless configuration file, 63 making VMs become servers, 94 manipulate graphic display of utilization data in profile viewer, 70 manually making servers become VMs, 95 modify data presentation in profile viewer, 69 modifying a collection schedule, 61 move Capacity Advisor workload, 102 moving a VM, 98 parking Capacity Advisor workload, 104 remove a utilization limit, 79 removing a collection schedule, 61 removing a VMware DRS cluster from a scenario, 97 removing Capacity Advisor workload, 104 removing systems from a scenario, 99 removing VM hosts from a VMware DRS cluster in a scenario, 97 renaming a scenario, 90 select targets and set data range when creating reports, 71 setting advanced options in the agentless data collection file, 63 sutomating finding solution to load balance servers or VM hosts, 113 switch to alternate resource metrics in profile view, 71 updating collected data on all systems, 62 updating the data the Profile Viewer displays, 62 viewing forecast data in a profile viewer, 86 processor, 155 hyperthreaded, 11 module, 155 multicore, 11 socket, 155 Profile Viewer access in Capacity Advisor, 67 example, 20 panning, 70 show valid or invalid allocation, 70 show valid or invalid data, 70

Q
quality of service, 23

R
report generate in Capacity Advisor, 71 selecting details for scenario comparison, 74 setting date range in scenario comparison, 74 reports available graphic displays of data, 161 reports and graphs Capacity Advisor procedure overview, 67 requirement disk space, 12 licensing, 12 resources insufficient on VM host for consolidation, 112

S
sampling interval, 25 scenario calibrating power for multiple systems at once, 109 calibrating power for single system, 108 Capacity Advisor operations overview, 86 copy in Capacity Advisor, 90 creating for Capacity Advisor, 86 editing in Capacity Advisor, 88 opening, 105, 108 remove from Capacity Advisor, 92 rename in Capacity Advisor, 90 server consolidation planning, 36, 46 servers viewing all in HP SIM screens, 64 service quality of, 23 service level agreement, 23 service level objective sizing for, 21 Serviceguard cluster node, 119 data collection, 17 workload, 119 SG Member, 119 simulator, 23 stars meaning in Capacity Advisor, 26 Static Profile creating a baseline workload, 127 parameters for workload in Capacity Advisor scenario, 125 static profile providing estimates for, 127 sums and peaks, 25 support, 121 support information, 121 sustained minutes limit example, 29
195

system add existing to Capacity Advisor scenario, 94 create for Capacity Advisor, 93 edit for Capacity Advisor, 94 overprovisioning error, 28 remove from Capacity Advisor, 99 system consolidation automated solutions, 31 System tab accessing Capacity Advisor Profile Viewer, 68 systems Capacity Advisor operations overview, 93

VM guest utilization exceeds VM host utilization, 168 workload performance accuracy, 168 workloads no longer available in scenario for Linux systems, 172

U
utilization aggregate, 11 CPU, 153 data, 11 disk I/O bandwidth, 154 forecasting growth, 33 historical, 11, 15 memory, 155 network I/O bandwidth, 155 utilization limit defaults, 27 defined, 27 for percentage of time, 28 for sustained time, 28 global, 29 precedence table, 30 scenario workload, 29 seenario-wide, 29 specifying one or more, 28 workload, 29 utilization limits editing in Profile Viewer, 69 utilization monitor, 23 Utilization Provider, 17 data collection, 18, 19 start daemon, 167 stop daemon, 167 UUID, 120

T
task result HP PMP data import to Capacity Advisor, 65 task results HP OVPA data import to Capacity Advisor, 65 time unsynchronized, 167 time zone impact on data collection, 27 trend determination in Capacity Advisor, 31 troubleshooting, 165, 175 absence of licensing, 165 absence of user authorization, 166 automatic power management for Linux systems, 172 cannot import PMP data, 170 capprofile data import, 165 collection agents or services not running, 166 CPU utilization seems high on nodes running Microsoft Windows 2003 Server, 168 create scenario wizard requires Adobe Flash Player, 166 data cannot be imported, 170 data collection agent not installed, 166 data collection not configured, 166 data seems to have disappeared, 169 Edit Scenario window not visible, 171 exporting large data sets, 171 HTML report format too wide for printer, 171 licensing before discovery is complete, 165 licensing or authorization issues, 171 Microsoft Internet Explorer timeout, 165 missing profile graph in profile viewer with error message, 172 network connectivity, 166 no power metrics appear for simulated VMware DRS cluster, 173 out-of-memory errors in Java heap, 170, 171 running reports with very large data sets, 171 socket and core count seem off, 168 socket count in population report, 168 system configuration, 165 system credentials, 166 system name duplication error, 172 systems no longer available in scenario, 172 unsupported data collection method, 166
196 Index

V
valid data factors affecting reporting in Capacity Advisor, 32 selecting appropriate business interval, 32 setting threshold values for Capacity Advisor reports, 32 view Capacity Advisor profile viewer, 67 virtual machine, 15, 120 calculating performance when running in a cluster, 58 move in Capacity Advisor, 98 VM guest viewing in profile viewer, 70 VMware ESX calculating Hypervisor Memory Overhead for Capacity Advisor, 128 VMware vSphere calculating Hypervisor Memory Overhead for Capacity Advisor, 129 vseassist, 12

W
warning explanation of messages, 176

WBEM, 178 what-if actions viewing, 91 workload, 11, 15 analysis, 20 calculating performance for, 24 considerations when moving in Capacity Advisor, 102 Copy Profile, 125 create for Capacity Advisor, 100 demand profile, 20 edit for Capacity Advisor, 101 move in Capacity Advisor, 102 multipliers for adjusting to changes in server configuration, 124 OTHER, 155 park in Capacity Advisor, 104 remove from Capacity Advisor, 104 Serviceguard, 119 Static Profile, 125 unassigning in Capacity Advisor, 104 workload stacking automated solutions, 31 Workload tab accessing Capacity Advisor Profile Viewer, 68

197