Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

AutoRAID: Display of Performance metrics and recommendations

SOLVED
Go to solution
Yogeeraj_1
Honored Contributor

AutoRAID: Display of Performance metrics and recommendations

Hi experts,

Please help.

When i have an error when trying to display performance metrics and recommenddations.
=============================================
k250 #arraydsp -m 1125000001 1126000001 $autoraid
Performance log data is unavailable for the interval specified
arraydsp: Error in command execution
k250 #arraydsp -r 11250000 11260000 $autoraid
Performance log data is unavailable for the interval specified
arraydsp: Error in command execution
=============================================

Anybody please help
Regards
Yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
3 REPLIES
Farid Feknous
Frequent Advisor

Re: AutoRAID: Display of Performance metrics and recommendations

Hi

I think that you have enter a wrong date you need to enter a valid date it means date already loged for example

arraydsp -m 11240000 11250000 4autoraid

Regards
Djamil
Insu Kim
Honored Contributor

Re: AutoRAID: Display of Performance metrics and recommendations

Take a look at the thread below.

http://us-support2.external.hp.com/cki/bin/doc.pl/sid=77e54ae408a079d4d8/screen=ckiSearchResults

Hope this helps,
Never say "no" first.
Insu Kim
Honored Contributor
Solution

Re: AutoRAID: Display of Performance metrics and recommendations

It looks like that the link has a problem.
I copied and pasted the whole ducument below.

"Performance log data is unavailable" error when running arraydsp DocId: KBRC00000868 Updated: 11/13/00 8:58:00 AM

PROBLEM
The following error is received when trying to check the performance
metrics on an HP AutoRaid disk array:


TP2-root> arraydsp -m 01011200 01101200 0000001057EB
Performance log data is unavailable for the interval specified
arraydsp: Error in command execution


Logprint shows all the records (logprint -s 01011200 -e 01101200 -
tperf).
I also checked disk and controller logs and I did not find any errors.

Why does this error occur?
RESOLUTION
The arraydsp -r and -m commands rely on "clean" data in the
logs to run. If there are any invalid entries in the logs, the following
error will be received when running arraydsp:


TP2-root> arraydsp -m 01011200 01101200 0000001057EB
Performance log data is unavailable for the interval specified
arraydsp: Error in command execution


The following error may also appear in the /var/adm/syslog/syslog.log
file:

Nov 2 14:50:27 mims2 syslog: HP Advanced Disk Array serial number ?:
Server software logging suspended


Several events can cause the "Invalid" entries:

1. An system initialization anytime during the time period
requested.

2. No data transfer during the time period requested. The performance
algorithm requires at least two hours of data and looks at every
hour of data after that to compare and report performance. At least
one I/O has to be logged each hour of the time period requested.

3. The ARMServer process was stopped or not logging during the time
period requested.

4. Specifying invalid times when running arraydsp.

In some instances, running logprint to verify the entries in the
log file will give you corrupted output (verifying that either the catalog
file (LOGCATLG) or the log files is/are corrupted) - which is the reason
why arraydsp cannot list the entries for the time period specified.
This will require removal of the log files and catalog file
(see steps 1-6 below).

However, even if the LOGCATLG file appears valid, and entries in
the log files are viewable, these error messages can still be received.

Perform the following steps to resolve the errors:

1. Stop ARMServer process:

/sbin/init.d/hparray stop

2. Make note of the /var/opt/hparray/log/LOGCATLG
permissions/ownership.

3. Execute the "> LOGCATLG" command to clear the file contents.

4. Restart the ARMServer process:

/sbin/init.d/hparray start

Run performance metrics when more history is available in the log files.
If there are only a few logs with invalid data, those logs should eventually
fall out of the requested time period, and valid performance data will be
available.
Never say "no" first.