 |
Index for
Section 1 |
|
 |
Alphabetical
listing for C |
|
 |
Bottom of
page |
|
caa_report(1)
NAME
caa_report - reports availability statistics for application resources
SYNOPSIS
/usr/bin/caa_report [-o|-s|-h|-a application] [-b begin-date] [-e end-date]
OPTIONS
-o Display availability information for applications that have a non-zero
uptime.
-s Displays availability information on all applications for which
statistics exist.
-h Display usage statement.
-a application
Display availability information for application specified only. Only
one application can be specified.
-b begin-date
Display availability information starting at begin-date.
-e end-date
Display availability information on applications until end-date.
DESCRIPTION
The caa_report command reports availability statistics for resources
managed by the cluster application availability (CAA) subsystem. The output
shows the percentage uptime for a specified time period for each
application resource. If a begin or end time is not specified, the
application assumes a begin time equal to the first time the application
was run on the cluster and an end time equal to the current time.
The CAA subsystem maintains a history of each application resource from the
time it is first started. This information is obtained by analyzing the
start and stop EVM events posted by CAA.
The files tracking the application uptime history are updated automatically
at 0300 hours each day and each time that the caa_report command is
executed by root. The time and frequency of the periodic merge is
configurable by changing the crontab format specified in
/var/cluster/caa/clustercron/caa_report.clustercronData.
To ensure accuracy of the availability measurements, at least one caad
daemon must be running on the cluster. Stop EVM events are assured to be
posted as long as any caad daemon on any node is running.
A user can specify a starting time and ending time to measure the
percentage uptime within that range. The time for either value may be
specified in the formats used by the date command or any ISO 8061 format.
If your chosen time format contains spaces, you need to surround the time
with double quotes.
The following are rules regarding time bounds and their use:
· The end-date must be after the begin-date.
· If an end-date is specified that is after the current time, then the
current time is used.
· If a begin-date is specified for an application that has never been
run at or before that time, then the first time that the application
was started will be used.
· If a begin-date is specified which is during a period that the
application was down, but the application had been running at some
point before that time, the time entered is used.
· The time displayed with the output is always the actual time used for
the percentage measurement.
EXAMPLES
1. The following example shows all the uptime percentage for all
applications:
/usr/bin/caa_report
Application Availability Report for rubble
Applications starting/ending uptime
---------------------------------------------------------------
autofs NEVER STARTED 0.00 %
cluster_lockd Fri Jul 27 11:00:48 2001 99.80 %
Thu Oct 4 12:31:14 2001
clustercron Fri Jul 27 11:01:08 2001 74.54 %
Thu Oct 4 12:31:14 2001
dmiller1 Tue Sep 25 13:57:51 2001 12.51 %
Thu Oct 4 12:31:14 2001
2. The following example shows the uptime percentage for applications
with non-zero uptime:
/usr/bin/caa_report -o
Application Availability Report for rubble
Applications starting/ending uptime
---------------------------------------------------------------
cluster_lockd Fri Jul 27 11:00:48 2001 99.80
Thu Oct 4 12:32:26 2001
clustercron Fri Jul 27 11:01:08 2001 94.54 %
Thu Oct 4 12:32:26 2001
dmiller1 Tue Sep 25 13:57:51 2001 12.51 %
Thu Oct 4 12:32:26 2001
3. The following example shows percentage uptime for all applications
since September 1, 2001, until the time at which the command was
executed:
# caa_report -b 9/1/01/00:00
Application Availability Report for rubble
Applications starting/ending uptime
---------------------------------------------------------------
cluster_lockd Thu Sep 1 00:00:00 2001 98.98 %
Thu Oct 4 12:38:56 2001
clustercron Thu Sep 1 00:00:00 2001 98.99 %
Thu Oct 4 12:38:56 2001
dmiller1 Thu Sep 1 00:00:00 2001 94.28 %
Thu Oct 4 12:38:56 2001
4. The following example shows the uptime percentage for all applications
from September 1, 2001 through September 30, 2001:
/usr/bin/caa_report -b 9/1/01 -e 9/30/01
Application Availability Report for rubble
Applications starting/ending uptime
---------------------------------------------------------------
cluster_lockd Thu Sep 1 00:00:00 2001 98.98 %
Thu Sep 30 00:00:00 2001
clustercron Thu Sep 1 00:00:00 2001 98.99 %
Thu Sep 30 00:00:00 2001
dmiller1 Thu Sep 1 00:00:00 2001 96.67 %
Thu Sep 30 00:00:00 2001
EXIT VALUES
The following exit values are returned:
0 Successful completion
non-zero
A failure has occurred.
SEE ALSO
Commands: caa_profile(8), caa_register(8), caa_relocate(8), caa_start(8),
caa_stat(1), caa_unregister(8)
Daemon: caad(8)
File: caa(4)
TruCluster Server Cluster Administration
|
Index for
Section 1 |
|
|
Alphabetical
listing for C |
|
 |
Top of
page |
|