Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
VSE Management Software Release Notes Version A.03.00.01 > Chapter 5 Application-Specific Release Notes

Capacity Advisor Release Notes

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

See also “Using Serviceguard to Migrate Integrity VM Guests Workaround Invalidates Data” in Chapter 2 “Documentation Corrections and Additions”.

Double Counting Utilization Data

It is possible to have the same process included in two monitored workloads. When this happens, the resources used by that process are added into both workloads, resulting in double counting.

This double counting can be seen in the profile viewer in Capacity Advisor. The profile graph for a system is different when viewed outside a scenario than when viewed inside the scenario. Data shown outside a scenario is the actual system total, whereas system data shown inside a scenario is the sum of the workloads. Double counting causes the trace inside a scenario to be higher.

Workaround

Be careful when you define monitored workloads.

  • When defining workloads by user, be sure not to include a given user in two different workloads.

  • When defining workloads by executable, be sure each executable is specified in only one workload.

  • Mixing user and executable workloads requires extra care.

Impossible Data Is Not Filtered

Occasionally erroneous data readings occur. Capacity Advisor filters out utilization data that is below 0, but it does not filter out all data that is unlikely or impossibly high. These stray readings have little effect on averages or on 90th-percentile values computed from the data, but they can significantly alter peak values.

Workaround

  • Double check the data before making any decisions based on peak data.

  • Capacity Advisor has a mechanism to mark a data reading as invalid. Marking data invalid is useful for eliminating these bad readings. Whenever you spot a reading that is obviously wrong, mark it as invalid.

Warnings During Initial Data Collection from a Virtual Machine

Depending on the order the data is collected, the capcollect command can generate the following warning the first time data is collected from a virtual machine:

Warning: unable to determine the 
    HPVM Host for Guest "guestname"
Valid CPU utilization data is
    not available.

Workaround

Collect the data again. This should clear up the error.

HP SIM Displays Data in Multiple Time Zones

Some times in HP SIM are displayed in the time zone used by the browser, whereas other times are in the time zone of the CMS. Capacity Advisor times are always in the time zone of the CMS.

Workaround

Be aware of the source of times displayed in HP SIM and whether they are in the time zone of the browser or of the CMS.

Default Report Begin and End Times Are Not Always Midnight

The start and end times of the default report are not always midnight to midnight, as might be expected.

Workaround

Review the start and end times when creating a Capacity Advisor utilization report.

Saving Capacity Advisor Report ZIP Files Can Make Internet Explorer Nonresponsive

If you are using Internet Explorer and you attempt to save a report ZIP file, two File Download popup windows can appear, and older versions of Internet Explorer can become nonresponsive. In other situations, the report creation screen becomes nonresponsive after saving the ZIP file.

Workaround

Two File-Download Windows

To recover, select a window that at least partially conceals the first popup window. This enables the second popup window. After responding to the second popup, Internet Explorer should be responsive.

Nonresponsive Report Creation Screen

To recover, click the Save Report link and cancel the operation when prompted by Internet Explorer about saving the file. The report creation screen should become responsive after the save operation is cancelled.

Scenarios Can Model Unsupported Configurations

Capacity Advisor cannot always verify that the scenarios defined can actually be implemented on the systems being analyzed. For example, running a 4-way virtual machine on a 2-way VM Host is not supported, but it is possible to construct such a scenario.

Workaround

Use Capacity Advisor to model real-life systems and situations. Make sure that your scenarios are based on supported configurations.

Possible Data Loss When Virtual Machines are Shut Down and Restarted

Obtaining accurate utilization data for a virtual machine requires information from the Utilization Provider on both the virtual machine and its VM Host. The CPU utilization values for a virtual machine gathered from the Utilization Provider running within the virtual machine does not accurately reflect the true CPU utilization, but does provide the Memory, Network, and Disk utilization values. To obtain accurate CPU utilization values for a virtual machine, the values from the corresponding FSS partition on the VM Host are used. This requires matching the virtual machine with its FSS partition on the VM Host. If a virtual machine is shut down and restarted, it might run in a different FSS partition after restarting than it did before. When capcollect runs, it notes the current assignment of virtual machines to FSS partitions and uses that assignment to associate CPU utilization data from an FSS partition with the correct virtual machine. To prevent misleading CPU utilization values being recorded for a virtual machine, if a virtual machine has been restarted during a particular 24-hour period from midnight (in the GMT time zone) to the following midnight, all CPU utilization values in that period preceding the restart are not stored.

Workaround

To minimize the gaps in utilization data for virtual machines, collect Capacity Advisor data on a virtual machine just before it is restarted. The next periodic collection from the virtual machine fills in the data after the restart and preserves the data collected before the restart.

