HP Capacity Advisor Version 4.1 User'sGuide

HP Part Number: T8670-90010Published: January 2009

© Copyright 2006-2009 Hewlett-Packard Development Company, L.P.

Legal Notices

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor'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 expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPshall 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 OpenGroup 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.

Table of Contents

About This Document.......................................................................................................11Intended Audience................................................................................................................................11Typographic Conventions.....................................................................................................................11Related Information..............................................................................................................................11

Related Technical Papers.................................................................................................................12Publishing History................................................................................................................................12HP Encourages Your Comments..........................................................................................................13

1 Introduction...................................................................................................................15Setup Considerations............................................................................................................................17

Licensing Requirements..................................................................................................................17Installation.......................................................................................................................................17Collection Agents............................................................................................................................17Disk Space Requirements................................................................................................................17Credentials.......................................................................................................................................17Dependencies...................................................................................................................................17

Upgrades and Reinstallation................................................................................................................17Upgrading Software on the CMS....................................................................................................18Upgrading Agents on the Managed Nodes....................................................................................18

Navigating Within HP SIM, Virtualization Manager, and Capacity Advisor......................................18

2 Features.........................................................................................................................19Data Collection......................................................................................................................................20

Data Collection Infrastructure.........................................................................................................20Comparison of Agentless and UP Data Collection.........................................................................21HP PMP Data Differs from Utilization Provider Data....................................................................22

Differences in Memory Data .....................................................................................................22Differences in Network Data .....................................................................................................22

Related Topics.......................................................................................................................23Experimentation....................................................................................................................................23Sizing for Service Level Objectives.......................................................................................................25Modeling Considerations.....................................................................................................................25Capacity Advisor Commands..............................................................................................................26

3 Key Capacity Advisor Concepts.................................................................................27Capacity Planning Goals.......................................................................................................................27

Quality of Service ............................................................................................................................27Utilization Monitor, Calculator, and Simulator....................................................................................27

Data Handling for Virtual Machines...............................................................................................27Resources for Which Capacity Advisor Collects Data.........................................................................28

Upper Bounds..................................................................................................................................28Measuring and Analyzing Resource Utilization..................................................................................28

Peaks and Sums...............................................................................................................................29Sampling Interval............................................................................................................................29Headroom........................................................................................................................................29

Headroom Star Ranking.............................................................................................................29Interpreting the Headroom Star Ranking.............................................................................30

Missing or Invalid Data...................................................................................................................31

Table of Contents 3

Utilization Limits ............................................................................................................................31Specifying Utilization Limits......................................................................................................31

Sustained Time Limits..........................................................................................................32Percentage of Time Limits....................................................................................................32

Understanding Utilization Limit Messages...............................................................................33Percentage of Allocation.......................................................................................................33With Sustained Limits...........................................................................................................33With Percentage of Time Limits............................................................................................33

Scope of Utilization Limits.........................................................................................................33Adjusting for Platform Changes......................................................................................................34

Scaling Multipliers for Platforms...............................................................................................34CPU Multiplier......................................................................................................................34Memory Multiplier...............................................................................................................35

Multipliers for Workloads..........................................................................................................35CPU Workload Multiplier.....................................................................................................36Memory Workload Multiplier..............................................................................................36Network I/O Workload Multiplier........................................................................................36Disk I/O Workload Multiplier...............................................................................................37

Determining Estimated Utilization Assumptions for a Workload............................................37Adjusting for Virtualization Changes.............................................................................................38

CPU Virtualization Overhead %................................................................................................38CPU Virtualization Overhead %...........................................................................................38

Hypervisor Memory Overhead..................................................................................................39Hypervisor Memory Overhead............................................................................................39Doing the Math for Hypervisor Memory Overhead............................................................39

Automating Solution Generation: HP Smart Solver.............................................................................40HP Smart Solver: Types of Solutions...............................................................................................40

Determining Trends in Capacity Advisor............................................................................................41Aggregation of Points in Business Interval Bins.............................................................................41

Choosing an Appropriate Business Interval..............................................................................41Exclusion of Points...........................................................................................................................41

Factors That Affect Data Validity...............................................................................................41Linear Regression............................................................................................................................42Error Analysis..................................................................................................................................42

Forecast Calculations............................................................................................................................42The Forecast Model Hierarchy........................................................................................................43Forecast Model Attributes...............................................................................................................43

Cooling Calculations.............................................................................................................................44Cooling Multiplier...........................................................................................................................44

4 Planning with Capacity Advisor.................................................................................45Getting Ready.......................................................................................................................................45Task: Planning Server Consolidation....................................................................................................46

Understanding the Process..............................................................................................................46Example: Consolidating to an Existing Server: Stacking Programs................................................47

Step 1: Determine Which Systems to Consolidate.....................................................................48Step 2: Create a Scenario............................................................................................................48Step 3: Edit the Scenario.............................................................................................................49

Adding Processors................................................................................................................51Move Workloads...................................................................................................................52Increase the Memory.............................................................................................................53

Step 4: Estimate the New Quality of Service..............................................................................54Further Analysis....................................................................................................................57

Task: Estimating the Effect of Adding or Moving Processors..............................................................60

4 Table of Contents

Introduction.....................................................................................................................................60Estimating the Effect of Moving Processors..............................................................................60Estimating the Effect of Adding Processors...............................................................................61

Task: Determining Where to Put a New Workload..............................................................................62Introduction.....................................................................................................................................62

Using the Smart Solver.........................................................................................................................63Example...........................................................................................................................................63

The Existing Data Center Configuration....................................................................................63The Data Center Goal.................................................................................................................63Automating with the Smart Solver............................................................................................64

Types of Smart Solver Solutions......................................................................................................65Results: Automated Consolidation to VMs...............................................................................65

Expected Results...................................................................................................................65Possible Anomalies in the Results........................................................................................66

Results: Automated Load Balancing of Servers or VM Hosts...................................................66Expected Results...................................................................................................................66Possible Anomalies in the Results........................................................................................66

Results: Automated Workload Stacking....................................................................................67Expected Results...................................................................................................................67Possible Anomalies in the Results........................................................................................67

Getting More Detail.........................................................................................................................67

5 Basic Procedures..........................................................................................................69Overview...............................................................................................................................................69Accessing Capacity Advisor.................................................................................................................70Gathering Data for Capacity Advisor...................................................................................................70

Impact of Data Collection on Managed System Performance.........................................................71Data Collection Options..................................................................................................................71First Data Collection (or the Automated Nightly Collection).........................................................72Interpreting Task Results.................................................................................................................73

Error Notification on the Standard Out Tab..............................................................................73Scheduling a Data Collection..........................................................................................................74Modifying a Collection Schedule....................................................................................................75Removing a Collection Schedule.....................................................................................................75Updating Collected Data.................................................................................................................76

Updating Collected Data on All Systems...................................................................................76Updating Collected Data on Selected Systems..........................................................................76Updating Data Displayed in a Profile Viewer...........................................................................77

Collecting Data Without Using an Agent........................................................................................77Adding Systems to the Configuration File.................................................................................77Listing Systems Currently in the Configuration File.................................................................78Removing Systems.....................................................................................................................78

Remove One or More Systems..............................................................................................78Remove All Systems.............................................................................................................79

Setting Advanced Options.........................................................................................................80Data Collection and the HP Insight Capacity Advisor Consolidation software.............................80

Assigning the Consolidation Software License to a Server.......................................................81The HP SIM License Manager..............................................................................................81

Using Capacity Advisor with Consolidation Software Server Data..........................................81Viewing the Licensed Servers in HP SIM..................................................................................82

Importing Data for Use in Capacity Advisor..................................................................................82From the HP SIM Optimize Menu — Import HP OVPA Data..................................................82From the HP SIM Optimize Menu — Import HP PMP Data.....................................................83From the Command Line...........................................................................................................83

Table of Contents 5

Possible Sources of Discrepancies in Collected Data......................................................................83No Data Collected for a Managed Node....................................................................................84Data Timestamp Appears to be Incorrect..................................................................................84Dynamic Memory in HP Integrity Virtual Machines................................................................84

Producing Graphs and Reports............................................................................................................84Using the Profile Viewer..................................................................................................................85Utilization Reports Overview..........................................................................................................88

Generating a Scenario Report....................................................................................................89Stepping Through the Report Wizard........................................................................................89Using the Report Wizard to Create a Scenario Comparison......................................................91

An Example Scenario Comparison Report...........................................................................92Calculating a Virtualization Consolidation Ratio......................................................................92

Analyzing Trends............................................................................................................................93Forecasting Future Utilization..............................................................................................................93

Defining Forecast Models................................................................................................................93The Forecast Model Hierarchy...................................................................................................93Accessing the Global Forecast Model........................................................................................94

Defining the Global Forecast Model.....................................................................................94Accessing the Forecast Model for a Workload or System..........................................................95

Defining the Forecast Model for a Workload or System......................................................95Accessing the Forecast Model for a Scenario.............................................................................96Accessing the Forecast Model for a Workload Within a Scenario.............................................96Defining a Forecast Model.........................................................................................................97Disabling a Forecast Model........................................................................................................97Enabling a Forecast Model.........................................................................................................97

Generating Forecasts.......................................................................................................................97Viewing Forecast Data in a Profile Viewer................................................................................97Viewing Forecast Data in a Utilization Report..........................................................................98

Working with Scenarios........................................................................................................................98Introduction.....................................................................................................................................98Creating a Planning Scenario..........................................................................................................98Editing a Scenario..........................................................................................................................100Controlling the Data Display.........................................................................................................100

Change the Meter Style Selection.............................................................................................100Change the Data Interval by Setting the Data Range...............................................................100Change the Meter Representation............................................................................................102

Copying a Scenario........................................................................................................................102Renaming a Scenario.....................................................................................................................103Undoing or Editing Changes to Scenario......................................................................................103

Getting There............................................................................................................................103To View Applied What-If Actions............................................................................................103To Edit Applied What-If Actions..............................................................................................104

Modifying Resource Utilization Values..............................................................................104Deleting a Scenario........................................................................................................................104

Working with Systems........................................................................................................................105Introduction...................................................................................................................................105Creating a System..........................................................................................................................105Adding an Existing System...........................................................................................................106Editing a System............................................................................................................................106Editing Network and Disk I/O Capacity.......................................................................................107Removing a System.......................................................................................................................108Moving a Virtual Machine.............................................................................................................108

Working with Workloads....................................................................................................................109Introduction...................................................................................................................................109Creating a Workload......................................................................................................................109

6 Table of Contents

Editing a Workload........................................................................................................................110Moving a Workload.......................................................................................................................111

Move Considerations................................................................................................................111Parking a Workload.......................................................................................................................113Removing a Workload...................................................................................................................113

Working with Power...........................................................................................................................114Power Cap Data.............................................................................................................................114Power Calibration..........................................................................................................................115

Calibration Options..................................................................................................................115Auto IPM Calibration...............................................................................................................115

IPM Configuration Checklist (Single System mode)..........................................................115IPM Calibration (Single System mode)...............................................................................116Notes and Known Problems with Auto Calibration..........................................................116

Manual Calibration...................................................................................................................116Determining idle/max Values for Non-Blade Servers .......................................................117Determining idle/max Values for Blade Servers.................................................................117

Automating Time-Consuming Simulations........................................................................................118Automated Solution Finding: System Consolidation to VMs.......................................................119

Begin with a Scenario...............................................................................................................119Choose the Systems to Consolidate..........................................................................................119Step 1 of 3: Define the Destination System(s) and Attributes..................................................119Step 2 of 3: Set Level of Effort for Smart Solver Calculation....................................................120Step 3 of 3: View Smart Solver Solutions..................................................................................120

Reviewing the Consolidation Results.................................................................................121Automated Solution Finding: Load Balance of Servers or VM Hosts ..........................................121

Begin with a Scenario...............................................................................................................121Choose the VM Hosts or Servers to Load-Balance...................................................................121Step 1 of 3: Define the Solution Constraints.............................................................................122Step 2 of 3: Set Level of Effort for Smart Solver Calculation....................................................122Step 3 of 3: View Smart Solver Solutions..................................................................................122

Reviewing the Results.........................................................................................................122Automated Solution Finding: Workload Stacking........................................................................122

Begin with a Scenario...............................................................................................................123Choose the Workloads to Stack................................................................................................123Step 1 of 3: Stack the Specified Workloads onto Servers..........................................................123Step 2 of 3: Set Level of Effort for Smart Solver Calculation....................................................124Step 3 of 3: View Smart Solver Solutions..................................................................................124

Reviewing the Consolidation Results.................................................................................124

6 Using Capacity Advisor with Serviceguard............................................................125Using Serviceguard to Migrate HP Integrity VM Guests...................................................................125Data Collection in a Serviceguard Environment................................................................................126

A Command Reference.................................................................................................127capcollect (1M)....................................................................................................................................128capovpaextract (1M)............................................................................................................................131capprofile (1M)....................................................................................................................................133capprofile (4).......................................................................................................................................137capreport (1M).....................................................................................................................................140capreport(4).........................................................................................................................................143capagentlesscfg(1M)............................................................................................................................147cappmpextract.....................................................................................................................................149

Table of Contents 7

B Units and Terminology..............................................................................................151

C Snapshots of a Scenario Comparison Report........................................................155

D Troubleshooting in Capacity Advisor .....................................................................163Connection Problems..........................................................................................................................163Data May Appear to be Old When it is Not.......................................................................................164Data Seems to be Incorrect..................................................................................................................164Out-of-Memory Errors in the Java Heap............................................................................................165Scenario Editor Issues.........................................................................................................................165Workload and System Relationships May Not Match When Comparing Capacity Advisor andVirtualization Manager Information...................................................................................................166

E Capacity Advisor Messages.....................................................................................167Command Error Messages..................................................................................................................167Command Warning Messages............................................................................................................168HP Smart Solver Error Messages........................................................................................................172HP Smart Solver Informational Messages..........................................................................................173

Glossary.........................................................................................................................175

Index...............................................................................................................................199

8 Table of Contents

List of Figures2-1 Capacity Advisor Data Collection Infrastructure.........................................................................202-2 CPU Utilization for Managed System puny03v8........................................................................232-3 CPU Utilization for Managed System puny03v7........................................................................242-4 Combined What-If CPU Utilization for puny03v8 and puny03v7............................................242-5 CPU Utilization with Selected Percentiles of Utilization..............................................................254-1 Example of Bar Graphs (Meters) on a System tab in the Scenario Editor.....................................495-1 Comparison of Three Scenarios in a Capacity Advisor Report....................................................92E-1 Example 1. Solver Error Messages When Systems Have Insufficient Resources to Place a

Workload.....................................................................................................................................172E-2 Example 2. Solver Error Messages When Too Few Systems Are Available for the Calculated

Required Capacity Needed.........................................................................................................173E-3 Example 3. Solver Information Messages When Workload Requirements Exceed Available

Capacity.......................................................................................................................................174

9

List of Tables2-1 A Comparison of Agentless Versus Utilization Provider Data Collection...................................212-2 Commands and Their Functions...................................................................................................263-1 Headroom Stars Defined...............................................................................................................303-2 Percent of Time Conversions.........................................................................................................323-3 Scope of Utilization Limits............................................................................................................343-4 Settings to Guide Estimated Utilization Assumptions for Workload...........................................373-5 Forecast Models.............................................................................................................................433-6 Forecast Model Attributes.............................................................................................................434-1 VM Host Configuration.................................................................................................................634-2 Legacy Standalone Servers............................................................................................................635-1 Capacity Advisor Report Types....................................................................................................855-2 Forecast Models.............................................................................................................................935-3 Calibration Choices.....................................................................................................................1155-4 IPM Calibration Links.................................................................................................................116A-1 Defaults........................................................................................................................................140B-1 Units and Terminology................................................................................................................151B-2 Data Collection for CPU Utilization by Platform........................................................................151B-3 Data Collection for Disk I/O Bandwidth Utilization by Platform...............................................151B-4 Data Collection for Memory Utilization by Platform..................................................................152B-5 Data Collection for Network I/O Bandwidth Utilization by Platform........................................153E-1 Error Messages and Their Correction..........................................................................................167E-2 Warning Messages in Capacity Advisor.....................................................................................168

10 List of Tables

About This DocumentThis document describes how to use HP Capacity Advisor to make better decisions about howto manage a virtualized server environment. Capacity Advisor uses Utilization Provider agents(WBEM services providers) to collect historical data on resouce utilization. This can be used toforecast system utilization.

Intended AudienceThis document is intended to be used by capacity planners and other technical professionalsinvolved with data center operations, administration, and planning. An understanding of systemadministration concepts and procedures is assumed.

Typographic ConventionsThis document uses the following typographic conventions.Book Title Title of a book or other document.Linked Title Title that is a hyperlink to a book or other document.http://www.hp.com

A Web site address that is a hyperlink to the site.

Command Command name or qualified command phrase.user input Commands and other text that you type.computeroutput

Text displayed by the computer.

Enter The name of a keyboard key. Note that Return and Enter both refer to thesame key. A sequence such as Ctrl+A indicates that you must hold downthe key labeled Ctrl while pressing the A key.

variable The name of an environment variable, for example PATH or errno.value A value that you may replace in a command or function, or information in

a display that represents several possible values.find(1) HP-UX manpage. In this example, “find” is the manpage name and “1” is

the manpage section.

Related InformationThe latest versions of manuals and white papers for HP Insight Dynamics — VSE, the VSEManagement Software, and related products can be downloaded from the HP Web:• Documents for HP Insight Dynamics — VSE and related HP ProLiant software can be found

at http://www.hp.com/go/insightdynamics/docs.• Documents for VSE Management Software and related HP Integrity software can be found

at http://docs.hp.com/en/vse.htmlThe VSE Management Software and related products include command reference pages withdetails about commands, file formats, and related information. For a list of all VSE ManagementSoftware command reference pages and where they are installed, see the HP VSE ManagementSoftware Version 4.1 Installation and Update Guide for HP-UX.Reference pages for Capacity Advisor commands appropriate for use on supported Microsoft®Windows® operating systems are included at the end of this guide and in the online CapacityAdvisor Help reference.Additional related information can be found in the following documents and web sites:

Intended Audience 11

• VSE Management Software Support Matrix• The HP VSE Managed Node Software Update web site (http://vsemgmt.external.hp.com/)• HP Virtual Server Environment (http://www.hp.com/go/vse)• HP Virtual Server Environment Reference Architectures (http://www.hp.com/go/vsera)• HP Systems Insight Manager (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 SummerStudy on Energy Efficiency in Buildings.

• Hewlett-Packard Development Company, LP; 2007. Hardware Consolidation with IntegrityVirtual Machines (PDF).

• Hewlett-Packard Development Company, L.P.; April 2008. HP Insight Power Manager(PDF).

• Microsoft Corporation, 2007–2008. Performance Tuning Guidelines for Windows Server2008.

• Microsoft Corporation, 2008. System Requirements for Virtual Server.• VMware, Inc, 2006–2007. Resource Management Guide: ESX Server 3.0.1 and VirtualCenter

2.0.1.

Publishing History

Publication DateSupported Operating SystemsManufacturing Part Number

January 2009See the VSE Management Version 4.1 Software Support Matrix.T8670-90010

May 2008CMS:HP-UX 11i v1 December 2004 or laterHP-UX 11i v2 September 2004 or laterHP-UX 11i v3 (IA and PA)Managed systems: HP-UX 11i v1, HP-UX 11i v2, HP-UX 11i v3(IA and PA)Linux 64, Windows 64

T8670-90001

June 2007CMS:HP-UX 11i v1 December 2004 or laterHP-UX 11i v2 September 2004 or laterHP-UX 11i v3 (IA and PA)Managed systems: HP-UX 11i v1, HP-UX 11i v2, HP-UX 11i v3(IA and PA)Linux 64, Windows 64

T2784–90026

September 2006CMS:HP-UX 11i v1 December 2004 or laterHP-UX 11i v2 September 2004 or laterManaged systems: HP-UX 11i v1, HP-UX 11i v2,Linux

T2784-90005

12

HP Encourages Your CommentsYour comments and suggestions regarding product features will help us develop future versionsof the Virtual Server Environment Management Software. Use the following e-mail address tosend feedback directly to the VSE Management Software development team:vse@hpuxweb.fc.hp.com.

NOTE: HP cannot provide product support through this e-mail address. To obtain productsupport, contact your HP Support Representative, your HP Services Representative, or yourauthorized HP reseller. For more information about support services, see the support Web siteat http://www.hp.com/go/support.

For other ways to contact HP, see the Contact HP Web site at http://welcome.hp.com/country/us/en/contact_us.html.

HP Encourages Your Comments 13

14

1 IntroductionHP Capacity Advisor is a utility that allows you to monitor and evaluate system and workloadutilization of CPU cores, memory, network and disk I/O, and power. With this information, youcan 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 configurationor to a network. A single system can include multi-core or hyper-threaded processors.Capacity Advisor helps you evaluate system consolidations, load balancing, changing systemattributes, and varying workloads to decide how to move workloads to improve utilization. Thequantitative results from Capacity Advisor can aid the planner in estimating future systemworkloads and in planning for changes to system configurations. With Capacity Advisor, youcan perform the following tasks within an easy-to-navigate, clearly notated graphical userinterface:• Collect utilization data on CPU cores, memory, network and disk I/O, and power• View historical resource utilization for whole-OS and sub-OS workloads on HP-UX and

whole-OS workload resource utilization on Microsoft® Windows systems.• View historical workload resource utilization and aggregate utilization across the partitioning

continuum (nPars, HP-UX vPars, HP-UX Virtual Machines)• 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 future resource needsCapacity 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 machinesCapacity Advisor can use data collected over time to show the results of these configurationchanges in many ways. Graphical views are available so you can see what the effects of thechanges are over time. Tables are available that give the percentage of time and the degree towhich the system is busy; this information is valuable in comparing resource utilization andquality of service before and after a change. Other tables show how many minutes per month thesystem is unacceptably busy–a measure valuable for both quality of service and for estimatingTiCAP bills. Because Capacity Advisor works from data traces collected over time, it is muchmore accurate than using only peak data or average data in understanding your systems and theworkloads 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 otherresources before you actually implement a move.Capacity Advisor incorporates numerical values of several components in its analysis andmodeling, including:• Number of CPU cores• CPU speed• Memory size• Network I/O bandwidth• Disk I/O bandwidth• Power usage

15

• Platform multipliers (see “Adjusting for Platform Changes” (page 34))• Virtualization adjustments (see “Adjusting for Virtualization Changes” (page 38))

16 Introduction

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

Licensing RequirementsCapacity Advisor is installed when all VSE components are installed. For specific informationabout trial and LTU (License To Use) licensing on supported platforms, see theHP InsightDynamics— VSE and HP VSE Management Software 4.1 Getting Started Guide at http://docs.hp.com/en/vse.html. For added information on using the HP Insight Capacity Advisor Consolidation Softwarelicense, see “Data Collection and the HP Insight Capacity Advisor Consolidation software”(page 80).

InstallationCapacity Advisor is installed with other VSE components, so no separate installation is required.(See the VSE Management Software installation guide at http://docs.hp.com/en/vse.html asappropriate for your operating system.) To use Capacity Advisor, you must have a valid license.

Collection AgentsCapacity Advisor uses the same data collection agents as Virtualization Manager and problemsassociated with agents can be diagnosed with vseassist. See the HP VSEManagement SoftwareVersion 4.1 Installation and Update Guide for HP-UX for additional information.Capacity Advisor also can collect data from licensed Microsoft® Windows® systems withoutthe use of an agent. See “Collecting Data Without Using an Agent” (page 77).

Disk Space RequirementsPlan to allot 34.6 MB for each workload to collect and preserve a maximum of four years of datafor use by Capacity Advisor. For additional information on disk space requirements, see thecapcollect page in the “Command Reference” in this manual. Also see the HP Systems InsightManager Installation and User Guide.

CredentialsTo use Capacity Advisor, to collect data, and to run reports, you must have credentials (a validuser name and password) and appropriate toolbox authorization on systems where you plan touse Capacity Advisor. For specifics about setting up user authorizations, see the HP InsightDynamics — VSE and HP VSE Management Software 4.1 Getting Started Guide.

DependenciesCapacity Advisor has the same software and hardware dependencies as HP VirtualizationManager. These dependencies apply to both managed systems and the CMS. For details, see theHP Insight Dynamics — VSE and HP VSE Management Software 4.1 Getting Started Guide.

Upgrades and ReinstallationWhen upgrading or reinstalling software used with Capacity Advisor, there are differentconsiderations and procedures for the following, described in the next sections:

Setup Considerations 17

• Updating software on the CMS• Updating agents on the managed nodes

Upgrading Software on the CMSWhen VSE is removed and reinstalled, Capacity Advisor can miss collecting some data on theCentral Management System (CMS). To avoid this, back up the VSE Management Softwaredatabase before removing VSE and restore the database after it is reinstalled, using the followingcommands:• vseinitconfig —b (before removing VSE)• vseinitconfig —s (after reinstalling VSE)For more information about usingvseinitconfig and restoring the VSE Management Softwaredatabase, see the appropriate VSE Management Software installation guide at http://docs.hp.com/en/vse.html.

Upgrading Agents on the Managed NodesWhen upgrading the Utilization Provider to version 1.6.0.0 on a managed node, the data collectedon that node that day is lost. Only data after the upgrade is kept. For example, if the UtilizationProvider upgrade occurs at 3:00 pm UTC on a managed node, the previous 15 hours of data arelost for that node. No data from prior days is lost. The data-gathering "day" starts at midnightUTC. If the upgrade of the Utilization Provider occurs at noon Central Daylight Time (UTC+5),17 hours of utilization data are lost. To minimize data loss, upgrade the Utilization Provider assoon after UTC midnight as possible.To minimize missing data, you may use the following procedure:Procedure 1-1 To Upgrade an Agent on a Managed Node from the Command Line1. Collect data from the managed node. For example,

$ capcollect system.to.be.upgraded

2. Export the utilization data for this day from the system to save it. For example,$ capprofile -x -b 20070309 -e 20070310 system.to.be.upgraded >/var/tmp/system.profile

3. Upgrade the utilization provider software on the managed node shortly after UTC midnight;for example, on Monday.

4. Allow capcollect to collect the partial day from the new provider after the UTC day isover, that is, after UTC midnight, say; for example, on Tuesday.

IMPORTANT: This step is crucial, because if you re-import your exported data before theUTC day is over, capcollect will overwrite it when it collects for the day.

5. Import the saved profile data for the system. For example,$ capprofile -i -o system.to.be.upgraded </var/tmp/system.profile

Using this procedure is practical only if the cost of losing a day's data is greater than the cost ofusing the procedure.

Navigating Within HP SIM, Virtualization Manager, and Capacity AdvisorAvoid using your browser Back and Forward buttons (except when navigating in the onlinehelp). When you use these buttons, the user interface cannot tell that you have changed to adifferent view. This can cause problems, including incorrectly displaying which objects areselected 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 thebrowser screen area.

18 Introduction

2 FeaturesCapacity Advisor lets you test configuration changes before actually making them in your datacenter, 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 obtains data for analysis from the following data collectors:• HP Utilization WBEM Provider• HP OpenView Performance Agent (OVPA)• Performance Management Pack (PMP)• an agentless solution on Microsoft Windows systems.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 usageCapacity Advisor enables you to collect resource data and create visualization graphs with thefollowing views:• Historical utilization and trends• Data peaks• Peak durations• Forecastswith the following utilization limits:• amount of acceptable resource usage• sustained time• percentage of timeCapacity Advisor enables you to create scenarios for what-if planning and forecasting, performingtasks such as the following:• For systems in scenarios:

— Create systems— Remove systems— Edit system attributes— Move virtual machines

• For workloads in scenarios:— Create workloads— Collect utilization data for workloads— Import existing workload profiles— Edit workload demands— Move workloads between systems

19

— Park workloads— Delete workloads

• For scenarios themselves:— View and undo/redo scenario changes— Use the HP Smart Solver technology to perform:

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

— Create scenario comparison reports

For additional information about Capacity Advisor and how it fits into the Virtual ServerEnvironment, refer to The HP Virtual Server Environment, Dan Herington and Bryan Jacquot,Hewlett-Packard Development Co., 2006.

Data CollectionData collection is at the heart of Capacity Advisor and a task is created during configuration toautomatically collect utilization data from all licensed VSE resources added to HP SIM. (See“First Data Collection (or the Automated Nightly Collection)” (page 72).)HP recommends that once you have become familiar with using Capacity Advisor, you shouldreview 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 datais available when you need it for analysis.

Data Collection InfrastructureIn the data collection infrastructure, each component plays a role, as shown in Figure 2-1. It allbegins with data collection.

Figure 2-1 Capacity Advisor Data Collection Infrastructure

20 Features

11 Scenario data is storedautomatically for

6 TheData Collector gathersdata from the VSE

1 The Agentless DataCollector Service runs onMicrosoft Windowsmanaged systems only.

continued use in theScenario Editor.

database and includes itin the historical database.

2 Agentless data collected bythe Agentless Data

12 Use the Scenario Editor tomanipulate the collected

7 You can import data (HPOVPA and HP PMP) intothe historical database foranalysis.

Collector Service is madeavailable to the CapacityAdvisor Data Collector.

data associated withworkloads and systems.

8 13Automatic data conversionoccurs when importing

Use the Profile Viewer toexamine a graphical3 The Utilization Provider

enables the operation of display of the utilizationdata into the CapacityAdvisor database. of a specific resource for athe Capacity Advisor

Data Collector. specific workload orsystem.

9 Historical data is stored foruse in Capacity Advisor.4 Microsoft Virtual

Machine Manager (VMM) 1410 Use theReport Generator tocreate reports to examine.

The Utilization Calculatoruses historical datadata is made available tocollected over time tocreate reports.

the Capacity AdvisorData Collector.

15 Use the web browser towork with CapacityAdvisor and exploit itsfeatures.

5 VSE data collected by theUtilization Provider ismade available to theCapacity Advisor DataCollector.

Collecting Data for a Workload with a HP Serviceguard PackageStarting with VSE Management Software version 3.0, you can associate a VSE-monitored workloadwith a Serviceguard package. This association will allow VSE Virtualization Manager to showworkloads moving from one system to another within minutes of the Serviceguard migration.It will also allow Capacity Advisor to show an uninterrupted history of utilization data for aworkload across these migrations.Associating VSE monitored workloads and Serviceguard packages requires that Virtual Vaulthas been installed on the Central Management Server (CMS) and that the corresponding versionof the Utilization Provider has been installed on all member systems of the Serviceguard cluster.All nodes of the cluster must be running the appropriate version of the Utilization Provider. Forspecific version information, see the HP Systems Insight Manager screen: Help About HPSystems Insight Manager.

Comparison of Agentless and UP Data CollectionThis help topic compares the potential benefits and possible drawbacks that accompany the useof agentless data collection versus using the Utilization Provider (UP) to collect data from systemslicensed for Capacity Advisor.

Table 2-1 A Comparison of Agentless Versus Utilization Provider Data Collection

Agentless Configuration FileUtilization Provider (UP)

Available for Windows systems onlyAvailable for HP-UX, Linux, OpenVMS, and Microsoft®Windows® systems

Equally useful in data quality, accuracy, and richness.

Leverages existing data on the system; no additional agenthosting or update required.

Requires hosting and updating the UP agent

Data Collection 21

Table 2-1 A Comparison of Agentless Versus Utilization Provider Data Collection (continued)

Agentless Configuration FileUtilization Provider (UP)

Susceptible to network or CMS downtime as data iscontinuously collected (every five minutes by default) bythe CMS across the network from each managed system.

Not susceptible to downtime in the network or the CMS.Collected data is held for a maximum of 30 days by theUP for transfer to the database on the CMS. By default,UP data is transferred once each day.

Small additional load on CPU and memory resourcesincurred by the agentless data collection service runningon the CMS.

No additional load on CPU or memory resources incurredon the CMS.

Collection Precedence:When a system is listed in the agentless data configuration file and also is running the UtilizationProvider, the data collection function in Capacity Advisor will store the set of agentless datarather than the Utilization Provider data. Where you have decided that agentless data collectionis your preferred collection method, you may want to remove the Utilization Provider from thosesystems.

What Happens When You Switch from Agentless Collection to the UP:If you remove systems from the agentless configuration file and install the Utilization Provideron those systems, the data collected in the current day via agentless means may be lost. Shouldthis occur, you can expect to see a gap when viewing reports that include the day on which theswitch was made.

HP PMP Data Differs from Utilization Provider DataDifferences in data imported from HP Performance Management Pack (HP PMP) affects howyou should interpret resulting analysis and scenarios as compared to data collected from theUtilization Provider.

Differences in Memory DataCapacity Advisor normally measures memory collected from the Utilization Provider, whichreturns 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 UtilizationProvider does not. The memory use reported by HP PMP is about 20% higher than memory usereported by the Utilization Provider.Because Capacity Advisor assumes a different memory amount than HP PMP provides, CapacityAdvisor may overestimate the memory needed when using HP PMP data to analyze stackingseveral 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 sizein a new configuration, you should not use a mix of HP PMP and Utilization Provider data whenlooking for a trend in memory utilization.

Differences in Network DataHP PMP does not report the correct network IO when network interface cards (NICs) are beingteamed 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 reportsthe 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 ofthe Utilization Provider data.

22 Features

If you know you have teamed NICs, or if you suspect your imported network data is twice ashigh 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 willbe able to mark data as invalid. You can do this from the Profile Viewer, or by using thecapprofile(1M) command.

Related Topics

“Data Handling for Virtual Machines” (page 27)“Using the Profile Viewer” (page 85)“Command Reference” (page 127)

ExperimentationAfter you read this document, you can better understand Capacity Advisor by experimenting,considering different configurations and workload placement, and by trying them out in what-ifscenarios. A scenario identifies the workload demand profile that creates your experimentalsimulations.When you do workload analysis on systems, you view graphs and reports that represent CPUor memory utilization by time. For example, Figure 2-2 shows a graph of CPU utilization for asingle system over a one-month period.

Figure 2-2 CPU Utilization for Managed System puny03v8

1 Peak (highest) value.Similarly, Figure 2-3 shows CPU utilization for a second system over the same period.

Experimentation 23

Figure 2-3 CPU Utilization for Managed System puny03v7

1 Peak value.Comparing these two graphs shows that workload peaks on the two systems do not occursimultaneously, 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 tosatisfy the needs of the workloads, while reducing the number of CPU cores (originally eachsystem 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 theworkloads onto one system.

Figure 2-4 Combined What-If CPU Utilization for puny03v8 and puny03v7

1 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 thisworkload demand.

24 Features

Sizing for Service Level ObjectivesAs part of planning configuration changes, you can also consider your service level objectivesor quality of service goals.The following utilization graph shows only one month of data; longer periods of data providean 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 initiallyavailable in this exercise. Even this reduction may not provide the best fit, as the vast majorityof the work (90%) is completed with less than .5 of one core, and 99% of the work is completedwith one core.For example, as shown in Figure 2-5, CPU utilization has one peak at 1.7 CPU cores, with manylower peaks. If you configure your system to always meet the demand of this single 1.7-CPUpeak, and you do not adjust the CPU allocation, a significant fraction of the CPU allocation inthis 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. Furtherexperimentation in Capacity Advisor with resource allocations, consolidations, and utilizationlimits will help you arrive at the best fit for these workloads.With Capacity Advisor's visualization and reporting tools, you can make a considered estimateof server resource utilization using different scenarios and easily refine allocations by tweakingvalues in the scenarios. Such estimates can help you minimize overspending for capacity youuse rarely, and maximize utilization of your systems to ensure that your systems have the capacityneeded at the level you require.

Modeling ConsiderationsCapacity Advisor methodology makes certain assumptions in its data analysis. These assumptionsinclude using a default CPU scaling factor and normalization based on CPU speed. You canintroduce a different scaling factor to better approximate the configuration being modeled in awhat-if scenario. Memory is not normalized. Scale factors can be set on the Capacity AdvisorEdit Workload and Move Workload screens. See“Adjusting for Platform Changes” (page 34)for more information.On the Edit Scenario screen, you can select either the System or Workload tab to manipulatethe planning scenario and specify which metric representation to view: average, 90th percentile, peakor max 15-min (maximum 15-minute sustained). The Meter Style can be absolute numbers or in

Sizing for Service Level Objectives 25

percentages. By changing the metrics to view, you can explore multiple options for system andworkload deployment. See “ Controlling the Data Display” (page 100) for more information.

Capacity Advisor CommandsIn 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, as listedin Table 2–2. For additional information, see the corresponding reference pages (seeAppendix A “Command Reference”).

Table 2-2 Commands and Their Functions

FunctionCommand

Collects inventory and performance utilization data frommanaged systems requiring installation or configuration of agentson the managed systems. (Available on Microsoft® Windows®systems only.)

capagentlesscfg

Collects utilization data from identified systems that you use toexamine workload scenarios and do capacity planning.

capcollect(1m)

Exports HP OVPA system data from the specified managedsystem and imports the data into Capacity Advisor. capovpaextractallows importing data from non-VSE systems if the OVPA versionis supported. See the command reference page for supportedOVPA versions.

capovpaextract(1m)

Exports HP PMP system data from the specified managed systemand imports the data into Capacity Advisor. See the commandreference page for supported PMP versions. (Available onMicrosoft Windows systems only.)

cappmpextract(1m)

Imports, exports, displays, invalidates or removes utilizationdata for a specific workload.

capprofile(1m)

Defines the format of Capacity Advisor import and export files.capprofile(4)

Creates a Capacity Advisor Report from the command line.capreport (1M)

Defines the format of a command file to use with the capreportcommand.

capreport (4)

26 Features

3 Key Capacity Advisor ConceptsCapacity 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 ”)• Optimizing resource utilization• Meeting internal and external security requirements• Reducing costsHP Capacity Advisor can help lessen the conflicts among goals by buttressing decisions withbetter information and more robust models. Effective use of Capacity Advisor can help you todouble resource utilization in many situations.The most important step in accomplishing capacity planning goals is to clearly understand thegoals and the relationship among them: optimizing response time may preclude most efficientresource 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 overallquality of service.

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

Utilization Monitor, Calculator, and SimulatorHP Capacity Advisor performs numerous functions. At a fundamental level, it collects data fromutilization monitoring daemons on systems and workloads. Using this data, Capacity Advisorcan report on utilization of memory, core processing units, I/O bandwidth, and power. It cancalculate 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. Thisgoes beyond simple addition of maximum loads to provide a dynamic addition of componentsbased on the time sequence of utilization measurements taken from the actual loads running onreal systems (see “Peaks and Sums”).

Data Handling for Virtual MachinesData collected by Capacity Advisor for use in the Profile Viewer and historical utilization reportscan vary from data reported by tools that run inside a virtual machine. These tools include HP-UXand Linux commands such as top, ps, and sar, and on Microsoft Windows, the task manageror 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 27

time used by threads that simulate the virtual processors. However, there are also threadsthat simulate the IO cards and disks in the virtual system. Capacity Advisor collects dataon all of these threads, which can cause the Capacity Advisor data for a specific virtualmachine’s 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 CPUutilization of more than 100% being reported for a virtual machine.

• Capacity Advisor data for VM host CPU utilization can be lower than what the guestoperating system reports, especially during periods of high utilization. Capacity Advisorrecords 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 theVM host allotted to each virtual machine. In contrast, the guest OS records virtual CPUutilization, which includes time when the VM wants to run, but is suspended while anotherVM is using the resources on the VM host.

Because Capacity Advisor corrects for these effects, the collected data has much less “noise” init, and better reflects the CPU time that was actually used by any one VM.

Resources for Which Capacity Advisor Collects DataHP Capacity Advisor collects and analyzes data for utilization of the following resources:• CPU cores• Memory• Network I/O• Disk I/O• Power

Upper BoundsUpper bounds represent the maximum capacity of a resource for a given system. The maximumcapacity is used in Capacity Advisor for items such as the network and disk I/O utilization graphsof systems, the graphs and values shown in the Profile Viewer, and the Capacity Advisor SmartSolver calculations.CPU Capacity The maximum CPU capacity of a system is the product of the number of CPUcores and the clock speed of the system.Memory The maximum capacity of memory is the amount of memory on the system.Network I/O The maximum capacity for network I/O defaults to the high-water mark (i.e.,maximum observed/collected value) for network I/O. However, to set the upper bound to a valueyou choose, select Configure ⇒ Edit Network and Disk I/O Capacity from the Visualizationtab in Virtualization Manager.Disk I/O The maximum capacity for disk I/O defaults to the high-water mark (that is, themaximum observed/collected value) for disk I/O. However, to set the upper bound to a valueyou choose, select Configure ⇒ Edit Network and Disk I/O Capacity... from the Visualizationtab in Virtualization Manager.Power Expected maximum and minimum power values for systems and workloads arecomputed using the CPU and power utilization data collected from Insight Power Manager(IPM). However, these values can also be set manually from the Virtualization Manager menubar (select Configure ⇒ Calibrate Power (All Selected Systems)...) for specified systems orfrom the Capacity Advisor Edit Scenario: System tab menu bar (select Edit ⇒ Calibrate Power(All Selected Systems)...) for a specific scenario.

Measuring and Analyzing Resource UtilizationIn using Capacity Advisor, it is helpful to understand how the tool approaches sampling anddata analysis, and the user-provided information that affects these.

28 Key Capacity Advisor Concepts

Peaks and SumsMeasuring utilization of computing resources is more complex than simply determining themaximum memory or processor utilization.Sum of Peaks An old standby in capacity planning is to simply take the peak of the two loadsand use that to determine the maximum required capacity; this is the “sum of peaks”. While thiswill definitely provide a robust solution, it does not take into account the timing of the peak ofthe 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 HPCapacity Advisor, takes into account the timing of the maximum utilization peaks in the individualloads. By adding together utilization at each measured interval and then taking the maximumof the resulting time sequence, a more accurate measure of the required maximum resource canbe determined. This can lead to cost savings when planning the resources required to consolidateloads onto new or existing servers.

Sampling IntervalHP Capacity Advisor Utilization Provider runs on each monitored system to collect informationon resource utilization. At the CPU-clock cycle level, a processor is either busy or idle. ForCapacity 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 averagingtends to flatten the graphs, particularly when compared with real-time graphs in which eachdata point is the average of values from the 15 preceding seconds.For data collected using the agentless solution, collection intervals may vary depending on valuesthat you set and the number of machines in the collection.

HeadroomHeadroom is the difference between the observed utilization on a system and the maximumavailable capacity. That is, the headroom of a system is the amount of additional capacity thatcan 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.Optimum headroom varies depending on size of system. While a single processor system mightrequire 50% headroom to preserve reasonable response times, a 16-way system might havereasonable response times when loaded at 80%.Adequate headroom can also depend heavily on the characteristics of the loads; highly interactivesystems require much more headroom than those that can tolerate delays in response time; batchsystems may get by with very little headroom at all.

Headroom Star RankingVarious reports and results show headroom star rankings. Use the following chart to understandthe headroom ranking system.

Measuring and Analyzing Resource Utilization 29

Table 3-1 Headroom Stars Defined

Number of Stars Showing Green for Workload or System

543210

Not only do allworkloads fit,but double theresource usagefor any singleworkload couldfit.

Allworkloads fit,and at least75%headroom forany singleworkload isavailable.

Allworkloads fit,and at least50%headroom forany singleworkload isavailable.

Allworkloads fit,and at least25%headroom forany singleworkload isavailable.

Allworkloads fitin the system,but no orlittleheadroom isavailable.

One or moreworkloads donot fit in thesystem; theutilizationlimits areviolated.

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 totalnumber of cores on the VM host. The VM host clock speed, network capacity, and diskcapacity are all inherited by the VM guest when it is moved onto the VM host.

• fit means the utilization limits (see “Utilization Limits ” (page 31)) on the workloads aremet

• headroom means “room for growth”

Interpreting the Headroom Star Ranking

Headroom star rankings for a host are a weighted average of all of the star rankings of theworkloads on that host. The weighting tends to give the highest weight to the lowest ranking.One low ranking can dramatically lower the ranking for the entire host.In the case of a VM host, the star rankings account for how well the workloads fit into theirvirtual machines, as well as how well the virtual machines fit on the VM host. The ranking forthe VM host will be low if any of the virtual machines are too small for their workloads.

Interpreting the Star Ranking 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.1GHz VM host.You can avoid having the Smart Solver produce inaccurate or useless results by re-sizing yoursystems 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 theSmart Solver. (Select What-if Actions ⇒ Edit System... on the System tab on the Edit Scenarioscreen.) If you change the number of cores from 1 to 2 or 2 to 3 before consolidating, the resultingvirtual machines will have enough cores to cover the virtualization overhead or a slower VMhost.Re-sizing the virtual machines after running the Smart Solver can be less effort, as you only haveto re-size the VMs that have fewer stars than your desired goal. After adding more cores to theVMs for which CPU resources are too tight, you can rerun Smart Solver to balance the load onthe VM hosts to improve the solution a bit more.

30 Key Capacity Advisor Concepts

TIP: Use a “Scenario Comparison report” [p. 91] to compare the headroom stars ranking forsaved scenarios.

Missing or Invalid DataData collected by Capacity Advisor is used in the scenarios you create and manipulate. Duringan interval when no data was collected, the data is considered missing (data may not have beencollected, for example, because a system was down during data collection). Invalidated (orinvalid) 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 datacollected has only old data. For more information on this topic, see the section on Handling OldData in the Capacity Advisor Error Messages appendix in this document.

Utilization LimitsUtilization limits allow you to set specific service level objectives for workloads. Beyond overallsystem utilization, these utilization limits place service level objectives on one or more specificutilization metrics (CPU, memory, network, or disk utilization) for any given workload. Whenmaking automated changes, such as the automated system consolidation done by the HP SmartSolver, these utilization limits are honored in determining a solution. Utilization limits also applyto the automated load balance of servers and virtual machines, and to automated workloadstacking.Thedefault utilization limitsused globally across Capacity Advisor in the absence of user-definedlimits 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 performancewith a minimum of queuing in jobs.)

• Memory utilization cannot exceed 100% of the capacity. Typically memory should be set ata value <100% to allow for memory use by the dynamic buffer cache and operating systemactivity.

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

Specifying Utilization LimitsThere 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

Measuring and Analyzing Resource Utilization 31

— network I/O bandwidth— disk I/O bandwidth

• The Time Criteria You can specify the time portion of a utilization limit in either of twoways:— Sustained (consecutive) time limits— Percentage of time limits

For more information about time limits, see “Sustained Time Limits” (page 32) and “Percentageof Time Limits” (page 32)

TIP:You Can Specify More Than One Utilization Limit for a Resource Using the Utilization LimitsEditor, you can add multiple settings for a resource. For example, you can create multiple differentutilization 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 durationNot Specifying a Limit Allows HP Smart Solver to Over-provision Systems To achieve best resultswith the Smart Solver, it is better to set specific limits, rather than to depend on the defaultsettings for limits to provide the best fit.

Sustained Time Limits

A sustained limit specifies a limit where the resource cannot exceed that utilization limit for Xconsecutive minutes. For example, if X is 20, this means that the resource cannot exceed theutilization limit for 20 consecutive minutes.Because the Capacity Advisor collects data samples every 5 minutes, the timeX for the sustainedlimit 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 thedesignated percent of time, where percent of time is related to the percentile utilization rangesin 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 oftime to hours per week, which may help you in specifying percent of time utilization limits.

Table 3-2 Percent of Time Conversions

Hours/Day(24–hour day)

Hours/ WeekMinutes/ WeekPercent of Time

.241.68100.81

.483.36201.62

.725.04302.43

1.208.40504.05

2.4016.81008.010

3.6025.21512.015

4.8033.62016.020

6.0042.02520.025

32 Key Capacity Advisor Concepts

Table 3-2 Percent of Time Conversions (continued)

Hours/Day(24–hour day)

Hours/ WeekMinutes/ WeekPercent of Time

7.2050.43,024.030

24.00168.0010080.0100

Understanding Utilization Limit Messages

Percentage of Allocation

The utilization limit messages are shown as a percentage of allocation, where allocation is subset ofthe 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 coresare added (say through dynamic CPU migration with vPars), the CPU utilization limit of 50%would mean 50% of 3 cores, or 1.5 cores.The allocation values for network and disk may be updated each time utilization data is collectedfrom the system using the capcollect command. (See the “Command Reference” in thisguide.) If a new high observed value occurs during the time period collected, the network ordisk allocation value for the system is increased to reflect it. This increased value then affectsany network or disk utilization limits for workloads on that system. The current allocation valuesfor 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 allocationfor 20 consecutive minutes, where the allocation of hardware is based upon a 3–core system. Theutilization limit message would read:CPU utilization may not exceed 50% of allocation or 1.5 cores for morethan 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. Theutilization limit message would read:CPU utilization may not exceed 50% of allocation or 1.5 cores for morethan 10% of the time.

Scope of Utilization LimitsUtilization limits can be set to apply broadly or narrowly within the Capacity Advisor userinterface:• Globally. These limits apply to every workload, wherever workloads are analyzed.• ByWorkload. 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 shownin the table below.You can disable a more specific scope where you do not want a specific scope to apply.

Measuring and Analyzing Resource Utilization 33

Table 3-3 Scope of Utilization Limits

OverridesDescriptionLimitsScope

• Nothing• Applies to all workloads for which a more specific utilization limit isnot provided.

• Cannot be disabled

GlobalUtilizationLimit

Moreglobal

• Global• Applies to a specific workload unless a more specific utilization limitis provided.

• Can be enabled or disabled

WorkloadUtilizationLimit

• Global• Workload

• Applies to all workloads within a scenario for which a more specificutilization limit is not provided.

• Can be enabled or disabled

ScenarioUtilizationLimit

MoreLocal

• Global• Workload• Scenario

• Applies to a specific workload within a scenario.• Can be enabled or disabled

ScenarioWorkloadUtilizationLimit

Adjusting for Platform ChangesCapacity Advisor gives you the ability to provide compensating factors to help Capacity Advisoradjust needed resources when analyzing moving workloads from one platform to another.(For information on how utilization is calculated for each resource, see Appendix B (page 151).)

Scaling Multipliers for PlatformsThe following are situations that you will want to adjust for when modifying a scenario becausethey affect 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.

CPU Multiplier

Meaning The ratio of change in CPU utilization due to using a different platform (PA-RISC,Itanium, or Xeon, for example) to host workloads in the scenario than the platform originallyassumed. 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 faster processing, you may expect a decrease in

CPU utilization. Use .9 to arrive at a 10% decrease in utilization.• Itanium to PA-RISC: because PA-RISC has slower processing, you may expect an increase

in CPU utilization. Use 1.1 to arrive at a 10% increase in utilization.• Itanium to Proliant (Xeon): you may expect a substantial increase in CPU utilization. Use

2.0 to arrive at a 100% increase in utilization.• Proliant (Xeon) to Itanium: you may expect a substantial decrease in CPU utilization. Use

.5 to arrive at a 50% decrease in utilization.Detailed Example Assume that you benchmark your current application on a test machine thatis similar to one that is currently running a production application. Assume that the test machine

34 Key Capacity Advisor Concepts

is a two-way 550 MHz PA-RISC system with a benchmark of 400 CPU seconds to complete, using400 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 tocomplete, using 600 MB of RAM.Because Capacity Advisor automatically scales CPU times to the clock speed of the CPU coresin the system, you will need to do the same to supply a useful alternative CPU Multiplier to helpCapacity Advisor adjust to platform changes in a scenario.To compute the CPU Multiplier, calculate the ratio of the CPU seconds multiplied by the clockspeed for the new and the old platform:(100*1600)/(400*550) = 0.73The multiplier of 0.73 represents a 27% decrease in CPU utilization.

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 originallyassumed. 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 For this example, refer to the assumptions stated in the “Detailed Example”shown in the CPU Multiplier section.To compute the Memory Multiplier, calculate the ratio of the memory used for the new and theold platform:600/400 = 1.5The 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 thesoftware application. In the case of memory utilization, factors like the number of CPU coresand the use of virtual machines have no effect unless the application tests for these factors andchanges its behavior accordingly.

Multipliers for WorkloadsThe 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 areanticipated for workloads in a new data center configuration.

Measuring and Analyzing Resource Utilization 35

TIP:These workload multipliers are also available to use when editing a simulation that representsa real workload in your data center. However, in this situation, you will achieve more accuratepredictive results if you use forecasting growth rates to model anticipated change in an existingworkload.

CPU Workload Multiplier

Meaning The relative change in CPU utilization desired when sizing an existing workload tobetter simulate a new workload in a scenario. CPU utilization by the new workload that you arecreating can be made smaller, the same, or larger than that of the workload chosen as the baselinevalue.

TIP: You do not need to account for different CPU clock speeds in this multiplier. CapacityAdvisor will do this automatically.To account for differences in platforms, use the CPU Multiplier.

Default The default value is 1.0 (no change).Where you might use this multiplier• when creating a workload or editing its attributesExamples To increase the CPU utilization of a new workload by 10% of the chosen baselineworkload, 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 simulatea new workload in a scenario. Memory utilization by the new workload that you are creatingcan 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 attributesExample To increase the memory utilization of a new workload by 20% of the chosen baselineworkload, enter a multiplier of 1.2.

Network I/O Workload Multiplier

Meaning The relative change in network I/O utilization desired when sizing an existingworkload 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 attributesExample To decrease the network I/O available to a new workload by 5% of that available tothe chosen baseline workload, enter a multiplier of .95.

36 Key Capacity Advisor Concepts

Disk I/O Workload Multiplier

Meaning The relative change in disk I/O utilization desired when sizing an existing workloadto better simulate a new workload in a scenario. Disk I/O can be made smaller, the same, or largerthan 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 attributesExample To increase the disk I/O available to a new workload by 10% of that available to thechosen baseline workload, enter a multiplier of 1.1.

Determining Estimated Utilization Assumptions for a WorkloadUse 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 existsfor a workload to examine alternatives. When you use a static workload profile (Static Profile),you create a profile based on independent values.

Table 3-4 Settings to Guide Estimated Utilization Assumptions for Workload

DescriptionAttributeField

Drop-down list of previously defined workloadsfrom which to copy attributes for the newworkload.

Select WorkloadCopy Profile

Default: 1.0See “CPU Workload Multiplier” (page 36) formore information.

CPU Workload Multiplier

Default: 1.0See “Memory Workload Multiplier” (page 36)for more information.

Memory Workload Multiplier

Default: 1.0See “Network I/O Workload Multiplier”(page 36) for more information.

Network I/O Workload Multiplier

Default: 1.0See “Disk I/O Workload Multiplier” (page 37)for more information.

Disk I/O Workload Multiplier

A positive or negative integer used to move anoccurrence of peak activity to an alternate desiredtime.For example, suppose that peak activity in theprofile data set occurred at 12:00 PM, but thedesired peak time to be simulated is 9:00 AM.Setting the Offset Hours to –3 will move thepeak time in the simulation from 12:00 PM to 9:00AM.Default: 0

Offset Hours

Measuring and Analyzing Resource Utilization 37

Table 3-4 Settings to Guide Estimated Utilization Assumptions for Workload (continued)

DescriptionAttributeField

Fractional or whole number of cores assumed tobe used by the new workload on the assignedsystem. Default: 0.0

CPU Core UtilizationStatic Profile

Processor speed assumed for the system fromwhich the workload came. Default: 0.0

CPU Speed (GHz)

Memory assumed to be used by the newworkload. Default: 0.0

Memory Utilization (GB)

Network bandwidth assumed to be used by thenew workload. Default: 0.0

Network I/O Utilization (Mb/s)

Disk bandwidth assumed to be used by the newworkload. Default: 0.0

Disk I/O Utilization (MB/s)

Providing Estimates for a Static Profile:The baseline that you enter should represent your best guess as to the load the particularapplication or workload will place on the system where you assign it. For example, if you havean application that you plan to assign to a 4–core system, and it typically uses two cores, youwould enter 2.0 for CPU utilization. In the same way, you would enter a processor speed basedon the system the workload originally ran on, and the amount of memory usually consumed bythe workload on its previous system.Once you have a baseline workload that represents current behavior, you can create additionalworkloads with different values to experiment with variations in CPU speed, available memory,and variable utilization limits to discover the behavior and performance of the workload indifferent scenarios.

Adjusting for Virtualization ChangesCapacity Advisor gives you the ability to provide compensating factors to help Capacity Advisoradjust needed resources when analyzing moving workloads from a physical system to a virtualmachine 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 B (page 151).)

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

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.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 machineExample: Making a server become a virtual machine If your virtualization software wouldcause a 15% increase in CPU utilization due to the overhead for virtualization software, enter

38 Key Capacity Advisor Concepts

15 for the CPU Virtualization Overhead % to account for the additional demand on the CPUcore(s) when changing a server to a virtual machine.Example: Making a virtual machine become a server If your virtualization software requires a15% increase in CPU utilization due to the overhead for virtualization software in the virtualmachine, enter -15 for the CPU Virtualization Overhead % to account for the gain in CPUavailability when changing a virtual machine to a server.

NOTE: Typical values for CPU Virtualization Overhead fall between 10% and 20% of the CPUresource. If your measured values in growth of CPU usage due to virtualization are greater than20% for a particular workload or set of workloads, virtualization may not be the appropriatesolution for that server.

Hypervisor Memory OverheadThe following section presents the scaling factor that you can use to more accurately simulatethe impact of including a hypervisor in your scenario. With the addition of a hypervisor, memoryutilization increases due to the operation of the hypervisor. The Hypervisor Memory Overheadhelps 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 supplyyour 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 GBSource: Hardware Consolidation with Integrity Virtual Machines

VMware ESX

To compute the memory overhead of the hypervisor, use the following formula:Total Physical Memory – (Total Physical Memory – 284 MB)/1.078This formula is derived from a least squares fit of observed values in test systems running VMwareESX. VMware documentation provides tables that outline how much memory overhead to expectbased 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.

Microsoft® Virtual Server

Depending on which version of Windows® Server is used as a host, Microsoft recommendsbetween 256 MB and 512 MB of physical memory be available for the operating system andhypervisor. In addition, Microsoft Virtual Server incurs 32 MB of overhead per guest, and supportsup to 64 guests.

Measuring and Analyzing Resource Utilization 39

To estimate the hypervisor overhead, use the following formula:512 MB + (32 MB x Number of Guests Hosted)Example: For a system hosting 4 guests, the estimated Hypervisor Memory Overhead will be:512 MB + (32 MB x 4 guests) = 640 MB (.63 GB)Source: System Requirements for Virtual Server on Microsoft TechNet web site.

Microsoft Hyper-V

Microsoft recommends at least 512 MB (.5 GB) of physical memory be available for basichypervisor features.In addition, for each guest, plan on 32 MB of overhead for the first GB of RAM allocated to aguest, 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 ofguest RAM))Example: For a system hosting 2 guests with 2 GB of RAM, and 2 guests with 1 GB of RAM, theHypervisor 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 memoryoverhead for Hyper-V. This provides a generous estimate of memory overhead, as thisconfiguration will maximize the size of the memory overhead. As a result, allowing CapacityAdvisor to estimate the Hypervisor Memory Overhead for Hyper-V will leave extra headroomon Hyper-V hosts when providing consolidation recommendations.Source: Performance Tuning Guidelines for Windows Server 2008 on the Windows HardwareDeveloper Central web site.

Automating Solution Generation: HP Smart SolverThe Smart Solver recommends where to place workloads among the pool of selected servers toreduce the number of servers used or to balance workloads across the servers. The Smart Solvertechnology uses workload traces to quantify the demands placed by the workloads on the serversand uses the workload traces to recommend viable placement solutions, subject to user-definedconstraints, such as workload utilization limits and the specific resources that may be used.

HP Smart Solver: Types of SolutionsThese planning scenario simulations can be automated:Consolidation to Virtual Machines You can simulate the consolidation of existing physicalsystems into virtualized resources, thereby converting the physical systems into VM guestshosted on VM hosts. To create the simulation, you can use data from existing VM hosts or createtemplate-generated “what-if” systems based on characteristics that you specify. This featuremakes it possible for you simulate a replacement or upgrade of existing legacy systems to fewersystems hosting virtual machines.Workload Stacking You can simulate stacking individual workloads onto existing serversand/or onto template-generated “what-if” systems based on characteristics that you specify. Thisfacility allows you to consolidate existing workloads into as few systems as possible.Load Balancing You can simulate balancing system loads across several servers or virtualmachines, such that workloads are distributed evenly across a set of resources, withoutoverloading the subset of the servers.

40 Key Capacity Advisor Concepts

Determining Trends in Capacity AdvisorDetermining trends from collected utilization data can be a challenging task. Accurate trendanalysis requires adequate historical data and an understanding of the cyclic nature of the databeing 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 Capacity Advisor combinesaggregation of points based on known business cycles to deal with cyclic patterns with exclusionof points to deal with special events, to provide data for a linear regression.

Aggregation of Points in Business Interval BinsTo reduce the impact of cyclic changes in the historical data, a user-specified business period isused to break the data into time-interval based “bins” and each bin is then represented by asingle point. The point can be the average, the peak, or the 90th percentile of the data (90% ofthe points are less than the value). A bin will not be used unless the percent of points within thebin that are valid exceeds the threshold you have specified.

IMPORTANT: A trend will not be calculated unless at least two bins with an adequate percentageof valid points exist within the range of data being analyzed.

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

Exclusion of PointsYou can set the report period to exclude a special event or mark the time period invalid to excludepoints collected during that period from a trend analysis.

Factors That Affect Data ValidityWithin any data collection period, events can occur in the polled systems that affect the qualityof data available during that time period. Capacity Advisor identifies data points that couldadversely affect the quality and validity of report results.The following are examples of events that Capacity Advisor can recognize (and disregard) aspotential sources of invalid points:

Determining Trends in Capacity Advisor 41

• 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 toconsider in your capacity planning. (See The Graph section for hints on how to do this.)

• Partial collection from a virtual machine or a VM host. When Capacity Advisor is unableto apply a correction that accounts for all activity on a VM host, it marks any partial datacollection as invalid.

How this relates to setting a Validity ThresholdThe Validity Threshold that you set should reflect your tolerance for obtaining a sufficient amountof valid data in the collection period that you designate. If the reports that you run show thatthe given threshold is not obtainable for the designated time period, this may indicate that manyof 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 reportoutcome may be a less reliable indicator of probable resource usage, or you can select a differentor longer data collection period to improve the likelihood of obtaining a sufficient percentage ofvalid points for a good report.

Linear Regressionlinear regressionThe linear regression is based on a least squares fit that minimizes the sum of the squares of thevertical 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 bemisleading. Any trend analysis based on less than a dozen aggregate points should be carefullycompared with the historical data to see if it "makes sense." The maximum number of data pointsfor the trend analysis is the total time for the report divided by the business interval, becausebusiness 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 ofhistorical data before trying to analyze trends.

Error AnalysisYou 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 +/- 1indicate increasing validity of the data representation.

Forecast CalculationsHP Capacity Advisor forecasting allows you to combine a range of historical data (the forecastdata 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 thecurrent date, the historical utilization data must be projected into the future. The projection isindicated in the utilization graphs by a colored background. This projection is done based on aforecast model. Forecast models can be defined globally, for individual workloads or systems, fora scenario, and for individual workloads within a scenario. Because the process for defining aforecast 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.

42 Key Capacity Advisor Concepts

The Forecast Model HierarchyThe forecast model can be specified at four different levels within Capacity Advisor, with morespecific forecast models overriding more general models, as indicated in the following table:

Table 3-5 Forecast Models

OverridesDescriptionForecast

• NothingApplies to all workloads in CapacityAdvisor for which a more specificforecast is not provided.

Global Forecast

• GlobalApplies to a specific workload inCapacity Advisor unless a morespecific forecast is provided.

Workload Forecast

• Global• Workload

Applies to all workloads within aCapacity Advisor scenario for whicha more specific forecast is notprovided.

Scenario Forecast

• Global• Workload• Scenario

Applies to a specific workload withina Capacity Advisor scenario.

Scenario Workload Forecast

Forecast Model AttributesTable 3-6 Forecast Model Attributes

DescriptionField

The forecast data range defines the set of historical data on which theforecast will be based. The forecast data range can be specified as:• A fixed interval ending on a specific date• A fixed interval beginning on a specific date• The time interval between two dates• A fixed interval ending on the last full day of data collection

Forecast Data Range Selection

When this feature is checked, forecasts are generated using the data thatis available, even if the data is incomplete. When the existing data rangeis shorter than the specified forecast range, then the forecast range isshortened to fit the available data. Default: on (checked)Unchecking the box prevents a forecast from being generated until a datarange is specified that contains an interval of collected data sufficient tofill the forecast period.Example: Assume that you want to view activity one week (7 days) intothe future using the most recent week of data. However, in this particularweek, 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 theforecast interval is filled.

Automatically adjust the specifiedrange to use existing data

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 fordecreasing utilization, or zero to indicate no change. Default: zero (0)Annual project growth rates in force for a workload within a scenario aredisplayed in the Scenario Workloads Resource Utilization Table on theEdit Scenario Workload tab.

Annual Projected Growth Rate

Forecast Calculations 43

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 theuser. It is applied linearly, so that a point 1 year from the starting point of a forecast is the resultof the full growth rate being applied to the data. The data within the range provided by the useris used to “tile” the future by applying the portion of the growth rate appropriate to each pointto each point in the data range and repeating the data set until the desired end point is reached.

Cooling CalculationsThe following section describes the multiplier that you can use to more accurately report incooling costs within your data center.

Cooling MultiplierMeaning The ratio of the energy consumed by the air conditioning system to remove heat fromthe 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 avalue between 0.3 and 1.6.Default Value .6Where you might use this multiplier• to create a power utilization reportExample A value entered of 0.9 would mean that for every 10 kilowatt-hours of energy usedby the computers, another 9 kilowatt-hours of energy are needed to cool the machine room.See the HP Capacity Advisor User Guide for related technical papers on this subject.

44 Key Capacity Advisor Concepts

4 Planning with Capacity AdvisorGetting Ready

In order to get maximum value from the Capacity Advisor tools, it is important to:• Be familiar with the HP SIM 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 DIMMswith lots of slots versus when 4 GB DIMMs are more appropriate.) HP software can accountfor 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 utilizationcharacteristics of the applications you are considering.

Getting Ready 45

Task: Planning Server ConsolidationThis section starts with a generic procedure for consolidating servers (“Understanding theProcess”), followed by an example of server consolidation (“Example: Consolidating to an ExistingServer: Stacking Programs”).

Understanding the ProcessConsolidatingworkloads to a new server or to free up an existing server is a common task. CapacityAdvisor can help to inform the decisions about how to consolidate the workloads.

NOTE:Try the HP Smart Solver Once you understand the basics of how Capacity Advisor works, youwill realize that many of the steps illustrated in this example can be done faster and on a broaderscale using the HP Smart Solver to automate the analysis of multiple possibilities. See “Usingthe Smart Solver” (page 63) for more information.

There are three fundamental approaches to consolidating servers:• Stacking workloads (representing applications) into standalone servers or nPartitions.• Stacking virtual machines into standalone systems or nPartitions.• Stacking nPartitions and virtual partitions into complexes.The task description below is based on stacking virtual machines. For other approaches, the stepdescribing editing the scenario would be different.Prerequisites To plan for consolidating servers:• You should be familiar with Capacity Advisor operations (see “Basic Procedures” (page 69)).• You must be logged in to HP Systems Insight Manager. (See “Accessing Capacity Advisor”

(page 70).)• You must have already collected data on the systems of interest (see “Gathering Data for

Capacity Advisor” (page 70)).Procedure 4-1 To Consolidate Server LoadsFor specific descriptions of each field on the user interface screens, click the help topic link onthe software screen for each task.1. Determine the Systems to Consolidate

This should include:• The servers with loads you wish to consolidate.• The server to which you wish to consolidate the loads (this can be a new server or an

existing one).Be sure to take into consideration the following:• Connectivity: are the LANs and SANs needed by all the systems to be merged available

to the server being targeted as the new host?• Security: do any of the systems require isolated networks; are any of the systems subject

to HEPA requirements?• Ownership: are all of the applications and systems to be combined owned by a common

organization or are all the owners agreeable to the consolidation?• Licensing: are there any licensing restrictions that will prevent moving the applications;

are there any advantages to moving the applications to a common server (such ascombining applications using SAP or Oracle licenses to a single server)?

• Quality of Service: are the Quality of Service requirements for each application and serverwell understood?

46 Planning with Capacity Advisor

2. Create a ScenarioFollow the procedure in “Creating a Planning Scenario” (page 98). Remember to select theservers containing the applications that you wish to consolidate and, if it is not already inthe scenario, the server you are targeting for the consolidated loads.

NOTE: You cannot specify a Virtual Machine (VM) directly. Specify a VM host to cause allthe VMs hosted by that host to be included in the scenario. Once a VM host is added to ascenario, its VM guests are accessible individually.

3. Edit the ScenarioIn this part of the process, you build a model of the new configuration that you wish toevaluate.Follow the procedure in “Editing a Scenario” (page 100) to edit the newly created scenario.While editing the new scenario, you will need to:a. Set up the host system, including making it a VM host. This involves following the

procedures in either “Creating a System” (page 105) to create a system with thecharacteristics of the new system or “Editing a System” (page 106) to change thecharacteristics of an existing system to reflect any changes being made in the existinghost.

b. Create a VM for each of the systems you are planning to consolidate by following theprocedure in “Creating a System” (page 105).

c. Move the workloads from the systems that you are planning to consolidate to theappropriate VMs by following the procedure in “Moving a Workload” (page 111). Atthis point, you can adjust resource allocations (for example, CPU cores and speed, andmemory) to model any projected change in the required resources or to accommodatedifferences in architecture and software configuration, using the procedure describedin “Editing a Workload” (page 110). See “Adjusting for Platform Changes” (page 34)for examples of applying platform multipliers to accommodate differences inarchitecture.

NOTE: The meter bars in utilization tables show resource usage and provide a quickestimate of the effect of moving each workload.

4. Estimate the New Quality of ServiceGenerate a report on the scenario following the procedure in “Producing Graphs and Reports”(page 84)

5. Repeat the Editing and Estimating Steps if NecessaryIt is sometimes necessary to run through a number of variations on the scenario to determinethe best consolidation strategy. You can repeat the preceding two steps to determine theoptimum configuration, including whether adding Temporary Instant Capacity (TiCap)processors could help optimize your cost structure.

Example: Consolidating to an Existing Server: Stacking ProgramsThis example demonstrates how Capacity Advisor can be used to plan for the simplest methodof server consolidation: stacking programs. It illustrates many screens that you will encounterin Capacity Advisor.

Task: Planning Server Consolidation 47

NOTE:Try the HP Smart Solver Once you understand the basics of how Capacity Advisor works, youwill realize that many of the steps illustrated in this example can be done faster and on a broaderscale using the Smart Solver to automate the analysis of multiple possibilities. See “Using theSmart Solver” (page 63) to learn about the Smart Solver.

Assume that several virtual machines were set up over the last few months to support applications.There is good data on resource utilization, and it is a good time to see if consolidating theapplications can free up resources for other uses.The steps referenced in the following titles are from the procedure “Understanding the Process”(page 46).

Step 1: Determine Which Systems to ConsolidateThis step requires a profound knowledge about the systems. Many questions need to be answeredabout each system. Different consolidation models make different questions appropriate andothers inconsequential. The questions listed below are derived from the questions in the genericprocedure provided above.• What set of patches (patch level) is required by the applications? (This does not matter if

virtual machines are used for consolidation.)• What changes to settings of kernel tunables have been made? (This does not matter if virtual

machines are used for consolidation.)• 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

productions systems.This list is simply illustrative, many other questions may need to be answered for your particularenvironment.For the purposes of this exercise, the following three virtual machines running on puny03 arebeing considered for consolidation:• puny03v7

• puny03v8

• puny03v9

Each of the three systems has two processors and:• Is running applications based on the same database program, which is licensed per CPU• Is running the same operating system, with the same set of patches• Requires the same settings of kernel tunables for the database application• Uses the same LAN• Uses the same SAN• Has minimal security requirements that are adequately provided by the corporate firewall

Step 2: Create a ScenarioCreate a new scenario:

48 Planning with Capacity Advisor

1. Select Optimize ⇒ Capacity Advisor ⇒ Create Scenario... from the upper menu bar.2. On the Select Systems for the new Scenario screen, click in the check box beside the

desired system to include it in the scenario. This system is the VM host for the virtualmachines to be consolidated.

3. Click the Next button.4. Fill in the Scenario Name and the Description fields.5. Click the Next button.6. Check the values presented on the Verify Scenario Parameters screen of the Create New

Scenario wizard and then click the Finish button.

Step 3: Edit the ScenarioWhen finished creating a new scenario, the Edit Scenario screen automatically opens for editingthe new scenario.

TIP:To Return to a Scenario at a Later Time... Locate the name of the scenario in the list presentedon the VSE Management: Capacity Advisor tab screen. Click the scenario name to open theCapacity Advisor - Edit Scenario window for that scenario.

The current systems in the scenario are listed on the System tab. The bar graphs in the tableshow the peak resource utilization from data collected for the current week. The following imageshows the three virtual machines mentioned at the beginning of this planning example.

Figure 4-1 Example of Bar Graphs (Meters) on a System tab in the Scenario Editor

The weekly data is representative of recent utilization and can be calculated quickly, but doesn'talways give a comprehensive picture.For a more comprehensive picture, look at a month's worth of data. Change the simulationinterval to a month by clicking the first drop-down list of the Simulation Interval (where yousee the word “Week”) and selecting Month from the list.

Task: Planning Server Consolidation 49

Once the screen has refreshed, new information about resource utilization is available. In thiscase, you can see that the utilization peaks for CPU, memory, and I/O disk bandwidth haveincreased.

Look at the CPU utilization profile for the system with the heaviest load (in this case, puny03v8),by clicking the first bar graph beside its name. A profile viewer for the selected resource andsystem opens.

There are several periodic peaks that use a little over half of the available CPU resource. Themajority of the time usage is below 25 percent of the available cores. Examining the tabularsummary can provide more insight into the resource usage on this server:

50 Planning with Capacity Advisor

From the table, you can see the average utilization is less than 7 percent of the available resource,while the 90th Percentile value is less than 9 percent of two cores. Also note that there are timeswhen applications are using a little over half of the CPU allocation for the allowed 15–minuteduration.

Adding Processors

Returning to the Edit Scenario screen through the “Go back to....” link, you can review thenumber of cores on each of the systems in a scenario in the Scenario Systems table. (See “Step3: Edit the Scenario” (page 49) for example screen shots.)In this example, all of the VMs have the same number of cores allocated (2 cores at 1.10 GHz foreach VM). A look at the month long accumulation of peaks shows that the usage of the VM CPUcore allocation ranges from 60% to 84% among the three servers. By mousing over the machinename in the left column of the systems table, you can see the current utilization limits set forthese VMs (they are allowed to exceed 85 percent utilization 0 percent of the time).

Altogether, this indicates that for best fit, a consolidated VM will need more than 2 cores tosupport all the applications.Based on the one month of data in this example, it seems unlikely that the consolidated VM willneed the 6 cores currently allocated to the three separate VMs. Taking into consideration thehistoric CPU usage and the utilization limit for all three virtual machines, one additional core isadded to the target consolidation VM, puny03v8

Task: Planning Server Consolidation 51

NOTE: It is possible to refine this estimate further by changing the utilization limits or byforecasting future growth. Also, the longer the period of data analyzed, the better the analysisof resource utilization.

Add one processor to puny03v8:1. Click the check box preceding puny03v8 in the list of systems.2. Select What-If Action ⇒ Edit System... from the Edit Scenario-System tab menu bar.3. In the resulting Edit Scenario - Edit System screen, increase the number of processors to

three. This will represent moving an additional processor from the other VMs into this one.

NOTE: You will soon realize that all of the operations done separately in this example canbe done at once on the Edit System screen if you have taken care to estimate the potentialdesired change up front for each of the resources tracked by Capacity Advisor. Thus, youcan tweak the resource allocations at the same time via this screen as you refine the fitthrough additional changes.Also, note that you can use What-If Actions ⇒ Undo/Edit/View Applied What-If Actionsto disable or re-enable changes that you have made or to easily edit multiplier values. (See“To Edit Applied What-If Actions” (page 104) and “Adjusting for Platform Changes”(page 34).)

4. Click the OK button.You are returned to the Edit Scenario-System tab screen.The CPU Utilization bar graph for puny03v8 now shows about 55% utilization of the 3cores.

Move Workloads

Next, move the workloads from selected servers (puny03v7 and puny03v9) to the consolidationserver (puny03v8).1. Click the Edit Scenario-Workload tab.2. Click the check boxes preceding the virtual machines that contain the workloads that you

are going to move.3. Select What-If Action ⇒ Move Workload... from the Edit Scenario-Workload tab menu

bar.4. When the screen repaints, locate the workloads that are to be moved. You can see that it is

possible to modify the default multiplier values for these systems at this location. For thisexample, it is not necessary to adjust the CPU or memory utilization multipliers because thesystems are already virtualized, and the processors and operating systems are the same forall the workloads.

5. Now locate the target system for the consolidation.Study the changes to the utilization meters and note the 5–star headroom ratings in thistable. (See “Headroom” (page 29) to understand the headroom rating and how to interpretit.)For this example, the following information is seen:

52 Planning with Capacity Advisor

None of the stars are green for the target system. This indicates that the new workloads donot fit the current configuration of the target system. Also notice:• Adding the workloads only incrementally increased the utilization of the cores on the

target system.• The problem is that the current settings for memory allocation are insufficient for the

additional workloads. The memory allocation should be increased, though the utilizationlimit on the memory could also be adjusted, if desired.

• Note that disk IO usage has increased to 94 percent of that allocated to puny03v8. Theutilization limit for disk I/O on puny03v8 is set to allow disk I/O activity to exceed the95 percent limit, 0 percent of the time.

6. Click the radio button preceding the target system.7. Click the OK button.8. Click the Edit Scenario-System tab and locate the puny03v8 system. The current result

of the consolidation simulation looks like this:

Increase the Memory

Returning to the Edit Scenario screen through the “Go back to....” link, you can review theamount of memory on each of the virtual machines in a scenario. (See “Step 3: Edit the Scenario”(page 49) for an example screen shot.)In this example, all of the VMs have the same amount of memory allocation (.99 GB). However,all of the VMs are using over half of their allocation, which means that a consolidated VM willneed more memory.To provide adequate memory, edit the system again.1. Click the System tab to open it.2. Check that the consolidated system (puny03v8) is still selected, and click What-If

Action ⇒ Edit System... from the System tab menu bar.3. On the resulting Edit Scenario - Edit System screen, change the memory size to 3 GB,

which represents moving memory from the other two servers to this one. While it mightappear that a smaller addition of memory would be adequate, the scenario values for memoryutilization only account for the memory used by the workloads, not the operating systemoverhead memory usage such as the data buffer cache.

4. Click the OK button.The list of systems with new values is displayed on the System tab.

Task: Planning Server Consolidation 53

Step 4: Estimate the New Quality of ServiceTo quickly estimate the quality of service of the new configuration, it is useful to review boththe utilization limits on the workloads and the combined resource utilization history of theworkloads now on puny03v8.To see the current utilization limits assigned to the workloads on the consolidated server, mouseover the workload name in the name column of the System table on the Edit Scenario-Systemtab.Because all of the workloads have the same limits in this example, we can review the limits forthe puny03v8 workload.

Now click on the CPU Utilization bar graph to open the Profile Viewer for this resource. Noticein the next example screen shot, in the Interval Metric Summary table, that peak utilization onthis system is now at 62 percent of 3 cores. As the limit for CPU utilization is 85 percent for anyworkload, it appears that more CPU is assigned than is needed for this system. In this example,the number of CPU cores probably could be set to 2.5 instead of 3 and still meet the utilizationlimits for this resource.

54 Planning with Capacity Advisor

Click the Memory radio button above the graph to switch to the memory utilization ProfileViewer. The graph indicates that memory utilization is steady, and the table data shows thatmeasured utilization comfortably approaches the utilization limit set at 65 percent for this resource.Collecting data on the system after consolidation can provide a better picture of how muchmemory is actually used by the system once it is deployed.

Task: Planning Server Consolidation 55

In Step 8 of “Moving Workloads”, it appeared that I/O disk utilization would be very near theutilization limit set for the VM host (95 percent). Click the I/O Disk radio button to check on I/Odisk bandwidth utilization.The graph and table data indicate that I/O disk bandwidth utilization is well within the utilizationlimit for the VM host.

56 Planning with Capacity Advisor

Further Analysis

The simulation scenario just completed shows that combining applications from the three virtualmachines can lead to a significant reduction of the number of processors required (from 6 CPUcores to 2.5 or 3). Using peak-of-sums modeling provides a clearer picture of resource usage ascompared to the traditional sum-of-peaks model. Depending on the licensing model for thissetup, the number of licenses required for the underlying database application may have beenreduced also. Would it be possible to reduce the number of processors further?Return to the CPU utilization profile by clicking on the CPU radio button and locate the 90thPercentile value in the Interval Metric Summary table:

This value indicates that 90 percent of processing is occurring using only 19 percent (1/5) of theavailable CPU cores. A detailed report can give more insight into what this implies for the numberof CPU cores needed.

Generate a Report on the Scenario

To investigate further reduction of CPU allocation, generate a report on the scenario:

Task: Planning Server Consolidation 57

1. Close the Capacity Advisor - Edit Scenario window.2. From the Capacity Advisor menu bar on the Capacity Advisor tab in Virtualization Manager,

select Report ⇒ Capacity Advisor Scenario Utilization Report....3. Place a check mark on both the Utilization Summary and Details to see all possible data

reported.

4. Click the Next button.The Select Report Targets screen opens.

5. Click the “Edit Scenario Selection” link.The list of scenarios is displayed.

6. Click the check box to the left of the scenario name and OK.The Select Report Targets screen opens with systems listed from the scenario that youselected.

7. Specify the date range for the report.8. Click Next.

The Select Report Details screen opens.

9. Select the type(s) of resources for which you want to see data.10. Select the type of scale for data presentation: percentage, absolute numbers, or both.11. Select the graph size, and click Finish.

The Report Created screen opens.

12. Click the “Browse Report” link, and view the report.Other variations on creating a report are available. See “Stepping Through the Report Wizard”(page 89).

Using the Report

This report combines many tabular summaries that provide detailed descriptions of the resourceutilization. The one most helpful in this instance is the Time spent at or above each percentof allocation table for CPU utilization. Scroll down to see it.

58 Planning with Capacity Advisor

From the 60% line in the table, with 0.02% of the time spent at that level, only an absolutelymission critical application would require more than three processors. Dropping down to the40% row, with 1.64% of the time spent at or below that value, some applications might be ableto tolerate dropping down to two processors. What final allocations are decided upon will be abusiness decision once the alternatives are understood.

Task: Planning Server Consolidation 59

Task: Estimating the Effect of Adding or Moving Processors

IntroductionIt 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 CapacityAdvisor, you can make more informed decisions about re-configuring your servers to improvethe 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 basedon a simple peak utilization value, but on knowing the answers to questions such as whetheryour system is more than 70% busy for an unacceptable percentage of the time.Two procedures are described below:• “Estimating the Effect of Moving Processors”• “Estimating the Effect of Adding Processors” (page 61)

Estimating the Effect of Moving ProcessorsPrerequisites To estimate the effect of moving processors:• You should be familiar with Capacity Advisor operations (see “Basic Procedures” (page 69)).• You must be logged in to HP Systems Insight Manager. (See “Accessing Capacity Advisor”

(page 70).)• You must have already collected data on the systems of interest (see “Gathering Data for

Capacity Advisor” (page 70)).Procedure 4-2 To Estimate the Effect of Moving ProcessorsFor specific descriptions of each field on the user interface screens, click the help topic link onthe software screen for each task.1. Determine the Current Quality of Service

Follow the procedure in “Utilization Reports Overview” (page 88) to generate a report withyour preferred metric for quality of service for the systems that might be exchangingprocessors.

2. Determine the Systems that Should Exchange ProcessorsMake sure to consider issues such as ownership of the systems the processors are movingamong and compatibility of the processors.

3. Create a Scenario that Includes the Systems That Will Exchange ProcessorsFollow the procedure in “Creating a Planning Scenario” (page 98) to create a scenarioincluding the systems you are planning to exchange processors among.

4. Move Processors From Donor Systems to The ReceiversFollow the procedure described in “Editing a System” (page 106) to:a. Edit the donor systems to reduce number of processors.b. Edit the receiving systems to increase the number of processors.

5. Check the New Quality of ServiceFollow the procedure in “Producing Graphs and Reports” (page 84) to generate a report onthe resource utilization of the systems in the scenario. Compare this new resource utilizationwith that described in the report that you generated before moving the processors.

6. If Necessary, Repeat Moving Processors and Checking Quality of ServiceIf the desired improvement in quality of service is not achieved, try moving processorsamong other systems in the scenario.

60 Planning with Capacity Advisor

Estimating the Effect of Adding ProcessorsPrerequisites To estimate the effect of adding processors:• You should be familiar with Capacity Advisor operations (see “Basic Procedures” (page 69)).• You must be logged in to HP Systems Insight Manager. (See “Accessing Capacity Advisor”

(page 70).)• You must have already collected data on the systems of interest (see “Gathering Data for

Capacity Advisor” (page 70)).Procedure 4-3 To Estimate the Effect of Adding ProcessorsFor specific descriptions of each field on the user interface screens, click the help topic link onthe software screen for each task.1. Determine the Current Quality of Service

Follow the procedure in “Producing Graphs and Reports” (page 84) to generate a reportwith your preferred metric for quality of service on the systems that are being consideredto receive additional processors.

2. Determine Where to Add Processors.When adding processors to an environment, it is frequently desirable to consider addingthem to more than one system. Use this step to determine the set of systems that are mostlikely to benefit from adding processors.

3. Add Processors to SystemsFollow the procedure in “Editing a System” (page 106) to add processors to one or moresystems.

4. Check the New Quality of ServiceFollow the procedure in “Producing Graphs and Reports” (page 84) to generate a report onthe resource utilization of the systems in the scenario. Compare this new resource utilizationwith that described in the report that you generated before adding the processors.

5. If Necessary, Repeat Adding Processors and Checking Quality of ServiceIf the desired improvement in quality of service is not achieved, try adding processors toother systems in the scenario.

Task: Estimating the Effect of Adding or Moving Processors 61

Task: Determining Where to Put a New Workload

IntroductionAdding a new application or set of applications to an existing server environment requires carefulplanning. Deciding where to add the new workload can be challenging; can it be placed on anexisting server, or is a new system required? With HP Capacity Advisor, the planning can bebased on real data and realistic modeling of the results of adding a new workload to the currentenvironment.

NOTE:Try the HP Smart Solver Once you understand the basics of how Capacity Advisor works, youwill realize that many of the steps illustrated in this example can be done faster and on a broaderscale using the Smart Solver to automate the analysis of multiple possibilities. See “Using theSmart Solver” (page 63) to learn about the Smart Solver.

Prerequisites To determine where to put a new workload:• You should be familiar with Capacity Advisor operations (see “Basic Procedures” (page 69)).• You must be logged in to HP Systems Insight Manager. (See “Accessing Capacity Advisor”

(page 70).)• You must have already collected data on the systems of interest (see “Gathering Data for

Capacity Advisor” (page 70)).Procedure 4-4 To Determine Where to Put a New WorkloadFor specific descriptions of each field on the user interface screens, click the help topic link onthe software screen for each task.1. Obtain Data from a Test Machine

The most accurate models are based on real data, collected over a long enough period oftime to capture the variations in load due to periodic peaks in usage (such as eventshappening “late Thursday night” or “the first and 15th of the month”). Collect data for atleast a week, and preferably for long enough to capture any periodic variations. If you cannotcollect data from a test machine and have data from a similar application running on anexisting system, you can create a new workload based on the existing data and scale it toprovide a “best guess” model of the new application's resource utilization.

2. Create a ScenarioFollow the procedure in “Creating a Planning Scenario” (page 98) to create a scenario withthe test system running the new application and all the candidate host systems.

3. Edit the Test Machine WorkloadFollow the procedure in “Editing a Workload” (page 110) to make any modifications to thedata collected on the workload necessary to reflect estimated future production loads. Thismight include increasing the processor load and/or memory usage.

4. Move the WorkloadFollow the procedure in “Moving a Workload” (page 111) to move the workload from thetest machine it has been running on to one of the potential host machines. The bar graphson the Edit Scenario - Move Workload screen provide a rough estimate of the effect ofmoving the workload to each of the candidate hosts.

62 Planning with Capacity Advisor

5. Estimate the New Quality of Servicea. Follow the procedure in “Using the Profile Viewer” (page 85) to obtain a quick overview

of the resource utilization of the system with the added workload.b. Follow the procedure in “Utilization Reports Overview” (page 88) to generate a detailed

report on the new configuration.In addition to the quantitative measures of the “goodness” of a system, it is important touse your knowledge of such things as how the system will be used, system ownership, andfuture constraints. This is an area where your knowledge of the context the application willbe run in can be as important as the estimated resource utilization.

6. If Necessary, Repeat Moving the Workload and Estimating the Quality of ServiceIt the new quality of service is not adequate, try moving the workload to another systemand estimating the quality of service. If none of the potential hosts provides an adequatequality of service, consider adding or moving processors to support the new application(see “Task: Estimating the Effect of Adding or Moving Processors” (page 60)).

Using the Smart SolverThe Smart Solver automates the manual process of repeatedly moving workloads onto differentsystems to determine an optimal solution to a problem. Below, one example use of the SmartSolver is shown; then, the various types of automated scenario changes that the Smart Solvercan provide are explained. For detailed steps while using Capacity Advisor, see the contextualonline help, accessed by pressing the Help or ? within the Capacity Advisor screens.

Example

The Existing Data Center ConfigurationSuppose you have an existing data center with two new homogenous HP Proliant servers thatact as VM hosts with the following VM guests:

Table 4-1 VM Host Configuration

VM GuestsHost

vm1hostA

vm2, vm3hostB

Existing in the data center is also a heterogeneous legacy environment consisting of olderstandalone servers. These servers have various workloads and uses; an abbreviated table of theseis shown below:

Table 4-2 Legacy Standalone Servers

UsageLegacy Servers

compilation/build serversystemC

anon ftp serversystemD

file serversystemE

......

web/wiki serversystemH

The Data Center GoalSuppose you want to eliminate the old servers, consolidating them to be VM guests on yourexisting VM hosts. Furthermore, you want to do the following:

Using the Smart Solver 63

• You wish to consolidate the legacy servers onto as few VM hosts as possible.• However, if all six legacy workloads do not fit onto the existing two VM hosts, new VM

hosts should be created until all the workloads are placed• Once the minimum number of VM hosts are determined, all the legacy workloads should

be load-balanced among those VM hosts.• When placing workloads onto the VM hosts, no existing successful utilization limits should

be broken. For example, if none of the legacy servers utilization limits are violated, whenthe workloads are placed on the VM hosts, none of the VM hosts' utilization limits shouldbe violated.

• You want to add 5% CPU usage to the legacy workloads to account for any overhead of thevirtualization software that may be encountered due to moving from a standalone systemto running as a VM guest.

Automating with the Smart SolverYou could manually attempt the various permutations of consolidating the legacy systems tothe VM hosts while maintaining the existing rules for utilization limits using the utilization datayou have gathered from the various workloads, keeping in mind that you want to create newVM hosts only when absolutely needed and the virtualization overhead, and then load balancethe workloads. Or you could run the Smart Solver to do this for you. Here's how:Assumptions The process below assumes you already have the following:• a working CMS• the VM hosts and legacy servers have been discovered by SIM• permissions and licensing to run Capacity Advisor• collected data for the workloads involvedThe Process Below is the general process for this situation to utilize the Smart Solver. (Detailedsteps and screen descriptions for the required screens below are described in the online help.)1. Create a new scenario that contains the existing VM hosts (hostA and hostB) and the legacy

servers.2. In the list of scenarios, edit this new scenario by clicking on the scenario's name.3. In the list of systems and workloads, select all the legacy servers (systemC, systemD, ...

systemH).4. Using the What-If Action menu under the System tab, select the Smart Solver menu pick

Automated System Consolidation to VM.... Within the first Smart Solver screen, selectyour desired parameters:a. Select Destination Hosts

1) Select the radio button that describes the target VM hosts. In this case, you wish touse the existing VM hosts and have any new VM hosts created if the legacyworkloads do not fit on the existing VM hosts; therefore, select the radio buttontitled Use existing hardware for workload placement and use host templatefor overflow.

2) Check the boxes of the existing VM hosts (hostA and hostB) shown in the systemstable.

3) Create a template VM host system for any new VM hosts that may need to becreated to handle all legacy workloads. The values for CPU, memory, etc., canmatch those of the existing VM hosts for a more homogenous configuration.

b. Enter CPU Virtualization Overhead Enter 5.0 for the 5% CPU utilization overhead (theoverhead of the virtualization software that may be encountered due to moving froma standalone system to being a VM guest).

64 Planning with Capacity Advisor

c. Check Load Balancing Option Check the box to turn on load balancing. This movesthe workloads so that resulting solution has the workloads of the VM guests balancedacross the VM hosts.

d. Select the Level of Effort Higher levels of effort by the Smart Solver require more timeand often produce better results.

e. Click the OK button to begin the Smart Solver computations.

Viewing the Results Once the Smart Solver has completed, you will be shown its results. In thiscase, it shows the best configuration for converting and placing the legacy systems onto VMhosts based on the above parameters. You can expand the various sections for detailed information.Saving and Reviewing the Results Additionally, you can save the results into a new scenarioby selecting the Save As button. Once the scenario is saved using the Save As button, youshould be taken back to the list of scenarios. From there, you can create a Scenario Comparisonreport, a comparative report of the original scenario with its legacy standalone servers and thenew scenario with these servers now converted and running as VM guests. Depending uponyour report options and the data you've collected for the systems, you can see everything fromhow the consolidation uses previously wasted (unused) CPU cycles to changes in power costs.

Types of Smart Solver SolutionsThe following sections describe the various Smart Solver solutions that you can choose to runon an existing scenario.

Results: Automated Consolidation to VMs

Expected Results

The solutions show the systems converted to VM guests on VM hosts. These VM hosts are eitherexisting VM hosts, what-if generated template VM hosts, or a combination, depending on whatdestinations you selected. When a combination of VM hosts are chosen, the placement of VMguests 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 theconsolidation solution. In other words, if the consolidation solution results in any VM hosts beingunused (and therefore, not required in the solution), the unused systems will not be involved inthe 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 theminimal requirement for headroom, while taking into consideration resource utilization andutilization 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 utilizationacross the resulting systems) was selected, the VM guests were load balanced across the systemsthat had 1 or more VM guests.Resource Capacity. Workloads that specify utilization limits for a metric (for example, memoryor 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, thatworkload 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 appliedbefore using the Smart Solver. This can be any type of utilization limit, including the defaultglobal utilization limit.Headroom Ranking The headroom ranking shows the amount of available resource above theexisting resource utilization that will exist for the resulting solution in the simulation. Amongthe solutions that require the same target systems, the solution with the tightest fit is shown.

Using the Smart Solver 65

Possible Anomalies in the Results

Fewer Systems Shown. The Smart Solver solution can contain fewer VM host targets than wereoriginally 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 canfit 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 balancedonly 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. VMhost C is not included for the load balancing calculation.Headroom Ranking Shows Zero (0) Stars. The headroom ranking shows zero stars even thoughit appears that there is sufficient room on the VM host for the workloads. This happens wheneverone 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 servers are not already violating autilization limit (Choose What-if Actions Edit System...)

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, utilizationlimits, and headroom, where the goal is to distribute workloads so that each system hascomparable headroom and therefore, similar headroom ranking.Resource Capacity. Workloads that specify utilization limits for a metric (for example, memoryor 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, thatworkload 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 appliedbefore using the Smart Solver. This can be any type of utilization limit, including the defaultglobal utilization limit.Headroom Ranking The headroom ranking shows the amount of available resource above theexisting resource utilization that will exist for the resulting solution in the simulation. Amongthe 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 becausesmaller systems generally are assigned a smaller percentage of usage than larger systems, andvery 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 smaller4 GB system at 87% has only 500 MB of headroom. Aiming for 87% usage on both systems wouldnot yield a balanced solution. Instead, a balanced solution is to fill the larger system to 87% andfill the smaller system to only 50%. With this placement, workloads placed on either system willhave the same amount of headroom to grow (2 GB).No Apparent Change from Original Configuration. The solution may be the same as the originalscenario, and it looks as though no computation was performed. Actually, with the currentattributes and constraints, the Smart Solver could not find a better solution than the currentconfiguration 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 displayedin RED text).No Apparent Change on 1 or More Systems. The solution may show no change on 1 or moredestination systems. Thus, it may appear that the Smart Solver did not include the server in its

66 Planning with Capacity Advisor

computations. In actuality, the Smart Solver determined that as part of the best solution, it wasbest to leave these target systems with their original configurations.Fewer Systems Shown. The Smart Solver solution can contain fewer VM host targets than wereoriginally 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 canfit into VM hosts A and B, then only VM hosts A and B are shown in the solution.Smaller Systems Appear Unused. The solution may not display smaller systems, making itappear 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 therobustness of those systems. If the workloads fit on larger, more robust systems and the smallersystems 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 onlythe two large systems, and load balancing will occur only on those two systems.

Results: Automated Workload Stacking

Expected Results

The solutions show the target systems with the selected workloads placed to require as few ofthe target systems as possible. The target systems are either existing VM hosts, what-if generatedtemplate VM hosts, or a combination, depending on what targets you selected. When acombination of VM hosts are chosen, the placement of VM guests goes first to existing VM hosts.and then to the template-generated VM hosts.Resource Capacity. Workloads that specify utilization limits for a metric (for example, memoryor 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, thatworkload 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 appliedbefore using the Smart Solver. This can be any type of utilization limit, including the defaultglobal utilization limit.Headroom Ranking The headroom ranking shows the amount of available resource above theexisting resource utilization that will exist for the resulting solution in the simulation. Amongthe 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 wereoriginally 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 canfit 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 balancedonly 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. VMhost C is not included for the load balancing calculation.

Getting More DetailIn 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.

Using the Smart Solver 67

Choosing Systems to Consolidate:When choosing systems, the automated compute engine is not cluster-aware; this includesServiceguard as well as VMware clusters. It is possible that a system within a cluster could bemoved out of the cluster during the automated compute engine process. Therefore, within agiven selection, you should either have no cluster members or include all or a subset of membersfrom one cluster.

Related Topics“Automated Solution Finding: System Consolidation to VMs” (page 119)“Automated Solution Finding: Load Balance of Servers or VM Hosts ” (page 121)“Automated Solution Finding: Workload Stacking” (page 122)

68 Planning with Capacity Advisor

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

OverviewHP Capacity Advisor provides a collection of utilities for the capacity planner, but to begin usingthem, you must start with the following:• Access the product (see “Accessing Capacity Advisor” (page 70)).• Gather data (see “Gathering Data for Capacity Advisor” (page 70)).With access, and collected data, you can do the following tasks:• Manipulate scenarios (simulations that allow you to ask "what if?" questions based on real

data), including the following actions:— Create scenarios. You can select the systems to use in the scenario, name the scenario,

and provide a short description. See “Creating a Planning Scenario” (page 98).— Edit scenarios.You can adjust the simulation parameters (such as the interval, beginning

and ending dates), move workloads and virtual machines, and create and edit systems.See “Editing a Scenario” (page 100).

— Copy a scenario lets you start with an existing scenario to build a new one. See “Copyinga Scenario” (page 102)

— Rename a scenario. See “Renaming a Scenario” (page 103)— View, modify, or undo changes to a scenario. See “Undoing or Editing Changes to

Scenario” (page 103).— Control the behavior of a scenario by modifying the time interval and reported metric.

See “ Controlling the Data Display” (page 100).— Delete unwanted scenarios. See “Deleting a Scenario” (page 104).

• Manipulate systems within a scenario. Systems can represent real systems or just simulatenew systems, and can be either physical or virtual systems. You can do the following tasks:— Create systems for the scenario. See “Creating a System” (page 105).— Add an existing system to the scenario. See “Adding an Existing System” (page 106).— Edit system resources. See “Editing a System” (page 106).— Move virtualmachineswithin the scenario. See “Moving a Virtual Machine” (page 108).— Removing systems. See “Removing a System” (page 108).

• Manipulate workloads within a scenario. Workloads represent applications running onsystems and can be moved across systems within a scenario. You can do the following tasks:— Create workloads within the scenario. See “Creating a Workload” (page 109).— Edit workload attributes. See “Editing a Workload” (page 110).— Move workloads within the scenario. See “Moving a Workload” (page 111).— Park workloads. Parking a workload removes the effects of the workload from the

scenario, losing the definition of the workload. See “Parking a Workload” (page 113).— Remove workloads from the scenario. See “Removing a Workload” (page 113).

• View graphs and review data, including the following actions:— Access the ProfileViewer. The Profile Viewer provides a graphical display and a tabular

summary of resource utilization. See “Using the Profile Viewer” (page 85).— Generate and review resource utilization reports. Reports can combine information

from multiple systems and workloads, from historical data or from data that is computedfrom a scenario. (See “Utilization Reports Overview” (page 88). ) Reports can then besaved to a file and then mailed to others or put on a web server.

Overview 69

Accessing Capacity AdvisorBefore you can use HP Capacity Advisor, you must access it using HP Systems Insight Manager(HP SIM).This procedure assumes the following:• You are familiar with HP Systems Insight Manager. For information on HP SIM, select

Help ⇒ For HP Systems Insight Manager from the upper, HP SIM menu bar to access theHP Systems Insight Manager Technical Reference Guide

• You have appropriate licenses to use Capacity Advisor on the Central Management Server(CMS) and the systems you wish to monitor with HP Capacity Advisor (see HP InsightDynamics — VSE and HP VSE Management Software 4.1 Getting Started Guide).

Procedure 5-1 Accessing Capacity Advisor1. Open a Web browser.2. Enter the following in the address field (it is not always labeled in browsers):

http://SIM-Host:280/

where SIM-Host is the server running HP Systems Insight Manager (HP SIM).

3. Press Enter.A login screen is displayed (if security dialogs are presented first, respond appropriately).

4. Fill in the User name and Password fields.5. Click Sign In or press Enter.

The screen displayed will depend on the last session you had in HP Systems Insight Manager.

6. If the VSE Management: Capacity Advisor screen is not displayed, selectOptimize ⇒ Capacity Advisor ⇒ View Scenarios ... from the HP SIM menu bar.The VSE Management: Capacity Advisor screen is displayed, with a list of the scenariosthat have already been created.

Gathering Data for Capacity AdvisorHP Capacity Advisor works best when using generous amounts of data to generate reports andcreate meaningful simulation scenarios. Though it is most efficient and effective to collect dataon a regular schedule, you can also start an up-to-date data collection for reports and profilegeneration at any time. Collected data is kept on a managed system for 30 days and on the CMSfor four years.To create a meaningful simulation scenario or to view the historical resource utilization of aworkload, you must collect data from representative systems or the systems for which you wantto monitor resource utilization.Once you have collected the data, you can create simulation scenarios or experiment with differentconfigurations and workloads to evaluate your system capacities. You can use Capacity Advisorto 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 HP SIM and VSE Management Software, you musthave the following configured on the CMS:

70 Basic Procedures

• Authorization in the Central Management Server (CMS) to run the Capacity Advisor toolboxon the managed system

• WBEM credentials in the CMS to access WBEM on the managed system

Impact of Data Collection on Managed System PerformanceThe data collection process is purposely designed to consume few resources on the managedsystems from which data is being collected. This means you can feel free to collect data wheneveryou want. However, the data collection process can take a relatively long time to run to completionwhen collecting data from a large number of systems.Collected Capacity Advisor data is not the same as VSE data. For a diagram of the CapacityAdvisor data collection infrastructure, see Figure 2–1.

Data Collection OptionsWhen preparing to collect data for use in scenarios or for obtaining historical activity reports,consider the following:• 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 provided with VSE Management Software, by way of agentlessmeans, or by import from other HP data collectors)For discussions of various collection agencies, see “Comparison of Agentless and UP DataCollection” (page 21) and “HP PMP Data Differs from Utilization Provider Data” (page 22).

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

Deciding From Which Servers to Collect Data collection via Capacity Advisor is limited to thosesystems recognized as servers within HP Systems Insight Manager (HP SIM). The list of allpossible servers can be viewed by opening the All Systems view or the All Servers view in theHP SIM left navigation bar. The list of all possible servers that are licensed with VSE ManagementSoftware can be viewed by opening the All VSE Resources view in the HP SIM left navigationbar or by opening HP Virtualization Manager (Tools ⇒ VSE Management... on the HP SIMmenu bar).You may also have servers in mind where data collection has been accomplished using softwareother than the Utilization Provider. This can be done by collecting data from licensed systemsfor which Capacity Advisor has agentless data collection capability or by importing data collectedby other agents, such as HP OpenView Performance Agent or HP Performance ManagementPack.Regardless of the method of data collection, once the data is brought into the VSE ManagementSoftware database, it can be used in Capacity Advisor scenarios and reports for analysis andplanning. For information on bringing agentless and imported data into Capacity Advisor, seethe following topics:How to Collect Data Using Capacity Advisor Data collection functions are accessible frommultiple locations:• the HP SIM Configure, Optimize, and Tasks & Logs menus• the VSE Visualization tab (Tools menu)• the VSE Capacity Advisor tab (Tools menu)• using capcollect, capagentlesscfg, capovpaextract, or cappmpextract on the command line.(see

“Command Reference” (page 127))

Gathering Data for Capacity Advisor 71

NOTE:Licensing and Data Collection Typically, servers from which data are collected are licensed forCapacity Advisor and VSE Management Software. However, it is possible that not all servers ina data center or network are licensed to run VSE. One way to gather data from these servers foruse in scenarios is to install the Utilization Provider (in the VSE agent depot) and license eachserver with the HP Insight Capacity Advisor Consolidation software. You can also license eachserver where which you intend to use agentless data collection.For information on installing the Utilization Provider, see VSE Management: Download Agentsand Providers (scroll down for instructions). For general information about licensing systems,see the HP Insight Dynamics — VSE and HP VSE Management Software 4.1 Getting Started Guide .For discussion of using the HP Insight Capacity Advisor Consolidation software to collect datafor a systems consolidation effort, see “Data Collection and the HP Insight Capacity AdvisorConsolidation software” (page 80).

When to Collect Data Data collection via Capacity Advisor can be controlled to occur at differenttimes 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 collectionOnce you have determined the method and location for data collection, updating the data storedin the Capacity Advisor database operates the same regardless of how the data was collected.

First Data Collection (or the Automated Nightly Collection)In general, the procedures for collecting data are similar: you must select the target system orsystems, schedule the collection task for a later run or to run now, and start the task.Upon installation of VSE Management Software (and Capacity Advisor in particular), CapacityAdvisor is set to automatically collect data from all discovered managed nodes that are licensedto run Capacity Advisor and from managed nodes that have the HP Insight Capacity AdvisorConsolidation Software license. The data collection is set to start at midnight on the CMS timeclock. This is called the nightly data collection. It occurs automatically at this time unless anduntil it is disabled or rescheduled to a different time.

For Large Numbers of Managed Nodes:Collecting data from a large number of managed nodes (>500 nodes) at once can consume allavailable memory on the CMS. To avoid running out of memory, consider scheduling datacollection for two or more manageable blocks of nodes (<500 nodes each) to occur at differenttimes.For collections of >1000 nodes, this default nightly collection will fail. If it is important to collectdata from more than 1000 nodes, and memory use is not an issue, alter the default nightlycollection. The schedule that you create in this way should not fail at higher numbers of nodesas long as there is sufficient memory for the collection.The following procedure can be used to stop automatic collection on a large number of systemsor to move the nightly collection time to a period more suitable to your network.

Prerequisites To alter the automated nightly data collection:• You must be logged in to HP Systems Insight Manager as a privileged Administrator user

or root. (see “Accessing Capacity Advisor” (page 70)).Procedure 5-2 To Alter the Automated Nightly Data CollectionFor specific descriptions of each field on the user interface screens, click the help topic link onthe software screen for the task.

72 Basic Procedures

1. Select Tasks & Logs ⇒ View All Scheduled Tasks... from the HP SIM menu bar.2. From the list of current tasks, select Collect ALL Capacity Advisor Data Nightly....3. If you would like to modify the timing, click Edit.

The Task Confirmation screen is displayed.

4. Click Schedule.5. Select Periodically from the list labeled When would you like this task to run?.6. In the area labeled Refine Schedule:, set the time of your choice.7. Click Done.

The Task Results screen is displayed. The data collection will start when the system clockreaches 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 andDone. If you now want to schedule a regular data collection for one or more blocks ofmachines, see “Scheduling a Data Collection” (page 74).

Interpreting Task ResultsOnce the Status field shows Complete, the collection task is complete. An Exit code of 0meanscomplete success. Positive values indicate partial or complete failure. For a complete explanationof the error codes, see capcollect(1M).The results of the task are presented in the Stdout and Stderr tab windows. The messages onthe Stdout tab include indications of any errors that occur. Be sure to click both tabs for a completeunderstanding of what happened. See also Appendix D (page 163)and “Capacity AdvisorMessages” (page 167) for additional information to help you troubleshoot data collection errors.

Error Notification on the Standard Out TabWhile error messages are sent to the Stderr tab, the fact that errors have occurred is indicatedon the Stdout tab. The messages sent to the Stdout tab are explained below. .

All utilization data collected for whole-OS workload "system-name"

All utilization data collected for workload "workload-name" on "system-name".

All physical CPU utilization data collected for HPVM "vm-name" from HPVM Host "vm-host-name".

Data collection succeeded on the system. No need to check the Stderr tab if this is the onlytype of notification.

Some utilization data collected for "system-name"

Although data collection was not entirely successful, some utilization data was collected. Checkthe 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.

Gathering Data for Capacity Advisor 73

No data was collected from one or more systems. Check the Stderr tab. For each of the failedsystems, there will be one or more messages, including the host name.

As you review and analyze the resulting data collection, you may notice discrepancies. See“Possible Sources of Discrepancies in Collected Data” (page 83) for information.

Scheduling a Data CollectionAs conditions evolve over time or to manage data collection for large numbers of servers, youcan schedule one or more periodic data collections in addition to, or in place of, the automatednightly collection. At the scheduled time, Capacity Advisor will pull data collected by theUtilization Provider or via the agentless configuration file into the VSE database on the CMS forstorage.Prerequisites To create a collection schedule:• You must be logged in to HP Systems Insight Manager (see “Accessing Capacity Advisor”

(page 70)).Procedure 5-3 To Collect Data on Selected SystemsFor specific descriptions of each field on the user interface screens, click the help topic link onthe software screen for the task.1. Select Optimize ⇒ Capacity Advisor ⇒ Collect Capacity Advisor Data... from the HP

SIM 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 selectingfrom:.A list of filters is presented.

3. Select an appropriate filter from the list. All Systems will list all the available systems, whileother choices will constrain the selection list to subclasses of systems. The choice All VSEResources restricts the list to those likely to be licensed for data collection.

4. 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. (Foradditional help on selecting targets, see the HP Systems Insight Manager Technical ReferenceGuide on “Creating a Task”.)

5. Click Apply.The Verify Target Systems screen of the wizard displays the resulting list of target systems.

6. If you wish to collect data on more targets, click Add Targets and repeat the preceding twosteps.

7. 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. Click Remove Targets.The targets with check marks in the check boxes disappear from the list.

8. Once the list has the correct set of targets, click Next.The Task Confirmation screen of the wizard is displayed.

9. To start a one-time collection immediately, click Run Now.The Task Results screen is displayed. See “Interpreting Task Results” (page 73).

10. To schedule the timing for a periodic collection, click Schedule.11. The Schedule Task screen is displayed.12. Select Periodically from the list labeled When would you like this task to run?.

74 Basic Procedures

13. In the area labeled Refine Schedule:, set the time of your choice.14. Click Done.

The Task Results screen is displayed. The data collection will start when the system clockreaches the time that you have set.

See “Interpreting Task Results” (page 73) for more information about the Task Results screen.

Modifying a Collection ScheduleAs collection needs change over time, you can modify an existing schedule for better results.Prerequisites To modify a collection schedule:• You must be logged in to HP Systems Insight Manager (see “Accessing Capacity Advisor”

(page 70)).• You must be the creator of the collection schedule that you want to modify, or a privileged

administrator user.Procedure 5-4 To Modify a Collection ScheduleFor specific descriptions of each field on the user interface screens, click the help topic link onthe software screen for the task.1. Select Tasks & Logs ⇒ View All Scheduled Tasks...from the HP SIM menu bar.

The All Scheduled Tasks screen displays a list of the tasks that have been associated withyour current user ID.

2. Click the radio button beside the task you wish to reschedule.3. Click Edit.

The Task Confirmation screen of the Collect Capacity Advisor All wizard displays.

4. Click Schedule.The Schedule Task screen of the wizard displays.

5. Modify the Schedule Task screen of the Collect Capacity Advisor Data All wizard.6. Click Done.

The All Scheduled Tasks screen displays.

Removing a Collection ScheduleAs your collection needs change over time, you might need to remove a collection schedule.Prerequisites To remove a collection schedule:• You must be logged in to HP Systems Insight Manager (see “Accessing Capacity Advisor”

(page 70)).• You must be the creator of the collection schedule that you want to modify, or a privileged

administrator user.Procedure 5-5 To Remove a Collection Schedule1. Select Tasks & Logs ⇒ View All Scheduled Tasks... from the HP SIM menu bar.

The All Scheduled Tasks screen displays a list of the tasks associated with your currentuser ID.

2. Click the radio button beside the task that you wish to delete.3. Click Delete.

A confirmation screen displays.

Gathering Data for Capacity Advisor 75

4. 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 areno available tasks to display.” replaces the list of tasks.

Updating Collected DataAt times, such as when you are generating reports and developing or refining scenarios, youmay want to trigger data collection so that your work is based on the most up-to-date data. Youmay want to do one of the following actions:• Update the collected data on all available systems ( see “Updating Collected Data on All

Systems”).• Update the collected data from some systems (see “Updating Collected Data on Selected

Systems”).• Update the collected data presented in a Profile Viewer report (see “Updating Data Displayed

in a Profile Viewer”).

Updating Collected Data on All SystemsYou 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 HP Systems Insight Manager (see “Accessing Capacity Advisor”

(page 70)).• Your user name and password must be recognized for privilege elevation. Privilege elevation

gives you temporary access to advanced tasks in HP SIM and VSE Management Software.(See “Networking and Security” in the online HP Systems Insight Manager Technical ReferenceGuide to learn how to assign privilege elevation permission to a user.)

Procedure 5-6 To Update Collected Data on All Systems1. Select Optimize ⇒ Capacity Advisor ⇒ Collect Capacity Advisor Data ALL... from the

HP SIM menu bar.This starts the wizard for collecting data from all systems licensed for Capacity Advisor.

2. Fill in your user name and password to elevate your access privilege for this task.3. Click Run Now.

See “Interpreting Task Results” (page 73) for more information about the Task Resultsscreen.

Updating Collected Data on Selected SystemsAt times, you might want to collect data on selected systems. In this case, follow the sameprocedure as for “Scheduling a Data Collection” (page 74), steps 1–9.

76 Basic Procedures

Updating Data Displayed in a Profile ViewerTo update the data in a Profile Viewer display:• You must be in a Profile Viewer (see “Using the Profile Viewer” (page 85)).Procedure 5-7 To Update Data that a Profile Viewer is Displaying• 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 commandare shown at the top of the screen.

Collecting Data Without Using an AgentThis section describes how to progress through the screens that you encounter when configuringa list of systems from which to gather data without the use of an agent for use in Capacity Advisor.Agentless data collection is currently available for systems that run supported versions ofMicrosoft® Windows® operating system and that are licensed for Capacity Advisor.

Adding Systems to the Configuration FileThis section describes the procedure to follow when adding systems to the agentless data collectionconfiguration file.

Prerequisites

To add one or more systems:• You must be logged in to HP Systems Insight Manager with “VSE All Tools” or “Capacity

Advisor” tools permissions.• The systems to be added must be running a Microsoft® Windows® operating system.• The systems to be added must be licensed for Capacity Advisor.Procedure 5-8 Adding Systems to the Agentless Data Collection FileThis procedure assumes that you are starting from the Virtualization Manager Visualization tabin an appropriate perspective view.1. In the Visualization tab window, click the check box on the upper left hand corner of each

server that you want to add to the agentless data configuration file.Each selected box changes color.

2. From the Visualization tab menu bar, select Configure ⇒ Agentless Data Collection ⇒ AddAgentless Systems...

The Verify Target Systems screen opens. The systems selected in the previous step arelisted.

TIP:Are the managed node names fully qualified? Make sure that the managed node namesthat you select to add to the agentless data collection configuration file are fully qualified.Using incomplete domain names in the agentless data collection file forces the network tospend more time (and packets) to ascertain the identity of the server from which to collectdata. Using fully qualified domain names to identify systems in your network lessens thenetwork traffic required for agentless data collection significantly.

3. Optionally, you can use the control buttons on this screen to add or remove systems fromthis list.

Gathering Data for Capacity Advisor 77

4. When satisfied that the list is complete, click Next.The Task Confirmation screen opens.

5. Confirm the information, then click Run Now.The Task Results screen opens.

6. When the command completes successfully, the current contents of the configuration fileare listed on the Stdout tab.At this point, agentless data collection from the systems that were added to the configurationlist begins.If you suspect an error, check the Stderr tab for more information.

For specific screen descriptions, see “Add Agentless Systems Screens” in Capacity Advisor Helponline in the software.

Listing Systems Currently in the Configuration FileThis section describes the procedure for determining the current settings for agentless dataconfiguration on a CMS, particularly the list of systems from which to collect data using thismethod.

Prerequisite

To view the contents of the configuration file:• You must be logged in to HP Systems Insight Manager with any level of VSE permissions.Procedure 5-9 List Systems in the Agentless Data Collection File1. Select an appropriate menu pick.

For example, from the Capacity Advisor tab, select Configure ⇒ Agentless DataCollection ⇒ List Selected Systems....

2. The Task Confirmation screen opens.3. Click Run Now.

The Task Results screen opens.When the command completes successfully, the current contents of the configuration fileare listed on the Stdout tab.If you suspect an error, check the Stderr tab for more information.

For specific screen descriptions, see “List Agentless Systems Screens” in Capacity Advisor Helponline in the software.

Removing SystemsThis section describes the procedures that you can follow when you want to remove some or allsystems from the agentless data collection configuration file.

Remove One or More Systems

Use this procedure when you want to remove some, but not all systems from the agentless datacollection file.

78 Basic Procedures

Prerequisites

To remove one or more systems:• You must be logged in to HP Systems Insight Manager with “VSE All Tools” or “Capacity

Advisor” tools permissions.Procedure 5-10 Remove One or More Systems from Agentless Data Collection FileThis procedure assumes that you are starting from the HP SIM Configure menu.1. Optionally, review the current configuration list prior to removing systems from the list.

a. Select Configure ⇒ Configure VSE Agentless Collection ⇒ List AgentlessSystems....

b. Click through the progression until you can view the current configuration details. (See“Listing Systems Currently in the Configuration File” (page 78) for information aboutthis step.)

c. Click View Printable Report to access a printable report of the current configurationlist of agentless systems.

2. Select Configure ⇒ Configure VSE Agentless Collection ⇒ Remove AgentlessSystems....The Verify Target Systems screen opens.

3. Create the list of systems to be removed from the agentless data configuration file.a. Click Add Targets, and select systems to add to the removal list.b. When the list of systems to remove is complete, click Apply.

The new list is displayed.

4. Click Next.The Task Confirmation screen opens.

5. Review the information given.6. Click Run Now.

The Task Results screen opens. The results of the action appear in the Stdout and Stderrtabs. For successful execution, the Stdout tab displays the current information included inthe agentless data collection configuration file.At this point, agentless data collection from the systems that were removed from theconfiguration list is stopped.

Remove All Systems

Use this procedure when you want to remove all systems at once from the agentless data collectionconfiguration file.

Prerequisites

To remove all systems:• You must be logged in to HP Systems Insight Manager with “VSE All Tools” or “Capacity

Advisor” tools permissions.Procedure 5-11 Remove All Systems from Agentless Data Collection FileThis procedure assumes that you are starting from the Capacity Advisor tab in VirtualizationManager.1. Select Configure ⇒ Agentless Data Collection ⇒ Remove All Selected Systems....

The Task Confirmation screen opens.

2. Review the information given.

Gathering Data for Capacity Advisor 79

3. Click Run Now.The Task Results screen opens. The results of the action appear in the Stdout and Stderrtabs.At this point, agentless data collection from all the systems that were removed from theconfiguration list is stopped.

For specific screen descriptions, see “Remove Agentless Systems Screens” in Capacity AdvisorHelp online in the software.

Setting Advanced OptionsThis section describes the procedure to use when defining advanced options to be included inthe agentless data collection configuration file.

Prerequisite

To change advanced options:• You must be logged in to HP Systems Insight Manager with “VSE All Tools” or“Capacity

Advisor” tools permissions.Procedure 5-12 Setting Advanced Options in the Agentless Data Collection FileSelect an appropriate menu pick.For example, from the Capacity Advisor tab, select Configure ⇒ Agentless DataCollection ⇒ Advanced Agentless Options....The Specify Parameters screen opens.1. Optionally, change the polling interval.2. Optionally, change the number of collector threads to assign to the task of collecting this

data.3. When satisfied with changes, click Run Now.4. The Task Results screen opens.

When the command completes successfully, the current contents of the configuration fileare listed on the Stdout tab.If you suspect an error, check the Stderr tab for more information.

For specific screen descriptions, see “Advanced Agentless Options Screens” in Capacity AdvisorHelp online in the software.What Now? Once you have edited the agentless data collection configuration file to containthe set of desired servers and options, you might want to:• View reports and graphs to determine the effects of the changes (see “Using the Profile

Viewer” (page 85)).

Data Collection and the HP Insight Capacity Advisor Consolidation softwareHP provides the HP Insight Capacity Advisor Consolidation software specifically to address theneed to understand resource utilization on servers that are targeted for consolidation onto othersystems. Such servers often will not be running VSE Management Software. Yet, being able touse Capacity Advisor's planning facilities can greatly reduce the amount of time needed to plana consolidation effort.The HP Insight Capacity Advisor Consolidation software provides you with an additional,limited license to obtain data from these types of servers for use in Capacity Advisor scenarios.For 6 months from the time the license is locked into its assignment to a server, you can collectdata to use in your consolidation planning scenarios within Capacity Advisor.

80 Basic Procedures

Assigning the Consolidation Software License to a ServerThis help topic focuses on applying and using the HP Insight Capacity Advisor Consolidationsoftware. For an overall discussion of licensing for Capacity Advisor and other VSE ManagementSoftware, see theHP Insight Dynamics—VSE andHPVSEManagement Software 4.1 Getting StartedGuide.

The HP SIM License Manager

The HP SIM License Manager allows you to view the available and applied licenses for allproducts in the HP SIM License Manager database. You can use License Manager to add HPInsight Capacity Advisor Consolidation software licenses to the database and to assign them tomanaged servers known to HP SIM. For VSE license information and general instructions onhow to add these licenses to HP SIM, see “VSE Licenses” in the VSE Management Software Help.To use HP SIM License Manager, you must have administrative rights on the CMS and you mustbe authorized for the All Tools toolbox on the managed systems that you want to license.Procedure 5-13 Use License Manager to View and Assign LicensesFor specific descriptions of each field on the user interface screens, click the help topic link onthe software screen for the task.1. From the HP SIM menu, select Deploy ⇒ License Manager.... License Manager displays

the Product License Information screen.2. Select HP Insight Capacity Advisor Consolidation software from the displayed list. To see

all of the servers that are currently licensed for that product, click Licensed System(s)....3. To view the number of available licenses, select HP Insight Capacity Advisor Consolidation

software and click Manage Licenses....4. The number of available licenses and the number of assigned licenses are displayed.

NOTE:Available licenses are those that have been added to the pool of licenses, but that have notbeen assigned to a particular server.Assigned licenses are licenses from the pool that are assigned to particular servers. Generally,assigned licenses can be unassigned, returning them to the pool of available licenses.However, this ability to release an assigned license for use on a different server is limited.Once a user of Capacity Advisor takes an action that obtains or uses data from the licensedserver, that license assignment becomes permanent for the duration of the license (a usedlicense). Until then, the license can be unassigned.

5. Click Assign Licenses to begin selecting the target systems.

Using Capacity Advisor with Consolidation Software Server DataBecause servers using the HP Insight Capacity Advisor Consolidation software are not licensedfor VSE Management Software, you must use HP SIM Optimize menu options for CapacityAdvisor 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 utilization and scenario comparison reports

Gathering Data for Capacity Advisor 81

Viewing the Licensed Servers in HP SIMAnother implication of this limited license is that servers with this license are not visible in theVisualization tab of HP Virtualization Manager. To see these servers in a list, look for “AllServers” 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 Because serversusing the HP Insight Capacity Advisor Consolidation software for inclusion in scenarios or forcreating reports.

Importing Data for Use in Capacity AdvisorTo import system utilization data, the system must be discovered by HP SIM.For systems that you know are running HP OpenView Performance Agent (OVPA), you canverify 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 HP SIM menu bar,select Options ⇒ Discovery.... You must be a privileged Administrator user or root to see thisoption.) For help on adding a system manually, see the “Discovery and Identification” topic inthe HP Systems Insight Manager Technical Reference Guide. After you add a system, verify that thesystem appears in “All Systems” view.For systems running HP Performance Management Pack (PMP), select Optimize ⇒ CapacityAdvisor ⇒ List 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,you can import system utilization data into Capacity Advisor.

From the HP SIM Optimize Menu — Import HP OVPA DataPrerequisites To import OVPA-collected data for selected systems:• You must be logged in to HP Systems Insight Manager (see “Accessing Capacity Advisor”

(page 70)).• The system(s) must be discovered by HP SIM.Procedure 5-14 Import HP OVPA Data Into Capacity Advisor1. Click Optimize ⇒ Capacity Advisor ⇒ Import OVPA System Data....2. Select the target system(s).

The Verify Targets screen displays.

3. 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. Optionally, specify [-p] if the import is for a non-VSE workload.6. 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 Resultsscreen. For general help on interpreting the information in this screen, see the HP Systems InsightManager Technical Reference Guide 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

82 Basic Procedures

standard error (stderr) information displayed on tabbed panes in this screen. Check both tabsfor relevant information.

From the HP SIM Optimize Menu — Import HP PMP DataPrerequisites To import PMP-collected data for selected systems:• You must be logged in to HP Systems Insight Manager (see “Accessing Capacity Advisor”

(page 70)).• The system(s) must be discovered by HP SIM.Procedure 5-15 Import HP PMP Data Into Capacity Advisor1. Click Optimize ⇒ Capacity Advisor ⇒ Import PMP System Data....2. Select the target system(s).

The Verify Targets screen displays.

3. 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. Optionally, specify [-p] when the import is for a non-VSE workload.6. Optionally, specify [-o] when you want the new data to overwrite existing data for the

system within the Capacity Advisor database.7. 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 Resultsscreen. For general help on interpreting the information in this screen, see the HP Systems InsightManager Technical Reference Guide 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) andstandard error (stderr) information displayed on tabbed panes in this screen. Check both tabsfor relevant information.

From the Command Line• Add user login information to the SSH settings for your specific system on the System

Protocol Settings screen (Options ⇒ Protocol Settings ⇒ System Protocol Settings).• From the command line on the CMS, and logged in as root, execute the capopvaextract

or cappmpextract command, giving the fully qualified host name as the first argument.(See the corresponding command reference pages in the “Command Reference” for moreinformation.)For example:# capovpaextract node12.company.com

Possible Sources of Discrepancies in Collected DataSeveral possibilities exist to explain discrepancies that may appear in the data or that may affectdata collection. Check these possibilities to understand what actions you can take to correct thediscrepancy.

Gathering Data for Capacity Advisor 83

No Data Collected for a Managed NodeIf you do not obtain data on systems from which you expect to collect data, use the license scanto help you discover if a lack of licensing for Capacity Advisor may be the problem.To learn about VSE Management Software licenses, including those for Capacity Advisor, review“Adding and Applying Licenses” inHP Insight Dynamics—VSE andHPVSEManagement Software4.1 Getting Started Guideprior to starting a license scan. Also see “Data Collection and the HPInsight Capacity Advisor Consolidation software” (page 80).To start the license scan:1. Select Deploy ⇒ License Manager... from the HP SIM menu bar.2. Follow the progression for designating the systems for which you want to review licensing.Should you decide to modify the current licensing, consult the “Adding and Applying Licenses”section of the HP Insight Dynamics — VSE and HP VSE Management Software 4.1 Getting StartedGuide for information on how to assign licenses to servers.

Data Timestamp Appears to be IncorrectFor best accuracy in providing simulation solutions and historic reporting of actual systemresource use, it is assumed that the time clocks of managed nodes are synchronized with thetime clock of the central management server. If, on gathering or collecting data, the date stampon your data is not current, the time or time zone on a managed node may be set incorrectly inrelation to the CMS. For instructions on correcting this, see “Data May Appear to be Old Whenit is Not” (page 164).

Dynamic Memory in HP Integrity Virtual MachinesA dynamic memory feature is available in HP Integrity VMs. This allows the memory allocatedto each virtual machine to be changed without rebooting the virtual machine. Capacity Advisoris aware of this feature and records both the memory allocated to each virtual machine, as wellas how much of this memory is in use for each five-minute interval. Both of these values arecorrect 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 sarwill not be aware of the dynamic memory feature and can show memory sizes that are differentfrom what is recorded by Capacity Advisor. For example, if a virtual machine is initially bootedwith 16 GB of memory, and is then re-sized to 4 GB, the built-in commands will not know aboutthe change and will show 16 GB for physical RAM. Capacity Advisor, however, will show thatthe available memory for the VM is 4 GB. Also, when a virtual machine is sized less than itsmaximum size, some built-in commands will show the kernel using more memory than it isactually using.

Related Topics

Producing Graphs and ReportsHP Capacity Advisor can generate both graphical and tabular data for presentation.The following table presents the various report types and their attributes. All report types giveyou the opportunity to view utilization data for all the resource types examined by CapacityAdvisor: CPU , memory, network I/O, disk I/O, and power.

84 Basic Procedures

Table 5-1 Capacity Advisor Report Types

What You Can Find (or Do) ThereReport Type

• See graphed data for one resource for one system or workload at a time• Manipulate time span to show forecast utilization and pan through extended time periods.• View historic activity of real systems and workloads or simulated activity within a scenario• Modify various parameters and redraw the profile with new values

Profile Viewer

• Tabular and graphic display of data for one or more resources for one or more systems orworkloads, or for a complex of systems

• Manipulate time span to show forecast utilization.• View historic activity of real systems, complexes, and workloads or simulated activity within

a scenario• Download the report for viewing locally.

Utilization reports

• Compare key values for 2–4 scenarios at a time in a format that makes it easier to look acrossthe scenarios at one time.

• Download the report for viewing locally.

Scenariocomparison report

A fundamental difference exists between reports based on scenarios and those generated bydirectly specifying systems, complexes, and workloads. All metrics reported in scenario-basedreports rely on summing the workload data to create a simulated perspective. When generatedbased on direct specification of systems, complexes, and workloads, reports rely on collecteddata from real systems for each resource type, which may differ from the sum of the workloadsused in simulations.Reports based on scenarios provide the easiest way to simulate a combination of systems andworkloads. Complexes cannot be specified as components in a scenario, so reports on complexesmust be generated by creating a utilization report and directly selecting the complex option .

Using the Profile ViewerThe Profile Viewer provides a quick summary of historical resource utilization, presenting datagraphically as well as in tabular summaries. See also “Profile Viewer Screen” in Capacity AdvisorHelp for specific descriptions of the screen functions.A Profile Viewer can be accessed from the system meters on the Visualization tab, the HP SIMOptimize menu, or from the meters or menu selections on the Edit Scenario tabs in CapacityAdvisor.A Profile Viewer opened from the Visualization tab generally displays the actual resourceutilization data collected from the selected node.However, for non-OS node types such as an enclosure, a complex, or a vpar monitor, which donot have an operating system (OS) or hypervisor from which to collect actual resource utilizationdata, the Profile Viewer calculates the utilization profile by aggregating the actual data from allof the associated child nodes (blades, nPartitions, or vPartitions, respectively).A Profile Viewer opened from the scenario editor, on the other hand, always aggregates datafrom all of the workloads on a system or from all of the virtual machines (VM) running on a VMhost when the VMs are included in the scenario. This is true even when there is actual datacollected for the operating system or hypervisor. Aggregation is done to account for themodifications 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 modeledhardware. Due to the malleability of a scenario, it is possible that a scenario profile of a nodecould differ from profile viewed from the Visualization tab in Virtualization Manager for thereal 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-guestworkloads is not collected for use in the 4.1 release of Capacity Advisor. Therefore, profile views

Producing Graphs and Reports 85

accessed from the scenario editor do not account for utilization by workloads that are not VMguests.The following sections describe how to access the Profile Viewer from various locations withinHP SIM.Prerequisites To access and use the Profile Viewer:• You must be logged in to HP Systems Insight Manager (see “Accessing Capacity Advisor”

(page 70)).• You must have collected data on the systems of interest (see “Gathering Data for Capacity

Advisor” (page 70)).Some functions of the Profile Viewer require Capacity Advisor Tools permissions to be seen andused.Procedure 5-16 To Access the Profile Viewer from the HP SIM Optimize Menu1. Select Optimize ⇒ Capacity Advisor ⇒ View Profile...

The target selection wizard opens.

2. Select one system to view and click Apply. .3. 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 forthe selected system, and the system is licensed to work with Capacity Advisor, you arepresented the opportunity to collect data immediately, calibrate power, and edit I/O capacity.At minimum, you will need to collect data prior to continuing this task.

Procedure 5-17 To Access the Profile Viewer from the Systems Listed on the Visualization Tab1. Select Tools ⇒ VSE Management...

Virtualization Manager opens with the Visualization tab at the forefront.

2. To view a profile on a desired system, click a utilization meter for a resource to open theProfile Viewer for that resource on that system. (For information on the meters presentedon the Visualization tab, see “Utilization Metrics” in Virtualization Manager Help.)

Procedure 5-18 To Access the Profile Viewer When Editing a ScenarioThis procedure assumes that you are starting from the Capacity Advisor - Edit Scenario screenin the System tab view.For information on getting to this location, see “Editing a Scenario” (page 100).1. If you want to view the profile of a system:

• Click any of the horizontal bar graphs in the system table that represent currentutilization of a resource. Profile views are available for any and all of the current resourcetypes for which data is available (CPU, memory, network and I/O bandwidth, andpower usage).The Capacity Advisor - Profile Viewer screen displays with the data for the selectedresource type and system.

86 Basic Procedures

2. If you want to view the profile of a workload:a. Click the Workload tab.

The Workload tab opens.

b. When bar graphs are displayed in the workload table:• Click any of the horizontal bar graphs representing current utilization of a resource.

Profile views are available for any and all of the current resource types for whichdata is available for workloads (CPU, memory, and network and I/O disk bandwidthusage).The Capacity Advisor - Profile Viewer screen displays with the data for the selectedresource type and workload.

c. If no bar graphs 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 View ⇒ Workload Profile... from the menu bar.The Capacity Advisor - Profile Viewer screen displays.

Procedure 5-19 To Change the View Within the System Hierarchy1. Find the Hierarchy near the top of the screen2. 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-20 To Modify Select Settings in a Profile ViewerYou can change select settings that control modeling limits, and then view the resulting changesin the data when the new settings are applied.1. Locate the set of links that appear below and to the right of the profile identification summary

information and above the data range selector.2. 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 powersettings, and edit utilization limits.When viewing profiles from the HP SIM Optimize menu, you can also edit I/O capacity and/orimmediately collect data.

The editor for the setting opens.

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 aswhen you are viewing the profile for a system or complex), navigational controls arepresented to the right of the Hierarchy label near the top of the screen, such as links anddrop-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-21 To Change the Time and Data Range Displayed in the Profile ViewerOptionally, you can adjust the data range and interval. The default display, a Fixed Interval,shows the most recent seven days of activity.

Producing Graphs and Reports 87

1. You can select a different Fixed Interval in the drop down selector, or you can change toan 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. Set the beginning and end dates for the interval that you want to view.3. Click OK to apply the new interval to the graph and table data.

The screen displays the new interval and data.

Procedure 5-22 To Switch to Alternate Utilization Resource MetricsYou can cause the Profile Viewer to display any of the resource metrics provided by CapacityAdvisor.• 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, updatingboth the utilization graphic and the Interval Metric Summary table.

Procedure 5-23 To Manipulate the Graphic Display of Utilization DataFor specific descriptions of each field on the user interface screens, click the help topic link onthe software screen for the task.1. Optionally, use the pan right (> Pan or >> Pan) and pan left (< Pan or << Pan) 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 bluebackground in the graph indicates the area in the graph where activity is forecast based onhistoric data and user-selected settings.

2. Optionally, turn off the bandwidth capacity indicator by deselecting the Show Capacityradio 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 Allocationradio button. (Visible on CPU and memory utilization metric viewers.)The screen repaints with the dashed blue capacity indicator line removed.

4. Optionally, turn on the Show Invalid Data selection to see the points that have been droppedfrom the display and analysis (if any).

5. Optionally, use the Profile Editor to set the data time frame and click Validate or Invalidateto set the status of the date range.Changes made here will be reflected in the graphic and Interval Metric Summary table.

6. When finished viewing the graph and table data for a scenario system or workload, clickthe Go back to .... link to return to your original starting point in the Edit Scenario screens.

For information on accessing special editors from the Profile Viewer, see“Accessing the ForecastModel for a Workload or System” (page 95).

Utilization Reports OverviewCapacity Advisor Utilization Reports provide valuable summaries and details of resource usagefor CPU, memory, network and disk I/O bandwidth, and power consumption and costs. Thesereports are useful for understanding current resource utilization or planning for futurerequirements. Reports can present resource utilization for a scenario, or for one or more complexes,systems, or workloads.A fundamental difference exists between reports based on scenarios and those generated bydirectly specifying systems, complexes, and workloads. All metrics reported in scenario-basedreports rely on summing the workload data to create a simulated perspective. When generatedbased on direct specification of systems, complexes, and workloads, reports rely on collected

88 Basic Procedures

data from real systems for each resource type, which may differ from the sum of the workloadsused in simulations.Reports based on scenarios provide the easiest way to simulate a combination of systems andworkloads. Complexes cannot be specified as components in a scenario, so reports on complexesmust be generated by direct selection of the complex option.

Generating a Scenario Report

Prerequisites

To generate a report:• You must be logged in to HP Systems Insight Manager. (See “Accessing Capacity Advisor”

(page 70).)• You must have already collected data on the systems of interest (see “Gathering Data for

Capacity Advisor” (page 70)).• You must be authorized and licensed on all systems you wish to include in the report (see

HP Insight Dynamics — VSE and HP VSE Management Software 4.1 Getting Started Guide ).Procedure 5-24 To Generate a Scenario Report1. 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 Optimize ⇒ Capacity Advisor ⇒ View

Scenarios... from the HP SIM menu bar.The Capacity Advisor tab opens with a list of scenarios.

2. Click the radio button preceding the scenario about which you wish to generate a report.The row containing the scenario is highlighted and the radio button is filled in to indicateselection.

3. Select Reports ⇒ Capacity Advisor Scenario Utilization Report... from Capacity Advisormenu bar.The wizard starts.

NOTE:Reports can only be generated about systems licensed to run Capacity Advisor components.

Stepping Through the Report WizardThis general description of the Report Wizard applies to all utilization reports, though optionsvary within the wizard depending on the report type and other options selected.Procedure 5-25 Select Report ContentFor specific descriptions of each field on the user interface screens, click the help topic link onthe software screen for the task.1. The Report Wizard opens on the Select Report Content screen.

Select for a utilization summary or summary and details.

NOTE: You may also select to run a trend report and a power report at the same time thatyou run a utilization report.

2. Click the Next button.The Select Report Targets screen opens.If you selected a scenario prior to starting the Report Wizard, this screen displays the systemsassociated with your scenario selection.

Producing Graphs and Reports 89

Procedure 5-26 Select Targets and Set Date RangeFor specific descriptions of each field on the user interface screens, click the help topic link onthe software screen for the task.1. Click one of the visible links to edit or choose a scenario, one or more complexes, one or

more systems, or one or more workloads to appear in the report.A new screen opens with an appropriate list of known scenarios, complexes, systems, orworkloads.

2. Click the check box to the left of each object's name that is to appear in the report.3. Click OK.

The Select Report Targets screen reopens with an updated list of targets and a date rangeselector visible.

4. Check that the selected targets are correct.5. Note the available date range of all collected data, which appears above the date range

selector, and the default date range (30 days prior to the current day).6. If the default date range is acceptable, click Next.7. If a different data set is desired, change the date and time, then click Next.

The Select Details screen opens.

Procedure 5-27 Select Details Specific to Report TypeFor specific descriptions of each field on the user interface screens, click the help topic link onthe software screen for the task.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 by clicking the appropriate check boxes.2. Select the type of scale for data presentation: percentage of allocated resource, absolute

numbers, or both by clicking the appropriate radio button.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. If you chose trend report details,a. Select the Business Interval (default: 1 week).

Requiring higher percentages of valid points can make the business intervals analyzedmore meaningful, but can also reduce the number of business intervals available forthe analysis, making the overall analysis less useful.

b. Select the minimum percentage of valid data points that must be present within theperiod (default: 95%), called the Valid Threshold.

c. Choose the data aggregation type (default: average), called Compute Trending of.5. 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.c. Optionally, designate a cooling cost multiplier.

See “Adjusting for Platform Changes” (page 34).

d. Designate a time interval for display of results (default: by day).6. Click Finish.

The Report Created screen opens.

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

90 Basic Procedures

The Capacity Adviser Help Reference accessible from the software provides additional informationto guide you in defining a report.

Using the Report Wizard to Create a Scenario ComparisonThe Scenario Comparison Report feature allows you to compare two to four scenarios in a tabularand graphical side-by-side comparison report.Procedure 5-28 Getting There• You can get to the Scenario Comparison Report feature by either of these paths:

• From the HP SIM menu bar, select Optimize ⇒ Capacity Advisor ⇒ ScenarioComparison Report.

• From the Capacity Advisor tab: select the scenarios that you want to compare. Thisenables the Report ⇒ Capacity Advisor Scenario Comparison Report menu pick.

Procedure 5-29 Selecting Report Targets in a Scenario Comparison• From this screen, you edit and/or confirm the scenarios to include in the report and set the

date range selection. You cannot edit systems, workloads, or complexes in this reportingview.

Procedure 5-30 Selecting Scenarios and Setting the Date Range1. 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 5to 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 comparethem side-by-side. For example, to compare six scenarios, run one report with four scenariosand one report with two scenarios. Lay the printouts side-by-side to compare various aspectsof the scenarios.

2. Select Edit Scenario Selection.A new screen appears showing the possible scenarios to include in the comparison report.

3. Check the box to the left of the scenarios to include.4. Choose one of the following actions:

• Press OK to accept the selections and return to the Select Report Targets screen. A DateSelection area appears in the screen.

• Press Cancel to end the report creation and return to your originating screen.5. 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.6. Click Next to continue to the Select Report Options screen.Procedure 5-31 Selecting Report Details in a Scenario ComparisonThe options in a scenario comparison are limited to CPU, Memory, and Power resource usagetypes. All selectable fields are combined into one section called General Report Options.1. Put a check in the box(es) next to the resource types that you want to compare.2. 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 PowerReport Options.

3. Choose the scale (absolute utilization numbers, percent of allocated resources used, or both).4. Press Finish to create and complete the report.

Producing Graphs and Reports 91

An Example Scenario Comparison Report

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

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). Formore snapshots from this same report, see Appendix C (page 155).

Calculating a Virtualization Consolidation RatioIt can be useful to look at the resulting ratio of virtual machines to physical servers after runninga system or workload consolidation simulation to help in evaluating the return on investmentfor a particular configuration of machines. Currently, Capacity Advisor does not supply thisratio in its reports, but you can easily calculate ratios for a set of scenarios that you wish tocompare.Prerequisites• You must be logged in to HP Systems Insight Manager (see “Accessing Capacity Advisor”

(page 70)).• You must have created a planning scenario that represents the system configuration that

you want to consolidate. (See “Creating a Planning Scenario” (page 98) and “Editing aScenario” (page 100).)

• 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 differentconsolidation simulations. (See “Using the Smart Solver” (page 63).)

• You must have run a scenario comparison report that includes your initial planning scenarioand your consolidated scenario results. (See “Using the Report Wizard to Create a ScenarioComparison” (page 91).)

Procedure 5-32 Calculate Virtualization Consolidation Ratios Using Data from a Scenario ComparisonReport1. Examine the scenario comparison report. (As an example, see Figure 5-1 (page 92).)

92 Basic Procedures

2. For the systems scenario in the report, subtract the Number of VM Hosts in that scenariofrom the Number of Physical Servers Including VM Hosts. This value represents thenumber of physical servers that are to be consolidated into virtual machines.

3. 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 92), you can determine that the number ofphysical servers to be consolidated is 20.The ratio for the small system consolidation is 20/6, and the ratio for the big system consolidationis 20/3 – meaning that the 20 physical servers can fit on 6 small VM hosts or 3 larger VM hosts.

Analyzing TrendsHP Capacity Advisor provides trend analysis to allow you to better understand how the utilizationof resources has changed over time.For information on creating a trend report, see “Stepping Through the Report Wizard” (page 89)and “Determining Trends in Capacity Advisor” (page 41).

Forecasting Future UtilizationHP Capacity Advisor provides multiple levels of forecast models to allow precise control offorecasting future utilization.• For information on defining forecast models, see “Defining Forecast Models” (page 93).• For information in viewing forecasts, see “Generating Forecasts” (page 97)

Defining Forecast ModelsWhenever a Capacity Advisor report or profile is generated with an end date later than thecurrent date, the historical utilization data is projected into the future. The projection is indicatedin the utilization graphs by a colored background next to the usual white background.This projection is done based on a forecast model. Forecast models can be defined globally, forindividual 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 isin the hierarchy of forecast models, the procedures below are broken into two parts: accessingthe forecast model and defining it.

NOTE: Although forecast models cannot be deleted, all but the global forecast model can bedisabled and enabled. Follow the appropriate procedure for accessing the forecast model andthen follow the procedure for disabling or enabling it.

The Forecast Model HierarchyThe forecast model can be specified at four different levels within Capacity Advisor, with morespecific forecast models overriding more general models, as indicated in the following table:

Table 5-2 Forecast Models

OverridesDescriptionForecast

• NothingApplies to all workloads in CapacityAdvisor for which a more specificforecast is not provided.

Global Forecast

• GlobalApplies to a specific workload inCapacity Advisor unless a morespecific forecast is provided.

Workload Forecast

Forecasting Future Utilization 93

Table 5-2 Forecast Models (continued)

OverridesDescriptionForecast

• Global• Workload

Applies to all workloads within aCapacity Advisor scenario for whicha more specific forecast is notprovided.

Scenario Forecast

• Global• Workload• Scenario

Applies to a specific workload withina Capacity Advisor scenario.

Scenario Workload Forecast

Accessing the Global Forecast ModelThe annual growth rates for the global forecast model are frequently based on an organization'splanned growth rate. The global forecast model applies to all reports generated on systems andcomplexes. Reports on workloads or scenarios without a forecast model also use the globalforecast model.Prerequisites To define the global forecast model:• You must be logged in to HP Systems Insight Manager. (See “Accessing Capacity Advisor”

(page 70).)• You must have sufficient authorization to define the global forecast model (see HP Insight

Dynamics — VSE and HP VSE Management Software 4.1 Getting Started Guide).Procedure 5-33 To Access the Global Forecast Model1. 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 Optimize ⇒ Capacity Advisor ⇒ View

Scenarios... from the HP SIM menu bar.The Capacity Advisor tab opens with a list of scenarios.

2. From the Capacity Advisor menu bar, select Configure ⇒ Global Forecast...

The Forecast Editor - Global Forecast Model screen displays.

Defining the Global Forecast Model

The settings that you define here are applied globally in the absence of other specifically targetedforecast models.This procedure assumes that you have opened the Global Forecast Model screen (see “Accessingthe Global Forecast Model” (page 94).) For specific descriptions of each field on the user interfacescreens, click the help topic link on the software screen for the task.1. Provide a brief description of the forecast model in the Description field.2. 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.

3. Select the date range for defining the period of data collection to use as the basis for theforecast.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 orEnding, and general date

indicator (default: Last Full Day)4. 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

94 Basic Procedures

utilization, and zero for no change). The default is 1% projected annual growth for everyresource.

TIP: You can estimate projected annual growth by including trend calculations in utilizationreports derived by analyzing historical data. (See “Determining Trends in Capacity Advisor”(page 41) and “Stepping Through the Report Wizard” (page 89).)

5. Click the OK button to save and apply a new definition for global forecasting.

Undoing Changes to the Global Forecast:If you change your mind about values while editing this screen, use the Revert button toreplace 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 forecastvalues once before, and then decide that you prefer the default values, you will have to setthe values to 1 for each resource and click OK to have the original default values in operation.

Accessing the Forecast Model for a Workload or SystemWhen the resource utilization of an individual workload or system is expected to differ fromthat predicted by the global forecast model, a workload- or system-specific forecast model canbe created.Forecasting for workloads or systems is done from within a Profile Viewer associated with theworkload or system. See “Using the Profile Viewer” (page 85) for information on how to accessthe viewer from the HP SIM Optimize menu or from a scenario.

IMPORTANT: The forecast model for a system is not inherited by any sub-OS workloads. If asystem with sub-OS workloads is included in a scenario, the forecast model will not be usedwithin the scenario.

Prerequisites To define the forecast model for a workload or system:• You must be logged in to HP Systems Insight Manager. (See “Accessing Capacity Advisor”

(page 70).)• You must have sufficient authorization to define the forecast model for a workload or a

system (see HP Insight Dynamics— VSE and HP VSEManagement Software 4.1 Getting StartedGuide).

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 85).)Procedure 5-35 To Define the Forecast Model for a Workload or System1. If you are not on the VSE Management: Virtualization Manager screen, from the upper,

HP SIM menu, select Tools ⇒ VSE Management....The VSE Management: Virtualization Manager 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 VSE workloads.

Forecasting Future Utilization 95

3. Open a Profile Viewer by clicking a utilization meter for a particular system on theVisualization tab or by clicking a utilization link for a particular workload on the Workloadtab.The Profile Viewer screen is displayed for the system or workload.

4. Click the Edit Forecast Model... link on the Profile Viewer.The Forecast Editor: Workload Forecast Model screen displays.

5. • 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 ScenarioDefining a separate forecast for a scenario allows you to provide estimates of utilization basedon differing growth projections.Prerequisites To define the forecast model for a scenario:• You must be logged in to HP Systems Insight Manager (see Accessing Capacity Advisor).• You must have created the scenario (see “Creating a Planning Scenario” (page 98)).Procedure 5-36 To Access the Forecast Model for a Scenario1. 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 Optimize ⇒ Capacity Advisor ⇒ View

Scenarios... from the upper, HP SIM menu bar.The Capacity Advisor tab opens, with a list of scenarios.

2. The names of scenarios for which you have authorization to define a forecast model aredisplayed as links. Click the link to open the scenario editor.

3. From the System tab, select Edit ⇒ Scenario-wide Forecast...

The Forecast Editor: Scenario-wide Forecast Model screen is displayed.

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.

What Now? You might want to:• Edit a Scenario (see “Editing a Scenario” (page 100)).• View a forecast based on the new forecast model (see “Generating Forecasts” (page 97)).

Accessing the Forecast Model for a Workload Within a ScenarioIf the resource utilization of an individual workload within a scenario is expected to changedifferently from the scenario forecast model, a different forecast model can be provided for theworkload.Prerequisites To define the forecast model for a workload within a scenario:• You must be editing a scenario (see “Editing a Scenario” (page 100)).Procedure 5-37 To Define the Forecast Model for a Workload Within a Scenario1. If you are not viewing the workloads, click the Workload tab.

The Workload tab opens, revealing a list of the workloads in the scenario.

2. Click the check box preceding a single workload.

96 Basic Procedures

3. Select Edit ⇒ Scenario Workload Forecast... from the menu bar.The Forecast Editor: Scenario Workload Forecast Model screen is displayed.

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.

What Now? You might want to:• View a forecast based on the new forecast model (see “Generating Forecasts” (page 97)).

Defining a Forecast ModelOnce you have accessed a forecast model, use he following procedure to define it.Procedure 5-38 To Define a Forecast ModelFor descriptions of each of the fields noted in this procedure, see the screen description for themodel with which you are working in the Capacity Advisor online help reference. See “TheForecast Model Hierarchy” (page 93)for a list of the model screen descriptions.1. Provide a brief description of the forecast model in the Description field2. 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 historicaldata to help you estimate future growth (see “Forecast Calculations” (page 42)).

4. Click the OK button.

Disabling a Forecast ModelProcedure 5-39 To Disable a Forecast ModelWhile it is not possible to delete a forecast model, forecast models at all levels below the globalforecast model can be disabled by accessing the appropriate forecast model and using thefollowing procedure.1. Click the Disable radio button.2. Click the OK button.

Enabling a Forecast ModelIf you have previously disabled a forecast model, you can re-enable it by accessing the appropriateforecast model and using the following procedure.Procedure 5-40 To Enable a Forecast Model1. Click the Enable radio button.2. Click the OK button.

Generating ForecastsOnce you have defined one or more forecast models, you can view the results of the forecastmodels two ways:• For a quick view, “Viewing Forecast Data in a Profile Viewer”• For a more thorough report, “Viewing Forecast Data in a Utilization Report” (page 98)

Viewing Forecast Data in a Profile ViewerThe profile viewer provides a quick view of resource utilization for a system, complex, orworkload. Once the profile viewer is posted, you can view the forecast by extending the daterange into the future.

Forecasting Future Utilization 97

To view forecasts within a Profile Viewer:• You must be in a Profile Viewer. (See “Using the Profile Viewer” (page 85).)Procedure 5-41 To View Forecast Data Within a Profile Viewer• 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 backgroundand forecast data will be plotted on a colored background.

Viewing Forecast Data in a Utilization ReportUse the procedure specified in “Producing Graphs and Reports” (page 84) 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 plottedon a colored background.

Working with Scenarios

IntroductionScenarios are collections of systems and workloads, both real and “What-If” creations. Whilescenarios are based on real data, you can modify parameters to model changes to the environmentand the configuration of systems and workloads.• Creating scenarios (see “Creating a Planning Scenario”)• Editing scenarios (see “Editing a Scenario” (page 100))• Copying scenarios (see “Copying a Scenario” (page 102))• Renaming scenarios (see “Renaming a Scenario” (page 103))• Showing or modifying changes to scenarios (see “Undoing or Editing Changes to Scenario”

(page 103))• Controlling the behavior of scenarios (see “ Controlling the Data Display” (page 100))• Removing scenarios (see “Deleting a Scenario” (page 104))

Creating a Planning ScenarioScenarios are used to model system behavior by performing “What-If” operations based oncollected data. The first step in using scenarios is creating one.Prerequisites To create a scenario:• You must be logged in to HP Systems Insight Manager. (See “Accessing Capacity Advisor”

(page 70).)• You must have already collected data on the systems of interest (see “Gathering Data for

Capacity Advisor” (page 70)).• 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 — VSE and HP VSEManagement Software 4.1 Getting Started Guide).

To create a scenario:• You must be logged in to HP Systems Insight Manager (see Accessing Capacity Advisor).Procedure 5-42 To Create a Scenario1. Select Optimize ⇒ Capacity Advisor ⇒ Create Scenario... from the HP SIM menu bar.

The Capacity Advisor - Create New Scenario wizard opens to Step 1 of 3, Create a Nameand Description for the Scenario.

2. Type in a unique Scenario Name. Follow the character rule listed below the field.3. Type a short description in the Description field.

98 Basic Procedures

TIP: As the number of scenarios grows, the description field can help you to differentiatesimilarly named scenarios.

4. Click Next .Screen 2 of 3, Select Systems for the New Scenario, displays.

5. Click the check boxes that precede the systems that you want to include in the scenario (youcan add or remove systems later, if necessary).Check marks appear in the check boxes by the selected systems and the rows containing thesystems are highlighted.

The System That I Want Has No Data Collected:If any of the systems that you want to use in the scenario are in the list of systems licensedfor Capacity Advisor with no data collected for them, you need to collect data on them beforecreating a scenario (see “Gathering Data for Capacity Advisor” (page 70)) .Systems that are licensed for Capacity Advisor but that have no data collected are listedbelow the list of available systems. For information on collecting data on a system for thefirst time, see “Gathering Data for Capacity Advisor” (page 70).If any of the systems that you want to use in the scenario are not listed anywhere on thepage, make sure they are licensed for Capacity Advisor and that your login is authorizedto access them (see HP Insight Dynamics— VSE and HP VSEManagement Software 4.1 GettingStarted Guide).

When you are satisfied that all systems that you want to include in the scenario are availableto you and have data collections associated with them, return to this procedure.

6. Click Next .Step 3 of 3, Verify Scenario Parameters, displays.

7. Verify the name, description, and systems to be included in the scenario.8. Verify that you want to open a scenario editing session, and then click Create. The check

box for this appears below the list of systems and is checked by default.The Edit Scenario screen opens, and you can begin editing additional values for systemsand workloads to further refine your planning simulation.

The Edit Scenario Window on Mozilla Firefox:In the case where the Edit Scenario window is already open, but hidden beneath otherwindows when you create a new scenario, it is not obvious that the window has refreshedwith your new scenario information. This can occur when using Mozilla Firefox with multiplewindows open on your display. To more easily access the refreshed window, set Firefox toallow Javascript to raise or lower windows. Then, when you create a new scenario, thepre-existing Edit Scenario window will rise to the forefront of the display.

If you do not want to immediately open a scenario editing session, uncheck the scenarioediting check box, and then click Create. The main window refreshes with the list of scenarios(on the Capacity Advisor tab), including your new scenario definition.

What Now? Once you have created a scenario, you might want to:• Edit a Scenario (see “Editing a Scenario” (page 100)).• View reports and graphs to determine the effects of the changes (see “Producing Graphs

and Reports” (page 84)).

Working with Scenarios 99

Editing a ScenarioEditing a scenario allows you to modify the systems and workloads in a scenario. This can bedone 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 theloss of any unsaved changes in the previously opened session. If you were running an automatedsolution in your previous session, the automated calculations are immediately halted and nosettings or results are saved.

Prerequisites To edit a scenario:You must be logged in to HP Systems Insight Manager. (See “Accessing Capacity Advisor”(page 70).)• You must have created the scenario. (See “Creating a Planning Scenario” (page 98).)Procedure 5-43 To Edit a Scenario1. 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 Optimize ⇒ Capacity Advisor ⇒ View

Scenarios... from the upper, HP SIM 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 ofthe scenario you want to edit.The Capacity Advisor - Edit Scenario screen will be displayed.

What Now? While you are editing a scenario, you can:• Control the scenario parameters (see “ Controlling the Data Display” (page 100)).• View, enable, and disable changes to the scenario (see “Undoing or Editing Changes to

Scenario” (page 103)).• Work with systems (see “Working with Systems” (page 105)).• Work with workloads (see “Working with Workloads” (page 109)).• View reports and graphs to determine the effects of the changes (see “Producing Graphs

and Reports” (page 84)).• Perform an automated scenario change (see“Using the Smart Solver” (page 63).)

Controlling the Data DisplayThe default values for the Simulation Interval and the Metric View Selection may not accuratelyrepresent the interval of interest and the preferred metric. These are easily adjusted.

Change the Meter Style SelectionPrerequisites:• You must be editing a scenario (see “Editing a Scenario” (page 100)).Procedure 5-44 To Change the Meter Style Selection• Click the Absolute or Percent radio button.

The meter bars in the scenario resource utilization table display the data as absolute numbersor as percentages, according to your selection.

Change the Data Interval by Setting the Data RangeSet the interval within a data collection period that you want to use as the foundation for asimulation or to view a specific historic period.

100 Basic Procedures

Prerequisites:• You must be editing a scenario (see “Editing a Scenario” (page 100)), or• You must be viewing data in a Profile Viewer

NOTE: Changes to the data interval persist across sessions.

Procedure 5-45 To Change the Data Range1. 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 datacollection 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 relationshipthe 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. Change the date, if needed, to work well with your other Data Range selections5. Click OK to refresh the scenario resource utilization table with data collected during the

defined interval.6. Click Cancel to return to the previous data range for this scenario.

Working with Scenarios 101

What Now? Once you have modified scenario parameters, you might want to:• View reports and graphs to determine the effects of the changes (see “Producing Graphs

and Reports” (page 84)).

Change the Meter RepresentationPrerequisites:• You must be editing a scenario (see “Editing a Scenario” (page 100)).

NOTE: Changes to the Meters Represent: options are applied to the current scenario editingsession, but options return to the default values at the beginning of any new session.

Procedure 5-46 To Change Meters Represent: Drop Down• 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 sustainedThe scenario resource utilization table displays the new values for each resource, includingviolations of utilization limits set for each resource.

Copying a ScenarioScenarios are used to model system behavior by performing “What-If” simulations based oncollected data. It is frequently desirable to use an existing scenario as the starting point fordeveloping a new scenario. Copying a scenario provides an easy way to accomplish this.Prerequisites To copy a scenario:• You must be logged in to HP Systems Insight Manager. (See “Accessing Capacity Advisor”

(page 70).)• You must be authorized on all systems in the scenario (see HP Insight Dynamics — VSE and

HP VSE Management Software 4.1 Getting Started Guide).Procedure 5-47 To Copy a Scenario1. 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 Optimize ⇒ Capacity Advisor ⇒ View

Scenarios... from the upper, HP SIM menu bar.The Capacity Advisor tab will open, with a list of scenarios.

2. The names of any scenarios you have authorization to copy will be displayed. Click theradio button preceding the scenario you wish to copy.The row containing the scenario will be highlighted and the radio button will be filled in toindicate selection.

3. Select Create ⇒ Copy Planning Scenario.... The Copy Scenario confirmation screen willbe displayed.

4. Modify the Name and Description fields as appropriate.5. Click the OK button.

You will be returned to the Capacity Advisor tab.

What Now? Once you have copied a scenario, you might want to:

102 Basic Procedures

• Edit a Scenario (see “Editing a Scenario” (page 100)).• Rename a scenario (see “Renaming a Scenario” (page 103)).

Renaming a ScenarioScenarios are used to model system behavior by performing “What-If” operations based oncollected data. Over time, more appropriate names for scenarios may become apparent. Renaminga scenario allows you to change the name.Prerequisites To rename a scenario:• You must be logged in to HP Systems Insight Manager. (See “Accessing Capacity Advisor”

(page 70).)• You must have created the scenario. (See “Creating a Planning Scenario” (page 98).)Procedure 5-48 To Rename a Scenario1. 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 Optimize ⇒ Capacity Advisor ⇒ View

Scenarios... from the upper, HP SIM menu bar.The Capacity Advisor tab will open, with a list of scenarios.

2. The names of any scenarios you have authorization to rename will be displayed as links.Click the radio button preceding the scenario you wish to rename.The row containing the scenario will be highlighted and the radio button will be filled in toindicate selection.

3. Select Modify ⇒ Rename Planning Scenario... from the Capacity Advisor tab menu bar.The Rename Scenario screen will be displayed.

4. Modify the Name and Description fields as desired.5. Click the OK button.

You will be returned to the Capacity Advisor tab.

What Now? Now that you have renamed a scenario, you may want to:• Edit a Scenario (see “Editing a Scenario” (page 100)).

Undoing or Editing Changes to ScenarioAs you work on a scenario, you can review, delete, or disable/enable selected system changes.

IMPORTANT: Disabling or enabling What-If actions can cause subsequent and dependentWhat-If actions to fail. Be prepared to re-enable any changes if you get errors in the scenario.

Getting ThereWhen you are editing a scenario , from either the System or Workload tab, select What-IfAction ⇒ Undo/Edit/View Applied What-If Actions from the menu bar. The Edit Scenario -Undo/Edit/View Applied What-If Actions screen will be displayed. A list of changes made tothe scenario with check boxes preceding them is visible, with the earliest changes at the top ofthe list.

To View Applied What-If ActionsIf you only wanted to review the changes, click Close once you are done reviewing. You will bereturned to the Capacity Advisor - Edit Scenario screen.

Working with Scenarios 103

To Edit Applied What-If ActionsIf 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 tore-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 in the check boxes preceding the changes you want to delete.You can check either one step or a range of steps that have been grouped together.Then, click Delete.

Modifying Resource Utilization Values

For rows where this feature is available, you can change the scaling factors (multipliers) associatedwith a change.1. Click the check box to the left of the row where you want to change the value.2. Change the value using the field in the column labeled Modifiable Values.3. Click Modify.Once you are done with all your changes (you can come back as many times as you wish), clickClose .You will be returned to the Capacity Advisor - Edit Scenario screen. The changes you disabledor deleted will no longer be in effect and those you re-enabled will be in effect again. You shouldbe able to see the resulting modifications reflected in the data presented on the Edit ScenarioSystem or Workload tab screens.What Now? Once you have modified changes, you might want to view reports and graphs todetermine the effects of the changes (see “Producing Graphs and Reports” (page 84)).

Deleting a ScenarioOver time, as scenarios become irrelevant, removing them will reduce the list you have to searchto find your scenarios.Prerequisites• You must be logged in to HP Systems Insight Manager. (See “Accessing Capacity Advisor”

(page 70).)• You must have created the scenario (see “Creating a Planning Scenario” (page 98).) or be

the HP SIM administrator (see the HP SIM help by selecting Help ⇒ For HP SystemsInsight Manager from the upper, HP SIM menu bar).

Procedure 5-50 To Delete a Capacity Advisor Scenario1. 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 Optimize ⇒ Capacity Advisor ⇒ View

Scenarios... from the upper, HP SIM 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. Ifyou are the administrator, you can delete any scenario. Click the radio button preceding thescenario you wish to delete.The row containing the scenario will be highlighted and the radio button will be filled in toindicate selection.

104 Basic Procedures

3. Select Delete ⇒ Planning Scenario from the Capacity Advisor tab menu bar.The Delete Scenario confirmation screen will be displayed, with the name of the scenariothat 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.

Working with Systems

IntroductionSystems can represent physical hardware, Virtual Machines (VM), or Virtual Machine Hosts. Theycan be real systems from your current environment or “What-If” creations to represent newsystems you are planning. You can also modify a system based on an existing system to representplanned configuration changes. The following tasks are described:• Creating a system (see “Creating a System”)• Adding an existing system to the scenario (see “Adding an Existing System” (page 106))• Editing a system (see “Editing a System” (page 106))• Moving a virtual machine system (see “Moving a Virtual Machine” (page 108))• Removing a system (see “Removing a System” (page 108))

Creating a SystemWhen developing a scenario to model future configurations, you can create systems to representsystems you are considering adding to the configuration.Prerequisites To create a system in a scenario:• You must be editing a scenario (see “Editing a Scenario” (page 100)).Procedure 5-51 To Create a System in a ScenarioFor specific descriptions of each field, click the help topic link on the software screen for thistask.1. If you are not on the System tab within the Edit Scenario window, click the System tab.

The System tab opens, displaying the list of systems currently in the scenario.

2. Select What-If Action ⇒ Create Systems... from the menu bar.The Edit Scenario - Create System screen displays.

3. Fill in the System Name field.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 acomma (,) within the System Name field.

4. Select the appropriate System Model and Hardware Processor Family in the SystemHardware section.

5. Select the appropriate system type.The screen repaints with the options appropriate to the selected system type.

6. Select the appropriate operating system.7. If you selected VM Guest in step 5, now select a VM host.8. Modify the CPU Resources as appropriate.9. Modify the Memory Size as appropriate.10. Optionally, modify the network and disk I/O Capacity as appropriate.

Working with Systems 105

11. Click Apply to save the system definition and stay on the Create System screen, or clickOK to save the system definition and return to the Edit Scenario screen..

What Now? Once you have created a system, you might want to:• Edit a system (see “Editing a System” (page 106)).• Move a virtual machine (see Moving a Virtual Machine).• Remove a system from the scenario (see “Removing a System” (page 108)).• Create a workload (see “Creating a Workload” (page 109)).• Move a workload (see Moving a Workload).

Adding an Existing SystemAs your environment changes, you may want to add an existing system to a scenario.To add existing systems to a scenario:• You must be editing a scenario (see “Editing a Scenario” (page 100)).Procedure 5-52 To Add an Existing System to a Scenario1. If you are not on the System tab, click the System tab.

The System tab will open, listing the systems in the scenario.

2. Select Edit ⇒ Add Existing Systems... from the menu bar.The Edit Scenario - Add Existing Systems screen will be displayed. The systems withavailable HP Capacity Advisor data will be displayed in a list with check boxes beside them.Any systems licensed for Capacity Advisor will be named below the list.

3. If any of the systems you want to add to the scenario are not displayed on this page, youneed to license them for Capacity Advisor (see the section “Activating Licenses” inHP InsightDynamics—VSE and HP VSEManagement Software 4.1 Getting Started Guide) and collect dataon them (see “Gathering Data for Capacity Advisor” (page 70)).

4. If the systems you wish to add to the scenario are in the list of licensed systems withoutavailable Capacity Advisor data, collect data on them (see “Gathering Data for CapacityAdvisor” (page 70)) and continue with the next step.

5. Click in the check boxes beside the systems you want to add to the scenario to select them.Check marks will appear in the check boxes and the row containing he system will highlightto indicate selection.

6. Click the OK button.The System tab of the Capacity Advisor - Edit Scenario screen will open.

What Now? Once you have added a system to a scenario, you might want to:• Edit a system (see “Editing a System” (page 106)).• Remove a system from the scenario (see “Removing a System” (page 108)).

Editing a SystemWhen constructing a scenario, it is frequently necessary to modify the characteristics of a systemto reflect future changes to existing hardware or to reflect the characteristics of a planned system.Prerequisites To edit a system in a scenario:• You must be editing a scenario (see “Editing a Scenario” (page 100)).Procedure 5-53 To Edit a SystemFor specific descriptions of each field on this screen, click the help topic link on the softwarescreen for this task.1. If you are not on the System tab within the Edit Scenario window, click the System tab.

The System tab opens, displaying the list of systems currently in the scenario.

106 Basic Procedures

2. In the list of scenarios, click the check box preceding the name of the system that you wantto edit.A check mark appears in the check box.

3. Select What-If Action ⇒ Edit System... from the menu bar.The Edit Scenario: Edit System screen displays in a new window.

4. Modify the system attributes as desired. These attributes can be changed:• System Hardware• CPU Resources• Memory Size• I/O Capacity

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

What Now? Once you have edited a system, you might want to:• Simulate moving one or more systems to a VM host (manually or with automated assistance

from HP Smart Solver).View reports and graphs to determine the effects of the changes (see “Producing Graphsand Reports” (page 84)).

Editing Network and Disk I/O CapacityUse the Edit Network and Disk I/O Capacity page to set the upper bound value of network anddisk I/O capacity for the selected set of systems. Setting this upper bound creates the maximumcapacity value for such items as the network and disk I/O utilization graphs shown for thesystems, the graphs and values shown in the Profile Viewer, and the Capacity Advisor SmartSolver calculations. Further, when using Capacity Advisor, the currently set upper bound valueshere are propagated as the upper bound values for the systems when a scenario containing thesystems are created.Prerequisites To edit capacity of network and disk I/O for a scenario:• You must be on the Virtualization Manager Visualization tab.Procedure 5-54 Setting the Upper Bound Values1. On the Network and Disk I/O Capacity page, choose to use either one of the following

values:• the maximum observed network and disk I/O readings

This uses the actual maximum value read from the system, also known as the “highwater mark”. Use this when you have no overriding preference about the maximumvalue for capacity and can use whatever is read from the system as the default.

• manually specified network and disk I/O capacity valuesUse this when you want to modify the system's upper bound so that it is more realisticwith regards to your actual usage. For example, if you have a 1 Gb network pipe, butrealistically, the system rarely uses above 10 Mb, you can set the maximum networkI/O capacity to 10 Mb/s.If you have selected to manually specify a value, the Network and Disk I/O Capacityfields will become selectable. In the respective fields, you should enter the desired upperbound values; Network I/O is measured in Mb/s (megabits per second) and Disk I/O ismeasured in MB/s (megabytes per second). Setting the manual maximum value greaterthan the observed maximum is allowed.

Working with Systems 107

2. Once you have chosen the desired upper bound, you can either• Click Apply to set the network and disk I/O capacity and remain on the Network and

Disk I/O Capacity page. The information for the selected system is updated on thebottom table titled Selected Systems.

• Click OK to set the network and disk I/O capacity and return to the VirtualizationManager Visualization view.

• Click Cancel to keep the default settings and return to the Visualization view.

Removing a SystemAs your scenarios evolve, you might need to remove systems from a scenario to represent plannedor actual changes.Prerequisites To remove systems from a scenario:• You must be editing a scenario (see “Editing a Scenario” (page 100)).Procedure 5-55 To Remove Systems from a Scenario1. If you are not on the System tab, click the System tab.

The System tab will open, with a listing the systems in the scenario.

2. Click in the check boxes beside the systems you want to remove from the scenario to selectthem.Check marks will appear in the check boxes.

3. Select Edit ⇒ Remove Systems... from the menu bar.A confirmation screen listing the systems you are removing will be presented.

4. Click the OK button.You will be returned to the Capacity Advisor - Edit Scenario screen with the systems youselected removed.

What Now? Once you have removed systems, you might want to:• View reports and graphs to determine the effects of the changes (see “Producing Graphs

and Reports” (page 84)).

Moving a Virtual MachineMoving Virtual Machines (VMs) among VM hosts allows you to redistribute virtual equivalentsof existing systems across physical servers. Capacity Advisor automatically takes into accountuse of dynamic memory by a Virtual Machine.Prerequisites To move a virtual machine:• You must be editing a scenario (see “Editing a Scenario” (page 100)).Procedure 5-56 To Move a Virtual System1. If you are not on the System tab, click the System tab.

The System tab will open, listing the systems in the scenario.

2. Click in the check box preceding the virtual system you wish to move.A check mark will appear in the check box.

3. Select What-if Action ⇒ Move Virtual Machine... from the menu bar.The Edit Scenario - Move Virtual Machine screen will be displayed, with a list of all theVM hosts available to host the VM.

108 Basic Procedures

NOTE: bar graphs representing the CPU Utilization and Memory Utilization that willexist if the VM were moved to each of the VM hosts provide a quick estimate of how theVM will “fit” on each of the host systems.

4. Click in the circle preceding the name of the VM host that will be the new host for the VM.The circle will be filled in and the row containing the VM host will be highlighted indicatingthe selection.

5. Click the OK button.The System tab of the Capacity Advisor - Edit Scenario screen will open.

What Now? Once you have moved a virtual machine, you might want to:• View reports and graphs to determine the effects of the changes (see “Producing Graphs

and Reports” (page 84)).

Working with Workloads

IntroductionWorkloads represent applications running on systems. The following tasks are described:• Creating a workload (see “Creating a Workload”)• Editing a workload (see “Editing a Workload” (page 110))• Moving a workload (see “Moving a Workload” (page 111))• Parking a workload; parking a workload removes the effects of the workload from the

scenario without losing the definition (see “Parking a Workload” (page 113))• Removing a workload (see “Removing a Workload” (page 113))

Creating a WorkloadWhen you are modeling future configurations, you can create new workloads to representapplications that will be added. The workload can be based on either a static baseline or profiledata from an existing workload.Prerequisites To create a workload in a scenario:• You must be editing a scenario (see “Editing a Scenario” (page 100)).Procedure 5-57 To Create a WorkloadYou can create workloads from the System or Workload tab. For specific descriptions of eachfield on this screen, click the help topic link on the software screen for this task.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 systemon which you want to run the workload(s).A check mark will fill the check box and the line containing the system will behighlighted.

2. Select What-If Action ⇒ Create Workloads... from the menu bar.The Edit Scenario: Create Workloads screen opens.

3. Fill in the Workload Name(s).

4. Optionally, add a detailed description of the workload(s) in the Workload Descriptionfield.

Working with Workloads 109

5. a. If you intend to park the workload(s), confirm that the check box labeled Park/UnassignWorkload 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.

6. Select a system on which to run the workload(s).

NOTE: You can move the workload(s) later as needed.

7. a. If you want to use collected data from a real workload in your computing environment toserve as the baseline information for the new workload(s), select Copy Profile.

b. If you want to supply static values, select Static Profile.

NOTE: Static values remain the same throughout scenario simulations unless modifiedby editing the workload attributes. Copied profile values can change with changes tothe date range selected for the scenario because the data range determines the set ofcollected 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 37) forinformation about each requested attribute.

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

What Now? Once you have created a workload, you might want to:• Edit a workload (see “Editing a Workload” (page 110)).• Move a workload (see “Moving a Workload” (page 111)).• Park a workload (remove the association between the workload and the server; see “Parking

a Workload” (page 113)).• Remove a workload (see “Removing a Workload” (page 113)).

Editing a WorkloadWhen constructing a scenario, it is frequently necessary to modify the characteristics of a workloadto reflect future changes in application or in the users of the application. Use the Edit Workloadsscreen to make modifications to workload characteristics.There are two types of workloads, those that reflect current workloads on the system and thosethat are created in for a scenario. While both can be edited, the characteristics that can be editedare different for each. If you are editing a workload created for a scenario, you can change thebasis from static to workload based and vice-versa.

110 Basic Procedures

Edit Only One Scenario at a Time :Opening a new edit scenario session when another editing session is already open causes theloss of any unsaved changes in the previously opened session. If you were running an automatedsolution in your previous session, the automated calculations are immediately halted and nosettings or results are saved.

Prerequisites To edit a workload in a scenario:• You must be editing a scenario (see “Editing a Scenario” (page 100)).Procedure 5-58 To Edit a WorkloadFor specific descriptions of each field on this screen, click the help topic link on the softwarescreen for this task.1. If you are not on the Workload tab, click the Workload tab.

The Workload tab will open, listing the workloads in the scenario.

2. Click the check box preceding the name of the workload that you wish to edit.A check mark will appear in the check box and the row containing the workload will behighlighted to indicate selection.

3. Select What-If Action ⇒ Edit Workloads... from the menu-bar.The Edit Scenario: Edit Workload screen will be displayed in a new window.

4. If you are editing a workload that uses profile data, or you want to change the workload sothat it will use profile data, modify those fields as appropriate. See “Determining EstimatedUtilization Assumptions for a Workload” (page 37) for more information about the CopyProfile fields.

5. If you are editing a workload that uses a static profile created for this scenario, or you wantto change the workload that it will use static information, modify those fields as appropriate.See “Determining Estimated Utilization Assumptions for a Workload” (page 37) for moreinformation about the Static Profile fields.

6. Click OK.The Workload tab of the Capacity Advisor: Edit Scenario screen opens.

What Now? Once you have edited a workload, you might want to:• Move a workload (see Moving a Workload).• Park a workload (remove the association between the workload and the server; see “Parking

a Workload” (page 113)).• View reports and graphs to determine the effects of the changes (see “Producing Graphs

and Reports” (page 84)).

Moving a WorkloadMovingworkloads allows you to redistribute workloads, including virtual equivalents of existingsystems, across physical servers. While moving workloads, you can compensate for differencesamong systems by adjusting platform multiplier values. These values can be determined byrunning applications on systems representing the hardware and software configurations beingused.

Move ConsiderationsIn considering where to move a workload, think about the following aspects of a move:

Working with Workloads 111

• architecture — is the workload moving from one architecture to a system with the samearchitecture? If the workload may move to a system with a different architecture, what arethe implications of architectural differences?

• operating system — is the workload moving from one operating system to a system with thesame OS? If the workload may move to a system with a different OS, what are theimplications?

• 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?

NOTE: When measuring CPU utilization of Virtual Machines, it is possible for the reportedutilization to be greater than the number of virtual CPU cores (vCPU cores) associated with theVirtual Machine.While the number of Virtual Machine host threads allocated to the process for the virtual machineis restricted to the number of virtual CPU cores, the Virtual Machine host threads used toimplement 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.

Prerequisites To move a workload in a scenario:• You must be editing a scenario (see “Editing a Scenario” (page 100)).Procedure 5-59 To Move a Workload1. If you are not on the Workload tab, click the Workload tab.

The Workload tab opens, listing the workloads in the scenario.

2. Click the check box preceding the workload you wish to move.A check mark appears in the check box, and the row containing the workload is highlighted.

3. Select What-if Action ⇒ Move Workloads... from the menu bar.The Edit Scenario: Move Workloads screen displays.

4. Change the Meter Style, if desired.5. Change the Data Range if a different simulation interval is desired, and click OK to refresh

the table display.

TIP: Longer simulation intervals provide a better picture of activity on the system overtime than shorter intervals do.

6. Change the Meter Representation if a different calculation is desired .7. The first table presents the workloads selected for the move. As you look at the information

presented in this table, consider the factors that affect correctly sizing the workloads for themove.

8. If the original system that the workload resided on differs significantly from the intendeddestination system on which you intend to run the workload, use the CPU and memoryplatform multipliers in this table to adjust for differences between the characteristics of thetwo systems.

9. In the next table, labeled To: (Selected System), take a few moments to mouse over variousentries in the table and analyze the information presented. This table lists the possibledestination systems available in this scenario, their current resource utilization information,and their headroom rating.

10. Select a system to be the new host for the workload.

112 Basic Procedures

11. Click OK.The Workload tab of the Edit Scenario screen opens showing the new workloadrelationships.

What Now? Once you have moved a workload, you might want to:• View reports and graphs to determine the effects of the changes (see “Producing Graphs

and Reports” (page 84)).

Parking a WorkloadWhen constructing a scenario, it can be desirable to temporarily remove the effects of workloadsto reflect potential changes, without permanently removing the workloads. This is referred toas “parking” the workloads.Prerequisites To park workloads in a scenario:• You must be editing a scenario (see “Editing a Scenario” (page 100)).Procedure 5-60 To Park Workloads1. If you are not on the Workload tab, click the Workload tab.

The Workload tab will open, listing the workloads in the scenario.

2. 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 behighlighted, to indicate selection.

3. Select What-If Action ⇒ Park Workloads... from the menu bar.The Edit Scenario - Park Workloads screen will be displayed.

4. Confirm that the workloads listed under Workload Name hosted on the systems listedunder Contained In are the workloads you wish to park.

5. Click the OK button.The Workload tab of the Capacity Advisor - Edit Scenario screen will open.

What Now? Once you have parked a workload, you might want to:• View reports and graphs to determine the effects of the changes (see “Producing Graphs

and Reports” (page 84)).

Removing a WorkloadWhen working with a scenario, it is sometimes desirable to remove workloads to reflect potentialchanges.Prerequisites To delete workloads from a scenario:• You must be editing a scenario (see “Editing a Scenario” (page 100)).Procedure 5-61 To Delete Workloads1. If you are not on the Workload tab, click the Workload tab.

The Workload tab will open, listing the workloads in the scenario.

2. 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 behighlighted to indicate selection.

3. Select What-If Action ⇒ Delete Workloads... from the menu bar.The Edit Scenario - Delete Workloads screen will be displayed.

4. Confirm that the workloads listed under Workload Name hosted on the systems listedunder Contained In are the workloads you wish to delete.

Working with Workloads 113

5. Click the OK button.The Workload tab of the Capacity Advisor - Edit Scenario screen will open.

Working with PowerWith the cost of power for operation and cooling increasing, power has become a resource thatyou may want to measure and manage. Within VSE, power metrics, graphs, and reports aredisplayed for both actual systems and systems within capacity planning scenarios.Capacity Advisor gives you insight into the current power cap for HP systems that have theseoptions available and operating. Capacity Advisor is “aware” of licensed systems where powercaps are used, and you can create reports that include the current power cap set on a system andthe percentage of time that the power cap was enforced on a particular machine during thereporting period.Power usage for systems can be calibrated to provide real-time metrics visible in VisualizationManager and to provide estimations and projections for systems included in Capacity Advisorplanning scenarios.

Power Cap DataThe power cap function allows you to set a limit in watts for a server, and the server will ensurethat its power consumption never exceeds that limit. That, in turn, can reduce power and coolingcosts. It can also help to ensure that a data center does not draw more energy from the powergrid than it is allocated to use, reducing the likelihood of experiencing unplanned downtimenecessary to stay within a power allocation limit.The potential drawback to not setting the power cap high enough is degraded hardware responsetime, which an administrator can rectify by adjusting the cap -- or accept in exchange for theassociated savings. For detailed information on how power caps work in HP hardware, see HPInsight Power Manager.Within Capacity Advisor, you can generate a power report to see historic power usage data thatincludes power cap settings and enforcement time, for systems where this feature is available.The following image shows an example of the power cap data included in a Capacity Advisorpower report.

The power caps settings shown are provided by the administrator who is managing powerconsumption of servers. Capacity Advisor obtains these settings and the enforcement data forreporting purposes from HP Insight Power Manager. For information on how to generate aCapacity Advisor report that includes power usage data, see “Producing Graphs and Reports”(page 84).

114 Basic Procedures

Power CalibrationWhen you are calibrating power data settings, you are specifying the following:• how power metrics should be displayed for graphs, meters, and reports• how the power estimation should be calibrated:

— manually (you specify idle/max watts)— auto calibrated (using power and CPU data from IPM/iLO2)— none (no power metrics are displayed)

Within VSE, there are two areas for calibrating power settings:• For the Actual System (using Virtualization Manager )• Within a Scenario (using Capacity Advisor: Edit Scenario)These two areas are discussed in the sections below.

TIP: The various Power Calibration screens look similar, but you can tell whether you arewithin a scenario rather than interacting with the actual system using Virtualization Managerbecause when you are within a scenario, the page title will show the usual Edit Scenario: prefixand the scenario name will be displayed near the top of the page.

Calibration OptionsOn the power calibration screens you can specify what power data sources will be used. Thechoices are below:

Table 5-3 Calibration Choices

DescriptionChoices

Do not estimate power utilization.None

Import and use only IPM power data to calibrate power estimates .Auto IPM calibrate only.

Attempt to use IPM power data. If no IPM data is available, then use the manualcalibration data.

Auto calibrate. If unable to autocalibrate, use the manualcalibration settings.

Use only manual calibration data.Manual calibrate only.

Auto IPM CalibrationIf you select to use auto calibration, the power data comes from IPM (Insight Power Manager).This requires not only IPM running on the target system, but also a connection from the VSEapplication to IPM and iLO2 (Integrated Lights Out) of the target system.

IPM Configuration Checklist (Single System mode)

If the connection to IPM and ILO2 is not already established, you can use the power calibrationscreens in Virtualization Manager to establish this connection. For a specific system (i.e., in SingleSystem mode), use the IPM Configuration Checklist to guide you through the connection steps.From top to bottom, follow the steps sequentially. Each row in the checklist represents a step:• A green checkmark in the row means that the step is correct and running properly.• A red x in the row means that there is a problem with the step. Use the information and

links under the Notes column to resolve the problem.• A blue question mark means the state is unknown. This usually means that one of the

above steps has a problem (and red x).If you follow the checklist sequentially from top to bottom, you should be resolving the problemsof the row containing a red x before attempting to resolve any issues with the rows containingthe blue question marks.

Working with Power 115

IPM Calibration (Single System mode)

After the IPM and iLO2 connection has been established (i.e., all the icons in the IPMConfiguration Checklist contain a green checkmark), use the links in the IPM Calibration areato perform the actual calibration.

Table 5-4 IPM Calibration Links

DescriptionLink

Compute the power data to obtain power estimates..Calibrate

Clear the current power estimates.Clear Calibration Data

Collect power data from the system. This may take a few minutes.Collect iLO2 Data

If there are any calibration issues once the IPM and iLO2 connection is established, use the LastAttempted Calibration area to fix the issues. Similar to the IPM Configuration Checklist, resolvethe Last Attempted Calibration rows sequentially from top to bottom.

Notes and Known Problems with Auto Calibration

• Importing IPM data can take a significant amount of time when the IPM data is large.• Auto calibration from IPM also requires good IPM data points (sufficient power and CPU

sample history). For IPM, this means a minimum of a 30% change in CPU usage over thelast 30 days.

• Moving the HostnameIf you move the hostname of a physical system to a different physical system, you shouldre-calibrate the power data after SIM has discovered the new physical system.

• Known Problem: Collecting iLO2 License Step .One of the steps in the IPM Configuration Checklist is to collect the iLO2 license. Thefollowing are known issues with this step:— You must be able to ping the iLO2 from the CMS using only the system name (not the fully

qualified domain name).◦ This is due to the fact that the SIM LM (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 iLO2 added to the IP configuration of the CMS.

— You must be able to access the iLO2 via SSH from the CMS.◦ SIM LM collects iLO2 licenses via SSH.◦ There is a maximum of 2 concurrent SSH sessions for iLO2.◦ SIM LM/iLO2 has an issue that causes iLO2 SSH sessions to be abandoned but not

reclaimed. This causes the iLO2 SSH to deny new connections and the SIM LMiLO2 license collection to fail. The only workaround is to reset the iLO2 (i.e., usethe reset button at the bottom of the iLO2 diagnostics page in the iLO2 web GUI).

Manual CalibrationManual calibration allows you to manually calibrate a system by specifying idle/max values.Determining idle/max values is important in accurately estimating power usage. These valuescan be determined by model and hardware configuration. For your convenience, HP has providedpower calculators to aid you in this process. For more information on how these power calculatorsare created, see Power Calculator Development PDF.

116 Basic Procedures

IMPORTANT: Values given by these power calculators only estimates. Actual results may varydepending on application loading, ambient temperature, and other factors.

NOTE: For some servers, the power calculator may only indicate a max value and no idle value.In these cases, you should specify the given max value, and leave the idle value empty. Capacityadvisor will automatically calculate the idle value as 80% of the provided max value.

Determining idle/max Values for Non-Blade Servers

1. Locate the appropriate power calculator for a given model number.a. The power calculators for Proliant DL/ML/PL servers can be found at http://

h30099.www3.hp.com/configurator/powercalcs.asp.b. See the

The power calculators for Integrity RX and Superdome servers can be found at http://h20341.www2.hp.com/integrity/cache/472199-0-0-0-121.html#calculators.

2. Configure power calculator to match your desired hardware configuration. Each powercalculator allows for different hardware configurations, such as amount of processors andmemory, in order to yield the most accurate results.

3. Determine idle/max values by locating the Total System Input Power Requirement. Thisvalue 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 values 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 max power value can be determined.

1) Use the indicated Total System Input Power Requirement as the max powervalue.

2) Leave the idle value blank. Capacity Advisor will automatically use an idle valueas 80% of the provided max value.

Determining idle/max Values for Blade Servers

An HP Blade System has a distributed power architecture, which makes it difficult to determineidle/max values for an individual blade. A single blade’s power usage would depend on rackconfiguration and power consumption of other blades within an enclosure.For HP Blades with iLO2, it is recommended not to use Manual Calibration. Auto Calibrationusing IPM-observed power consumption for an individual blade will yield more accurate results.However, manual idle/max values can still be determined by using the HP Blade System Sizerlocated at http://h71019.www7.hp.com/ActiveAnswers/cache/347628-0-0-0-121.html. Instructionsfor using the HP Blade System Sizer are below:

P-class HP Blades and HP Blade System Sizer:

1. Go to the HP Blade System Sizer and start with an empty configuration.2. Specify Rack and Power configuration.3. Select enclosure1 and specify the appropriate enclosure type.4. Calculate idle value for single blade:

Working with Power 117

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.

5. Calculate the max value for single blade:a. Configure a single bay with a blade matching your desired configuration.b. Specify utilization to 100%.c. Select Update Calculation and record the Total System Input Power Requirement as

maxSingle.6. 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.7. Calculate max value for two blades:

a. Configure two bays with blades matching your desired configuration.b. Specify utilization to 100%.c. Update Calculation, and record the Total System Input Power Requirement as

maxMultiple.8. Calculate the idle/max power values to use:

a. Idle power value will be: idleMultiple – idleSingle.b. Max power value will be: maxMultiple – maxSingle.

C-class HP Blades and HP Blade System Sizer:

1. Go to the HP Blade System Sizer and start with an empty configuration.2. Specify Rack and Power configuration.3. Select enclosure1 and specify the appropriate enclosure type.

a. Configure a single bay with a blade matching your desired configuration .b. Specify utilization to 100%.

4. Select enclosure2 and specify the appropriate enclosure typea. Configure two bays with blades matching your desired configuration.b. Specify utilization to 100%.

5. Select Update Calculation.6. 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 value will be: enc2Idle – enc1Idle.

7. 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. Idle power value will be: enc2Max – enc1Max.

Automating Time-Consuming SimulationsThe Smart Solver recommends where to place workloads among the pool of available servers toreduce the number of servers used or to balance workloads across the servers. The Smart Solvertechnology uses workload traces to quantify the demands placed by the workloads on the serversand uses the workload traces to recommend viable placement solutions subject to user-definedconstraints, such as workload utilization limits and the specific resources that may be used.

118 Basic Procedures

Automated Solution Finding: System Consolidation to VMsThis section describes the procedure for performing an automated system consolidation to virtualmachines. For screen descriptions, see “Automated System Consolidation Screens” in CapacityAdvisor Help.

NOTE: A consolidation adheres to the existing utilization limits. For information on utilizationlimits, see “Utilization Limits ” (page 31).

Begin with a ScenarioFrom 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 Modify ⇒ Edit Planning ScenarioA 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 PlanningScenario” (page 98)).)

Choose the Systems to ConsolidateTake the following actions on the Edit Scenario System tab.1. Using the check boxes, select the systems that you plan to consolidate.

NOTE: The HP Smart Solver is not cluster-aware; this includes Serviceguard as well asVMware clusters. Therefore, solutions can be presented that do not account for the clusterrelationship. To preserve this relationship in a simulation, therefore, choose systems thathave no cluster members, or include all or a subset of members from one cluster.

TIP: Before running the HP Smart Solver automation, ensure that your source servers donot violate any of the utilization limits set for those systems. (Choose What-if Actions EditSystem... to check this information.) When systems violate utilization limits, the SmartSolver solutions are unlikely to be useful.

2. Select What-If Action ⇒ Automated 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 Attributes1. Change the Meter Style, if desired.2. Change the Data Range if a different simulation interval is desired, and click OK to refresh

the table display.

TIP: Longer simulation intervals provide a better picture of activity on the system overtime than shorter intervals do.

3. Change the Meter Representation if a different calculation is desired .4. Select a destination host option.

Automating Time-Consuming Simulations 119

5. Depending on your host destination type, you will need to do one or both of the followingsteps.• 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 asdesired. (See “Host Template Fields” inCapacity Advisor Help for attribute descriptions.)Any new host systems will use this configuration.

6. Change solution constraints, if desired.7. Click OK.

Step 2 of 3 displays.

Step 2 of 3: Set Level of Effort for Smart Solver Calculation1. 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 informsyou of the amount of memory needed to generate the solution and the amount of memoryavailable. If the memory available is insufficient to generate the solution, you will need tocorrect this situation before continuing to run the Smart Solver.

2. Check the Smart Solver Configuration Values and Scenario Contents SummaryInformation 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 Solutions1. Review the proposed solution(s).2. 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.

120 Basic Procedures

Error: Insufficient Resources on the VM Host:Smart Solver informs you when the destination VM host has insufficient resources to host theconsolidated systems. When this occurs, click Return to Step 1 to adjust the attributes andconstraints for the VM host, or Cancel and return to the scenario editor. From there, adjust theresources on your destination VM host or add another VM host to the automated consolidationsimulation.

Reviewing the Consolidation Results

The results screen shows the consolidation summary.Mouse over the headroom stars to learn about the ranking of that system and any utilizationlimits violations that may have occurred as a result of the simulated placement.For more help, see “Results: Automated Consolidation to VMs” (page 65) .

Automated Solution Finding: Load Balance of Servers or VM HostsThis section describes the procedure for automating the search for an optimal load-balanced setof servers. For screen descriptions, see “Automated Load Balance of VM Hosts Screens” and“Automated Load Balance of Servers Screens” in Capacity Advisor Help.

NOTE: The solution will adhere to the existing utilization limits. For information on utilizationlimits, see “Utilization Limits ” (page 31).

Begin with a ScenarioFrom 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 Modify ⇒ Edit Planning ScenarioA 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 PlanningScenario” (page 98)).)

Choose the VM Hosts or Servers to Load-BalanceTake 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: The HP Smart Solver is not cluster-aware; this includes Serviceguard as well asVMware clusters. Therefore, solutions can be presented that do not account for the clusterrelationship. To preserve this relationship in a simulation, therefore, choose systems thathave no cluster members, or include all or a subset of members from one cluster.

TIP: Before running the Smart Solver, ensure that your source servers do not violate anyof the utilization limits set for those systems. (Choose What-if Actions Edit System... tocheck this information.) When systems violate utilization limits, the Smart Solver solutionsare unlikely to be useful.

2. Select What-If Action ⇒ Automated Load Balance of VM Hosts....The window displays step 1 of 3 for Automated Load Balance of VM Hosts....If you are load-balancing servers, select What-If Action ⇒ Automated Load Balance of Servers...

Automating Time-Consuming Simulations 121

Step 1 of 3: Define the Solution Constraints1. Change the Meter Style, if desired.2. Change the Data Range if a different simulation interval is desired, and click OK to refresh

the table display.

TIP: Longer simulation intervals provide a better picture of activity on the system overtime than shorter intervals do.

3. Change the Meter Representation if a different calculation is desired .4. Change solution constraints, if desired.5. Click OK.

Step 2 of 3 displays.

Step 2 of 3: Set Level of Effort for Smart Solver Calculation1. 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 informsyou of the amount of memory needed to generate the solution and the amount of memoryavailable. If the memory available is insufficient to generate the solution, you will need tocorrect this situation before continuing to run the Smart Solver.

2. Check the Smart Solver Configuration Values and Scenario Contents SummaryInformation 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 Solutions1. Review the proposed solution(s).2. 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.

Reviewing the Results

The results screen shows the solution summary.Mouse over the headroom stars to learn about the ranking of that system and any utilizationlimits violations that may have occurred as a result of the simulated load balancing.For more help, see “Results: Automated Load Balancing of Servers or VM Hosts” (page 66).

Automated Solution Finding: Workload StackingHP Capacity Advisor 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 Capacity Advisor then calculates and displays the best results for moving the workloads

122 Basic Procedures

based upon the parameters that you provided. This allows you to see the predicted results ofmoving existing workloads onto selected physical systems.This section describes the procedures for automating workload stacking. For screen descriptions,see “Automated Workload Stacking Screens” in Capacity Advisor Help.

NOTE: Workload stacking adheres to existing utilization limits. For information on utilizationlimits, see “Utilization Limits ” (page 31).

Begin with a ScenarioFrom 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 Modify ⇒ Edit Planning ScenarioA 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 PlanningScenario” (page 98)).)

Choose the Workloads to StackTake the following actions on the Edit Scenario Workload tab. The window will display theCapacity Advisor: Automated Workload Stacking screen with the selected workloads thatyou chose.1. Using the check boxes, select the workloads that you plan to stack.

NOTE: The HP Smart Solver is not cluster-aware; this includes Serviceguard as well asVMware clusters. Therefore, solutions can be presented that do not account for the clusterrelationship. To preserve this relationship in a simulation, therefore, choose systems thathave no cluster members, or include all or a subset of members from one cluster.

2. From the Workload tab, select What-If Action ⇒ Automated Workload Stacking....Step 1 of 3 displays.

Step 1 of 3: Stack the Specified Workloads onto Servers1. Change the Meter Style, if desired.2. Change the Data Range if a different simulation interval is desired, and click OK to refresh

the table display.

TIP: Longer simulation intervals provide a better picture of activity on the system overtime than shorter intervals do.

3. Change the Meter Representation if a different calculation is desired .4. Select a destination host option.

Automating Time-Consuming Simulations 123

5. Depending on your host destination type, you will need to do one or both of the followingsteps.• 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 asdesired. (See “Host Template Fields” inCapacity Advisor Help for attribute descriptions.)Any new host systems will use this configuration.

6. Change solution constraints, if desired.7. Click OK.

Step 2 of 3 displays.

Step 2 of 3: Set Level of Effort for Smart Solver Calculation1. 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 informsyou of the amount of memory needed to generate the solution and the amount of memoryavailable. If the memory available is insufficient to generate the solution, you will need tocorrect this situation before continuing to run the Smart Solver.

2. Check the Smart Solver Configuration Values and Scenario Contents SummaryInformation 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 Solutions1. Review the proposed solution(s).2. 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.

Reviewing the Consolidation Results

The results screen shows the consolidation summary.Mouse over the headroom stars to learn about the ranking of that system and any utilizationlimits violations that may have occurred as a result of the simulated placement.For more help, see “Results: Automated Workload Stacking” (page 67) .

124 Basic Procedures

6 Using Capacity Advisor with ServiceguardYou are likely to use both Capacity Advisor and Serviceguard together in your data center.Serviceguard organizes systems or nodes into Serviceguard cluster nodes, called SG Membersin Capacity Advisor screens such as Edit Scenario and Profile Viewer. In a Serviceguardenvironment, applications, services, and other entities are organized as packages that can movefrom one cluster node to another.

TIP: In the HP SIM Version C.05.00 environment, Serviceguard clusters must have uniquenames. 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

VSE management software organizes applications into workloads. Capacity Advisor collectsutilization data for both systems and workloads. As a package fails over from one system toanother, one of the workloads that Capacity Advisor is tracking might also move from one systemto another. Capacity Advisor continues to monitor the workload on the old system until theworkload is updated or edited to change the host name to that of the new host. Serviceguardpackages and Capacity Advisor workloads are defined independently but can overlap. AServiceguard workload is associated with one Serviceguard package in the Virtualization Managerand Capacity Advisor environment.With the latest release of Virtualization Manager, certain suboperating system workloads areassociated with Serviceguard packages. With this change, the capcollect commandautomatically concatenates the utilization of these Serviceguard-package workloads as theymove from one cluster node to another. This significantly simplifies the use of Capacity Advisorin a Serviceguard environment.

NOTE: Capacity Advisor assumes that Serviceguard-package workloads have been correctlydefined so that there is a reasonably close 1:1 relationship between a Capacity Advisor workloadand the Serviceguard-package workload. If multiple workloads are associated with the sameServiceguard package, Capacity Advisor results might be difficult to interpret.

The first Serviceguard-package workload created on a system also has an OTHER workloadassociated with it for the system where it is running (for example, such a workload would havea name such as system_name.OTHER). The OTHER workload for systems withServiceguard-package workloads in a Serviceguard cluster is associated with the system, notwith the Serviceguard-package workloads. It does not move as the Serviceguard package runningon the system moves to another system in the cluster. If all the Serviceguard-package workloadson a cluster member move to other nodes in the cluster, the OTHER workload for that systemdisappears from the display, and its utilization data becomes inaccessible until aServiceguard-package workload is run on that system. For additional information about thiscapability, see the Virtualization Manager documentation; for more information about workloads,including the OTHER workload, see the “Workloads” topic inVirtualizationManager Help online.

Using Serviceguard to Migrate HP Integrity VM GuestsWhen Serviceguard manages a configuration that contains Integrity VM, failover of a virtualmachine changes the UUID of the virtual machine. Several components of VSE Managementsoftware use the UUID as a search key, and they treat the single virtual machine as two distinctvirtual machines, one with the previous UUID and one with the later UUID. Capacity Advisortreats this as two or more different system traces for a failed over virtual machine. By defaultthese system workloads are named domainname, domainname.2, domainname.3, and so on. Each

Using Serviceguard to Migrate HP Integrity VM Guests 125

system workload has data for only when the virtual machine was running on a particular virtualmachine host, and when the virtual machine fails over, the workload and its utilization datagathered from the previous host becomes inaccessible. Collecting utilization data from the virtualmachine will gather utilization data for the newly created workload.This process affects only the system workload for the virtual machine. If monitored workloadsare defined inside the virtual machine, their data is tracked correctly even when the virtualmachine fails over to a new host. It is a good idea to create a workload inside any virtual machinethat you intend to fail over using Serviceguard to ensure that the utilization data of the virtualmachine is kept whole.

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 acrosstwo or more workloads. To prevent this, use the following procedure to treat these multipleworkloads 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 andcan give a complete picture of past utilization. The collection of these multiple workloads givesyou a nearly uninterrupted view of the historical utilization for the virtual machine.Virtual machines that are moved between hosts using the hpvmmigrate command preservetheir UUIDs and are not seen as two virtual machines.

Data Collection in a Serviceguard EnvironmentWhen you collect data from a virtual machine, capcollect is aware of the guest/hostrelationship 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 whenyou collect data when viewing a Serviceguard workload, capcollect collects data only fromthe 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 sincethe last time data was collected on all the systems in the cluster, there will be gaps in the dataprofile for the Serviceguard workload for those times when the workload was executing onanother cluster member. To fill these gaps, collect data manually from all nodes in the cluster.

126 Using Capacity Advisor with Serviceguard

A Command ReferenceThis reference section contains detailed descriptions of the Capacity Advisor commands.Commands Available on HP-UX and Microsoft Windows Operating SystemsThe command information included here is specific to HP-UX, though these commands are asloavailable to run on Windows. For examples on using these commands on Microsoft Windows,see the “Command Reference” in Capacity Advisor Help.• capcollect(1M)

The capcollect(1M) command collects Capacity Advisor data from systems to examineworkload scenarios, do capacity planning, and store data on the CMS.

• capovpaextract(1M)

The capovpaextract(1M) command exports OVPA system data from a specified managednode and imports the data into Capacity Advisor.

• capprofile(1M)

The capprofile(1M) command imports, exports, displays, invalidates and removes CapacityAdvisor data for workloads or systems.

• capprofile(4)

The capprofile(4) command defines the format of Capacity Advisor data files for importand export.

• capreport(1M)

The capreport(1M) command enables the user to create a report from the command line.• capreport(4)

The capreport(4) command defines the format of a command file with which the user cancreate a report from the command file.

• vseinitconfig(1M)

The vseinitconfig(1M) command configures or unconfigures the VSE ManagementSoftware, and can be used to back up and restore the Capacity Advisor databases. The detailsfor this command can be found in the HP VSE Management Software Version 4.1 Installationand Update Guide for HP-UX on the HP Virtual Server Environment technical documentsweb site

Commands Available on Microsoft Windows Only• capagentlesscfg

capagentlesscfg command collects data from Microsoft Windows systems without the useof an agent. Data from this collection method is picked up by capcollect for storage inthe VSE database for use in capacity planning.

• cappmpextract(1M)

The cappmpextract(1M) command exports HP PMP system data from the specified managedsystem and imports the data into Capacity Advisor.

127

capcollect (1M)NAMEcapcollect -- Collect Capacity Advisor data from systems to examine workload scenarios, docapacity planning, and store the data on the CMS.

SYNOPSISPath on CMS:• /opt/vse/bin

capcollect [-c] [hostname1, hostname2, ...hostnameN]

DESCRIPTIONThe capcollect command enables the user to collect historical utilization data from systemslicensed for Capacity Advisor for analysis on the Central Management Server (CMS). Utilizationdata is gathered from systems specified using Web-Based Enterprise Management (WBEM).WBEM Credentials for the systems are used as set up in HP SIM. The data gathered is stored onthe CMS in files.During a run, capcollect attempts to gather all WBEM utilization data stored on the managedsystem that is not already present on the CMS. Configuring capcollect to be run daily allowsthe last 24 hours of data to be gathered on each run. If a system is inaccessible when capcollectruns, 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 thatcollection be configured to occur daily.

NOTE: An automatic discovery task and automatic capcollect task start the 90-day triallicense for VSE for each discovered managed node.

Options-c Checks the suitability of each system for data collection by verifying its attributes in HP-SIM

and retrieving information about the system using WBEM. Error or warning messages areissued for problems that would prevent successful collection. No utilization data is gatheredand no previously collected data is removed.

-f Performs an IPM calibration only.-i Performs a collection from the ILO interface (can take up to 60 seconds per system).

Operandshostname 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 CapacityAdvisor 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).Disk space needed on the CMS is about 32K per day per workload. In addition toexplicitly created workloads, there is a workload for the whole system and aworkload for orphan processes not assigned to any others.

RETURN VALUESExit values are:0 Successful completion.1 An error was encountered. See the WARNINGS section.3 An error was encountered when creating a new workload in the database or reading an

existing workload from the database.

128 Command Reference

8 An invalid option was specified on the command line.9 An invalid option was specified on the command line.11 While accessing HP SIM to obtain licensing information and WBEM credentials, an error

occurred.12 One or more of the specified systems is not licensed for Capacity Advisor.13 No HP SIM system or WBEM credentials were available.14 While collecting data, an error occurred.15 An error was encountered accessing the WBEM server on a managed system.16 One or more of the system names specified on the command line could not be resolved as

a system name.17 One or more of the systems specified on the command line is running an operating system

type that is not supported.18 HP SIM has identified one of the systems specified as a device for which collection is not

supported.

EXAMPLESCollect Capacity Advisor data from the systems prod05 and sap_1.capcollect prod05 sap_1

WARNINGSWrite access to profile data using the capprofile(1M) command may be delayed while thecapcollect 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 PROCESS1. Retry the operation to see if the same error occurs.2. Verify that the system is connected to the network.3. Verify that the WBEM server process is running on the system.4. Use the /opt/wbem/bin/cimprovider -ls command on the managed node to verify

that the provider is responding to requests.

DEPENDENCIESYou must run the capcollect command on the HP-SIM CMS. For data collection to occur, theutilization provider must have been installed, configured, and running for at least 10 minutes.

EXTERNAL INFLUENCESBy default, capcollect waits as long as 60 seconds for a response from a WBEM request. Itwaits 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 Systems Insight Manager globalsetting, to a different value.For example, running the commandmxglobalsettings -s WBEMTimeOut=120

changes the time-out for WBEM requests to 2 minutes, or 4 + 2 minutes for a Microsoft Windowssystem 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 VirtualMachine Manager.

129

FILES/var/opt/vse/profile/bin

• Root directory for storing collected data.

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

RELEASE VERSIONcapcollect(1M ) A.04.01.00.xxHP Capacity Advisor Version 4.1, January 2009

SEE ALSOcapprofile(1M), capprofile(4)

130 Command Reference

capovpaextract (1M)NAMEcapovpaextract -- Export OpenView Performance Agent (OVPA) system data from the specifiedmanaged node and import the data into Capacity Advisor.

SYNOPSISPath on CMS:• /opt/vse/bin/

capovpaextract [ -b begin-time -e end-time ] [ -p ] managed_nodecapovpaextract -h

DESCRIPTIONcapovpaextract exports OVPA (MeasureWare data) system utilization information from thespecified managed node and imports the information into Capacity Advisor. The data returnedfrommanaged_node overwrites any existing data for the managed node. The user must have rootprivileges to run this command.capovpaextract allows importing data from non-VSE systems, such as older HP-UX systemsor Solaris systems so long as those systems are running a supported OVPA version. SupportedOVPA versions are listed in the Dependencies section of this command reference page.

OPTIONS-b start-time -e end-timeSpecifies 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-VSE workload. This providesan alternative to importing OVPA data from non-licensed systems to use in Capacity Advisorscenarios. If a non-VSE workload already exists in the Capacity Advisor data, an error messageappears. Non-VSE workloads are not associated with any licensed nodes and are not visible onthe VSE -> Workload tab.To import non-VSE workload data, use the following GUI action sequence starting from theCapacity Advisor tab: Modify -> Edit Planning Scenario -> What-If Action -> Create Workloads.Activate the radio button “Use profile data from workload” and choose a non-VSE workloadfrom the “Copy Profile” workload list. You must know ahead of time the name of the non-VSEworkload.-h

Displays command usage.

DependenciesThis command uses the remote execution facilities provided by HP-SIM, and therefore requiresthe configuration of SSH authentication within HP-SIM for the specified managed_node.Capacity Advisor supports the following versions of OVPA :

131

HP-UX• C.03.35 or laterSOLARIS• C.03.75 or laterLINUX• C.04.00 or later

EXAMPLESExtract 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-VSE workload totest.company.com.# capovpaextract -b 01/01/06 -e 06/31/06 -p test.company.com

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

RELEASE VERSIONcapovpaextract(1M ) A.04.01.00.xxHP Capacity Advisor Version 4.1, January 2009

SEE ALSOcapcollect (1M)

132 Command Reference

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

SYNOPSISPath on CMS:• /opt/vse/bin

capprofile -c [ -b begin-time ] [ -e end-time ] [ -y delimiter ] profileIDcapprofile -i [ -p ] [ -b begin-time ] [ -e end-time ] [ -o ] [ -y delimiter ] [ -S] profileIDcapprofile -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 profileIDcapprofile-x [-p ] [-b begin-time ] [-e end-time ] [-t ] [-y delimiter ] profileID...

DESCRIPTIONThe capprofile command manages utilization data collected on the Systems Insight ManagerCentral Management Server (CMS) for Capacity Advisor. With capprofile, you can exportprofile data, either as a file formatted for further processing, or as a table with headings; you canalso import data. With the capprofile command, you can display the names of systems orworkloads that have sufficient utilization data for Capacity Advisor to analyze and, for a particularsystem or workload, you can display those time intervals that have valid data. The capprofilecommand also lets you mark utilization data for specified time intervals as invalid.Refer to thecapprofile command reference pages for information oncapprofile file formats.The capprofile command compensates for certain imperfections in imported data. If profiledata is missing for a sample time, the data is assumed to be unavailable. No data for these samplesis shown in the profile viewer and the samples do not affect utilization aggregation. A warningis issued for each group of consecutive missing samples when importing. Duplicate entries mayappear 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-VSEworkloads, such as data from nodes without Capacity Advisor licenses.During a transition to Daylight Savings Time, sample times may decrease by an hour and thenincrement again as usual. After such a transition, samples are ignored until the time reaches thenext expected sample time.Sample times may differ from times aligned to the hour (the usual case) as long as they are 5minutes apart. Each sample time is modified to the nearest 5-minute multiple from the hour. Forexample, if the first sample time is 18 minutes after the hour, the time for the data sample isimported with a time of 20 minutes after the hour. The next sample time must be 23 minutesafter the hour, and it is imported with a time of 25 minutes after the hour, and so on. A warningis 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 messageissued:• 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.

133

Options-b begin-time Specifies the time to begin using profile data. If omitted, the first available

profile time is used.-c Checks an import file without importing its data. This checks for duplicate

sample times, sample times not aligned to hours, improperly formattedsamples, samples with negative values, and missing samples. A messageis issued for each inconsistency noted.

-e end-time Specifies the time to stop using profile data. If omitted, the last availableprofile time is used.Begin-time and end-time are defined as YYYYMM[DD[hh[mm]]] as follows:

MeaningUnits

Year (for example, 2005)YYYY

Month of the year (01-12)MM

Day of the month (01-31)DD

Hour of the day (00-23)hh

Minute of the hour (00-59)mm

If a day, hour or minute field is omitted, its value defaults to zero.

-h Displays command usage.-i Imports utilization data for a workload or system. The capprofile

command reference pages describe the format of the text representation ofthe imported data. The imported text is read from standard-in (stdin). Alsosee the -o and -S options.

-l Lists profile summaries. By default, this is a list of the systems andworkloads 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.

-m Marks utilization data as valid (v) or invalid (i) for a specified system ora group of systems or workloads. When a data range is specified, only datawithin that range will be affected. If no date range is specified, all data ismarked. Specify the utilization data to be marked by date range. Markingdata by a date range marks every sample in the specified range. Markingutilization data invalid does not remove or alter it; Capacity Advisor justignores it. Marking utilization data invalid excludes all utilization values(CPU, memory, disk or network I/O, and power) from consideration. Youcannot, for example, mark invalid only the CPU utilization portion of asample.Use -m i to mark data for a specified interval and profileID as invalid;use -m v to mark data as valid.

-o When used with the -i option, overwrites existing data.-p Indicates that the workload whose data is being imported is a non-VSE

workload. This provides an alternative to importing OVPA data fromnon-licensed systems to use in Capacity Advisor scenarios. If a non-VSEworkload already exists in the Capacity Advisor data, an error message

134 Command Reference

appears. Non-VSE workloads are not associated with any licensed nodesand are not visible on the VSE -> Workload tab.To import non-VSE workload data, use the following GUI action sequencestarting from the Capacity Advisor tab: Modify -> Edit Planning Scenario.The Edit Scenario window opens. Then select What-If Action -> CreateWorkloads from the menu. Activate the radio button “Use profile datafrom workload” and choose a non-VSE workload from the “Copy Profile”workload list. You must know ahead of time the name of the non-VSEworkload.

-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 isretired and its performance data is no longer needed. The profileID namesa specific workload. All system name profiles are fully qualified.

-S Saves the import-compartment attributes. Used in conjunction with -i toimport data. Saves the container attributes specified in the import headeras attributes for the target profile.

-t Exports data as a table.-x Exports utilization data for the specified profile as a sequence of lines. Each

line contains utilization values for a five-minute period. The format isspecified in the capprofile(4) manpage. The exported text is sent tostandard-out (stdout).

-y delimiter Specifies the delimiter character used to separate values in imported andexported data. The default delimiter is the comma. Valid delimiters, withor without double quotes, are: comma (,), slash (/), semicolon (;), colon(:) and vertical bar (|); some of these delimiters may need to be quoted orescaped.

EXAMPLESExport profile data from December 14, 2005 at midnight to midnight December 31, 2005 for theworkload 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. Allsamples between December 15 2005 at 11 a.m. and December 16 2005 at 12 p.m. (inclusive) aremarked 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 than100% can occur when there is invalid or uncollected data. For example, there may be one or twouncollected data samples on a node right after it reboots.)capprofile -lv

Name Available History Percent Validnode01.co.com 01/17/06 05:30 pm - 01/19/06 10:10 am 100.00%node02.com 12/18/05 05:00 pm - 01/20/06 01:05 pm 99.96%billing3 12/10/05 05:00 pm - 01/20/06 01:05 pm 100.00%node03.com.OTHER 01/15/06 03:05 pm - 01/18/06 12:55 pm 82.83%cimserver 01/17/06 05:30 pm - 01/19/06 10:10 am 99.78%

Import profile data from the file/tmp/nonVSEWorkloadFile.txt for the profile with profileIDnonVSEWorkload.capprofile -i -p nonVSEWorkload < /tmp/nonVSEWorkloadFile.txt

List profile summaries for non-VSE workloads:# capprofile -l -p Non-VSE-Workloads-Name

externalBilling2

135

accounting1monitoring

WARNINGSWhile the capcollect(1M) command is running, write access to profile data using thecapprofile(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 utilizationprofile data, which for each system, is about 32K per day per workload, taking into accountminimum 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 residesmust have space for (100 systems + 300 workloads) * 365 days * 32K = 4.45 Gigabytes. Witha file system that allocates storage in blocks greater than 24K, then use the larger block size.

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

RELEASE VERSIONcapprofile(1M ) A.04.01.00.xxHP Capacity Advisor Version 4.1, January 2009

SEE ALSOcapprofile(4), capcollect(1M), capovpaextract(1M), vseinitconfig(1M)

136 Command Reference

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

DESCRIPTIONDefines 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 thefollowing:• profile headers, including date and metric labels• utilization valuesThe collection period is 5 minutes. Each data line is called a sample.The first eight 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 Advisordatabase. The information includes a profile name, hostname, CPU count and speed, memorysize, OS platform or type, model information, and product version number. These are followedby date and metric labels.The format header is:

#Profile: name#Host: hostname#CPU: CPU_count@CPU_speedGHz#Memory: MEM_sizeMB#OS: platform#Model: model#Version: version_number[YYYYMMDDhhmm,] UTIS, metric [, metric, ...]The English characters shown above always appear in the field names and units specified in theheader, 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 datawas gathered for 1 CPU. Only integer values are valid. Note that CPU_count includes iCAPprocessors that are not enabled. This reflects the number of cores when dual-core processors arein use. The number of hardware threads when hyperthreaded processors are in use are NOTcounted 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.version_number: Capacity Advisor version number.metric: One of the following: CPU_ALLOC, CPU_UTIL, DISK_UTIL, MEM_ALLOC, MEM_UTIL,NET_UTIL, PHYS_CPUS, PHYS_MEM, PWR_UTIL, PWR_ALLOC.The last header line contains the comma-separated list of labels for the date and gathered metrics,with or without spaces, where the fields are defined as:YYYYMMDDhhmm: Timestamp in local time, given in units of YYYY (year), MM (month, as 01to 12), DD (day, as 01 to 31), hh (hours, as 00 to 23), and mm (minutes, as 00 to 59). This formatis also used to specify the begin and end times for the capprofile(1m) command. This fieldis optional when importing data.

137

UTIS: Universal Time (GMT) in seconds (standard UNIX time in seconds since 1 January 1970).CPU_ALLOC: Number of CPUs allocated (active CPUs only; cores or hardware threads onmulticore). Hyperthreaded processors are not counted in CPU_ALLOC.CPU_UTIL: CPU utilization expressed as the number of CPUs used (5 minute average).DISK_UTIL: Disk bandwidth utilization in MB/s (10^6 bytes, megabytes per second) (5 minuteaverage).MEM_ALLOC: Memory allocation in GB (gigabytes).MEM_UTIL: Memory utilization or amount of memory used in gigabytes (at end of intervalreading).NET_UTIL: Network bandwidth utilization, in Mb/s (10^6 bits, megabits per second) (5 minuteaverage).PHYS_CPUS: Number of physical CPUs (at end of interval reading).PHYS_MEM: Physical memory available, in GB (gigabytes).PWR_UTIL: Power utilization expressed as kW (5 minute average).PWR_ALLOC: Not available.The last line of the import file header must include at least one metric column label and mayhave any combination of the eight existing metric column labels, in any order. It must have theUTIS 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 incrementin 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 importonly 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 theheader. Utilization values for a sample are separated by a specified delimiter character or by acomma (default). The UTIL seconds must be in 5-minute intervals (increments of 300 seconds).For example, a file could contain the following profile format headers followed by the date andthe labels for each metric:#Profile: node05

#Host: node05.company.com

#CPU: 4@1.3GHz

#Memory: 4084MB

#OS: HPUX

#Model: ia64 hp server rx5670

#Version:A.02.50.00

YYYYMMDDhhmm, UTIS, CPU_ALLOC, CPU_UTIL, DISK_UTIL, MEM_ALLOC, MEM_UTIL,NET_UTIL, PHYS_CPUS, PHYS_MEM

NOTE: In the following examples, UTIS values are truncated to omit following zeroes.

EXAMPLESThe following example shows utilization data in compressed format created using the followingcommand:# capprofile -x -b20051201 -e2005120101 node05.company.com

#Profile: node05#Host: node05.company.com#CPU: 1 @ 1 GHz#Memory: 2024MB#OS: HPUX#Model: ia64 hp server rx5670#Version:A.02.50.00

138 Command Reference

YYYYMMDDhhmm,UTIS,CPU_UTIL,MEM_UTIL,NET_UTIL,DISK_UTIL,CPU_ALLOC,MEM_ALLOC,PHYS_CPUS,PHYS_MEM (NEW)YYYYMMDDhhmm,UTIS,CPU_ALLOC,CPU_UTIL,DISK_UTIL,MEM_ALLOC,MEM_UTIL,NET_UTIL,PHYS_CPUS,PHYS_MEM200509120000,11264184,0.02443,1.139648,0.003,0.0117,1.0,1.97656,1.0,1,97656200509120005,11264187,0.02283,1.150390,0.005,0.0146,1.0,1.97656,1.0,1,97656

The following example shows utilization data in a tabular format, aligned in columns.

#Host: node05 HP-UX B.11.23 #CPU: 1 @ 1.0 GHz #Version:A.02.50.00YYYYMMDDhhmm, UTIS, CPU_ALLOC, CPU_UTIL, DISK_UTIL, MEM_ALLOC, MEM_UTIL, NET_UTIL, PHYS_CPUS, PHYS_MEM200509120020, 11264196, 0.01, 2.14, 0.003, 0.02, 4.0, 3.98, 4.0, 3.98200509120025, 11264199, 0.03, 2.13, 0.005, 0.01, 4.0, 3.98, 4.0, 3.98200509120030, 11264202, 0.02, 2.15, 0.003, 0.01, 4.0, 3.98, 4.0, 3.98200509120035, 11264205, 0.02, 2.15, 0.004, 0.01, 4.0, 3.98, 4.0, 3.98200509120040, 11264208, 0.01, 2.13, 0.004, 0.01, 4.0, 3.98, 4.0, 3.98200509120045, 11264211, 0.02, 2.14, 0.003, 0.01, 4.0, 3.98, 4.0, 3.98200509120050, 11264214, 0.02, 2.14, 0.003, 0.02, 4.0, 3.98, 4.0, 3.98

The following example shows data gathered only for CPU allocation and utilization.

YYYYMMDDhhmm, UTIS, CPU_ALLOC, CPU_UTIL200605250020, 11264196, 0.01854, 2.14200605250025, 11264199, 0.03128, 2.13200605250030, 11264202, 0.02075, 2.15200605250035, 11264205, 0.02101, 2.15200605250040, 11264208, 0.01960, 2.13200605250045, 11264211, 0.02391, 2.14200605250050, 11264214, 0.02387, 2.14

AUTHORScapprofile(4) was developed by Hewlett-Packard Company.

RELEASE VERSIONcapprofile(4) A.04.01.00.xxHP Capacity Advisor Version 4.1, January 2009

SEE ALSOcapprofile(1M), capcollect(1M)

139

capreport (1M)NAMEcapreport -- Generate reports of historical data or utilization trends based on existing targets orthe existing configuration.

SYNOPSISPath: /opt/vse/bin

capreport -n system [-n system ...] [-t type ] [-b begin-time ] [-e end-time] [-W ]capreport -wworkload-name [-wworkload-name ... ] [-t type ] [-b begin-time] [ -e end-time ]capreport -f configuration-filecapreport -h

DESCRIPTIONThe capreport command displays historical data or utilization trends for selected targets,workloads or systems.Using capreport is an alternative provided for users to create reports using the command line(CLI); capreport provides several of the reports obtainable through the Capacity Advisor graphicaluser interface (GUI).capreport produces two reports, each focused on a different use of utilization information, asfollows:• A Utilization Report, which provides information on historical utilization for a specific target• A Trending Report, which provides information on past trends in resource utilizationcapreport provides reports for workload and system target types.The user can specify multiple workloads or systems, and multiple target types.capreport does not support generation of scenario comparison reports, nor complexes as atarget type.If the user omits both start and end times, the report includes all historical utilization dataavailable for the given target. If the user does not specify a valid date interval, capreport returnsan error message.The user obtains reports as HTML output saved as a file in the current directory. To specify adifferent directory, use the capreport configuration file. For information on the capreportconfiguration file, refer to the capreport(4) manpage.capreport generates reports using the following defaults:

Table A-1 Defaults

Default ValueSetting

current directoryoutput directory

includeddetail

600 pixelsgraph width

4:3aspect ratio

1 weekbusiness interval

95%valid threshold

averagingaggregation method

includederror analysis

140 Command Reference

Table A-1 Defaults (continued)

Default ValueSetting

utilizationreport type

noshow workloads

Optionscapreport recognizes the following options:-b begin-time The moment when to start collecting data (see -e endtime for

specific format).-e end-time Begin-time and end-time have the same format as follows:

YYYYMM[DD[hh[mm]]]where:YYYY -- Digits of the yearMM -- Month of the year (01-12)DD -- Day of the month (01-31)hh -- Hour of the day (00-23)mm -- Minute of the hour (00-59)

-W Display all physical children workloads of the selected systems.-f configuration-file Specifies an input file of commands to use instead of command

line values and arguments. Refer to the capreport(4) manpagefor the format of entries in the configuration-file.

-h Displays command usage.-n system Specifies the names of systems for which to report aggregate

utilization.-t report-type Specifies the type of report to be produced. The Utilization

Report (util) and Trending Report (trend) are available; theyare described above under Description.For both Utilization and Trending reports, the user can specifyworkloads or systems, but not complexes.

-w workload-name Specifies the names of workloads for which to report utilization.(Note: workloads seen by capreport may not be identical tothose on the VSE Workload tab.)

EXAMPLESShow capreport usage information.capreport -h

Create a Utilization Report (-t util) in the current directory for node01 (-n node01). The reportuses utilization data from November 18th, 2006 (-b 20061118) to December 20th, 2006 (-e 20061220).Note that util is the default report type.# pwd/user/current-directory# capreport -t util -n node01 -b 20061118 -e 20061220Report files generated on file:///user/current-directory/2007-3-1-123719-371/CapAdReport/index.html

Create a Trend report in HTML format in the current directory for node01 (-n node01). The reportuses historical utilization data from November 28th, 2006 (-b 20061128) to December 20th, 2006(-e 20061220).

141

# capreport -t trend -n node01 -b 20061128 -e 20061220Report files generated on file:///user/current-directory/2007-3-1-123725-111/CapAdReport/index.html

DEPENDENCIESThe user must run thecapreport command on the HP SIM Central Management Server (CMS).capreport creates reports only for systems licensed for Capacity Advisor on the CMS.

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

RELEASE VERSIONcapreport(1M ) A.04.01.00.xxHP Capacity Advisor Version 4.1, January 2009

SEE ALSOcapcollect(1M), capprofile(1M), capovpaextract(1M), capreport(4)

142 Command Reference

capreport(4)NAMEcapreport -- Format for Capacity Advisor capreport configuration file. Create a report from entriesin a file.

SYNOPSIScapreport configuration-file

DESCRIPTIONUsing the capreport configuration file provides a way for the user to specify report parametersthat are different from the default values. The user can specify all capreport command-lineparameters in a file that is used with the capreport command. Additional options can bespecified using a capreport configuration file that cannot be specified from the command linefor the capreport command.File Structure:

A valid capreport configuration file has the following structure, described below:• Report Declaration• Default Options• Detail OptionsReport Declaration:

Before setting default and detail options for reports, the user must define the name of each reportwith a statement in the following form: report=report_name_1[, report_name_2, ..., report_name_n]For example, the following line in a configuration file defines two reports:report=report01,report02

Your Default Options:

To set parameters that are common to all reports, use the following syntax:report.default.parameter=value

For example, the user requests the same report type for both report01 and report 02 using thefollowing lines:report =report01, report02report.default.type=util

The default report is valid for all detail options.Detail Options:

Once report names and default options are established, the user can optionally set their parametersusing the following syntax:report.report-name.parameter=valueValid parameters and their possible values are described next.REPORT TYPEreport.report-name.type=value

value can be either util(to create a Utilization Report) or trend(to create a Trending Report).SYSTEM NAMEreport.report-name.system=value

value is the name of the system for which to create a report. More than one system can be specifiedusing the following syntax:report.report-name.system=value1, value2, ...

This option is equivalent to capreport with the CLI option -n.WORKLOAD NAME

143

report.report-name.workload=value

value is the name of the workload for which to create a report. More than one workload can bespecified using the following syntax:report.report-name.workload=value, value2, ...

This option is equivalent to capreport with the CLI option -w.DATE SELECTIONreport.report-name.sdate=value1report.report-name.edate=value2

sdate specifies the report-start date, edate specifies the report-end date; value1 and value2 havethe same format as follows:YYYYMM[DD[hh[mm]]]where:YYYY -- Digits of the yearMM -- Month of the year (01-12)DD -- Day of the month (01-31)hh -- Hour of the day (00-23)mm -- Minute of the hour (00-59)This option is equivalent to using the capreport CLI option -b for sdate and -e for edate.REPORT CONTENTreport.report-name.details=value

value can be either yes, to include detail in the graphs in the report or no to omit graph detail.By default, detail is yes.GRAPHING OPTIONSreport.report-name.ratio=value1report.report-name.width=value2

value1, which sets the aspect-ratio, can be 4:3, 7:5, or 16:9 (default: 4:3); value2, which setsthe graph-width in pixels, can be 400, 500, or 600 (default: 600).REPORT OUTPUTreport.report-name.output=value

value is html.HTML OUTPUT DIRECTORYreport.report-name.outputdir=value

value specifies the output directory or folder for the html report files. If not specified, files areplaced in the current directory.AGGREGATION METHODreport.report-name.method=value

value is average, peak, or 90th (for 90th percentile).ERROR ANALYSISreport.report-name.eanalysis=value

value is yes (to include error analysis data in the report) or no (to omit such data).THRESHOLD VALUEreport.report-name.threshold=value

value is an integer greater than zero (0) and less than or equal to 100.BUSINESS PERIODreport.report-name.period=value

144 Command Reference

value represents the number of days (d) or weeks (w) in the business interval of interest. Forexample, reports for different business intervals might include one for 15 days (15d) and onefor 1 week (1w).

EXAMPLESExamples of command files used with capreport appear below. Note that any property valuecontaining an empty string must be set with quotation marks.The following example shows a simple configuration file with no default values and no multiplevalues for properties.#my_input_file_sample_1report=myreportreport.myreport.type=utilreport.myreport.workload=node01WorkloadOnereport.myreport.sdate=200611201120report.myreport.edate=200612050935report.myreport.detail=yesreport.myreport.ratio=7:5report.myreport.width=500report.myreport.output=html

The following example shows the creation of two different reports from the same command file.#my_input_file_sample_2report=myreport, myreport2report.myreport.type =utilreport.myreport.workload=node01WorkloadOnereport.myreport.sdate=200611201120report.myreport.edate=200612050935report.myreport.details=yesreport.myreport.ratio=7:5report.myreport.width=500report.myreport.output=html

report.myreport2.type=utilreport.myreport2.system=node03, node04report.myreport2.sdate=200611201120report.myreport2.edate=200612050935report.myreport2.details=yesreport.myreport2.ratio=7:5report.myreport2.width=500report.myreport2.output=html

The following example shows how to define default values, using the same reports from theprevious example that had many properties in common.#my_input_file_sample_3report=myreport, myreport2report.default.sdate=200611201120report.default.edate=200612050935report.default.details=yesreport.default.ratio=7:5report.default.width=500report.default.output=html

report.myreport.type=utilreport.myreport.workload=node01WorkloadOne

report.myreport2.type=utilreport.myreport2.system=node03, node04

AUTHORScapreport(4) was developed by Hewlett-Packard Company.

145

RELEASE VERSIONcapreport(4) A.04.01.00.xxHP Capacity Advisor Version 4.1, January 2009

SEE ALSOcapreport(1M), capprofile(1M), capovpaextract(1M)

146 Command Reference

capagentlesscfg(1M)NAMEcapagentlesscfg -- Set options for the Capacity Advisor Agentless Data Collection service, andgenerate a configuration file that contains a list of nodes from which data can be collected. TheAgentless Data Collection service is available for CMS on Microsoft® Windows® servers only.

SYNOPSISDefault path:• C:\Program Files\HP\vse\lbin

capagentlesscfg node1, node2,...nodeNcapagentlesscfg -o -n number_of_collectors -m minimum_interval node1,node2,...nodeNcapagentlesscfg -a node1, node2,...nodeNcapagentlesscfg -h

DESCRIPTIONcapagentlesscfg creates a list of nodes from which to collect data, and sets the number ofcollecting threads and the minimum time interval to occur between data collections. Collecteddata is written to a file that can be imported into Capacity Advisor. Once the command is run,data collection continues until it is disabled. The user must have Administrator privileges to runthis command.capagentlesscfg allows you to configure the collection of utilization data from systemslicensed for Capacity Advisor. This utility is useful where no Utilization Provider is present ona node for data collection or where less intrusive data collection is desired. When a system isconfigured for agentless data collection, Capacity Advisor uses agentless data for that systemeven if a Utilization Provider is installed on the system. When a system is not configured foragentless collection, data collection for the system is attempted using the Utilization Provider.

Options-a

Append the listed nodes to the current agentless configuration file.-h

Display the capagentlesscfg command usage-l

List the current configuration for agentless data collection.-m minimum_intervalOptional. Define the minimum time (in seconds) that must pass before the next collection canstart. Default value: 300 seconds (5 minutes). To restore the default value after an alternativevalue has been specified, use0 for the value ofminimum_interval. 14,400 [seconds] is the maximumvalue allowed.-n number_of_collectorsOptional. 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. Torestore the default value after an alternative value has been specified, use 0 for the value ofnumber_of_collectors. 100 [threads] is the maximum value allowed.-o

Overwrite the listed nodes in the current agentless configuration file with the new nodes listed.-r

Remove specified nodes from the agentless configuration file.-R

147

Remove all nodes from the agentless configuration file.

Operandsnode1, ...nodeNThe fully qualified domain names of nodes where data is to be collected via the agentlessconfiguration.

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

EXAMPLESGenerate a node list configuration file (capadcollector.nodes) and a properties file(capadcollector.properties) using default options for minimum interval betweencollections and number of collector threads used.# capagentlesscfg node1 node2 node3 node4

Generate a node list configuration file using default options and overwrite the existingconfiguration file.# capagentlesscfg -o node1 node2 node3 node4

Generate a node list configuration file with 3–minute intervals between data collections, andoverwrite the existing configuration file.# capagentlesscfg -o -m 180 node1 node2 node3 node4

Generate a node list configuration file with 5–minute intervals between data collections andusing two collector threads. Append the node list to the existing configuration file.# capagentlesscfg -a -m 300 -n 2 node1 node2 node3 node4

Remove named nodes from the configuration file:# capagentlesscfg -r node1 node2 node3 node4

Removes all nodes from the configuration file:capadagentlesscfg -R

AUTHORScapagentlesscfg was developed by Hewlett-Packard Company.

RELEASE VERSIONcapagentlesscfg A.04.01.00.xxHP Capacity Advisor Version 4.1, January 2009

SEE ALSOcapcollect(1M)

148 Command Reference

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

SYNOPSISPath:install_dir\bin C:\Program Files\HP\vse

cappmpextract -lcapovpaextract -hcappmpextract -x managed_node [ -b begin_time ] [ -e end_time ]cappmpextract -i managed_node [ -o ][ -p ] [ -b begin_time ] [ -eend_time ]

DESCRIPTIONThe main functionality of cappmpextract is to export PMP system utilization data for thespecified managed node and import into Capacity Advisor. The user must have Administratorprivileges to run this command. Because PMP is only available on a Windows CMS, this commandwill only work on a Windows CMS.The cappmpextract command also provides ways of (1) listing PMP managed nodes whichcontains 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-VSE managed nodes (non- licensednodes), so long as those nodes are being monitored by a supported PMP version. SupportedPMP versions are listed in the Dependencies section of this command reference page.

OPTIONS-i

Imports utilization data for a system into Capacity Advisor database. Also see the –o option.-b start-time -e end-timeSpecifies 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 dayIf no beginning and ending dates are provided, cappmpextract extracts all available data. Theuser can not provide only beginning or ending dates.-h

Displays command usage.-l

Lists all PMP managed nodes, including available data interval and percent of valid data foreach system. Any node listed by the -l option is a valid node to have its PMP data importedinto Capacity Advisor with the -i option.-x

Exports utilization data for the specified system from PMP to standard-out (stdout). The utilizationdata is exported in the same CSV format used by capprofile. The format is specified in the capprofile(4) command reference page-o

Used with the -i option. This allows cappmpextract to overwrite existing data.

149

-p

Indicates that the workload whose data is being imported is a non-VSE workload. This providesan alternative to importing PMP data from non-VSE licensed systems to use in Capacity Advisorscenarios. Non-VSE workloads are not associated with any licensed nodes and are not visibleon the VSE Workload tab.To import non-VSE workload data, use the following GUI action sequence starting from theCapacity Advisor tab: Modify -> Edit Planning Scenario. This will open the scenario that youselected. Then click What-If Action -> Create Workloads from the Edit Scenario menu. Activatethe radio button “Use profile data from workload” and choose a non-VSE workload from the“Copy Profile” workload list. You must know ahead of time the name of the non-VSE workload.

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

EXAMPLESExtract PMP data and import it into CapAd 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-VSE workload totest.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 intoCapacity Advisor:# cappmpextract –lName Available History Percent ValidSystemA 12/17/07 05:30 pm - 12/18/07 05:05 pm 97.53%SystemB 12/17/07 05:35 pm - 12/18/07 05:05 pm 97.52%

AUTHORScappmpextract was developed by Hewlett-Packard Company.

RELEASE VERSIONcappmpextract A.04.01.00.xxHP Capacity Advisor Version 4.1, January 2009

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

150 Command Reference

B Units and TerminologyThe units and terms listed in the following table are used within Capacity Advisor. For anexpanded list of terminology used within Capacity Advisor and VSE Management Software, seethe “Glossary”at the end of this guide.

Table B-1 Units and Terminology

MeaningUnit or Key Word

Active data-processing unit within a processor; a processor (CPU) can contain one or morecores. Multiple cores on the same physical unit provides the capability for multiprocessingwithin the same CPU.

core

Central Processing Unit. The computer chip that executes most programming instructions; canbe composed of one or more cores.

CPU

The number or percentage of CPU cores in use.Each Capacity Advisor data sample represents a 5–minute average of CPU cores used overthat period of time. These measurements are calculated by tracking CPU usage within thekernel at each polling interval in the following manner:

Table B-2 Data Collection for CPU Utilization by Platform

Collected FromCalculationPlatform

pstat()Total used CPU ticks during the intervaldivided by the total available CPU ticksduring the interval

HP-UX

/proc/statTotal used CPU ticks during the intervaldivided by the total available CPU ticksduring the interval

Linux

CPU PDH counterPercent busy since the start of the intervalMicrosoft® Windows®

HP Virtual MachineManagement Pack(VMM)

Imported as isProliant VM host andVMs

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 5minutes that span less than two sample periods. Any "missed" utilization is attributed tosystem processes.

CPU utilization

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

Table B-3 Data Collection for Disk I/O Bandwidth Utilization by Platform

Collected FromCalculationPlatform

pstat()Total bytes transferred during the intervalHP-UX

/proc/diskstatsTotal bytes transferred during the intervalLinux

PDH disk countersTotal bytes transferred out during the intervalMicrosoft Windows

HP Virtual MachineManagement Pack(VMM)

Imported as isProliant VM hostand VMs

disk I/O bandwidthutilization

Gigabytes. Unit used for memory: (10^9 bytes)GBs

151

Table B-1 Units and Terminology (continued)

Gigahertz. In Capacity Advisor, CPU capacity is defined in terms of clock speed expressed inmegahertz (10^6 hertz) or gigahertz (10^9 hertz). Clock speed refers to the rate at which acomputer performs its most basic operations such as adding two numbers.

GHz

Capability of some Intel® processors to create an additional virtual core that provides additionalprocessing efficiencies. Note that Capacity Advisor does not count Hyper-Thread virtual coresseparately.

Hyper-Threading

In Capacity Advisor, the hypervisor includes not only the virtualization platform, but also allfunctions performed by the host OS, as well as all virtual machine monitoring processes(everything on the VM host that is not a VM guest).

hypervisor

Capacity Advisor estimates hypervisor memory overhead by adding together all memoryused in support of running guests. This overhead can be estimated by adding together thememory 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 virtualizationplatform.

Except in the case of HP Virtual Machine, Capacity Advisor assumes a worst case scenariowhere all guests are allocated 1GB of memory, as this will maximize the hypervisor memoryoverhead.

hypervisor memoryoverhead

The difference between the average resource utilization on a system and the maximum availablecapacity. See Headroom for an explanation of headroom ranking (stars), and information oninterpreting the star rankings shown in automated solutions.

headroom

Megabits (10^6 bits) per second. Unit used for networking throughput.Mb/s

Megabytes per second (10^6 bytes per second). Unit used for storage media throughput.MB/s

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

Table B-4 Data Collection for Memory Utilization by Platform

Collected FromCalculationPlatform

pstat()Memory used by the usersHP-UX

/proc/statMemory used by the usersLinux

Memory used by the users + memory usedby the system + cache memory

Microsoft Windows

HP Virtual MachineManagement Pack(VMM)

Imported as isProliant VM hostand VMs

memory utilization

The ability of an application and operating system to split processing between processors orcores, thereby enabling parallel computing.

multithreading

152 Units and Terminology

Table B-1 Units and Terminology (continued)

Measured in Mb/s (10^6 bits, megabits per second).Each sample represents an average reading over the past 5 minutes. These measurements areobtained and calculated in the following manner:

Table B-5 Data Collection for Network I/O Bandwidth Utilization by Platform

Collected FromCalculationPlatform

MIB systemTotal bytes transferred during the intervalHP-UX

proc/net/devTotal bytes transferred during the intervalLinux

PDH countersTotal bytes transferred out during theinterval

Microsoft Windows

HP Virtual MachineManagement Pack(VMM)

Imported as isProliant VM host andVMs

Counters are sampled at the start and end of each interval.

network I/Obandwidthutilization

The system-name.OTHERworkload is used to account for all processes on a system that do notmatch any user-defined workloads. For more information, see “Workloads” in VirtualizationManager Help. On some Capacity Advisor displays, data is not available for this .OTHERworkload.

OTHER workload

Component that plugs into a processor socket. A processor can contain more than one core.processor

The packaging of one or more processors in a unit that connects to a single socket on thesystem bus.

processor module

The system board socket to which a processor is attached.processor socket

A compensating factor that Capacity Advisor uses to adjust needed resources when analyzinga move from one platform to another.

scaling multiplier

153

154

C Snapshots of a Scenario Comparison ReportThe following images provide clips from a report that compares three scenarios: one a collectionof physical servers and two consolidation solutions that illustrate changes that would occur aftermoving the physical servers to VM hosts. These images are provided to illustrate the types ofinformation that the report contains for each scenario included in a scenario comparison report.

155

Workload Detail

156 Snapshots of a Scenario Comparison Report

Scenario Inventory

157

158 Snapshots of a Scenario Comparison Report

159

160 Snapshots of a Scenario Comparison Report

161

162

D Troubleshooting in Capacity AdvisorBehaviors that you might see when working within the Capacity Advisor user interface that maynot have error or warning messages associated with them are explained in this appendix.

Connection ProblemsWithin an interdependent product like VSE Management Software, there are conditions that cancreate errors in connection that make it difficult or impossible to for some functions to completein Capacity Advisor.Cannot Collect Data from Utilization Provider on HP Proliant Servers Running Novell Suse Linux 9or 10 The Utilization Provider depends on OpenPegasus for data transfer to the VSE CMS,but OpenPegasus is not provided by default with Suse Linux 9 and 10. Remedy: UninstallOpenWBEM on these systems and install OpenPegasus. See the HP VSE Management SoftwareVersion 4.1 Installation and Update Guide for HP-UX for complete instructions.Errors in CMS or Managed Node Configuration VSE Management Software provides a toolcalled vseassist that you can use to identify and troubleshoot system configuration errorsthat may be preventing data collection or other use of Capacity Advisor. For full information onthe vseassist tool, seeHP Insight Dynamics—VSE andHPVSEManagement Software 4.1 GettingStarted Guide.Internet Explorer Times Out Before Report Generation Completes In the case where you requesta report using data from many managed systems (>100), Microsoft Internet Explorer may endthe session connection before the report is complete. This ends the report creation; no report isgenerated for viewing or download.Remedy: One way to address this behavior is to create a registry key on your local MicrosoftWindows system to extend the amount of time that Internet Explorer will wait before closingthe 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 perserver.)

• ReceiveTimeout extends the timeout boundary of the browser. (Use hexadecimal valuesto adjust the time to the desired number of hours, with 24 hours being the maximum timethat 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 forProfiling capprofile may hang when exporting large amounts of non-contiguous data (dataset contains significant periods when data was not collected interspersed with periods of datacollection). Remedy: Export contiguous chunks of data.Licensing - General To collect data from a managed node, that node must be licensed to fullyuse Capacity Advisor or must have a limited license (the HP Insight Capacity AdvisorConsolidation Software) for data collection only. For information on licensing, see the “Licenses”chapter in HP Insight Dynamics— VSE and HP VSEManagement Software 4.1 Getting Started Guideand “Data Collection and the HP Insight Capacity Advisor Consolidation software” (page 80).

Connection Problems 163

License Check Fails The licensing check conducted by Capacity Advisor will fail in the casewhere a duration license has been assigned or locked prior to HP SIM discovering the serialnumber of the system. Remedy: Confirm that a system has been fully discovered in HP SIMbefore assigning a duration license to it. For systems for which HP SIM does not attempt todiscover serial numbers, this problem does not occur. (For a definition of a “duration license”,see “About Licenses” in the online HP SIM Technical Reference Guide.)User Authorization Some operations in Capacity Advisor require Administrator orrootpermissions. As needed, check that you are logged in with the appropriate role orpermissions for the operation you are trying to do. For information on user authorizations, seethe “Licenses” chapter inHP Insight Dynamics—VSE andHPVSEManagement Software 4.1 GettingStarted Guide.

Data May Appear to be Old When it is NotWhen time or time zone on a managed node is set incorrectly (that is, it is not synchronized withthe clock time on the CMS), the user may collect data and see only old dates for data collected.Remedy: You must complete the following tasks (the process is different for each operatingsystem):1. Correct the time or time zone on your managed node.2. Stop and restart the Utilization Provider daemon.Brief instructions for these tasks are provided here.

Setting the Time or Time ZoneOn an HP-UX or Linux managed node, use the date(1) command to set the correct time. Onan HP-UX system, the source of the time zone varies depending on the local configuration. Seethe 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 forctime(3C) and environ(5). On SuSE Linux, see the file /etc/sysconf/clock. For otherversions of Linux, consult the operating system documentation.On Microsoft® Windows, right-click on the time displayed at the right end of the task bar andselect Adjust Data/Time. Select the Time Zone tab on the dialog box and select the correct timezone from the drop-down list at the top. Click OK to close the dialog box and use the new timezone.

Stopping and Restarting the Utilization Provider DaemonOn HP-UX and Linux, use the following command:kill `ps -ef | grep utild | grep -v grep | awk '{ print $2 }'`

On Windows 2003 Server: Start ⇒ Manage Your Server ⇒ Tools andUpdates ⇒ Administrative Tools ⇒ Services. Look for HP UtilProvider Data Collector inthe Name column. Right click on the row and select Stop. Wait for it to stop and then right-clickon it again and select Start. Close the Services window, the Administrative Tools window andthe Manage Your Server window.

Data Seems to be IncorrectVM Guest Resource Utilization Appears to Exceed the Resource Utilization of Its VM Host Whenviewing historical resource utilization data in a Profile Viewer, it can appear that the utilizationof a resource by a given VM guest exceeds the utilization of that resource by its VM host at agiven instance of time. (For example, you might see the I/O usage occasionally exceed the VMhost's high-water mark value (the dashed blue line in the Profile Viewer graph).In reality, it should never be possible for a VM guest's resource utilization to exceed that of itshost, since the utilization shown for a VM host is the aggregation of a resource's utilization forall VM guests running on that host. Yet this does occur on rare occasions due to differences inhow the data was collected, interpolated, and averaged into the 5–minute intervals that CapacityAdvisor stores in its database.

164 Troubleshooting in Capacity Advisor

Such anomalies become insignificant when the data is averaged over sample intervals greaterthan 5 minutes.Note that this situation typically occurs only when a single guest is running on the host and iscreating a very large load on the host.For other issues where data seems to be incorrect, see:• Data For Node Appears to Differ From One Profile Viewer to Another (page 166)• A Configuration Change is not Immediately Visible in all VSE Products (page 166)• “Data May Appear to be Old When it is Not” (page 164)

Out-of-Memory Errors in the Java HeapA few situations can cause the Java Heap to run out of memory.Running the Nightly Data Collection on 500+ Systems The Capacity Advisor product installsan automatically scheduled task named "Collect ALL Capacity Advisor Data Nightly" to run atmidnight to collect utilization data from all licensed systems listed in the "All Systems" collection.(This task runs the capcollect on the command line with no arguments.) The capcollectcommand can exceed its maximum allowed memory if this list of nodes is greater than 500systems. Remedy: See “First Data Collection (or the Automated Nightly Collection)” (page 72)to understand this error and determine an alternate way to collect all the utilization data.Spiking the mxdomainmgr Server Process When capcollect is executed, its initial invocationcauses a temporary spike in memory use of the server process named "mxdomainmgr". If theHP SIM server is currently managing a large number of systems, there is a small chance that thisspike in memory could cause the server process to reach its maximum configured memoryallocation.Remedy: See theHPVSEManagement Software Version 4.1 Installation and Update Guidefor HP-UX for more information on tuning VSE configuration parametersEditing a Scenario Containing a Large Number of Systems and/or Workloads When using the"Edit Scenario" page in Capacity Advisor, the number of workloads included in the scenario andthe selected data range to use for analysis will affect how much memory is used in the HP SIMserver process to read and analyze the scenario. Initially editing the scenario will invoke theaction to read and analyze the utilization data of all systems and workloads defined in thescenario. The greater the number of systems and the longer the date range, the more memoryand time is consumed to read and analyze the utilization data.Remedy:Experiment with differentcombinations of systems, workloads, and data ranges to arrive at a manageable, but still usefulscenario.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 requiredto provide a solution. With multiple users running automated “what-if” actions simultaneously,the server process can reach its maximum configured memory allocation. Remedy: See the HPVSEManagement Software Version 4.1 Installation andUpdate Guide for HP-UX; for more informationon tuning VSE configuration parameters.Running Reports With Very Large Data Sets or When CMS is Busy During the execution ofCapacity Advisor reports, consumed memory is monitored. Should consumed memory reach agiven threshold (85% of total JVM memory) the report execution stops and informs you thatthere is insufficient memory to complete the report(s ) Users trying to create more modest oreven small reports could see this message if the rest of the system is busy. Remedies: Increaseheap memory size allocated to the JVM and/or reduce memory pressure on the CMS. Try togenerate the report again.Exporting Four Years or 3 MB of Data into Capacity Advisor for Profiling capprofile abortswith data sets of this size. Remedy: Export multiple, smaller chunks of data.

Scenario Editor IssuesThis section discusses behaviors of the Scenario Editor that may cause confusion.

Out-of-Memory Errors in the Java Heap 165

Edit Scenario Window Not Seen A couple situations can cause you to “lose” the Edit Scenariowindow.• The window can be blocked by a browser pop-up blocker when you initially try to open it.

Remedy: Check that you have pop-up blockers turned off in the browser that you use tocontrol Capacity Advisor functions.

• In the case where the Edit Scenario window is already open in Mozilla Firefox, but is hiddenbeneath other windows when you create a new scenario, it is not obvious that the windowhas refreshed with your new scenario information. Remedy: set Firefox to allow Javascriptto raise or lower windows. Then, when you create a new scenario, the pre-existing EditScenario window will rise to the forefront of the display.

Workload and System Relationships May Not Match When ComparingCapacity Advisor and Virtualization Manager Information

A Configuration Change is not Immediately Visible in all VSE Products This information is updatedevery 5 minutes, but there still can be a period of time when the information that you can see inthe Virtualization Manager Visualization tab may differ from that presented in Capacity Advisor.Remedy: Click to the Workload tab in the Virtualization Manager and then click the "RefreshData" link on the far right corner of the screen above the table that lists discovered workloads.HP SIM Identification of a VM Host and its Virtual Machines Inconsistent If you open the CapacityAdvisor "Edit Scenario" page 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 ofthe virtual machines associated with it.Remedy:Re-identify the VM host and its virtual machinesto correct this issue. See the HP Systems Insight Manager Technical Reference Guide to learn how toidentify or discover systems from the HP SIM menu bar or from the command line. You needto 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 tabto ensure the information is also up-to-date for Capacity Advisor. If this problem persists, youmay need to runvseassist on the VM host to determine why HP SIM is not correctly identifyingthe VM host and its constituents.Data For Node Appears to Differ From One Profile Viewer to Another Though the Profile Viewerlooks the same and behaves similarly from whichever location it is accessed, the data displayedfor a node may indeed differ – it may be actual historic data or an aggregation of data, dependingon the location from which the viewer is accessed or the type of system being viewed. For adiscussion of data handling in the Profile Viewer, see “Using the Profile Viewer” (page 85).

166 Troubleshooting in Capacity Advisor

E Capacity Advisor MessagesCertain messages that you might see when working within the Capacity Advisor user interfaceor that are about data collected for use in Capacity Advisor are explained in this section. Messagesappearing in the user interface that are self-explanatory are not included here.

Command Error MessagesWithin the messages sections, messages appear in alphabetical order. Messages that start withsystem_name are placed at “s” in a list.During data import using the capprofile command, sample_time is the timestamp in local timeif 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 thissystem cannot proceed until this situation is corrected. detailed_messagewhere system_name is the name of an HP-SIM managed node from the names specified on thecommand line, and detailed_message is one of the Capacity Advisor data collection messages.

For additional information, refer to the “Command Reference” (page 127) in this guide, as wellas the HP SIM Technical Reference Manual or the HP SIM User Guide.

Table E-1 Error Messages and Their Correction

To CorrectPossible CauseMessage

Examine the output. If informationthere seems insufficient, runvseassist to troubleshoot connectionerrors.

Appears at the end of output ifdata collection failed on anysystem.

Collection failed on 1 system orCollection failed on n systems.

Use mxstart to start HP SIM on thecentral management server.

HP SIM is not running.Could not access the HP SIM instance onthis system; nested exception is:java.net.ConnectException: Connectionrefused.

• Check that the Utilization Provideris running on the system.

• Check that the system is licensedfor Capacity Advisor.

• Check that the workload is stillassociated with the same system (isCapacity Advisor informationup-to-date).

• Run vseassist to troubleshootconnection errors.

• The Utilization Provider maybe missing or incorrectlyconfigured on the managednode.

• The system may not belicensed for Capacity Advisordata collection.

• The workload may have beenmoved since the last automaticupdate in Capacity Advisor(update occurs every 5minutes).

Error collecting utilization data forwhole-OS workload "system-name" -no data collected.orError collecting utilization data forworkload "workloadname" on"system-name" - no data collected.orError collecting physical CPU utilizationdata for HPVM "vm-host" from HPVMHost "vm-name" - no data collected.

• Check that the server is up, andstart a new collection.

• Check that the workload is stillassociated with the same system (isCapacity Advisor informationup-to-date).

• Run vseassist to troubleshootconnection errors.

• A system may have been downduring the collection period.

• The workload may have beenmoved since the last automaticupdate in Capacity Advisor(update occurs every 5minutes).

Error collecting utilization data forwhole-OS workload "system-name" -some data collected.orError collecting utilization data forworkload "workloadname" on"system-name" - some data collected.orError collecting physical CPU utilizationdata for HPVM "vm-host" from HPVMHost "vm-name" - some data collected.

Command Error Messages 167

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

To CorrectPossible CauseMessage

Ensure that the node is licensed, andthat appropriate permissions for thenode are set. Run vseassist totroubleshoot connection errors.

Permissions for this node are notin place.

Error: Missing Capacity Advisorauthorization for node: system_name

Ensure that the system where theworkload is running has appropriateauthorization or credentials, thencollect data on that system again. Runvseassist to troubleshoot connectionerrors.

Missing authorization orcredentials for a system.

Error: No data has been collected for thespecified workload.

Check access and process activity. Runvseassist to troubleshoot connectionerrors.

See message text.system_name: Another HP SIM CentralManagement Server may be accessingthis system. CIM_ERR_NOT_FOUND:The requested object could not be found:Instance not found for RpID: FSS_3 anddatetime: date_time, GUID: n.

Run vseassist to troubleshootconnection errors.

See message text.system_name: Error attempting to accessthe WBEM server;CIM_ERR_NOT_FOUND: The requestedobject could not be found: Instance notfound for RpID: rpid and datetime:2006...,GUID: n.

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

The system specified bysystem_name during datacollection is running Version2.00.09 of HP-UX WBEM Serviceswithout required patches.

system_name: Error creating object.

Command Warning MessagesWithin the messages sections, messages appear in alphabetical order. Messages that start withsystem_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 127) in this guide, as well asthe HP SIM Technical Reference Manual or the HP SIM User Guide.

Table E-2 Warning Messages in Capacity Advisor

To CorrectProbable CauseMessage

Check for advisements and takecorrective action if desired.

Appears at the end of output ifany warnings were issued.

1 warning issuedorn warnings issued

Overlapping samples are automaticallyignored or invalidated in CapacityAdvisor. Import the data again, takingcare to designate date ranges that donot overlap.

Samples imported withcapprofile that overlap in timecannot be interpreted.

A series of overlapping samples beginsat time sample_time. The overlappingsamples starting at this time are ignored.

Discover the system from and HP SIMCMS running on a Microsoft ®Windows system and collect data fromthere.

Collection from VMware andMSVS Virtual Machines is onlysupported from a Windows HPSIM CMS.

Collection from system_name is notsupported on an HP-UX CMS.

168 Capacity Advisor Messages

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

To CorrectProbable CauseMessage

To cause the workload to be known,select system_name in the VSEManagement Visualization tab screen.Then select Tools ⇒ Update SystemWorkloads from the Visualization tabmenu.

The workload is not known toVSE.

Warning: Ignoring unknown monitoredworkload "workload_name" on"system-name".

The improperly formatted values willbe automatically marked as invalid,and will not be included in CapacityAdvisor reports.Some formatting errors can bemanually corrected. See thecapprofile(1M) command reference pagefor format examples.Use the Profile Viewer to determine ifthe sample contains a sufficientnumber of valid data points to providea meaningful report.

A sample line in the file importedwith capprofile containsvalues that are improperlyformatted.

Improperly formatted sample values attime sample_time have been ignored.

See “Out-of-Memory Errors in the JavaHeap” (page 165).

See “Out-of-Memory Errors in theJava Heap” (page 165).

Java Heap Space. Please see the HPCapacity Advisor User's Guide for moreinformation on this issue and possiblesolutions.

The missing samples will beautomatically marked as invalid andwill not be included in CapacityAdvisor reports. Use the ProfileViewer to determine if the samplecontains a sufficient number of validdata points to provide a meaningfulreport.

Samples imported withcapprofile are missing for oneor more sample intervals.

Missing sample for 1 time interval at timesample_time.orMissing samples for n time intervals attime sample_time.

The negative samples will beautomatically marked as invalid andwill not be included in CapacityAdvisor reports. Use the ProfileViewer to determine if the samplecontains a sufficient number of validdata points to provide a meaningfulreport.

A sample imported withcapprofile contained anegative value for the value of ametric.

Negative sample value at timesample_time has been ignored.

Ensure that the CMS has access toWBEM. Run vseassist totroubleshoot connection errors.

CMS access to WBEM, usingBastille, ipf, or other means, hasbeen shut down.

No systems are available from HP SIMin the “HPVSE” collection.

Add the required credentials to thesystems where you plan to runCapacity Advisor, or run thecimserver process. You can also runvseassist to troubleshoot connectionerrors.

Either no WBEM credentials havebeen entered in HP SIM or HPSIM could not successfully use thecredentials entered. The latter canhappen when acimserverprocess is not running on thesystem.

No WBEM credentials are available forsystem "system_name”. Please verifythat a valid WBEM account andpassword for this system are configuredin HP SIM (Options->ProtocolSettings->Global Protocol Settings).

Synchronize the managed node clockto the CMS system clock.

Capacity Advisor cannot analyzeutilization across multiplesystems or servers when systemclocks (and therefore, datatimestamps) are notsynchronized.

Sample time sample_time is not alignedto hour intervals.

Command Warning Messages 169

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

To CorrectProbable CauseMessage

The system or server is runningan operating system unsupportedby VSE.

Skipping system_name— collection fromthe some_operating_system operatingsystem is not supported.

From the HP SIM “All Systems” page,click the system name to go to the HPSIM System Page. On the “identify”tab, click the + next to “ProductDescription” to expand it. If the SystemType is “unknown” or “unmanaged,”capcollect cannot collect data fromthat system. Change the System Typeto “server.”

HP SIM has not discoveredenough information about thissystem for capcollect to beable to collect data from thesystem. capcollect requiresthat the System Type attribute hasthe value “server” to collect froma system.

System system_name has incompletesystem information. Check the system'sstatus in HP SIM.

Set up the trusted certificate bymanually installing the system'scertificate into the HP SIM TrustedSystem Certificate List.

See message text.system_name: HP SIM requires trustedcertificates for managed systems but notrusted certificate exists for this system.

Install the WBEM utilization provideron the system.

See message text.system_name: The Utilization WBEMProvider is not installed.

Correct the global or system protocolsettings for the affected system in HPSIM. You may need to rerun discoveryto have the settings take effect.

The capcollect commandcannot use the WBEM credentialsprovided by HP SIM, perhapsbecause of recent changes to theuser ID or password.

system_name: The WBEM credentialsprovided by HP SIM were not acceptedby the WBEM server.

On the managed system, execute thecommand/opt/wbem/sbin/cimserver

The WBEM provider on thesystem is not running and shouldbe restarted.

system_name: The WBEM server is notrunning and should be restarted.

See message text.See message text.system_name: Upgrade the UtilizationProvider on this system to versionA.01.06.00.00 or later.

Run vseassist to troubleshootconnection issues.

A network or system problemprevents contact with the WBEMserver.

system_name: Unable to contact theWBEM server. See thecapcollect(1M)manual page.

Run vseassist to troubleshootconnection issues.

system_name: System information is notavailable from the WBEM provider.Collection from this system cannotproceed until this situation is corrected.

If you prefer not to use the methoddescribed in the message, change thevalue for the CMS_HOSTNAMEproperty in thevseprefs.props filefrom localhost to some other name thatresolves to the IP address of the CMS.

See message text.The Name Resolution Service could notresolve localhost on the CMS. To correctthis, make sure that either the namelocalhost can be resolved on the CMS orchange the CMS_HOSTNAME setting in/etc/opt/vse/vseprefs.props toa hostname for the CMS that can beresolved. See the hosts(4) andnsswitch.conf(4) manual pages.

See message text.If HP SIM has not correctlydiscovered all of the systemattributes (operating system type,model, CPU count/speed, andmemory size) some of theattributes needed to export theprofile using the capprofilecommand are not available.

The system attribute "attribute-name"is not available from HP SIM for theworkload-name workload. Either run"Identify" on the system in HP SIM andexport the profile again, or correct thesefields in the header of the exportedprofile before importing it.

170 Capacity Advisor Messages

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

To CorrectProbable CauseMessage

If the profile data originated from acapprofile export, re-export thedata after running Options ⇒ IdentifySystems...on the system in HP SIM,or manually correct the values in theheader. See the capprofile(1M)command reference page for anexample of a correctly formatted file.

When importing a file usingcapprofile, the input fileheader must contain correctvalues for the system from whichthe profile data was gathered. Ifone or more attributes have thevalue <UNKNOWN>, the profilecannot be imported.

The system attribute "attribute-name"must be specified before this profile canbe imported.

Install the HP VM WBEM provider(vmProvider) on the virtual machineor correct the configuration problem.For help with using vseassist, seetheHP Insight Dynamics—VSE andHPVSE Management Software 4.1 GettingStarted Guide.

An HP virtual machine may bediscovered by HP SIM andlabeled as a standalone server ifthe system does not have aproperly configured WBEMprovider for HP VMs. Such asystem cannot be collected fromuntil it is discovered by HP SIMcorrectly.

The system "system_name" has noworkload defined. Make sure to selectTools ⇒ VSE Management...in HP SIMbefore running this command for the firsttime. For HPVM Guests, please be surethat the HPVM WBEM provider isproperly configured. If problems persist,run VSE Assist to further diagnose errors.

Verify that the name is spelledcorrectly or add the system to HP SIM.

The system name specified on thecommand line is not known to HPSIM.

The system system_name was not foundin the HP SIM database.

Set authorizations as needed. Forinformation on user authorizations inVSE, see HP Insight Dynamics — VSEand HP VSE Management Software 4.1Getting Started Guide.

See message text.The user has none of the required toolboxauthorizations on node cms_name, wherecms_name is the name of the CMS wherethe command was run.

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 username contains a domain, forexample, commandname– user“mydomain\myusername” –passmypassword

There was a problem connecting to theHP SIM server.

See message text.Unable to collect from system"system-name" because it is disabled inHP SIM.

Run vseassist to help locate theproblem.

A network or system problem ispreventing contact with theWBEM server.

Unable to contact the WBEM server. Seethe capcollect(1M) manual page.

The most recent sample is kept.More than one sample importedwith capprofile has the sametime stamp.

Values at duplicate sample timesample_time replace previous values forthis time.

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

Workload on the utilizationprovider on system_name is notknown to VSE. No utilization datais collected for this unknownworkload.

Warning: Ignoring unknown workloadworkload_name on system_name

Redefine the workloads so that theirutilization limits fall within theresource allocation for the system.

The sum of workload utilizationsexceeds system utilization.

Warning: Overlapping workloaddefinitions detected on system_name.

Command Warning Messages 171

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

To CorrectProbable CauseMessage

Install a version of the WBEM ServicesCore Product that is 2.00.08 or later.

capcollect relies on WBEM toreport the local time on a system,but Version 2.00.07 of the WBEMServices Core Product for HP-UXreports the local time incorrectly.Messages that do not indicate atime difference of about an hourand for which actual times on theservers are not an hour apart, arenot likely to be caused by thewrong WBEM version.

Warning: the system clock onsystem_name is ~60 minutes, ss secondsahead of the system clock on the CMS;this may render the utilization dataunusable for planning purposes. If thetime on the managed node is correct, thenode's version of 'HP WBEM Services forHP-UX' may be older than the minimum,A.02.00.08.

Ensure that clocks on systems in thescenario are synchronized to the clockon the CMS system.

When systems are used togetherin a scenario, Capacity Advisorassumes that the time axis of theutilization graphs for all systemsis the same. The time axis isobtained from the system clockon the system where theutilization data is gathered. If thesystem clock is not synchronizedwith the other systems and withthe CMS, the Capacity Advisorsummed utilization traces maynot be correct. This error messageis issued if the time differencebetween the system for whichdata is collected and the CMS ismore than 15 minutes.

Warning: the time difference of nnnseconds between the system clock onsystem_name and the system clock on theCMS may render the utilization datagathered unusable for planningpurposes.

HP Smart Solver Error MessagesIn situations where the Smart Solver is unable to produce a solution, one or more error messagesare displayed. Solver error messages are shown in red text on the user interface screen anddescribe the issues that prevent a solution from being found.In Example 1, three workloads ("puny03v10", "puny03v15", and "puny03v3") cannot be placedon any system because the available systems lack sufficient capacity for several resources (CPU,memory, and network I/O bandwidth).

Figure E-1 Example 1. Solver Error Messages When Systems Have Insufficient Resources to Placea Workload

172 Capacity Advisor Messages

When more than one workload does not fit, a summary line is included that reports the minimumsystem capacity required to place the workloads.Remember that the Smart Solver includes utilization limits set for the workload, system, orscenario-wide when calculating desired capacity for the solution. Therefore, one way to correctthe resource insufficiency would be to raise the utilization limits for the specified metrics. Anotherway would be to select or add additional systems having at least the minimum required capacity.In Example 2, the Smart Solver is unable to arrange the workloads such that they can all be placedon available systems, even though the systems have sufficient resources to place at least oneworkload per system.

Figure E-2 Example 2. Solver Error MessagesWhen Too Few Systems Are Available for the CalculatedRequired Capacity Needed

In contrast to Example 1, 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 systemsto place all the workloads.In this case, the Smart Solver can not derive a singular estimate of additional required capacityfor a resource because an estimate depends on whether the remaining workloads will all beplaced on a single system (thereby using the most restrictive utilization limits), or spread acrossmultiple systems.As a result, a range of estimates is displayed: the first value specifies the total aggregate demandif all workloads were placed together (20.5 GB in this example), while the second value is thesummed demand for each workload if it were placed separately (22.6 GB). The workload(s) usedin the estimation are named.It is possible that different combinations of the same workloads and systems can result in failureson different metrics. In Example 2, the Smart Solver message states that the failure to arrive at asolution is due to memory shortfalls, which occurred 100% of the time. Given the same workloadsand systems but an alternate solution, the Smart Solver may identify that 80% of the failureswere due to CPU overages while 20% were due to memory shortfalls.

HP Smart Solver Informational MessagesWhile working on a solution, the Smart Solver notes any non-critical issues that it encounters.These issues are presented on the Solution Results page in the "Smart Solver Solution Information"box. For example, in the following consolidation and load balance job:

HP Smart Solver Informational Messages 173

Figure E-3 Example 3. Solver Information MessagesWhenWorkload Requirements Exceed AvailableCapacity

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

174 Capacity Advisor Messages

Glossary90th percentile That utilization value in the selected time interval which 10% of the utilization values fall above,

and 90% fall below or are equal to.AcceleratedVirtualInput/Output

See AVIO.

activate When referring to a logical server, activate means to make a logical server definition availableto be deployed into the computing environment. An active logical server is one that is currentlyoperating within the computing environment. An inactive logical server is one that has beendefined but is not currently operating within the computing environment.

activate cell The process of changing an inactive cell into an active cell. A cell is activated when it is integratedinto an nPartition. A cell can also be activated through cell online activation.

activate I/Ochassis

The process of changing an inactive I/O chassis into an active I/O chassis. A chassis is activatedwhen the cell to which it is attached is activated.

activated core A core that has been turned on by theHP Instant Capacity (iCAP) software or during installation.Cores are activated with the icapmodify command (or the vparmodify command in anHP-UX virtual partition) while HP-UX is running.

active cell A cell that is available for use by the software running on the nPartition. This implies that thecell's cores and memory (and I/O, if the cell is attached to an active I/O chassis) are all availablefor use by the OS. An active cell has the following characteristics:• It is present and populated.• It is powered on.• It is assigned to an nPartition.• It is released from boot-is-blocked.

active I/O chassis An I/O chassis with an initialized link to the system bus adapter (SBA). The SBA link must beinitialized for software running on the nPartition to be able to use I/O cards installed in the I/Ochassis.

active logicalserver

A logical server that has been bound to both an HP SIM node and a VSE workload, and is boundto specific storage. Active logical servers can be in one of two states: powered on or poweredoff.See also inactive logical server, logical server.

active nPartition An nPartition is active if at least one of the cells in the nPartition is active.See also inactive nPartition.

add-on system A system that has been converted to an HP Instant Capacity (iCAP) system. This process isperformed by an HP service representative.

advisory mode SRD advisory mode lets you see what requests HP Global Workload Manager (gWLM) wouldmake for a compartment without changing its resource allocation.See also managed mode, deploy.

agent A program with a well-defined task that runs in the background and that is used to captureinformation or do processing tasks.

agentless datacollection

The collection of inventory and performance data from managed systems without requiringinstallation or configuration of agents on the managed systems.

agile addressing Supported on HP Integrity Virtual Machines running HP-UX 11i v3, a storage device addressingmodel that addresses a logical unit (referred to as LUN, this is the logical device that refers tothe physical storage device) by using the same device special file (DSF) regardless of the locationof the LUN. The addressing model uses a worldwide device identifier (WWID) to uniquelyidentify LUNs. The WWID is a device attribute that is independent of the device’s location ina SAN or in an adapter/controller access path. With a multipath device, the WWID allows onepersistent DSF to represent a LUN, regardless of the number of paths (known as lunpaths) tothe LUN. Therefore, an agile device address remains the same (is persistent) when changes aremade to the access path. Likewise, if additional lunpaths are offered to a given LUN (by adding

175

a new SCSI controller or new SCSI target paths), the DSF is unaffected: no new DSFs need beprovided. This model enables VM Manager to display one DSF for each multipath device insteadof displaying a separate DSF for each path to the device (as done when using the legacy addressingscheme).See also legacy addressing.

allocation The amount of a resource thatHPGlobalWorkloadManager (gWLM) sets aside for a compartmentafter arbitrating resource requests from the policies for all the compartments.In managed mode, gWLM makes an allocation available to a compartment. In advisory mode,gWLM reports what the allocation would be without changing resource allocations on a system.See also entitlement.

annual projectedgrowth rate

The rate at which utilization of a resource is projected to change.

application A logically related set of processes active on a host system (a running application ) and/or alogically related set of files on a host system disk (an installed application).HPApplicationDiscovery recognizes applications based on standard package installation, templatesthat are shipped with the product, and templates that are defined by users.

ApplicationDiscovery

HP Application Discovery. The HP VSE Management Software application that inventoriesrunning and installed applications in a network and provides application and process mapdata used for creating workloads in HP Virtualization Manager.See also application discovery.

applicationdiscovery

The process of finding applications and gathering performance and location data about themfor display and use.See also Application Discovery.

assign cell to annPartition

A modification of the Stable Complex Configuration Data to change a cell from a free cell to anassigned cell in a specific nPartition. Once assigned to an nPartition, a cell must be activated inorder to use the cell's resources.

association In HP Systems Insight Manager (HP SIM), an association is created by discovery andidentification of HP SIM system objects that are then associated with other objects. One

1.

type of association is containment. For example, clusters contain members, complexescontain nPartitions, and OS images contain resource partitions.

2. In HP Global Workload Manager (gWLM), a policy-workload association tells gWLM whichpolicy to use to manage that workload's resource allocation.

availableresources

Cells and I/O chassis that are not assigned to an nPartition; or cores, memory, and I/O resourcesthat are not assigned to a virtual partition. These resources are available to be used in newpartitions or can be added to existing partitions.

average The sum of all the utilization values divided by the number of data points for the selected timeinterval.

AVIO Accelerated Virtual Input/Output. An I/O protocol that improves virtual I/O performance fornetwork and storage devices used within the Integrity VM environment. The protocol alsoenables support for a greater number of virtual I/O devices per guest. Participating guests mustinclude a virtual I/O device configured to use the AVIO protocol.

backing store A device that is accessible to the Integrity VM Host and maps to a storage device on a virtualmachine.

base cabinet A compute cabinet that can be used as the only compute cabinet in a complex, or as half of a dualcompute cabinet complex. A base cabinet is always physically the left cabinet in the pair (whenviewed from the front) and is always the cabinet that contains the Service Processor.See also cabinet, expansion cabinet.

base cell A cell whose memory can participate in interleaved memory. For HP-UX releases prior to 11i v3(B.11.31) September 2007, all cells were base cells. The operating system also can place certainvital data in memory on base cells.A base cell does not participate in interleaved memory in the following situations:

176 Glossary

• If the cell was online activated.• If the cell's failure usage flag is set to Base, No Interleavewhen the nPartition is booted

after a cell hardware failure during the cell's self-tests.• If the cell is configured with 100% cell local memory.A base cell can be selected for cell online activation but not for cell online deactivation.Firmware automatically sets the active core cell to a cell type of Base when the nPartition isbooted.See also floating cell.

baseline A timeless demand profile used to generate demand profiles in forecasting.BCH Boot console handler. The system firmware user interface that allows boot-related configuration

changes and operations on PA-RISC systems. For example, BCH provides a way to specify bootoptions and the choice of boot devices. The EFI Boot Manager provides a similar function forItanium®-based systems.

BIB Boot-is-blocked. The state of a cell that is powered on but not allowed to boot. BIB exists as soonas power is enabled to a cell, although the system firmware completes its power-on self-testsequence before waiting for BIB to be cleared by the Service Processor. BIB is cleared when theService Processor is told to boot an nPartition. BIB is also cleared when the system firmwaredetermines that there is no active Service Processor in a complex.See also ready for reconfiguration.

BladeSystem HP BladeSystem is an infrastructure in a box that can support a combination of virtual machines,storage blades, and server blades. It comprises server blade compute nodes, integrated connectivityto data and storage networks, and shared power subsystems.See also BladeSystem enclosure, BladeSystem Integrated Manager.

BladeSystemenclosure

Hardware solution for consolidating server blades and all supporting infrastructure elements(such as storage, network, and power) into a single unit.See also BladeSystem Integrated Manager.

BladeSystemIntegratedManager

A component in HP Systems Insight Manager (HP SIM) that provides streamlined managementfor the entire HP BladeSystem product family. It enables users to quickly navigate their HPBladeSystem environments, including server blades, enclosure infrastructures, racks, and integratedswitches, through automatically generated blade-rack picture views and hierarchical trees.Accessible from an icon on the HP Virtualization Manager's Visualization view.

boot consolehandler

See BCH.

boot-is-blocked See BIB.bound core For vPars versions prior to A.04.xx, a core that can process interrupts for a virtual partition.

Bound cores cannot be migrated from one virtual partition to another if either of the partitionsis running. Every virtual partition must have at least one bound core.See also unbound core.

business period The time interval (a day or a week) for which to create an HP Capacity Advisor report.cabinet The physical enclosure that contains cells or I/O chassis. A cabinet also includes hardware that

provides power and cooling. Some cell-based servers support cabling several cabinets togetherto form a single complex.See also base cabinet, cabinet, compute cabinet, expansion cabinet, I/O expansion cabinet.

cabinet blowers The main cooling fans on top of HP Superdome server compute cabinets. They provide the mainairflow through the cabinet.

Capacity Advisor HP Capacity Advisor. The HP VSE Management Software application that performs analysisand planning of workloads on a system or across a set of systems.

capacity planning The analysis and planning of workloads on a system or across a set of systems.capacity-planningsimulation

The process of combining workload demand profiles, as prescribed by a scenario, to estimate thedemand profiles of the systems that contain the workloads. Statistics gathered from thesimulation can be summarized in reports.

177

CC Cell controller. A chip located on every cell board that has interfaces to the cores and memoryon the cell. The cell controller also has an interface to a system bus adapter and to the fabric. Thecell controller maintains data coherency across the cells in an nPartition.

cell A circuit board that contains processors and memory, all controlled by a cell controller (CC). Acell is the basic building block of an nPartition in a complex.

cell controller See CC.cell local memory See CLM.cell OLA See cell online activation.cell OLD See cell online deactivation.cell onlineactivation

The process of changing an inactive cell to an active cell in a booted nPartition without requiringa reboot. HP-UX releases prior to 11i v3 (B.11.31) September 2007 do not support online activationof cells.See also cell online deactivation.

cell onlinedeactivation

The process of changing an active cell to an inactive cell in a booted nPartition without requiringa reboot. HP-UX releases prior to 11i v3 (B.11.31) September 2007 do not support onlinedeactivation of cells.Only cells whose cell type is Floating can be deactivated online.See also cell online activation.

cell power on/off Enable or disable power to a cell. A cell cannot become active until power has been enabled. Itmust be inactive before power can be disabled. A cell location must be populated in order toenable power. Physical removal of a cell must not occur until power has been disabled.Powering a cell on or off will also power on or off an I/O chassis that is attached to the cell.

cell type A per-cell attribute in the Partition Configuration Data that specifies how the cell is used withinthe nPartition.The following cell types are supported by the HP-UX 11i v3 (B.11.31) September 2007 releaseand later:• base cell• floating cell

cell-based server A server in which all cores and memory are contained in cells, each of which can be assignedfor exclusive use by an nPartition. Each nPartition runs its own instance of an operating system.

centralmanagementserver

See CMS.

chassis log Term used for event log on cell-based servers based on the PA-8700 processor.CLI Command line interface. An operating system shell for direct entry of commands by the user.

See also GUI.clipping In HP Global Workload Manager (gWLM), the limiting of a policy's resource request.

Types of clipping include:• Compartment clipping A workload's compartment is already at its maximum size (for

example, as set using a vPars command), but policy requests are trying to increase it beyondits configured maximum.

• Policy clipping A workload is receiving the maximum CPU allocation allowed basedon its policy; however, the request would be higher if the policy maximum were higher.

• Priority clipping There are not enough resources for the compartments at lower prioritylevels because resources are required for compartments at higher priority levels. Note thatresources are allocated for fixed policies, OwnBorrow policies, and policy minimums beforegWLM considers priorities.

CLM Cell local memory. Cell memory that is not interleaved. A page of cell local memory comes froma single cell. Cell local memory provides better performance than interleaved memory forprocesses running on the cores in the cell that contains the memory.

178 Glossary

See also interleaved memory.cluster 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.CMS Central management server. A system in the management domain that executes theHPSystems

InsightManager (HP SIM) software. All central operations within HP SIM are initiated from thissystem.

codeword The mechanism used with HP Instant Capacity (iCAP) versions B.06.x and later for adjustingavailable usage rights for system components (RTU codewords), for applying an amount oftemporary capacity to a system (TiCAP codewords), and for applying Sharing Rights to aGiCAPsystem to enable the creation of one or more groups (GiCAP codewords). Codewords arepurchased from HP and retrieved from the Utility Pricing Solutions Portal.See also RTU, usage rights.

command lineinterface

See CLI.

compartment An nPartition, virtual partition, virtual machine, or resource partitionwhose resources are allocatedby HP Global Workload Manager (gWLM).Multiple compartments are grouped to form a shared resource domain (SRD). The compartmentsall share the resources of the SRD. A compartment can be in only one SRD. Each compartmentholds aworkload. gWLM manages each workload's resource allocation by adjusting the resourceallocation of its compartment.

compartmentconsumption

The amount of a resource being consumed by all of the cores in a compartment. For example, ifthe processes in a compartment consume a total of two cores, the compartment consumptionof cores is two.

CompartmentMax

The maximum amount of a resource that a compartment can have. This value is the maximumresource allocation allowed by the underlying compartment. However, HP Global WorkloadManager (gWLM) might reduce this number at times because an SRD has a large number ofcompartments and each compartment must receive a minimum portion of the resources.See also Max Size.

CompartmentMin

The minimum amount of a resource that a compartment can have. This value is the minimumresource allocation required by the underlying compartment.See also Min Size.

compartmentutilization

The compartment consumption of a given resource as a percentage of the compartment's size. Forexample, if a compartment's consumption is two cores and its size is four cores, the compartmentutilization of cores is 50%.

complex A complex includes one or more cabinets that are cabled together and all of the hardwareresources that they contain. A complex has a single Service Processor.See also server, system.

complex profile The data structure managed by the Service Processor that represents the configuration of acomplex. The complex profile consists of the Stable Complex Configuration Data for the entirecomplex, and Partition Configuration Data for each nPartition in the complex.

compute cabinet Any cabinet containing cells. An I/O expansion cabinet is not a compute cabinet.conditionalpolicy A policy for managing a workload's compartment. This type of policy indicates a policy that HP

Global Workload Manager (gWLM) should use when a certain condition occurs.configuredprocessor

A processor that has been configured at the boot console handler (BCH or EFI) and is nowavailable for activation by the HP Instant Capacity (iCAP) software.

constraints Resource allocation restrictions imposed by either the customer (for example,workloadplacementrestrictions), or the HP Virtual Server Environment (for example, a cell cannot be subdividedacross an nPartition).See also policy.

convergence rate Indicator of workload sensitivity to changes in CPU allocation. Larger values produce largerchanges in the allocation, causing faster convergence on the policy's target; smaller valuesproduce slower convergence on the target. The default rate is 1.0.

179

core The actual data-processing engine within a processor. A single processor might have multiplecores, and a core might support multiple execution threads.See also processor.

core cell Each nPartition has one cell that system firmware selects at boot time to be the core cell. This cellmust be attached to an I/O chassis that contains core I/O. The core cell has the following uniquecharacteristics:• It must be a base cell.• The nPartition's console uses the partition console interface in the core I/O that is attached to

the core cell.• The nPartition's real-time clock is located in the core cell's processor dependent hardware.• The core cell is used by system firmware as a master copy for some internal data structures.• The Service Processor passes event logs to the core cell.• The monarch processor is on the core cell.• Compatibility of other cells in the nPartition is checked against the core cell.

core I/O I/O hardware that provides the base set of I/O functions required by every nPartition. Core I/Oincludes the partition console interface and 10/100 BaseT network interface.

core-cell choices Information in each nPartition's Partition Configuration Data that guides system firmware inchoosing the nPartition's core cell. Cells that are identified as core cell choices are tried first (inthe order specified) before system firmware applies its default core-cell selection algorithm.

cross-bar chip See XBC.current virtualpartition

The virtual partition that is running the vPars command currently being executed.See also local nPartition.

custom policy A policy for managing the resources available to a workload. This type of policy allows you toprovide your own metric. HP Global Workload Manager (gWLM) then manages an associatedworkload, adjusting the resource allocation as needed based on the value of the metric. Youupdate values for the metric using the gwlmsend command on the operating system instancewhere the workload is running.

deactivate cell The process of changing an active cell into an inactive cell. A cell becomes inactive when a shutdownfor reconfiguration operation is performed on its nPartition. A cell can also be deactivated bysetting its use-on-next-boot value to No and then performing a reboot for reconfiguration operationon the nPartition.

deactivate I/Ochassis

The process of changing an active I/O chassis into an inactive I/O chassis. An I/O chassis isdeactivated when the cell to which it is attached is deactivated.

deactivated core See inactive core.deconfiguredprocessor

A processor that has not yet been configured at the boot console handler (BCH or EFI). HPInstant Capacity (iCAP) and HP Pay per use software cannot activate a processor that isdeconfigured.

demand profile A set of resource-demand readings made at regular intervals for some period of time. Thedemand profile of aworkload, system, or complex is used when doing capacity planning. Demandprofiles can be based on historical data or computed as part of a forecast.

deploy In HP Systems Insight Manager (HP SIM), to implement one or more components such assoftware, drivers, or licenses, rendering them under control of HP SIM.

1.

2. InHPGlobalWorkloadManager (gWLM), to enable gWLM control of a shared resource domain(SRD).Deploying an SRD in managed mode allows gWLM to control resource allocation withinthe SRD. For example, in an SRD that is based on processor sets (PSETs) for compartments,deploying an SRD in managed mode allows gWLM to migrate processing cores betweenPSETs.When deploying an SRD in advisory mode, gWLM reports only what the allocation wouldbe without actually affecting resource allocations on a system.

See also undeploy.DIMM Dual In-line Memory Module. A standard memory-chip format.

180 Glossary

discovery In system management applications, the process of finding and identifying network objects.In HP Systems Insight Manager (HP SIM), discovery finds and identifies all the HP systems

1.

within a specified network. In HP Application Discovery, discovery finds and identifies allrunning and installed applications within a specified network.

2. HP Global Workload Manager (gWLM) can examine systems that you specify andautomatically identify the nPartitions, virtual partitions, virtual machines, processor sets(PSETs), and Fair-Share Scheduler (FSS) groups that are present on those systems. gWLMcan also identify iCAP and TiCAP as well as GiCAP groups. You then form SRDs usingthe discovered items.

discovery ratio As used by HP Application Discovery, this is a comparison of matched to unmatched processesrunning on a host. The ratio is the percentage of processes that can be matched to discoveredapplications.

Dual In-lineMemory Module

See DIMM.

dynamicprocessormigration

A vPars feature that allows you to add unbound cores to a virtual partition, or remove them froma virtual partition, while the virtual partition is running.

echelon A set of DIMMs installed as a single failure group. If any DIMM in the echelon fails or isdeconfigured, the entire echelon is deconfigured. Some HP server models use an echelon sizeof 4 DIMMs; others use an echelon size of 2 DIMMs.

Effective Max See Max Size.Effective Min See Min Size.EFI Extensible Firmware Interface. The system firmware user interface that allows boot-related

configuration changes and operations on Itanium®-based systems. For example, EFI providesways to specify boot options and list boot devices. The boot console handler (BCH) provides asimilar function for PA-RISC systems.

entitlement The amount of a system resource (for example, processor) that is guaranteed to a virtualmachine. The actual allocation of resources to the virtual machine may be greater or less

1.

than its entitlement depending on the virtual machine's demand for processor resourcesand the overall system processor load.

2. The amount of a resource that is set aside for a compartment.

event log Information about system events made available from the source of the event to other parts ofa server complex. An event log indicates what event has occurred, when and where it happened,and its severity (the alert level). Event logs do not rely on normal I/O operation.The term “chassis log” was used in place of “event log” on earlier server models.

expansion cabinet A specially configured compute cabinet that can be connected to a base cabinet to create adual-compute-cabinet complex. The expansion cabinet is always the right-hand cabinet in thepair (when viewed from the front) and contains a hub to connect it to the Service Processor inthe base cabinet.See also cabinet, IOX.

ExtensibleFirmwareInterface

See EFI.

fabric Within a complex, the interconnect composed of cross-bar chips (XBC) and cells.failover The operation that takes place when a primary service (network, storage, or CPU) fails, and

the application continues operation on a secondary unit.failure usage flag A per-cell flag in the Partition Configuration Data that specifies how the cell will be reactivated

and whether it will participate in memory interleave after a hardware failure.Fair-ShareScheduler group

See FSS group.

field replaceableunit

See FRU.

181

fixed policy AnHPGlobalWorkloadManager (gWLM) policy for managing aworkload's compartment. This typeof policy allocates a workload's compartment a fixed (constant) amount of CPU resources.Fixed policies do not have a settable priority. gWLM satisfies compartment minimums first; next,it satisfies both fixed policies and policy minimums; finally, it satisfies other policy types.

floater processor See unbound core.floating cell A cell in an nPartition that cannot participate in interleaved memory (all of the cell's memory is

used as cell local memory). The operating system also does not place vital data in memory onfloating cells.A floating cell can be selected for cell online activation and cell online deactivation.If a floating cell is chosen to be an nPartition's core cell, firmware automatically sets it to be acell type of Base when the nPartition is booted.See also base cell.

forecast A prediction of system utilizations and workload demand profiles for some future time.forecast datarange

A time interval specifying the set of historical data to use for generating a forecast.

forecast model A combination of a forecast data range and a set of annual projected growth rates that are used toestimate future utilization.

free cell A cell that is not assigned to an nPartition. This applies to any cell location, regardless of whetherthe slot exists or is populated.

FRU Field replaceable unit. Hardware that can be replaced by a field engineer. This includes allcomponents that are hot-pluggable or hot-swappable. It also includes many components that mustbe powered off to be replaced.

FRU ID Data that provides identification information about a field replaceable unit (FRU), such as thepart number, serial number, revision and test history. The FRU ID typically is stored in anEEPROM that is located on the FRU.

FSS group Fair-Share Scheduler group. A group of processes that has its CPU allocation managed by theHP-UX FSS. FSS groups allow you to allocate fractions of cores, rather than only whole cores,to the processes in the group.

GiCAP HP Global Instant Capacity. Software that enables you to move usage rights for Instant Capacitycomponents within a group of servers. The GiCAP Group Manager page can be launched froman icon on the HP Virtualization Manager's Visualization view.See also iCAP, iCAP component, TiCAP.

Global InstantCapacity

See GiCAP.

Global WorkloadManager

See gWLM.

GNI Global noninterleaved memory, another name for cell local memory (CLM).guest See virtual machine.guest OS The operating system that is running on a virtual machine.GUI 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.

gWLM HP Global Workload Manager. The HP VSE Management Software application that allows youto centrally define resource-sharing policies that you can use across multiple HP servers. Thesepolicies increase system utilization and facilitate controlled sharing of system resources. gWLM'smonitoring abilities provide both real-time and historical monitoring of the resource allocation.

HA High availability. The ability of a server or partition to continue operating despite the failureof one or more components. High availability requires redundant resources, such as CPUresources and memory, in specific combinations.

182 Glossary

The high-availability status of a device group is usually indicated by the following notation.

The device group can experience a device failureand still function normally.

N+

The device group has just enough good devices tofunction normally. Subsequent failure of a devicein the group can cause the cabinet to shut down.

N

The device group does not have enough goodcomponents to function normally. If a cabinet isrunning and goes into an N- cooling state, then thecabinet is automatically shut down. If a cabinet hasan N- power state, then devices in the group cannotbe powered on. This means that if the cabinet isrunning, it continues running, but no additionaldevices can be powered on. If the cabinet is off andcomes up in the N- power state, then none of itsdevices can be powered on.

N-

hard reset A hard reset, like thereset (RS) command available at the Service Processorprompt, immediatelystops the operating system and all applications, without forcing a crash dump.See also TOC.

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

high availability See HA.host A system or partition that is running an instance of an operating system.1.

2. The physical machine that is the HP Integrity Virtual Machines VM Host for one or morevirtual machines.

host name The name of a system or partition that is running an OS instance.host OS The operating system that is running on the host machine.hot-pluggable A hardware component that can be added to or removed from a cabinet, with software

intervention, while the cabinet remains operational. Examples are PCI I/O cards, cells, and I/Ochassis.These components are hot-pluggable only to the extent that operating system and hardwaresupport is present. For example, with the initial HP-UX 11i release, a cell is hot-pluggablebecause it can be physically installed into a "hot" cabinet and powered on, but that version ofthe OS does not support cell online activation.See also hot-swappable, FRU.

hot-swappable A hardware component that can be added to or removed from a cabinet, without softwareintervention, while the cabinet remains operational. Examples are bulk power supplies, cabinetblowers, and I/O fans. These items are hot-swappable if their removal does not create an N-1HA situation. For example, if a cabinet's power status is N+1, then any one of the bulk powersupplies can be removed without affecting the operation of the cabinet.See also hot-pluggable, FRU.

HP SIM HP Systems Insight Manager (HP SIM). The platform and framework on which the HP VSEManagement Software products are deployed.

hyper-threading Intel®Hyper-Threading Technology. The ability of certain processors to create a second virtualcore that allows additional efficiencies of processing. This is not a true multi-core processor, butit adds performance benefits. True multi-core processors typically deliver much greaterperformance than equivalent hyper-threading technology.

I/O bay The physical location in a cabinet where an I/O support structure is located.

183

I/O chassis A PCI or PCI-X card cage and associated backplane that contains a system bus adapter and oneor more local bus adapters. An I/O chassis may or may not be physically removable.

I/O chassisenclosure

See ICE.

I/O DependentCode

See IODC.

I/O expansioncabinet

See IOX.

I/O fans The fans that are used to cool an I/O chassis. Found in both I/O expansion cabinets and computecabinets. I/O fans are distinct from cabinet blowers.

I/O supportstructure

A physical structure in cabinets where one or more I/O chassis are located. In some cabinets theI/O support structure is referred to as an I/O support tray, in other cabinets as an I/O chassisenclosure (ICE). The different names reflect the different physical characteristics of the supportstructures. The I/O support structure is removable in some cabinet types (for example, I/Oexpansion cabinet) and is not removable in others.

iCAP HP Instant Capacity. The HP Utility Pricing Solutions product that allows you to purchase andinstall 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 pricebecause the usage rights are not included. These Instant Capacity components are inactive butinstalled and ready for use. When extra capacity is needed, you pay the remainder of the regularprice for the usage rights to activate the components. If the regular price for the component isreduced by the time the usage rights are purchased, the remainder price is proportionallyreduced, providing additional savings.Earlier versions of iCAP were referred to as Instant Capacity on Demand, or iCOD.See also GiCAP, TiCAP.

iCAP component Also called a component without usage rights, an HP Instant Capacity (iCAP) component is acore, cell board, or memory that is physically installed in an iCAP system but is not authorizedfor use. Before it can be used, a right to use (RTU) must be purchased and a codeword must beapplied to the system.

iCAP core Also referred to as a core without usage rights, a core that is physically installed in anHP InstantCapacity (iCAP) system but does not have usage rights and is not activated. After obtainingusage rights, iCAP cores can be turned on by the iCAP software or during installation. Coreswith usage rights are activated with theicapmodify command (or thevparmodify commandin a virtual partition) while HP-UX is running.

ICE I/O chassis enclosure. A specific type of I/O bay on some models of HP Superdome server. AnICE provides mechanical and electrical support for up to two 12-slot I/O chassis.

iCOD See iCAP.iCODcomponent See iCAP component.iCOD core See iCAP core.iLO HP Integrated Lights-Out. An application that allows you to remotely configure, update, and

operate server blades and standalone systems.inactive cell A cell that is not available for use by software running on an nPartition. This term is usually

used to describe a cell that has the following status (though any cell that is not active is bydefinition inactive):• The slot is present and is populated.• Power is enabled.• Boot-is-blocked.• The cell is assigned to an nPartition.See also active cell.

inactive core A core that either has not yet been activated or that has been turned off by the HP InstantCapacity iCAP software and returned to the pool of inactive cores. These cores are availablefor activation. New HP-UX processes are not assigned to a deactivated core, and all processes

184 Glossary

running on the deactivated core are migrated to other cores (with the exception that interrupthandlers might not be migrated from deactivated cores).See also activated core, iCAP core.

inactive I/Ochassis

An I/O chassis that is not available for use by the software that is running on an nPartition. AnI/O chassis is inactive when it is attached to an inactive cell.See also active I/O chassis.

inactive logicalserver

A logical server that contains metadata but is not currently bound to a specific physical serveror system. Inactive logical servers that have never been activated might or might not be boundto storage.See also active logical server, logical server.

inactivenPartition

An nPartition in which all of its cells are inactive.See also active nPartition.

initial systemloader

See ISL.

InsightOrchestration

HP Insight Orchestration. A utility for integrating logical serverplanning, design, and provisioninginto a unified system.

Insight PowerManager

See IPM.

Insight Recovery HP Insight Recovery. An application for configuring primary and recovery sites and storagerecovery groups for logical servers.

Instant Capacity See iCAP.Instant Capacitycomponent

See iCAP component.

Instant Capacitycore

See iCAP core.

IntegratedLights-Out

See iLO.

Integrity VirtualMachines

See Integrity VM.

Integrity VirtualMachinesManager

See VM Manager.

Integrity VM HP Integrity Virtual Machines. A soft partitioning virtualization product that allows you toinstall and run multiple systems (virtual machines) on the same physical host system (Integrityserver or nPartition). The Integrity server or nPartition acts as a VMHost for the virtual machines(also referred to as guests). The virtual machines share a single set of physical hardwareresources, yet each virtual machine is a complete environment in itself and runs its own instanceof an operating system (referred to as a guest OS).See also virtual machine, VM Host.

IntelligentPlatformManagementInterface

See IPMI.

interleavedmemory

Memory that can be interleaved across more than one cell. Interleaved memory presents a singlelogical memory address range that is mapped to different physical memory ranges acrossmultiple cells.See also CLM.

invalid data InHPCapacity Advisor, data that could potentially skew reporting results and lead to inaccurateor misleading conclusions when capacity planning. Examples of events that Capacity Advisorcan 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

185

See also missing data, valid data.IODC I/O Dependent Code. IODC provides a uniform, architected mechanism to obtain platform

information. IODC is composed of two parts. The first part is a set of up to 16 bytes that identifyand characterize hardware modules. The second part is a set of entry points that provide astandard procedural interface for performing module-type dependent operations such as bootdevice, keyboard, and display device initialization and Input/Output routines. IODC isdocumented in the PA-RISC 1.1 I/O Firmware Architecture Reference Specification. NOTE:this link will take you outside of this help system. Your browser must have access to the internetto follow this link.

IOX I/O expansion cabinet. A cabinet that contains I/O devices (card cages) but no cells.See also expansion cabinet.

IPM HP Insight Power Manager. An integrated power monitoring and management applicationthat provides centralized control of server power consumption and thermal output at the levelof the data center. It extends the capacity of data centers by enabling you to reduce the amountof power and cooling required for ProLiant and Integrity servers.

IPMI Intelligent Platform Management Interface. A set of standards for remote multiplatform servermanagement. IPMI uses intelligent platform management hardware and a message-basedinterface.

ISL Initial system loader. This program implements the portion of the bootstrap process that isindependent of the operating system (OS). The ISL is loaded and executed after self-test andinitialization have completed successfully. It provides an interface to select an OS or load apredefined default OS.

Itanium®-basedsystems

Systems built on any version of the Intel® Itanium® architecture.

LBA Local bus adapter. A device that connects the system bus adapter (SBA) to an I/O bus, such asPCI. Multiple LBAs are connected to a single SBA.

leaf node An object at the lowest level of a graphical tree view. Leaf nodes have no child nodes.legacy addressing The storage device addressing model that uses the device special file (DSF) path as defined in

HP-UX 11i v2 and earlier versions. In contrast to the agile addressing model introduced withHP-UX 11i v3, the legacy device special file (DSF) is bound to a specific logical unit path (lunpath)to a storage device. For this reason, a device with multiple paths is represented by several legacyDSFs. If the physical storage device is reconnected to a host through a different host-basedadapter (HBA) or a different target port, the address represented by the DSF is affected, requiringreconfiguration of applications, volume managers, or file systems. Likewise, if additionallunpaths are offered to a given logical unit (through the addition of a new SCSI controller ornew SCSI target paths), an equal number of additional DSFs are required to address them.See also agile addressing.

local bus adapter See LBA.local nPartition Used in a context where an nPartition command is being executed, the local nPartition is the

nPartition that is running the command.See also current virtual partition, remote nPartition.

localnet A vswitch created by default when HP Integrity Virtual Machines is installed on a VM Host. Thelocal network created by this vswitch can be used for communications among guests but notfor communication between the VM Host and any guest or between any external system anda VM guest.

logical server A feature provided by HP Virtualization Manager, a logical server is a set of configuration andmetadata 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 bemodified. This feature allows you to populate an enclosure, load balance servers, and evacuateservers in case of disaster; it allows you to provision resources only when needed and increaseutilization of limited compute resources.See also active logical server, inactive logical server.

LTU License to use. One of the three main components ofHPGlobalWorkloadManager (gWLM):CMS,agents, and LTU for each agent. The CMS allows you to control and monitor gWLM. The agents

186 Glossary

run on the systems where you are managing workloads. You install an LTU on each systemthat runs an agent in order to continue full agent functionality beyond the initial trial period.

managed mode SRDmanaged mode letsHPGlobalWorkloadManager (gWLM) automatically adjust the resourceallocations for your compartments.See also advisory mode, deploy.

managed resource A resource that can be allocated and controlled byHPVirtualizationManager. Managed resourcesinclude: cores, memory, disks, and I/O bandwidth.

managed system A server or other system that can be managed by HP Systems Insight Manager (HP SIM) from aCMS . A managed system can be managed by more than one CMS.

managedworkload

A workload that is managed by HP Global Workload Manager (gWLM).

managementdomain

A CMS and its managed systems.

ManagementProcessor

See Service Processor.

master I/Obackplane

The main backplane in a complex into which you plug an I/O chassis.

max 15-min Maximum 15-minute sustained: data given in the Utilization Metric Summary screen of the HPCapacity Advisor Profile Viewer, the highest value in the selected time interval that was sustainedfor at least 15 minutes.

Max Size The maximum amount of CPU resources, measured in cores, that anHPGlobalWorkloadManager(gWLM) policy requests for its associated workloads.In graphs, the Effective Max is shown. This value is the smaller of Max Size and CompartmentMax (the maximum amount of a resource that a compartment can have).

measured value The current value of a metric being used in a policy.memory echelon See echelon.metric A specific measurement that defines a performance characteristic.metric viewselection

In HP Capacity Advisor, a combination of the statistical model (such as peak or average) usedto calculate the metric and whether it is to be presented as a percentage or an absolute value.

mezzanine card A printed circuit board that plugs directly into another plug-in card. Adapter cards are alsoavailable that enable a mezzanine card to plug into the larger slot of the target bus.

migratingprocessing cores

The process of activating and deactivating cores across partitions for load balancing.

Min Size The minimum amount of CPU resources, measured in cores, that anHPGlobalWorkloadManager(gWLM) policy requests for its associated workloads.In graphs, the Effective Min is shown. This value is the larger of Min Size and CompartmentMin(the minimum amount of a resource that a compartment can have).

missing data Data that was not collected by HP Capacity Advisor, perhaps because a monitored system wasdown during data collection. Such data is not used in analysis, though it may be shown in theProfile Viewer.See also invalid data, valid data.

monarchprocessor

Also known as the boot processor, this is the main controlling core of the operating system. Thiscore is designated asCPU 0. The LPMC monitor does not deactivate or replace a failing monarchprocessor.

monitoredworkload

A workload that can be monitored by HPVirtualizationManager but has no policy associated withit. Monitored workloads are not managed by HP Global Workload Manager (gWLM).

multithreading The ability of an application and operating system to allow parallel computing by dividingprocessing between multiple processors or cores.

node See system.

187

nPartition 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 instanceof an operating system or is further divided into virtual partitions.nPartitions can be used as compartments managed by HP Global Workload Manager (gWLM) aslong as several requirements are met. Refer to the gWLM online help for a description ofnPartition requirements.See also virtual partition.

nPartitionConfigurationPrivilege

A feature available on newer cell-based servers that can be used to restrict the ability of privilegedusers on one nPartition from affecting other nPartitions. This feature is configured by using thePARPERM command at the Service Processor command interface. For more information, refer tothe Partition Manager Configuration Privilege topic.

nPartitionProvider

The WBEM services provider for nPartition information about cell-based servers.

nPartition server See cell-based server.OA HP Onboard Administrator. An application for local and remote management of HPBladeSystem

c-Class server blade enclosures.OnboardAdministrator

See OA.

online activation The ability to activate a deactivated core using HP Instant Capacity (iCAP) software while HP-UXis running. No reboot is required. This is done with the icapmodify command or, in a virtualpartition, with the vparmodify command. Online activation is the default behavior of iCAP.

OS Operating system.OwnBorrowpolicy

AnHPGlobalWorkloadManager (gWLM) policy for managing aworkload's compartment. This typeof policy allows you to set the following values:• The minimum amount of CPU resources that a compartment should ever have.• The maximum amount of CPU resources that a compartment should ever have.• The amount of CPU resources that a compartment owns.A compartment is allocated the resources it owns when they are needed. When a workload isnot busy, gWLM may lend its CPU resources to other workloads that are busy, as long as thecompartment minimum is maintained. When it becomes busy, a compartment will immediatelyre-acquire any resources that were loaned to other compartments. A compartment with a busyworkload can borrow CPU resources up to its allowed maximum, if resources are availablefrom other compartments.You can assign a weight to an OwnBorrow policy in order to prioritize resource allocation.

owned size Resources, measured in cores, that are allocated to a compartment when they are required. Acompartment can lend its owned resources to other compartments.

PACI Partition console interface. Provides console access for an nPartition. PACI is a part of core I/O.package A package groups application services (individual HP-UX processes) together.

See also Serviceguard package.parked workload 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 waspreviously associated with a system may have historical data associated with it fromHPCapacityAdvisor or HP Global Workload Manager (gWLM). As with any workload, the historical data willbe 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.

188 Glossary

partition A subset of server hardware that includes core, memory, and I/O resources on which anoperating system (OS) can be run. This type of partitioning allows a single server to runan OS independently in each partition with isolation from other partitions.

1.

2. A resource partition, made up of either a Fair-Share Scheduler (FSS) group or a processor set,that runs within a single OS. This type of partitioning controls resource allocations withinan OS.

See also nPartition, virtual partition.PartitionConfigurationData

See PCD.

partition consoleinterface

See PACI.

partitiondatabase See vPars partition database.PartitionManager The HP VSE Management Software application that manages and configures nPartitions on

cell-based servers.partition name An ASCII string that identifies a partition using a name that is meaningful to the system

administrator. The allowed characters and maximum length are different for nPartition andvirtual partition names. For nPartitions, partition names do not have to be unique, because thepartition number provides a unique partition identifier. Virtual partition names must be uniquewithin the nPartition or server that is running vPars.

partition number An integer that uniquely identifies an individual nPartition within a complex. Each nPartitionis assigned a unique number from 0 to the maximum number of partitions supported minus1.

partition stablestore

See PCD.

Pay per use See PPU.PCD Partition configuration data. The part of the complex profile that provides partition-specific

information. The PCD can be thought of as an array with one element per possible partitionindexed by partition number. PCD provides the functionality of stable store in traditional systems.

PCI Peripheral component interconnect. A standard for the connection between a processor andattached devices.

PCI-X Peripheral component interconnect extended. An enhanced version of PCI.PDC Processor-dependent code.

See also system firmware.PDH Processor-dependent hardware. The ROM, nonvolatile memory, and PDH controller interface

for a cell board. The PDH comprises a controller and its external Flash EPROM, battery-backedSRAM, real-time clock, and external registers.

peak The highest utilization value in the selected time interval.percent residentmemory

A measure of the fractional amount of physical memory in use by a particular application fora period of time.

peripheralcomponentinterconnect

See PCI.

policy A collection of rules and settings that controlworkload resources managed byHPGlobalWorkloadManager (gWLM). For example, a policy can indicate the minimum and maximum amount ofCPU resources allowed for a workload, and a target to be achieved.A single policy can be associated with multiple workloads.

policy pass/fail A policy can either succeed or fail to meet its target. A failure can be due to clipping of the policy'sresource requests.

PPU HP Pay per use. A software product that is a part of the HP Utility Pricing Solutions program.PPU implements a pricing model in which you are charged for the usage of cores. You acquire

189

a specific hardware platform and number of cores, and are charged for usage of the cores basedon system demand.

PPU agent The HP Pay per use (PPU) software component that provides information to the utility meter.On HP-UX systems this component is implemented as a daemon named (ppud). On Microsoft®Windows® systems, this component is implemented as a service.

priority The importance of a policy, relative to other policies, as defined by the user. The highest priorityis 1. Lower priorities are 2, 3, and so on through 1000.HP Global Workload Manager (gWLM) uses priorities to determine the order in which to allocateresources when the sum of the resource requests exceeds the resources available in the SRD.Fixed policies do not have priorities; their resources are allocated before priorities are evaluated.If all resource requests have been met and resources are still available, the weight assigned toeach policy, not its priority, determines how the excess resources are distributed.

PRM Process Resource Manager. An HP product used to dynamically divide resource utilizationamong different applications and users. PRM controls the amount of resources that processesuse during peak system load.

process Execution of a program or image file. Execution can represent a user or operating system process.process map A script residing in /etc/opt/vse/scripts that enables you to create output process IDs

(PIDs).Process ResourceManager

See PRM.

processor The hardware component that plugs into a processor socket. Processors can contain more thanone core.See also core.

processormodule 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.

processor set See PSET.processor-dependent hardware

See PDH.Profile Viewer Provides a visual display of historical utilization data collected by HP Capacity Advisor, along

with additional information that you have provided. The Profile Viewer enables you to examinedifferent time intervals and different categories of data.

provision A function that makes a component operational. Provisioning might include installing,upgrading, loading, and configuring a software or hardware component. Provisioning a serverincludes loading the appropriate software (operating system and applications), customizingand configuring the system, and starting the server and its newly-loaded software. This makesthe system ready for operation.

pruned When a file is reduced to a set number of lines based on criteria determined by the system(application) or the software user.

PSET Processor set. A collection of processors grouped together for exclusive access by applicationsassigned to that processor set. Each application runs only on processors in its assigned processorset.

Quality of Service A combination of qualitative and quantitative factors such as up time, response time, andavailable bandwidth, that collectively to describe how well a system performs. The Quality ofService is frequently embodied in a Service Level Agreement or in a set of Service LevelObjectives between or among organizations.

ready forreconfiguration

The state of a cell location that permits its nPartition assignment to be changed. All cell locationswhose nPartition assignment is changed must be at the ready for reconfiguration state beforethe Service Processor can push out the new Stable Complex Configuration Data. A cell location isin the ready for reconfiguration state when any of the following conditions applies.

190 Glossary

• The cell location is not present.• No cell is present at that location.• The cell is not powered on.• The cell is inactive (usually, a cell that is powered on with the boot-is-blocked attribute set).

reboot forreconfiguration

The process of rebooting an nPartition in such a way that all active cells in the nPartition arereset with boot-is-blocked (BIB) set. When the operating system running on the nPartition hasfinished shutting down, these cells begin their power-on self-test sequence, then wait for BIBto be cleared by the Service Processor. When all of the cells in the nPartition complete self-test,the Service Processor boots the nPartition.On the HP-UX operating system, reboot for reconfiguration is performed using the reboot orshutdown command with the-R option. The-H option should not be used, so that the nPartitionwill automatically reboot after reconfiguration.On Linux and Microsoft Windows operating systems, the normal reboot process performsreboot for reconfiguration.See also shutdown for reconfiguration.

relativeheadroom The percentage by which the demand on a resource can grow before the utilization limits set forthe resource are exceeded.For example, in the case of a system running several workloads, the relative headroom for anyone workload is the percentage by which one workload can grow without exceeding theutilization limits set for itself and without causing any of the other workloads on the system toexceed their limits.See also headroom.

remote nPartition In a context where an nPartition command is being executed, a remote nPartition is any nPartitionother than the one that is running the command.See also local nPartition.

request The amount of a system resource that a policy asks HP Global Workload Manager (gWLM) to giveto the policy's compartment. Each policy makes a request, then gWLM arbitrates the requestsfrom all of the policies to determine what resources will be allocated to the compartments.Requests may be restricted by policy settings and by the compartment definition. For example,if a Min Size value is less than a Compartment Min value, the Compartment Min value is usedinstead of the Min Size value.See also custom policy, fixed policy, OwnBorrow policy, utilization policy.

resource partition A subset of the resources available to an operating system instance, isolated for use by specificprocesses. A resource partition has its own process scheduler. CPU resources in the partitionmay be allocated using Fair-Share Scheduler groups or processor sets. Policies for controlling theallocation of resources to the partition can be set using HP Global Workload Manager (gWLM).

resource pool A set of systems to consider as the possible location of a workload.See also shared resource domain (SRD), boundaries within which resources can be allocated andbalanced across workloads.

ResPar See resource partition.Right To Use See RTU.right-to-access See RTA.RTA Right-to-access. The initial fee that you pay to enter the HP Instant Capacity (iCAP) program

and physically acquire possession of an iCAP component (memory, cell board, or core) that isunauthorized for use and inactive.

RTU Right To Use. A type of codeword used to activate and adjust available usage rights forHP InstantCapacity (iCAP) components (memory, cell board, or core). An RTU codeword can be applied onlyto the system for which it was purchased, and the application of an RTU codeword adjusts thenumber of component-specific usage rights on the system.See also codeword, usage rights.

runningapplication

An application that is continually or intermittently active and able to consume resources.

191

SBA System bus adapter. The chip in an I/O chassis that provides a connection between the cellcontroller on a cell and the set of local bus adapters in the I/O chassis.

SBA link A link from an I/O chassis to its system bus adapter.SCCD Stable Complex Configuration Data. The portion of the complex profile that contains attributes

of the complex (serial number, model string, and so on) and the assignment of cells to nPartitions.scenario A possible configuration of systems and workloads under consideration when doing capacity

planning.See also what-if scenario.

securecompartment

A boundary that provides security to a compartment by controlling access and system capabilitiesavailable to a set of processes.

secure resourcepartition

A resource partition that is integrated with HP-UX Security Containment.

server Physical server: Hardware that can run one or more operating systems, including apartitionable complex. Also, hardware that can run an instance of the vPars monitor. Server

1.

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 typesof server hardware: standalone servers and cell-based servers.

2. 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 underIntegrity VM.

3. HP Systems Insight Manager (HP SIM) uses the term “server” for any standalone server,nPartition, or virtual server that is running an instance of an operating system or an instanceof the vPars monitor.

See also system.server blades Thin, modular, self-contained computer servers, containing one or more microprocessors and

memory. Server blades are designed for high density and eliminate many components such aspower cords and network cables that are present in traditional rack-mount systems. HPBladeSystem supports technologies such as hot-plug hard-drives, multiple I/O cards,multi-function network interconnects, and Integrated Lights Out.See also BladeSystem enclosure.

Service Processor An independent support processor for HP servers that support nPartitions. The Service Processorprovides a menu of service-level commands, plus commands to reset and reboot nPartitionsand configure various parameters.The Service Processor in HP servers is sometimes called the Management Processor (MP) orthe Guardian Service Processor (GSP).

Serviceguard Specialized software for protecting mission-critical applications from a wide variety of hardwareand software failures. With Serviceguard, multiple servers (nodes) and/or server partitions areorganized into an enterprise cluster that delivers highly available application services toLAN-attached clients. HP Serviceguard monitors the health of each node and rapidly respondsto failures in a way that minimizes or eliminates application downtime.

Serviceguardcluster

A Serviceguard cluster is a networked grouping of HP 9000 or HP Integrity servers (host systemsknown as nodes) having sufficient redundancy of software and hardware that a single pointof failure will not significantly disrupt service.

Serviceguardpackage

Packages are the means by which Serviceguard starts and halts configured applications. Apackage is a collection of services, disk volumes and IP addresses that are managed byServiceguard to ensure they are available.

Serviceguardworkload

A monitored workload associated with a Serviceguard cluster and a particular package within thecluster. The workload (and the utilization data reported) follows the package it is associatedwith as it moves between the nodes of the cluster.

shared resourcedomain

See SRD.

192 Glossary

shutdown forreconfiguration

The process of shutting down an nPartition in such a way that all active cells in the nPartitionare reset with the boot-is-blocked (BIB) attribute. When the operating system that is running onthe nPartition has finished shutting down, these cells begin their power-on self-test sequenceand then wait for BIB to be cleared by the Service Processor. As a result, the nPartition becomesinactive.On the HP-UX operating system, shutdown for reconfiguration is performed using theshutdownor reboot commands with the -R and -H (or -RH) options.On the Linux operating system the command shutdown -h now performs shutdown forreconfiguration.On Microsoft Windows operating systems the shutdown /h command performs shutdownfor reconfiguration.See also reboot for reconfiguration.

SIM See HP SIM.simulation See capacity-planning simulation.simulationinterval

ForHPCapacity Advisor, a combination of a duration and a starting or ending point that definesthe period of time over which the simulation is to be done.

Single SystemManagement

See SSM.

size The amount of a resource that a compartment actually has.When working with CPU resources, size can differ from the actual allocation when HP GlobalWorkload Manager (gWLM) is deployed in advisory mode.

SRD Shared resource domain. A collection of compartments that share system resources managed byHP Global Workload Manager (gWLM). The compartments can be nPartitions, virtual partitions,virtual machines, processor sets (PSETs), or Fair-Share Scheduler (FSS) groups.A server containing nPartitions can be an SRD as long as nPartition requirements are met. Theserequirements are detailed in the gWLM Getting the Most out of gWLM topic.A server or an nPartition divided into virtual partitions can be an SRD for its virtual partitioncompartments. A VM Host can be an SRD to its virtual machines. Similarly, a server, annPartition, or a virtual partition containing PSETs can be an SRD for its PSET compartments.Finally, a server, an nPartition, or a virtual partition containing FSS groups can be an SRD forits FSS-group compartments.A complex with nPartitions can hold multiple SRDs. For example, if the complex is dividedinto nPartitions named Par1 and Par2, Par1's compartments could be virtual partitions, whilePar2's compartments are PSETs.See also deploy, advisory mode, managed mode.

SRD states An SRD can be in one of two states: deployed or undeployed. When deployed, an SRD can be inone of two modes: advisory mode or managed mode.

SSL Secure Sockets Layer. Protocol for validating identity and for creating an encrypted connectionbetween a server and a Web browser.

SSM Single System Management. A method of viewing and managing systems without the use ofa central management server (CMS). In the SSM model, administrators log in to the system to bemanaged and use the management tools directly on that system. This is different than the CMSbased management model, in which administrators log in to the CMS, and use managementtools on the CMS that contact the managed systems.

Stable ComplexConfigurationData

See SCCD.

standalone server Hardware that can run one or more operating systems but does not support dividing hardwareresources into nPartitions.

193

system A server, nPartition, virtual partition, or virtual machine that is running an instance of anoperating system.

1.

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, orWBEM) must be presenton the system. Examples of systems include servers, workstations, desktops, portables,routers, switches, hubs, and gateways.

See also server.system busadapter

See SBA.

system firmware Code that provides a uniform, architected context in which to perform processor-dependentoperations. Also called processor-dependent code (PDC) on PA-RISC systems. On Itanium®-basedsystems, system firmware includes PAL (Processor Abstraction Layer), SAL (System AbstractionLayer), EFI (Extensible Firmware Interface), and ACPI (Advanced Configuration and PowerInterface).

systemheadroom See headroom.Systems InsightManager

See HP SIM.

target The value that drives a policy, thereby influencing its resource requests to HP Global WorkloadManager (gWLM).For a target CPU utilization, gWLM attempts to keep a workload's CPU utilization below thetarget by adding CPU resources when the workload is using too much of its current CPUallocation. For example, assume a workload has a utilization policy with a target of 80% and asize of 5 cores. If the workload is consuming 4.5 cores, its utilization percentage is 4.5/5, or 90%.The gWLM software attempts to allocate additional CPU resources to the workload to meetthe target. A size of 6 cores results in a utilization percentage of 4.5/6, or 75%, thus meeting thetarget.A target can also be a value that the workload must not exceed, such as x transactions persecond. In this case, adding resources helps the workload maintain the number of transactions.Alternatively, a target can be a scaling factor.

template An HP-supplied or user-defined set of rules, properties, or metadata that describe an object ina computing network.In HPApplication Discovery, templates specify the data collection and matching rules to be usedto define and discover an application.

TemporaryInstant Capacity

See TiCAP.

TiCAP Temporary Instant Capacity. An HP product that enables customers to purchase prepaid coreactivation rights, for a specified (temporary) period of time. Temporary capacity is sold in 30processing-day increments. TiCAP was formerly known as “TiCOD”.See also GiCAP, iCAP.

TiCOD See TiCAP.TOC Transfer of control. A soft reset, which terminates the operating system and all applications,

and causes a crash dump to be saved to the dump device, if one is defined.See also hard reset.

transfer of control See TOC.unassign a cell Modify the Stable Complex Configuration Data so that a cell is no longer assigned to an nPartition

and is instead a free cell. A cell must be inactive before it can be unassigned. If the cell was notinactive before the unassignment operation, then the operation will not be complete until thenPartition has performed a reboot for reconfiguration.

unassigned cell See free cell.unbound core 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.”

194 Glossary

The distinction between bound and unbound cores does not apply to vPars version 4.0 or later.See also bound core.

undeploy In HP Systems Insight Manager (HP SIM), to remove one or more components from controlof HP SIM.

1.

2. In HP Global Workload Manager (gWLM), to change the shared resource domain (SRD) stateto disable gWLM's management of system resources in a specified SRD.If an SRD is inmanagedmode, undeploying stops the migration of system resources betweencompartments in the SRD. If the SRD is in advisory mode, undeploying stops gWLM fromproviding information about the requests that would have been made.

See also deploy.unmatchedprocess

A found process that does not correlate to existing application templates or packages that HPApplication Discovery is using for discovery and monitoring. Unmatched processes may includecustom and third-party applications.

usage database The repository that contains HP Pay per use system-utilization information. You can access thisinformation through the Utility Pricing Solutions Portal.

usage rights The commodity used byHP Instant Capacity (iCAP) to activate or deactivate system components(memory, cell boards, and cores). Usage rights for a component are adjusted by the applicationof a Right to Use (RTU) codeword, and they can be shared between systems through the useof GiCAP.See also codeword, RTU.

use-on-next-boot A per-cell flag in the Partition Configuration Data. This flag is used by system firmware during theprocess of booting an nPartition. If a cell is assigned to an nPartition and this flag is not set, thenthe cell is not activated the next time that the nPartition is booted.

utilitiessubsystem

The utilities subsystem provides the platform management infrastructure for a complex. Itsfeatures and services are accessible through the Service Processoruser interface,PartitionManager,and other platform management tools. It includes the following components:• The Service Processor (one per complex).• The processor-dependent hardware controller module on the cell boards.• The partition console interface (PACI) module on the core I/O boards.

utility meter The software and hardware device that receives HP Pay per use system-utilization informationfrom the Pay per use software. The utility meter is initially installed and configured by an HPservice representative.

Utility PricingSolutions Portal

An HP web site that gives customers an interface to view theirHPPay per use system-utilizationinformation and to obtain codewords for HP Instant Capacity (iCAP) systems.

utilization limits The limits set on the usage of system resources such as CPU, memory, or network I/O by anapplication. Utilization limits are expressed as a percent of the system capacity and the amountof time an application is allowed to exceed this limit. The time that a limit is exceeded can beexpressed as a percentage of time or as a maximum duration of time.See also max 15-min.

utilization policy A policy for managing a workload's compartment. This type of policy has a target based onutilization. With a CPU utilization policy, HP Global Workload Manager (gWLM) attempts tokeep a workload's CPU utilization below the target by adding CPU resources when the workloadis using too much of its current allocation. For example, assume a workload has a utilizationpolicy with a target of 80% and an allocation of 5 cores. If the workload is consuming 4.5 cores,its utilization percentage is 4.5/5, or 90%. The gWLM software attempts to allocate additionalCPU resources to the workload to meet the target. An allocation of 6 cores would result in autilization percentage of 4.5/6, or 75%, thus meeting the target.You can set a priority for utilization policies to ensure that gWLM attempts to satisfy the policiesin a particular order. The highest priority is 1; lower priorities are 2, 3, and so on, through 1000.You can also set a weight for a utilization policy.

UtilizationProvider

The WBEM services provider for real-time utilization data from managed systems.

195

valid data In HP Capacity Advisor, data that meaningfully contributes to the user's ability to understandactual past resource usage and that provides reliable information for accurately forecastingcurrent and future capacity needs.See also invalid data, missing data.

VC HP Virtual Connect. A set of interconnect modules and embedded software for HP BladeSystemc-Class enclosures that simplifies the setup and administration of server connections, therebyenabling administrators to add, replace, and recover server resources dynamically.See also VCEM.

VC domain A logical grouping of servers, visible by expanding a VC domain compartment from the HPVirtualization Manager's Visualization view. Currently, only HP BladeSystem c-Class serversappear in a VC domain.See also VC domain group.

VCdomaingroup A logical collection of Virtual Connect domains. From the HP Virtualization Manager'sVisualization view, you can view a VC domain group and expand it to show VC domains.

VC manager See VCEM.VCEM Virtual Connect Enterprise Manager. A management tool for defining a server connection

profile for each server bay. This profile establishes the Media Access Control (MAC) addressesfor all Network Interface Controllers (NICs), the World Wide Names (WWNs) for all host busadapters (HBAs), and the SAN boot parameters. If the server blade in the server bay is replaced,the configuration and connection profile stays constant. You can launch VCEM from the HPVirtualization Manager for a VC domain group, VC domain, or BladeSystem.

vCPU Virtual CPU. A single-core virtual processor in a virtual machine.See also core, processor.

VFP Virtual Front Panel. An interface provided by the Service Processor that displays the boot/runstate of nPartitions.

Virtual Connect See VC.Virtual Connectdomain

See VC domain.

Virtual Connectdomain group

See VC domain group.

Virtual ConnectEnterpriseManager

See VCEM.

virtual console A vPars feature that allows a single hardware console port to be used as the console formultiple virtual partitions.

1.

2. The virtualized console of a virtual machine that emulates the functionality of theManagement Processor interface for HP Integrity servers. Each virtual machine has itsown virtual console, from which the virtual machine can be powered on or off and bootedor shut down, and from which the guest operating system can be selected.

virtual CPU See vCPU.virtual device 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 VMHost.

Virtual FrontPanel

See VFP.

virtual machine A software entity provided by HP Integrity Virtual Machines, VMware ESX, or Microsoft VirtualServer. This technology allows a single server or (with Integrity Virtual machines) nPartition toact as a VMHost for multiple individual virtual machines, each running its own instance of anoperating system (referred to as a guest OS). Virtual machines are managed systems in the HPVirtual Server Environment (VSE).

virtual machineapplication

The executable program on the VM Host that manifests the individual virtual machine. Itcommunicates with the loadable drivers based on information in the guest-specific configurationfile, and it instantiates the virtual machine.

196 Glossary

virtual machineconsole

See virtual console.

virtual machinehost

See VM Host.

virtual partition A software partition of a server, or of a single nPartition, where each virtual partition can run itsown instance of an operating system. A virtual partition cannot span an nPartition boundary.See also nPartition, virtual machine.

virtual partitionscan

A scan of the system to determine the allocation and status of processor (core), memory, andI/O resources in a vPars-enabled system.

virtual partitionserver

A specific layer, analogous to but not an operating system, that supports virtual partitions.

virtual switch See vswitch.VirtualizationManager

HP Virtualization Manager. Provides hierarchical visualization of servers and workloads, withseamless access to the management tools of the VSE technologies.

VM See virtual machine.VMHost A server running software such as HP Integrity Virtual Machines, VMware ESX, or Microsoft

Virtual Server, that provides multiple virtual machines, each running its own instance of anoperating system.

VMManager HP Integrity Virtual Machines Manager. The HP VSE Management Software application thatallows you to manage and configure Integrity VM.

vPars An HP software product that provides virtual partitions.See also virtual machine.

vPars monitor The program that manages the assignment of resources to virtual partitions in a vPars-enabledsystem. To enable virtual partitions, the vPars monitor must be booted in place of a normalHP-UX kernel. Each virtual partition running under the monitor then boots its own HP-UXkernel.The vPars monitor reads and updates the vPars partition database, boots virtual partitions andtheir kernels, and emulates certain firmware calls.See also VM Host.

vPars partitiondatabase

The database that contains the configuration information for all the virtual partitions on avPars-enabled system.

vswitch Virtual switch. Refers to both a dynamically loadable kernel module (DLKM) and a user-modecomponent implementing a virtual network switch. The virtualized network interface cards(NICs) for guest machines are attached to the virtual switches.

warmup The period of time during which HP Application Discovery is comparing discovered processesto the known installations of software and to template definitions of applications.

way An older term that describes the number of processors in a symmetric multiprocessing (SMP)system (for example, “4-way”.) This term is replaced by processor. (For example, “4-processor”.)

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

Web-BasedEnterpriseManagement

See WBEM.

weight A value that you assign to a policy to determine how system resources are allocated byHPGlobalWorkload Manager (gWLM) in the following scenarios:• gWLM addresses priority levels from highest to lowest, allocating system resources to all

requests at a given priority level before considering lower-priority requests. If requestscannot be satisfied at some priority level, the remaining resources are distributed so that

197

the total resource allocation for each workload is as close as possible to the proportion ofits weight relative to the sum of all the weights.

• If gWLM has satisfied all system resource requests at all priorities and there are resourcesstill to be allocated, gWLM will distribute the remaining resources by weight.

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 anactual configuration change.

wizard A sequential series of pages that transforms a complex task into simple steps and guides youthough them. The wizard makes sure that you provide all of the required information and donot skip any steps. At each step, a page is presented that allows you to specify the informationneeded to complete that step. Help is available at each step and you always have the option ofgoing back to continue the wizard from a previous step.

workload The collection of processes in a standalone server, nPartition compartment, virtual partitioncompartment, or virtual machine compartment. HP Global Workload Manager (gWLM) extendsthis concept to include processor set (PSET) compartments and Fair-Share Scheduler (FSS) groupcompartments. gWLM enables you to monitor and manage workloads by automatically adjustingthe resource allocations of compartments based on policies.See also managed workload, monitored workload, Serviceguard workload.

XBC Cross-bar chip. On some server models each cell in a compute cabinet plugs into a cross-barbackplane by means of a pair of connectors, thereby forming a connection between the cellcontroller on the cell board and a cross-bar chip. On other server models, cell controllers aredirectly connected to other cell controllers, thereby eliminating the need for a cross-bar backplane.

198 Glossary

Index

Aabsolute interval, 87agent

collection, 17agentless data collection for Capacity Advisor

adding additional systems to file, 77removing systems, 78viewing configuration, 78

all VSE resources, 20assigned license

defined, 81automated consolidation to VMs

expected results, 65possible anomalies, 66

automated load balancingexpected results for servers or VM hosts, 66possible anomalies, 66

automated solutions, 40automated workload stacking

expected results, 67possible anomalies, 67

automatic data collection, 20available license

defined, 81

Bback button

problem with use in Capacity Advisor, 18backup, 18business interval, 41

Ccalculator, 27Capacity Advisor scenario

modify parameters, 100parameters, modify, 100

capacity planning goals, 27capagentlesscfg, 77, 78capcollect command, 126capreport

command, 127command file, 127

changesundo previous in Capacity Advisor, 103

clocksetting on HP-UX, 164setting on Linux, 164setting on Windows, 164unsynchronized, 164

cluster, 15cluster node

Serviceguard, 125collection agent, 17collection schedule

create, 72

commandcapcollect, 126hpvmmigrate, 126

command filecapreport, 127

comments to HP, 13comparison report

selecting details in Capacity Advisor, 91selecting scenario targets in Capacity Advisor, 91

complexviewing in Profile Viewer, 87

configuration, 15consolidate workloads, 46conversion

data, 21conversion table

percent of time limit to minutes, hours, 32cooling multiplier, 44copy

Capacity Advisor scenario, 102Copy Profile

parameters for workload in Capacity Advisor scenario,37

CPU capacity, 28CPU Core Utilization, 37CPU Multiplier, 34

default value, 34CPU multiplier

examples, 34CPU Speed, 37CPU utilization

as measured for virtual machines, 27CPU Virtualization Overhead %, 38

default value, 38examples, 38

CPU Workload Multiplier, 36, 37default value, 36examples, 36

credentials, 17

Ddata

accuracy, 27as measured for CPU capacity, 28as measured for disk I/O, 28as measured for memory, 28as measured for network I/O, 28as measured for power usage, 28backup, 18Capacity Advisor

update, 76collect for Capacity Advisor, 70

first time, 72collect in Serviceguard cluster, 126collect nightly automatically, 72collection, 20

199

considerations in measuring resource utilization, 28conversion, 21export, 127gap, 126gather for Capacity Advisor, 70

first time, 72historical, 21import, 127import OVPA information into Capacity Advisor, 19import PMP information into Capacity Advisor, 19incorrect, 164invalid, 31invalidating, 127loss, 18measurement interval, 29missing, 31, 126old, 164OVPA, 127peaks, 19PMP, 127restore, 18utilization, 15

data collectionagentless, 21automatic, 20differences between HP PMP and Utilization Provider,

22menu options, 71precedence for agentless versus Utilization Provider,

22server resources, 28switching from agentless to Utilization Provider, 22timing options, 71Utilization Provider, 21

data collection, Capacity Advisor impact on systemperformance, 71

data collection, importing OVPA information, 71data collection, importing PMP information, 71data collection, records not current, 84data discrepancy

in Capacity Advisor, 83data handling

for virtual machines, 27data import

view results for HP OVPA system, 82view results for HP PMP system, 83

data rangechanging in Profile Viewer, 87

data-collection infrastructure, 20delay in refresh of system and workload configuration

dataassociated issues in Capacity Advisor, 166

disk I/Oedit capacity in Capacity Advisor, 107

disk I/O capacity, 28Disk I/O Utilization, 37Disk I/O Workload Multiplier, 37

default value, 37example, 37

dynamic memory, and data collection in CapacityAdvisor, 84

EEdit Scenario

accessing Capacity Advisor Profile Viewer, 86error

absence of licensing, 163absence of user authorization, 164difference in workload associations to systems, 166licensing before discovery is complete, 164message explanation, 167no data for managed node in Capacity Advisor, 84out of memory in Java heap, 165system configuration, 163time synchronization, 164

error analysis, 42error, connecting to systems, 163example

server consolidation, planning, 47existing server

consolidate programs with Capacity Advisor, 47exported data, 127

Ffeedback to HP, 13first data collection, 72fixed interval, 87forecast model

editing in Profile Viewer, 87precedence table, 43

Ggap

data, 126goals

capacity planning, 27graphs and reports

Capacity Advisor operations overview, 84growth rate

forecasting, 36

Hheadroom

defined, 29stars defined, 29

historical data, 21historical utilization, 19host name, 125HP Insight Capacity Advisor Consolidation software

finding licensed servers, 81limitations, 81

HP Performance Management Packdata collection, 22

HP SIMdocumentation, 11

HP Smart Solver, 40HP Virtual Machine

200 Index

calculating Hypervisor Memory Overhead for CapacityAdvisor, 39

hpvmmigrate command, 126Hypervisor Memory Overhead

calculating for HP Virtual Machine, 39calculating for Microsoft Hyper-V, 40calculating for Microsoft Virtual Server, 39calculating for VMware ESX, 39default setting, 39definition, 39examples, 39where used, 39

Iimported data, 127incorrect data, 164infrastructure

data collection, 20installation, 17Integrity VM, 125interval

business, 41sampling, 29

Llicense

requirements, 17License Manager

assigning HP Insight Capacity Advisor Consolidationsoftware licenses, 81

usage permissions, 81viewing HP Insight Capacity Advisor Consolidation

software licenses, 81license, checking status, 84licenses, assigning HP Insight Capacity Advisor

Consolidation software to a server, 81load balance

automated solutions, 40lost data, 18

Mmachine

virtual, 126managed node, importance of time and time zone settings

for data collection accuracy in Capacity Advisor, 84member

SG, 125memory

modeling, 25memory capacity, 28memory data, 22Memory Multiplier, 35

default value, 35examples, 35

Memory Utilization, 37Memory Workload Multiplier, 36, 37

default value, 36example, 36

memory, dynamic, 84

menu optionsfor HP Insight Capacity Advisor Consolidation

software server data, 81metric view

modify for Capacity Advisor, 100Microsoft Hyper-V

calculating Hypervisor Memory Overhead for CapacityAdvisor, 40

Microsoft Virtual Servercalculating Hypervisor Memory Overhead for Capacity

Advisor, 39missing data, 126modeling

predictive, 15multiplier, used in Capacity Advisor

cooling, 44CPU Multiplier, 34CPU Virtualization Overhead %, 38Disk I/O Workload Multiplier, 37Hypervisor Memory Overhead, 39memory , 35Memory Workload Multiplier, 36Network I/O Workload Multiplier, 36

multipliersmodifying applied what-if actions, 103

Nnetwork data, 22network I/O

edit capacity in Capacity Advisor, 107network I/O capacity, 28Network I/O Utilization, 37Network I/O Workload Multiplier, 36, 37

default value, 36example, 36

new applicationplanning, 62

new workloadplanning, 62

OOffset Hours, 37old data, 164old dates, 164operations

gather Capacity Advisor data, 70generate Capacity Advisor report, 88overview

Capacity Advisor graphs and reports, 84Capacity Advisor scenarios, 98Capacity Advisor systems, 105Capacity Advisor workloads, 109

overview of for Capacity Advisor, 69out-of-memory, 165overview

Capacity Advisor procedures, 69OVPA data, 21

importing, 82OVPA, importing data into Capacity Advisor, 71

201

Ppeak

data, 19peak width, 19peaks and sums, 29percent of time

limit example, 33percentage of allocation

defined, 33planning

server consolidation, 46with Capacity Advisor, 45

PMP, importing data into Capacity Advisor, 71power consumption, 28power settings

editing in Profile Viewer, 87procedure

accessing Capacity Advisor, 70accessing Capacity Advisor Profile Viewer from HP

SIM Optimize menu, 86accessing Capacity Advisor Profile Viewer from

Virtualization Manager Visualization tab, 86accessing Capacity Advisor Profile Viewer when

editing a scenario, 86accessing the profile viewer, 86adding existing systems to a scenario, 106adding systems to the agentless data collection file, 77altering the automated nightly data collection, 72automated consolidation to VMs

choose destination systems, 119choose systems to consolidate, 119set level of effort, 120view solutions, 120

automated load balance of serversview solutions, 122

automated load balance of VM hostschoose VM hosts to load-balance, 121view solutions, 122

automated load-balance of serversdefine constraints, 122

automated load-balance of VM hostsdefine constraints, 122set level of effort, 122

automated workload stackingchoose workloads to stack, 123open scenario, 123set level of effort, 124stack workloads, 123view solutions, 124

automating finding solution for workload stacking,122

automating finding solutions for system consolidationto VMs, 119

calculating a virtualization consolidation ratio, 92calculating idle/max power consumption values for

C-class HP blades, 118calculating idle/max power consumption values for

P-class HP blades, 117change the data range in Capacity Advisor, 101

changing the data interval by setting the data range inCapacity Advisor, 100

changing the meter bar calculation in a scenario, 102changing the Meter Style of a scenario display, 100controlling Capacity Advisor data presentation, 100copying a scenario, 102creating a collection schedule, 74creating a planning scenario, 98creating a scenario, 98creating a workload in a scenario, 109creatinga system in a scenario, 105deleting workloads from a scenario, 113determining idle/max power consumption values for

non-blade servers, 117edit Capacity Advisor workload, 110editing a scenario, 100editing a system in a scenario, 106editing a workload in a scenario, 111editing I/O capacity in Capacity Advisor scenarios, 107gathering data the first time, 72importing HP OVPA data, 82importing HP PMP data, 83listing systems currently in agentless configuration

file, 78modifying a collection schedule, 75move Capacity Advisor workload, 111moving a virtual machine, 108moving a workload in a scenario, 112parking workloads in a scenario, 113removing a collection schedule, 75removing one or more systems from agentless data

collection file, 79removing systems from a scenario, 108renaming a scenario, 103sutomating finding solution to load balance servers or

VM hosts, 121to delete a scenario, 104updating collected data on all systems, 76updating the data the Profile Viewer displays, 77upgrade Utilization Provider, 18

procedurescollect Capacity Advisor data, 70edit I/O capacity in Capacity Advisor scenarios, 107

processorhyperthreaded, 15multicore, 15

Profile Vieweraccess in Capacity Advisor, 85example, 23panning, 88showing valid or invalid allocation, 88showing valid or invalid data, 88

Qquality of service, 27

Rreinstallation, 18report

202 Index

generate in Capacity Advisor, 88selecting details for scenario comparison, 91selecting scenario targets for comparison, 91setting date range in scenario comparison, 91

reportsand Capacity Advisor licensing, 89

reports and graphsCapacity Advisor operations overview, 84

requirementdisk space, 17licensing, 17

resourceinsufficient on VM host for consolidation, 121

Ssampling

interval, 29scenario

Capacity Advisor operations overview, 98copy in Capacity Advisor, 102creating for Capacity Advisor, 98editing in Capacity Advisor, 100remove from Capacity Advisor, 104rename in Capacity Advisor, 103

server consolidationplanning, 46

serversviewing all in HP SIM screens, 82

servicequality of, 27

service and support, 13service level agreement, 27service level objective

sizing for, 25Serviceguard

cluster node, 125data collection, 21workload, 125

SG Member, 125show

Capacity Advisor changes, 103simulation interval

modify for Capacity Advisor, 100simulator, 27star

meaning in Capacity Advisor, 29Static Profile

creating a baseline workload, 38parameters for workload in Capacity Advisor scenario,

37sums and peaks, 29sustained minutes

limit example, 33system

add existing to Capacity Advisor scenario, 106create for Capacity Advisor, 105edit for Capacity Advisor, 106overprovisioning error, 32remove some from VSE agentless data collection, 79

system consolidationautomated solutions, 40

System tabaccessing Capacity Advisor Profile Viewer, 86

systemsCapacity Advisor operations overview, 105remove all from VSE agentless data collection, 79remove from Capacity Advisor, 108

Ttask result

HP PMP data import to Capacity Advisor, 83task results

HP OVPA data import to Capacity Advisor, 82time

unsynchronized, 164time zone

impact on data collection, 31trend

determination in Capacity Advisor, 41troubleshooting, 163, 167typographic conventions, 11

Uunassigned license

defined, 81user tasks

planningadd/move processor, 60move/add processor, 60new application, 62new workload, 62server consolidation, 46

utilizationaggregate, 15data, 15historical, 15, 19

utilization limitdefaults, 31defined, 31for percentage of time, 32for sustained time, 32global, 33precedence table, 34scenario workload, 33seenario-wide, 33specifying one or more, 32workload, 33

utilization limitsediting in Profile Viewer, 87

utilization monitor, 27Utilization Provider, 21

data collection, 21, 22start daemon, 164stop daemon, 164upgrade on a managed node, 18

UUID, 126

203

Vvalid data

factors affecting reporting in Capacity Advisor, 41selecting appropriate business interval, 41setting threshold values for Capacity Advisor reports,

42view

Capacity Advisor changes, 103Capacity Advisor profile viewer, 85

virtual machine, 19, 126move in Capacity Advisor, 108

VM Guestviewing in Profile Viewer, 87

VMware ESXcalculating Hypervisor Memory Overhead for Capacity

Advisor, 39VSE

documentation, 11VSE resources

all, 20vseinitconfig, 18

command, 127

Wwarning

explanation of messages, 168WBEM, 170

provider, 19what-if actions

disable applied actions, 103modify multipliers, 103re-enable applied actions, 103undo applied actions, 103viewing, 103

workload, 15, 19analysis, 23Capacity Advisor operations overview, 109considerations when moving in Capacity Advisor, 111Copy Profile, 37create for Capacity Advisor, 109demand profile, 23edit for Capacity Advisor, 110move in Capacity Advisor, 111multipliers for adjusting to changes in server

configuration, 35park in Capacity Advisor, 113remove from Capacity Advisor, 113Serviceguard, 125Static Profile, 37

workload stackingautomated solutions, 40

Workload tabaccessing Capacity Advisor Profile Viewer, 86

204 Index