To determine if you have a system that is reporting the incorrect
clock speed, see Identifying the UP Clock Error. If your system is affected, follow the procedures on this page
to deal with the problem.
Correcting the UP clock error requires a minimum of two steps:
install corrected software
remove or correct any data that has already been collected
IMPORTANT: The procedures described on this page assume that you are familiar
with the how to install patches on HP-UX and with command-line operations.
A basic understanding of Capacity Advisor is also necessary. The -i and -r options of the capprofile command can only be used by HP-SIM users who are authorized to use
the Capacity Advisor toolbox on the CMS.
Install the Correct Software
The first step is to stop collecting data with the wrong clock
speed.
Install patch PHKL_33752 on all the Dual Core Intel® Itanium® processor systems being monitored with Capacity
Advisor.
Update to the latest version of the HP-UX Utilization
Provider on all the Dual Core Intel Itanium systems being monitored
with Capacity Advisor.
After installing the correct software, the clock speed shown
in the scenario editor will continue to be wrong until the next time
utilization data is collected with capprofile. The historical data
will be wrong until corrected using the steps below.
After new utilization data is collected, the old CPU data will
be displayed incorrectly. You will see a jump in the CPU utilization
and allocation graph at the time of the previous collection. The new
data will be correct and the old data will be incorrect.
Figure 1 A step in the CPU Allocation Graph
Once you have confirmed that the correct clock speed is being
reported, you need to correct previously collected data.
Removing or Correcting Previously Collected Data
The second step in correcting this problem is to clean up the
incorrect data stored by Capacity Advisor. There are two general approaches
to this:
Remove the old data (appropriate if you have 30 days
or less of collected data or if you don't care about data older than
30 days). See “Removing the Old Data” to remove old data.
The easiest way to correct the data is to simply delete it.
You can delete the entire trace of data with the -r option of the capprofile command. When you next
run capcollect it will collect up to 30 days’
data and it will be stored with the correct clock speed. If you have
30 days or less of data, or if you do not consider it necessary to
keep the older data, this is sufficient.
Example 1 Commands run on the CMS to delete incorrect data and collect
correct data
$ capprofile emerald.fc.hp.com
Name Available History
emerald.fc.hp.com 04/15/07 06:00 pm - 05/18/07 12:05 am
$ capprofile -r emerald.fc.hp.com
$ capcollect emerald.fc.hp.com
All utilization data collected for "emerald.fc.hp.com".
$ capprofile emerald.fc.hp.com
Name Available History
emerald.fc.hp.com 04/17/07 06:00 pm - 05/18/07 10:05 am
$
Correcting the Clock Speed on Previously Collected Data
Deleting the profile data and recollecting results in up to
30 days of correct data. If you have a profile with much more than
30 days already stored you may want to correct the data. The steps
are:
Each step is described in the following procedure.
Procedure 1 To Correct the Clock Speed on Previously Collected Data
Identify the
range of incorrect data.
There are a few cases to consider in identifying the range of
incorrect data.
If the new dual core system has the same hostname as an older system that it replaced, then the
older data – the data from the prior host – may have been
collected correctly.
If the HP-UX Utilization Provider was updated a few
days, or weeks, ago the most recent data will be correct.
Differentiating between the conditions requires inspection
of the data.
Use the capprofile command
to list the utilization data for the system and look for large changes
in the allocated CPU values to identify the exact beginning and ending
time of the incorrect data.
Determine the ratio of
the two clocks on your system.
Determining the ratio of the two clocks on your system requires
knowing the clock speed Capacity Advisor used before updating the
Utilization Provider, and knowing the clock speed after the update.
This ratio can be found by:
Use capprofile to list the utilization
data for the system. Make sure to get some data from before and after
updating the utilization provider.
Divide the number of allocated CPUs after the update (an
integer) by the number of allocated CPUs before the update. The ratio
will be near 4.
Export the data with the incorrect
values.
Exporting the incorrect data is done with the capprofile command. Use the -x option to export data, use
the -b option to specify the beginning of incorrect
data, and use the -e option to specify the end of
the incorrect data.
Correct the incorrect values.
Correcting the incorrect clock speed can be done by editing
clock speed on the third line of the exported file. Whatever clock
speed it reported in your file, take it and multiply it by the ratio
of the clock speeds.
Example 2 Data Exported Before Collecting Data with Updated Utilization
Provider
If you exported your data before collecting any data with the
updated Utilization Provider then you will be replacing the incorrect
clock speed with the correct clock speed. For example, if the original
file starts with:
#Profile:somehost.at.your.com
#Host:somehost
#CPU:4 @ 0.4GHz
#Memory:4084MB
#OS:HPUX
#Model:ia64 hp server rx8640
#Version:A.02.50.00
you would change it to:
#Profile:somehost.at.your.com
#Host:somehost
#CPU:4 @ 1.6GHz
#Memory:4084MB
#OS:HPUX
#Model:ia64 hp server rx8640
#Version:A.02.50.00
Here, you replace incorrect
clock speed (0.4 GHz) with the correct clock speed (1.6 GHz).
Example 3 Data Exported After Collecting Data with Updated Utilization
Provider
If you have collected data since the update, then you will be
replacing the correct clock speed with one that is about 4 times the
actual clock speed. For example, if the original file starts with:
#Profile:somehost.at.your.com
#Host:somehost
#CPU:4 @ 1.6GHz
#Memory:4084MB
#OS:HPUX
#Model:ia64 hp server rx8640
#Version:A.03.00.00
You would change it to
read:
#Profile:somehost.at.your.com
#Host:somehost
#CPU:4 @ 6.4GHz
#Memory:4084MB
#OS:HPUX
#Model:ia64 hp server rx8640
#Version:A.03.00.00
Here you replace the
correct clock speed (1.6GHz) with a clock speed four times greater
than the actual clock speed (6.4GHz).
It is not an intuitive thing to put in a clock speed that is
4 times too high. This is done to compensate for the fact that the
CPU utilization and allocation data are about one fourth what it should
be.
Import the file of corrected values.
Importing the data is done with the capprofile command. Use the -o option to overwrite the existing
data. Do not use the -S option to reset the system
properties.
Printable version