OVPA Network Data Differs from Capacity Advisor Network Data

Sometimes the network data imported from Openview Performance Agent (OVPA, also know as the Measureware Agent) does not match the data collected by Capacity Advisor. The differences seem related to the use of auto port aggregation.

Workaround

Interpret data collected from OVPA differently from data collected by Capacity Advisor. OVPA data is the sum of BYNETIF_IN_BYTE_RATE and BYNETIF_OUT_BYTE_RATE for all LAN ports on the system. Capacity Advisor collects the total bytes in and out of each LAN port on the system but uses pstat(2) for the data.

Capcollect Can Fail After Updating the CMS from 11.11 to 11.23

One of the steps of the update process sometimes leaves some .save files in the directories reserved for Java plugins. When this happens the Java virtual machine tries to load these empty files and fails. This, in turn, causes the capcollect, vselicense, and capprofile commands to fail, even when the version of Java is correct, with a message similar to the following:

 # capcollect
 /opt/vse/lbin//capcollect[33]: could: The specified number is not 
 valid for this command.
 /opt/vse/lbin//capcollect[33]: could: The specified number is not 
 valid for this command.
 Unable to find an installed Java JRE meeting the minimum version 
 requirements.
 This command requires a minimum version of 1.4.2.07
 Unable to find a java executable.

Workaround

Remove the unneeded .save file. The file most likely to be on your system is /opt/java1.4/jre/lib/PA_RISC2.0/plugins/.save. You may need to remove a .save file from a directory matching /opt/java*/jre/lib/*/plugins.

The OTHER Workload is Deleted When the Last Workload on a Cluster Member is Deleted,

When the first monitored workload is created on a system a workload named OTHER is automatically created. When the last monitored workload is removed from a system the OTHER workload is automatically deleted. This is true for all systems, but on a Serviceguard cluster the workloads can automatically move to follow the cluster's packages. When the last monitored workload moves off of a cluster member, the OTHER workload is deleted.

When the OTHER workload is automatically deleted, its utilization history is deleted as well.

If a cluster member is shut down for any reason, all packages move off of the system to other cluster members. In turn, the CMS sees this and moves all the workloads associated with packages off of the system. Unless at least one workload is not associated with a package, the OTHER workload is deleted from the system that was shut down.

When a cluster member is restored, a new OTHER workload is created with no utilization data. This makes planning using the OTHER workload difficult.

Workaround

If you want to use the OTHER workload in your planning, create a workload associated with an executable that is not expected to consume any resources, such as /bin/true, on each member of the cluster. As long as this workload is not associated with a package, it never moves off of the system and the OTHER workload is not deleted.

Capacity Advisor Report Wizard GUI and capreport Command Use Different Default Values to Generate Reports

Capacity Advisor Report Wizard GUI and capreport command use different default values to generate reports for specific parameters. The following table shows the default values for each case:

Table 5-1 Report Default Values

CharacteristicGUICapreport
Report TypeUtilization and TrendUtilization
Include report detailsNOYES
ScaleAbsoluteAbsolute and Percentile
Aspect Ratio16:94:3
Valid Threshold95%50%
Error AnalysisDisabledEnabled

 

Workaround

The user should change the parameter to the desired value. The user can generate a custom report using a configuration file with the capreport command. For more information about how to use an input command file, see capreport(4).

The capreport Command Default Time Interval for Different Workloads Varies Within a Report

When two or more targets are used with data available in an overlapped date interval, the capreport command calculates a wrong report interval.

IMPORTANT: The report content is right, the report date interval is wrong. This problem occurs only when no date interval is provided in the command line options.

Workaround

When using the capreport command to generate a report on more than one workload, always use the command-line options -b and -e to explicitly set the interval for the report.

Null Message Included in capreport Output

If the options on the capreport command line cannot be parsed, the message Null can be returned.

Workaround

If you see the message Null in output from the capreport command, review the command-line syntax.

Report Help Link Does Not Work in capreport HTML Reports

In the HTML report generated by the capreport command, clicking the “?” help-link has no effect.

Workaround

Generate a report in the Report Wizard GUI (from the HP SIM menu, select Optimize->Capacity Advisor->Create Utilization Reports...) and look at the help page provided in this report. The same help page is included with any report so you do not need to generate the same report.

capovpaextract Command Dependencies

This command uses the remote execution facilities provided by HP SIM and, therefore, requires the configuration of SSH authentication within HP SIM for the specified managed node.

Capacity Advisor supports the following versions of OVPA :

Operating SystemOVPA Version
HP-UXC.03.35 or later
SolarisC.03.75 or later
LinuxC.04.00 or later

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2006-2007 Hewlett-Packard Development Company, L.P.