Table of Contents
Advertisement
Appendix G
High Availability
The answer to this problem will depend from site to site, but one good way to make this work is to
have a set of intermediate scripts between the crontab file and the commands it executes. These
scripts could test for the existence of any prerequisite files and/or file systems and only execute the
associated command if all the prerequisites are met. This is exactly the strategy we recommend for
the crontab entries for the sfs_backup_util in Section G.7: Metadata Backup Considerations on page
569.
G.6 Monitoring and Maintenance
G.6.1
clstat
One quick way to get an overview of a cluster's current status is using /usr/sbin/cluster/clstat. This
utility will report on which nodes are currently a part of the cluster and what interfaces are
currently available on them (boot, service, standby). It can run in either ASCII mode or X mode
depending on what services are available and how it is invoked. Below is a sample ASCII output:
In order for clstat to work, the clinfo daemon must be running. When cluster services are started,
there is an option to start clinfo or not. The default is not to start it, so it will have to be started
purposely in order for clstat to be utilized.
See the clstat man page for more information.
568
Figure H-17 sample output from 'clstat -a'
September 2002
HPSS Installation Guide
Release 4.5, Revision 2
Advertisement
Table of Contents
