The Image Services performance reports do not display the correct CPU statistics on an AIX LPAR server. The problem is caused by incorrect collection data being written to the perflog file.
Resolving the problem
Image Services 4.2.0
The problem is resolved in the Image Services 18.104.22.168 release by taking advantage of current AIX API calls that are available for LPAR CPU statistics. The Interim Fix is in IS 4.2.0 FP5.
After applying IS 4.2.0 FP 5 (or higher), the current /fnsw/local/sd/1/perflog must be removed prior to restarting the software because the internal format has changed.
Image Services 4.1.2
Due to compile limitations in Image Services 4.1.2 that prevent using the necessary API calls to resolve this problem, a work around is available. The work around, which can be downloaded from IBM Fix Central, is included in IS 4.1.2 FP16.
Image Services 4.1.2 Work Around Procedure
Before restarting the software, create a trigger file named /fnsw/local/trigger/vmstat_mon.
If the trigger file exists, the perf_mon command will run the vmstat -w -t <interval> command and output it to a file. The interval used will be the same as the interval specified in the perf_mon.script file. The vmstat information that is captured can be used to compare with the data in the performance reports. The vmstat output file is created in the /fnsw/local/logs/vmstatlog. directory. There will be one file for each day. If the trigger file is not created, the original problem of incorrect CPU statistics will persist.
NOTE: If the /fnsw/lib/perf/perf_mon.script file is configured to monitor activity every 15 minutes, the data represented in the performance reports is for the starting time. This means the data for 9:00 AM shows activity for 9:00 AM through 9:15 AM. The vmstat information for 9:00 AM shows activity from 8:45 through 9:00 AM.