how to see veritas version

bash-3.00# pkginfo -l VRTSvxvm
   PKGINST:  VRTSvxvm
      NAME:  Binaries for VERITAS Volume Manager by Symantec
  CATEGORY:  system
      ARCH:  i386
   VERSION:  5.0,REV=04.15.2007.12.15
   BASEDIR:  /
    VENDOR:  Symantec Corporation
      DESC:  Virtual Disk Subsystem
    PSTAMP:  VERITAS-5.0_x64_MP3.50:2008-08-17
  INSTDATE:  Sep 08 2012 23:44
   HOTLINE:  http://support.veritas.com/phonesup/phonesup_ddProduct_.htm
     EMAIL:  support@veritas.com
    STATUS:  completely installed
     FILES:      863 installed pathnames
                  30 shared pathnames
                  13 linked files
                 110 directories
                 409 executables
              287334 blocks used (approx)

bash-3.00# pkginfo -l VRTSvxfs
   PKGINST:  VRTSvxfs
      NAME:  VERITAS File System
  CATEGORY:  system,utilities
      ARCH:  i386
   VERSION:  5.0,REV=s_5_0x86A12_sol
   BASEDIR:  /
    VENDOR:  VERITAS Software
      DESC:  Commercial File System
    PSTAMP:  VERITAS-FS-5.0.3.0-2008-08-11-5.0MP3_x86=127337-02
  INSTDATE:  Sep 08 2012 23:54
   HOTLINE:  (800) 342-0652
     EMAIL:  support@veritas.com
    STATUS:  completely installed
     FILES:      196 installed pathnames
                  27 shared pathnames
                   4 linked files
                  40 directories
                  64 executables
               50312 blocks used (approx)

bash-3.00# modinfo|grep -i vx
 50 fffffffff5918000  44518 230   1  vxdmp (VxVM 5.0MP3: DMP Driver)
 93 fffffffff5c23000 2427b8 231   1  vxio (VxVM 5.0MP3 I/O driver)
 94 fffffffff5bf0350    e50 232   1  vxspec (VxVM 5.0MP3 control/status driv)
246 fffffffff590b540    ca0 233   1  vxportal (VxFS 5.0_REV-5.0MP3A25_sol port)
247 fffffffff68d6000 1f49f0  21   1  vxfs (VxFS 5.0_REV-5.0MP3A25_sol SunO)
250 fffffffff5f18000  53d78 237   1  vxfen (VRTS Fence 5.0MP3)
272 fffffffff6bd0000   aec0 234   1  fdd (VxQIO 5.0_REV-5.0MP3A25_sol Qui)
bash-3.00#
bash-3.00# ps -aef|grep -i vx
    root  2130     1   0 12:27:49 ?           0:00 /opt/VRTSobc/pal33/bin/vxpal -a actionagent -x
    root   631     1   0 12:25:15 ?           0:00 /sbin/vxesd
    root  3361  2412   0 12:27:54 ?           0:00 /sbin/sh - /usr/lib/vxvm/bin/vxcached root
    root  2411     1   0 12:27:52 ?           0:00 /sbin/sh - /usr/lib/vxvm/bin/vxsited root
    root  2409     1   0 12:27:52 ?           0:00 /sbin/sh - /usr/lib/vxvm/bin/vxrelocd root
    root  1995     1   0 12:27:09 ?           0:01 /opt/VRTSob/bin/vxsvc -r /etc/vx/isis/Registry -e
    root  2052     1   0 12:27:20 ?           0:03 /opt/VRTSobc/pal33/bin/vxpal -a StorageAgent -x
    root  3123  3120   0 12:27:53 ?           0:00 vxnotify -f -w 15
    root  6708     1   0 13:04:39 ?           0:00 vxconfigd -k
    root  3356  3354   0 12:27:54 ?           0:00 vxnotify -m -w 15
    root  2156     1   0 12:27:51 ?           0:00 /usr/sbin/vxdclid
    root  2020     1   0 12:27:12 ?           0:00 /opt/VRTSobc/pal33/bin/vxpal -a gridnode -x
    root  3362  3361   0 12:27:54 ?           0:00 vxnotify -C -w 15
    root  2412     1   0 12:27:52 ?           0:00 /sbin/sh - /usr/lib/vxvm/bin/vxcached root
    root  2414     1   0 12:27:52 ?           0:00 /sbin/sh - /usr/lib/vxvm/bin/vxconfigbackupd
    root  3120  2409   0 12:27:53 ?           0:00 /sbin/sh - /usr/lib/vxvm/bin/vxrelocd root
    root  3082  2414   0 12:27:53 ?           0:00 /sbin/sh - /usr/lib/vxvm/bin/vxconfigbackupd
    root  3086  3082   0 12:27:53 ?           0:00 vxnotify
    root  3354  2411   0 12:27:54 ?           0:00 /sbin/sh - /usr/lib/vxvm/bin/vxsited root

how to install veritas file system licence key

bash-3.00# vxlicinst

Symantec License Manager vxlicinst utility version 3.02.33.0
Copyright (C) 1996-2007 Symantec Corporation. All rights reserved.

Enter your license key : AJZE-NCS3-VNZX-4U4O-LKPP-PP34-OZPP-PPPR-P

License key successfully installed for VERITAS File System

=========================================
HOW TO SEE VERITAS LICENCES INSTALLED
=========================================
bash-3.00# vxlicrep

Symantec License Manager vxlicrep utility version 3.02.33.0
Copyright (C) 1996-2007 Symantec Corporation. All rights reserved.

Creating a report on all VERITAS products installed on this system

 -----------------***********************-----------------

   License Key                         = AJZE-FRJM-PTFR-M83D-PPW4-MPPP-PPP3-PP3R-P
   Product Name                        = VERITAS Volume Manager
   Serial Number                       = 2675
   License Type                        = PERMANENT
   OEM ID                              = 2006
   Site License                        = YES
   Point Product                       = YES

 Features :=

   Storage Expert                      = Enabled
   VxVM                                = Enabled
   FASTRESYNC                          = Enabled
   DGSJ                                = Enabled
   CPU Count                           = Not Restricted
   PGR                                 = Enabled
   VVS_CONFIG                          = Enabled
   Platform                            = un-used
   Version                             = 7
   Dynamic Lun Expansion               = Enabled
   Hardware assisted copy              = Enabled
   Cross-platform Data Sharing         = Enabled
   Maximum number of volumes           = Not Restricted


 -----------------***********************-----------------

   License Key                         = AJZ7-TU3I-J88P-B4UF-JO6P-PPPP-PPPP-3P6P-P
   Product Name                        = VERITAS Cluster Server
   Serial Number                       = 8546
   License Type                        = PERMANENT
   OEM ID                              = 2006
   Site License                        = YES
   Editions Product                    = YES

 Features :=
   Platform                            = Unused
   Version                             = 7
   Tier                                = Unused
   Reserved                            = 0

   Mode                                = VCS


 -----------------***********************-----------------

   License Key                         = AJZE-NCS3-VNZX-4U4O-LKPP-PP34-OZPP-PPPR-P
   Product Name                        = VERITAS File System
   Serial Number                       = 2675
   License Type                        = PERMANENT
   OEM ID                              = 2006
   Site License                        = YES
   Point Product                       = YES

 Features :=
   VXFS                                = Enabled
   QLOG                                = Enabled
   VXCKPT                              = Enabled

   CPU Count                           = Not Restricted
   Platform                            = un-used
   Version                             = 7
   File Change Log                     = Enabled
   Cross-platform Data Sharing         = Enabled
   Extra-Big File Systems              = Enabled
   Multi-Volume Support                = Enabled
   Quality of Storage Service          = Enabled
   Maximum number of file systems      = Not Restricted

veritas licence key in 5.1 on x86

bash-3.00# /opt/VRTS/bin/vxlicrep

Symantec License Manager vxlicrep utility version 3.02.34.0
Copyright (C) 1996-2008 Symantec Corporation. All rights reserved.

Creating a report on all VERITAS products installed on this system

 -----------------***********************-----------------

   License Key                         = AJZF-RSFT-EZVR-9B73-PPPO-4O4O-XPP6-RPPR-P
   Product Name                        = VERITAS Storage Foundation Enterprise
   Serial Number                       = 2675
   License Type                        = PERMANENT
   OEM ID                              = 2006
   Site License                        = YES
   Editions Product                    = YES

 Features :=
   Reserved                            = 0
   CPU Count                           = Not Restricted
   VxVM#VERITAS Volume Manager         = Enabled
   VXFS#VERITAS File System            = Enabled
   QLOG#VERITAS File System            = Enabled
   PGR#VERITAS Volume Manager          = Enabled
   VERITAS Storage Foundation Enterprise = Enabled
   Quality of Storage Service#VERITAS File System = Enabled

   Storage Expert#VERITAS Volume Manager = Enabled
   Platform                            = un-used
   Version                             = 5.1
   Dynamic Lun Expansion#VERITAS Volume Manager = Enabled
   Hardware assisted copy#VERITAS Volume Manager = Enabled
   Cross-platform Data Sharing#VERITAS Volume Manager = Enabled
   File Change Log#VERITAS File System = Enabled
   Cross-platform Data Sharing#VERITAS File System = Enabled
   Extra-Big File Systems#VERITAS File System = Enabled
   Multi-Volume Support#VERITAS File System = Enabled
   FASTRESYNC#VERITAS Volume Manager   = Enabled
   DGSJ#VERITAS Volume Manager         = Enabled
   VXCKPT#VERITAS File System          = Enabled
   VVS_CONFIG#VERITAS Volume Manager   = Enabled
   VXKEYLESS                           = Enabled


 -----------------***********************-----------------

   Product Name                        = VERITAS Volume Manager
   License Type                        = PERMANENT

 Features :=
   PGR                                 = Enabled
   PGR_TRAINING                        = Enabled
   Site Awareness                      = Enabled
   DGSJ                                = Enabled
   VVS_CONFIG                          = Enabled
   Hardware assisted copy              = Enabled
   RAID5SNAP                           = Enabled
   Storage Expert                      = Enabled
   Dynamic Lun Expansion               = Enabled
   Cross-platform Data Sharing         = Enabled



 -----------------***********************-----------------

   Product Name                        = VERITAS File System
   License Type                        = PERMANENT

 Features :=
   VXFDD                               = Enabled
   Quality of Storage Service          = Enabled
   VXCKPT                              = Enabled
   QLOG                                = Enabled
   File Change Log                     = Enabled
   Cross-platform Data Sharing         = Enabled
   Extra-Big File Systems              = Enabled
   Multi-Volume Support                = Enabled



 -----------------***********************-----------------

   Product Name                        = VERITAS Database Edition for Oracle
   License Type                        = PERMANENT

 Features :=
   DATABASE_EDITION                    = Enabled
   DBED_ORA_TOOLS                      = Enabled
   ODM                                 = Enabled



 -----------------***********************-----------------

   Product Name                        = VERITAS SANPoint Control
   License Type                        = PERMANENT

 Features :=
   SPC Lite                            = Enabled



 -----------------***********************-----------------

   License Key                         = AJZE-FRJM-PTFR-M83D-PPW4-MPPP-PPP3-PP3R-P
   Product Name                        = VERITAS Volume Manager
   Serial Number                       = 2675
   License Type                        = PERMANENT
   OEM ID                              = 2006
   Site License                        = YES
   Point Product                       = YES

 Features :=

   Storage Expert                      = Enabled
   VxVM                                = Enabled
   FASTRESYNC                          = Enabled
   DGSJ                                = Enabled
   CPU Count                           = Not Restricted
   PGR                                 = Enabled
   VVS_CONFIG                          = Enabled
   Platform                            = un-used
   Version                             = 5.1
   Dynamic Lun Expansion               = Enabled
   Hardware assisted copy              = Enabled
   Cross-platform Data Sharing         = Enabled
   Maximum number of volumes           = Not Restricted


 -----------------***********************-----------------

   License Key                         = AJZE-NCS3-VNZX-4U4O-LKPP-PP34-OZPP-PPPR-P
   Product Name                        = VERITAS File System
   Serial Number                       = 2675
   License Type                        = PERMANENT
   OEM ID                              = 2006
   Site License                        = YES
   Point Product                       = YES

 Features :=
   VXFS                                = Enabled
   QLOG                                = Enabled
   VXCKPT                              = Enabled

   CPU Count                           = Not Restricted
   Platform                            = un-used
   Version                             = 5.1
   File Change Log                     = Enabled
   Cross-platform Data Sharing         = Enabled
   Extra-Big File Systems              = Enabled
   Multi-Volume Support                = Enabled
   Quality of Storage Service          = Enabled
   Maximum number of file systems      = Not Restricted



 License Key                         = AJZ7-TU3I-J88P-B4UF-JO6P-PPPP-PPPP-3P6P-P
   Product Name                        = VERITAS Cluster Server
   Serial Number                       = 8546
   License Type                        = PERMANENT
   OEM ID                              = 2006
   Site License                        = YES
   Editions Product                    = YES

 Features :=
   Platform                            = Unused
   Version                             = 5.1
   Tier                                = Unused
   Reserved                            = 0

   Mode                                = VCS
   VXKEYLESS                           = Enabled

man page of vxconfigd

vxconfigd - Veritas Volume Manager configuration daemon

SYNOPSIS

vxconfigd [-dfk] [-D diag_portal] [-I inquiry_portal] [-m mode] [-r reset] [-R request_portal] [-x arg]

DESCRIPTION

The Veritas Volume Manager (VxVM) configuration daemon, vxconfigd, maintains disk configurations and disk groups in VxVM. vxconfigd takes requests from other utilities for configuration changes, and communicates those changes to the kernel and modifies configuration information stored on disk. vxconfigd also initializes VxVM when the system is booted.

OPTIONS

-d	Equivalent to -m disable, which starts vxconfigd in disabled mode.
-D diag_portal
	Specifies a rendezvous file path name for diagnostic operation connections to vxconfigd. /etc/vx/vold_diag is the default path name. The diagnostic portal exists in both the enabled and disabled operating modes.
-f	Starts vxconfigd in the foreground. This is often useful when debugging vxconfigd, or when tracing configuration changes. If -f is not specified, vxconfigd forks a background daemon process. The foreground process exits when the vxconfigd startup processing completes.
-I inquiry_portal
	Specifies a rendezvous file path name for inquiry operation connections to vxconfigd. /etc/vx/vold_inquiry is the default path name. The inquiry portal accepts only opcodes for connection requests and query requests submitted by vxprint. All other requests are rejected. The inquiry portal exists only when vxconfigd is operating in enabled mode.
-k	If a vxconfigd process is already running, -k kills it before any other startup processing. This is useful for recovering from a hung vxconfigd process. Killing the old vxconfigd and starting a new one usually does not cause problems for volume devices that are being used by applications, or that contain mounted file systems.
-m mode	Sets the initial operating mode for vxconfigd. Possible modes are: disable Starts vxconfigd in disabled mode. disable creates a rendezvous file for utilities that perform various diagnostic or initialization operations. disable can be used with the -r reset option as part of a command sequence to completely reinitialize Veritas Volume Manager configuration. Use the vxdctl enable operation to enablevxconfigd. enable Starts vxconfigd fully enabled (default). enable uses the volboot file to bootstrap and load in the boot disk group if the root disk is under VxVM control. It then scans all known disks for disk groups to import and imports those disk groups. enable also sets up entries in the /dev directories to define all of the accessible Veritas Volume Manager devices. If the volboot file cannot be read, or if the boot disk group cannot be imported, vxconfigd starts in disabled mode.
-r reset	Resets all Veritas Volume Manager configuration information stored in the kernel as part of startup processing. The reset fails if any volume devices are in use, or if an imported shared disk group exists. This option is primarily useful for testing or debugging.
-R request_portal
	Specifies a rendezvous file path name for regular configuration and query requests. /etc/vx/vold_request is the default. The regular request portal exists only when vxconfigd is operating in enabled mode.
-x arg	Turns on various parameters used for debugging or other aspects of vxconfigd operation. The argument, arg, is a decimal number, 1 through 9, or a string. A number value sets the debug information output level and is required to obtain any debug messages.
	The debugging level can also be changed while vxconfigd is running by using the vxdctl debug command.
	String arguments include: boot=volboot_path   Specifies the path name to use for the volboot file. This is primarily useful with the stub debug option. The volboot file contains the name of the boot disk group if the root disk is under VxVM control. It also contains a host ID that is stored on disks in imported disk groups to define ownership of disks as a sanity check for disks that might be accessible from more than one host. cleartempdir   Removes and recreates the /etc/vx/tempdb directory. This directory stores configuration information that is cleared after system reboots (or cleared for specific disk groups on import and deport operations). If the contents of this directory are corrupted, due to a disk I/O failure for example, vxconfigd will not start up if it is killed and restarted. Such a situation can be cleared by starting vxconfigd with -x cleartempdir. This option has no effect if vxconfigd is not started in enabled mode. Note: It is advisable to kill any running operational commands (vxvol, vxsd, or vxmend) before using the -x cleartempdir option. Failure to do so may cause these commands to fail, or may cause disastrous but unchecked interactions between those commands and the issuance of new commands. It is safe to use this option while running the graphical user interface, or while Veritas Volume Manager background daemons are running (vxsparecheck, vxnotify, or vxrelocd). darecs=darecs_path   Specifies the pathname to the file that contains persistent disk access records. This file contains a list of disks that are scanned and configured by VxVM. devprefix=prefixdir   Specifies a directory path name to prefix for any disk device accessed by vxconfigd. For example, with devprefix=/tmp, any access to a raw disk device named hdisk10would actually be directed to the file /tmp/dev/rdsk/hdisk10. In stubbed mode, vxconfigd can operate with such files being regular files. vxconfigd only requires entries in the prefixdir /dev directory in stubbed mode. See stub below for more information. log | nolog   Logs all vxconfigd console output directly to a file. This method of logging is very reliable in that any messages output before a system crash are available in the log file (if the crash did not corrupt the file system). You can enable direct vxconfigd logging with the -x log argument, and turn it off with the -x nolog argument. Logging is disabled by default. If direct logging is enabled, the default log file is /var/adm/ras/vxconfigd.log. This option can be used in conjunction with syslog | nosyslog. See syslog | nosyslog below for more information. The following command logs all debug and error messages to the specified log file:   vxconfigd -x9 -x log logfile=logfilename   Specifies an alternate vxconfigd direct log file. This option requires using the -x log argument. noautoconfig   vxconfigd usually configures disk devices that can be found by inspecting kernel disk drivers automatically. These auto_configured disk devices are not stored in persistent configurations, but are regenerated from kernel tables after every reboot. Invoking vxconfigd with -x noautoconfig prevents the automatic configuration of disk devices, forcing VxVM to use only those disk devices configured explicitly using vxdisk define or vxdisk init. nothreads   Runs vxconfigd single-threaded. request_threads=count   Specifies the number of request handlers that are configured when vxconfigd is started. The request_threads option overrides any default values or values set previously with the vxdctl command. The request_threads option is incompatible with the -x nothreads option. stub Specifies not to communicate configuration changes to the kernel. stub is typically used as a demonstration mode of operation for vxconfigd. In most aspects, a stubbedvxconfigd behaves like a regular vxconfigd, except that disk devices can be regular files and volume nodes are not created. A stubbed vxconfigd can run concurrently with a regular vxconfigd, or concurrently with any other stubbed vxconfigd processes, as long as different rendezvous, volboot, and disk files are used for each concurrent process. Other Veritas Volume Manager utilities can detect when they are connected to a vxconfigd that is running in stubbed mode. When a VM utility detects a stubbed-modevxconfigd, the utility typically stubs out any direct use of volumes or plexes itself. This allows utilities to make configuration changes in a testing environment that runs without any communication with the kernel or creation of real volumes or plexes. syslog | nosyslog   vxconfigd supports using the syslog() library call to log all of its console messages (this includes error, warning, and notice messages, but not debug messages). By default,vxconfigd redirects console messages to syslog() when it is first started. You can disable syslog() logging using the -x nosyslog argument, and turn it on with the -x syslogargument. You can also enable or disable syslog() logging at boot-time by editing the Veritas Volume Manager startup scripts. syslog can be specified along with log (described above) to obtain more reliable logging. For example, the following command logs all debug messages to the specified log file, and logs all error messages to both the direct log file and the conslog file:   vxconfigd -x9 -x log -x syslog synctrace   Flushes tracefile data to disk, invoking fsync, to ensure that the last entry is included in the file even if the system crashes. tagged=N   Displays the timestamp (in milliseconds) and elapsed time values of the vxconfigd subsystems that are executed when vxconfigd starts. The N argument controls the verbosity of the output. 1 is the lowest level of verbosity, and 8 is the highest. The command also displays the Begin and End messages of each subsystem, and any quantities that are relevant to that subsystem. For example, the number of LUN paths during device discovery. Elapsed time values are shown within the End messages and represent the computed elpased time between the Begin and End messages. Tagged messages can be used to help determine where time is being spect during vxconfigd startup. This is particularly useful in large LUN configurations. The following sample shows a typical output for tagged messages: timestamp | mstimestamp   Attaches a date and time-of-day timestamp to all messages written by vxconfigd to the console. If mstimestamp is used, a millisecond value is also displayed, allowing detailed timing of vxconfigd’s operation. tracefile=file   Logs all possible tracing information to the specified file.

EXIT CODES

If errors are encountered, vxconfigd writes diagnostic messages to the standard error output. vxconfigd exits if it encounters some serious errors. If an error is encountered when importing the boot disk group during a normal startup, vxconfigd enters disabled mode. See the Veritas Volume Manager Troubleshooting Guide for a list of error messages and how to respond to them.Defined exit codes for vxconfigd are:

0	The requested startup mode completed successfully. This is returned if -f is not used to startup vxconfigd as a foreground process. If vxconfigd is started as a foreground process, it exits with a zero status if vxdctl stop is used to exit vxconfigd.
1	The command line usage is incorrect.
2	Enabled-mode operation was requested, but an error caused vxconfigd to enter disabled mode instead. This is also returned for boot-mode operation if startup failed. However, with boot-mode operation, the background vxconfigd process exits as well.
3	The -k option was specified, but the existing vxconfigd could not be killed.
4	A system error was encountered that vxconfigd cannot recover from. The specific operation that failed is printed on the standard error output.
5	The background vxconfigd process was killed by a signal before startup completed. The specific signal is printed on the standard error output.
6	A serious inconsistency was found in the kernel, preventing sane operation. This can also happen because of version mismatch between the kernel and vxconfigd.
7	The -r reset option was specified, but the Veritas Volume Manager kernel cannot be reset. Usually this means that a volume is open or mounted.
8	An interprocess communications failure (usually a STREAMS failure). Has made it impossible for vxconfigd to take requests from other utilities.
9	Volumes that must be started early by vxconfigd could not be started. The reasons, and possible recovery solutions, are printed to the standard error output.

FILES

/dev	Directory containing raw and block device nodes for volumes (raw device names start with "r").
/etc/vx/darecs	File containing a list of disks to be scanned and configured.
/etc/vx/tempdb	Directory containing miscellaneous temporary files. Files in this directory are recreated after reboot.
/etc/vx/volboot	File containing miscellaneous boot information. See vxdctl(1M) for more information on this file.
/var/adm/ras/vxconfigd.log	Default log file.

man page of hagrp

hagrp - perform VCS service group operations

SYNOPSIS

hagrp -add group
hagrp -delete group
hagrp -link parent_group child_group dependency
hagrp -unlink parent_group child_group
hagrp -clear group [-sys system] [-clus cluster | -localclus]
hagrp -clearadminwait [-fault] group -sys system
hagrp -flush group -sys system [-clus cluster | -localclus]
hagrp -online [-force] [-nopre] group -sys system [-checkpartial system] [-clus cluster | -localclus]
hagrp -online [-force] group -any [-clus cluster | -localclus]
hagrp -offline [-force] [-ifprobed] group -sys system [-clus cluster | -localclus]
hagrp -offline [-force] [-ifprobed] group -any [-clus cluster | -localclus]
hagrp -switch group -to system [-clus cluster | -localclus [-nopre]]
hagrp -switch group -any [-clus cluster | -localclus]
hagrp -freeze group -persistent
hagrp -freeze group [-clus cluster | -localclus]
hagrp -unfreeze group -persistent
hagrp -unfreeze group [-clus cluster | -localclus]
hagrp -enable group [-sys system]
hagrp -disable group [-sys system]
hagrp -autoenable group -sys system
hagrp -enableresources group
hagrp -disableresources group
hagrp -ignore -group -clus cluster
hagrp -display [group(s)] [-attribute attribute(s)] [-sys system(s)] [-clus cluster | -localclus]
hagrp -state [group(s)] [-sys system(s)] [-clus cluster | -localclus]
hagrp -list [conditional(s)] [-clus cluster | -localclus]
hagrp -value group attr [system] [-clus cluster | -localclus]
hagrp -dep [group(s)]
hagrp -resources group [-clus cluster | -localclus]
hagrp -wait group attribute value[-clus cluster] [-sys system] [-time timeout]
hagrp -help [-modify | -link | -list]
hagrp -modify modify_options

AVAILABILITY

VRTSvcs

DESCRIPTION

A service group is an instance of a computer service that is made highly available with VCS. A group comprises one or more resources of various resource types, such as disks, volumes, or databases. Use thehagrp command to view information about and manage each group. See NOTES for how to specify "-" and "%" characters in the command line.

OPTIONS

-add group
	Add a service group to the cluster.
-delete group
	Delete a service group. The group must have no resources. To delete resources, use the hares command.
-link parent_group child_group dependency
	Specify dependencies between service groups. The variable dependency is one of the following: online global [ firm | soft ]   When VCS starts, the child group must be online on some system in the cluster before the parent group can come online. With the dependency set to firm, if the child group faults, the parent group must go offline until the child group fails over to another system, at which time the parent can return online. If VCS cannot bring the child group online in the cluster, the parent group remains offline. With the dependency set to soft, if the child group faults and fails over, the parent group continues online. If VCS cannot bring the child group online in the cluster, the parent group remains online. online local [ firm | soft ]   When VCS starts, the child group must be online on the same system in the cluster before the parent group can go online. With the dependency set to firm, if the child group faults, the parent group must go offline. If the child fails over, the parent group comes back online on the same system as the child. If VCS cannot bring the child group online in the cluster, the parent group remains offline. With the dependency set to soft, if the child group faults, the parent group continues to run on the local system until the child fails over to another system in the cluster, at which time the parent group will fail over to the same system as the child. If VCS cannot bring the child group online in the cluster, the parent group remains online. online remote [ firm | soft ]   When VCS starts, the child must be online on any other system in the cluster before the parent can go online. With the dependency set to firm, if the child group faults, the parent group goes offline. When the child group fails over to another system in the cluster, the parent group comes back online on a system other than the system on which the child is online. If VCS cannot bring the child group online in the cluster, the parent group remains offline. With the dependency set to soft, if the child group faults, the parent group continues to remain online unless VCS attempts to fail over the child group to the system on which the parent group is running; in this case, the parent group is taken offline, to be brought online elsewhere. If the child group cannot be brought online anywhere in the cluster, the parent stays online. offline local   The child group must be offline on the same system before the parent group can go online.
	A group dependency tree may be at most five levels deep, and each parent can have only one child. Parallel parent groups dependent on parallel child groups are not supported in online global or online remote dependencies. The configuration of parallel parent groups that are dependent on a failover child group is not supported in online local dependencies.
-unlink parent_group child_group
	Remove dependency between two service groups. Note that the dependency is not specified.
-clear group [-sys system] [-clus cluster | -localclus]
	Clear all faulted, non-persistent resources in the specified group by changing their state from faulted to offline. If no system is specified, all resources are cleared on all systems in the group’s SystemList. A message is printed if no faulted, non-persistent resources exist. If the Global Cluster option is in use, the command clears non-persistent faulted resources for the specified system or the specified cluster. Use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. For a system whose name is not unique among clusters, specify the name of its cluster. Only global service groups can be cleared from another cluster.
-clearadminwait [-fault] group -sys system
	Clear the ADMIN_WAIT state of all resources in the specified group on the specified system. If the resources continue in the ADMIN_WAIT state, use the -fault option to clear the ADMIN_WAIT state. The state is set to ONLINE | UNABLE_TO_OFFLINE or FAULTED, depending on the reasons the ResAdminWait trigger had been called. Note that the online, offline, switch, and flush operations cannot be performed on resources in the ADMIN_WAIT state. Also, when resources are in the ADMIN_WAIT state, the hastop command requires the -forceoption.
-flush group -sys system [-clus cluster | -localclus]
	Flush a service group and enable corrective action. All resources in the group that are waiting to go online automatically transition to not waiting. Resources waiting to go offline remain in that state. Failovers and switches in progress are cancelled. If the Global Cluster option is in use, the command flushes global service groups for corrective action on the specified system, local or remote. Use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. For a system whose name is not unique among clusters, specify the name of its cluster. Only global service groups can be flushed from another cluster.
-online [-force] [-nopre] group -sys system [-checkpartial system] [-clus cluster | -localclus]
	Start a service group by bringing its resources online on a specified system. Resources that have their AutoStart attribute set to zero (the default is one) are not started by this command unless resources that have AutoStart set to one depend on the resources. The -nopre option can be used within a user-defined Preonline event trigger script to bring a service group online without the executing the Preonline trigger again. The -checkpartial option is used by the Preonline trigger during failover. When a service group configured with Preonline=1 on one system (system 1) fails over to another system (system 2), only those resources online on system 1 prior to failover are brought online on system 2. If the Global Cluster option is in use, the command onlines the specified global service group on the specified system in the specified cluster. Use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. The -force option can be used to online a global group on a cluster when no authority for the group yet exists or when another cluster having the authority for the group is faulted. For a system whose name is not unique among clusters, specify the name of its cluster. Only global service groups can be brought online from another cluster.
-online [-force] group -any [-clus cluster | -localclus]
	The -any option can be used to start a service group by bringing its resources online on the best possible system in a cluster, based on the value of the group’s FailOverPolicy attribute. A parallel service group is brought online on multiple systems in a cluster if so configured. Resources that have their AutoStart attribute set to zero (the default is one) are not started by this command unless resources that have AutoStart set to one depend on the resources. If the Global Cluster option is in use, the command onlines the specified global service group on any system in the specified cluster. Use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. The -force option can be used to online a global group on a cluster when no authority for the group yet exists or when another cluster having the authority for the group is faulted. Only global service groups can be brought online from another cluster.
-offline [-force] [-ifprobed] group -sys system [-clus cluster | -localclus]
	Stop a service group by taking its resources offline on the specified system. The -force option is required to offline the ClusterService group.

Note: it is not recommended to offline the GlobalService group when the Global Cluster option is in use. If the Global Cluster option is in use, the command offlines the specified global service group on specified system in the specified cluster. Use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. For a system whose name is not unique among clusters, specify the name of its cluster. Only global service groups can be taken offline from another cluster.
-offline [-force] [-ifprobed] group -any [-clus cluster | -localclus]
	The -any option can be used to stop a service group by taking its resources offline on any system within a cluster. The -force option is required to offline the ClusterService group.
Note: Symantec recommends that you do not offline the GlobalService group when you use global clusters. If you use global clusters, the command offlines the specified global service group on any system in the specified cluster. Use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. The -force option can be used to offline a global group on a cluster when another cluster having the authority for the group is faulted. Only global service groups can be taken offline from another cluster.
-switch group -to system [-clus cluster | -localclus [-nopre]]
	Switch a service group from the system on which it is active to the specified system. This applies only to failover groups (groups that have the Parallel attribute set to zero).If you use global clusters, the command switches a global service group from a system to a specified system in the specified remote cluster. Use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. Only global service groups can be switched within or across clusters from another cluster. If you set the value of the PreSwitch group attribute to 1 in the global group definition of the remote cluster, the VCS engine invokes PreSwitch action for the resources that support the PreSwitch action. The engine switches a service group normally if all the actions succeed. If any of the actions fail, then the engine aborts the switch operation. See Veritas Cluster Server User’s Guide for more information. The -nopre option indicates that the VCS engine must switch the service group regardless of the value of the PreSwitch service group attribute.
-switch group -any [-clus cluster | -localclus]
	The -any option can be used to switch a service group to the best possible system on which it is currently not online, based on the value of the group’s FailOverPolicy attribute.If you use global clusters, the command switches a global service group from a system to a system in specified cluster, either local or remote. The -clus or -localclus option indicates a specific cluster. The -localclus option specifies the cluster in which the command is issued. Only global service groups can be switched within or across clusters from another cluster. With the -any option, the VCS engine does not invoke the PreSwitch action of any resources even if you set the value of the PreSwitch group attribute to 1. If you run this command to switch a parallel global service group across clusters, VCS brings the parallel service group online on all possible nodes in the remote cluster.
-freeze group -persistent
	Freeze a service group (disables onlining, offlining, and failover). The -persistent flag indicates the freeze is maintained after a system is rebooted, or the engine is stopped and restarted. NOTE that the configuration must be read-write to use this option.
-freeze group [-clus cluster | -localclus]
	Freeze a service group (disable onlining, offlining, and failover). If the Global Cluster option is in use, the command freezes the specified global service group in the specified cluster. Use the -clus or-localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. Only global service groups can be frozen from another cluster.
-unfreeze group -persistent
	Thaw a service group (reenables onlining, offlining, and failover). The -persistent flag indicates the freeze is maintained after a system is rebooted. NOTE that the configuration must be read-write to use this option.
-unfreeze group [-clus cluster | -localclus]
	Thaw a service group (reenables onlining, offlining, and failover). If the Global Cluster option is in use, the command unfreezes the specified global service group in the specified cluster. Use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. Only global service groups can be unfrozen from another cluster.
-enable group [-sys system]
	Enable a service group.
-disable group [-sys system]
	Disable a service group. Actions such as onlining and switching are not permitted on the group.
-autoenable group -sys system
	When VCS does not know the status of a given service group on a given system, it marks that service group as auto-disabled by setting the AutoDisabled attribute to 1 for that system. This can happen if VCS is not running on that system, or if all the resources in the service group on that system are not probed yet. A service group cannot be onlined or failed over if it is auto-disabled. If you want to override this behavior, you can use the autoenable option to clear the AutoDisabled flag for a service group on a system. For example, "hagrp -autoenable foo -sys bar" will clear the AutoDisabled flag for the service group foo on system bar.
Caution: To bring a group online manually after VCS has autodisabled it, make sure that the group is not fully or partially active on any system that has the AutoDisabled attribute set to 1 by VCS. Specifically, verify that all resources that may be corrupted by being active on multiple systems are brought down on the designated systems. Then, clear the AutoDisabled attribute for each system:# hagrp -autoenable service_group -sys system_name
-enableresources group
	Enable all resources in a service group. Agents monitor the resources in the group.
-disableresources group
	Disable all resources in a service group. Agents do not monitor the resources in the group.
-ignore group -clus cluster
	The -ignore option marks the selected remote group as offline on the specified remote cluster. The remote cluster specified should be in the \(oqfaulted\(cq state. This option is used in conjunction with the -status and -failover options of the haclus command. This ignores groups from the faulted cluster as seen from the local cluster. Ignored groups will not be listed in the output of the -status and -failover options of the haclus command.
-display [group(s)] [-attribute attribute(s)] [-sys system(s)] [-clus cluster | -localclus]
	Display the attributes and their values for a specified group (or all groups if no group is specified). If the system is specified, display the attributes and values for the specified group on the specified system. If the cluster is specified, display the attributes and values for the specified group on the specified cluster. If the Global Cluster option is in use, the command displays the specified information for all systems on all clusters. Use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. For a system whose name is not unique among clusters, specify the name of its cluster. Only the values of attributes of global groups can be displayed across clusters.
-state [group(s)] [-sys system(s)] [-clus cluster | -localclus]
	Display the current state of the specified groups on the specified system (or all systems if no system is specified) in the specified cluster. If the Global Cluster option is in use, the command lists the state of the specified system. Use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. For a system whose name is not unique among clusters, specify the name of its cluster. Only the states of global groups can be displayed across clusters.
-list [conditional(s)] [-clus cluster | -localclus]
	Displays a list of groups whose values match given conditional statement(s). Conditional statements can take three forms: Attribute=Value, Attribute!=Value, Attribute=~Value. Multiple conditional statements imply AND logic. If no conditional statement is specified, all groups in the cluster are listed. If the Global Cluster option is in use, the command lists the specified global groups on all clusters. Use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. Only global groups can be displayed across clusters.
-value group attr system [-clus cluster | -localclus]
	The -value option provides the value of a single group attribute. For example, "hagrp -value groupX State sysb -clus C2" displays the value of the \(oqState\(cq attribute for the group "groupX" on system "sysb" in the remote cluster C2. If no cluster is specified, the local cluster is considered. The system name must be specified for local attribute values but not for global attribute values. The -value option is used instead of the -display option when one specific attribute value is needed rather than a table of many attribute values. If the Global Cluster option is in use, the command displays the values for the attribute on all clusters. Use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued. For a system whose name is not unique among clusters, specify the name of its cluster. Only a global group’s attribute value can be displayed across clusters.
-dep [group(s)]
	Display dependencies between groups.
-resources group [-clus cluster | -localclus]
	List resources for a service group. For global clusters, use the -clus or -localclus option to indicate a specific cluster. The -localclus option specifies the cluster in which the command is issued.
-wait group attribute value [-clus cluster] [-sys system] [-time timeout]
	The -wait option is for use in scripts to direct the hagrp command to block until the value of the attribute is changed as specified, or until the timeout expires. If a timeout is not specified, the command line interface blocks indefinitely. timeout is an integer specifying seconds. See EXAMPLES. The -wait option can be used only with changes to scalar attributes. The -sys option can be applied only when the scope of the attribute is local. The -clus option applies only when applying the -wait option in a Global Cluster environment. The scalar group level attributes on the remote cluster are limited to those capable of being displayed using the hagrp -display -clus remote_cluster command.
-help [-modify | -link | -list]
	Display information about using hagrp. The -modify option provides modify specific help; the -link option provides link specific help; the -list option provides list specific help.
-modify modify_options
	The -modify option lets you modify a service group’s attributes. You must make the configuration read-write before modifying any attributes. Some attributes, such as ProbesPending, are internal to VCS and cannot be modified. You can modify any attribute that can be configured in main.cf. You may modify a scalar attribute’s existing value. You may not use -modify to change values already defined for a vector, a keylist, or an association attribute. For vector, keylist, and association attributes, use the modify_options, which include -add, -delete, -update, or -delete -keys. Refer to the following list of permissible -modify commands. You may display the commands by using -hagrp -help -modify. SCALAR hagrp -modify group attr value [-sys system] VECTOR Use the following command only when the attribute has no value:hagrp -modify group attr value ... [-sys system] For vector attributes that have values defined, only the following operations are allowed: hagrp -modify group attr -add value ... [-sys system] hagrp -modify group attribute -insert index value ... [-sys system] You can use the -insert option to add one or more values at a given index. You must enter a valid integer for index that can range from 1 to the maximum number of values. hagrp -modify group attr -delete key ... [-sys system] hagrp -modify group attr -delete -keys [-sys system] KEYLIST   Use the following command only when the attribute has no value:hagrp -modify group attr key ... [-sys system] For keylist attributes that have values defined, only the following operations are allowed. hagrp -modify group attr -add key ... [-sys system] hagrp -modify group attribute -insert index key ... [-sys system] You can use the -insert option to add one or more values at a given index. You must enter a valid integer for index that can range from 1 to the maximum number of values that exist for the key. hagrp -modify group attr -delete key ... [-sys system] hagrp -modify group attr -delete -keys [-sys system] ASSOCIATION   Use the following command only when the attribute has no value:hagrp -modify group attr {key value} ... [-sys system] For association attributes that have values defined, only the following operations are allowed. hagrp -modify group attr -add {key value} ... [-sys system] hagrp -modify group attr -update {key value} ... [-sys system] hagrp -modify group attr -delete key ... [-sys system] hagrp -modify group attr -delete -keys [-sys system]

EXAMPLES

To online group db_grp on system mars01, enter:

     # hagrp -online db_grp -sys mars01

From a script, to use the -wait option to direct the hagrp command to block until the service group db_grp comes ONLINE on system mars01, enter:

     # hagrp -wait db_grp State ONLINE -sys mars01

man page of halogin

halogin - utility that enables users to authenticate themselves in secure or non-secure VCS environments for the purpose of executing VCS commands

SYNOPSIS

halogin username [password]
halogin -endsession host
halogin -endallsessions
halogin -help

DESCRIPTION

The halogin command line utility provides users the means to authenticate themselves in VCS cluster environments, which may be secure or non-secure. A secure cluster uses Symantec Product Authentication Service utilities, while a non-secure cluster does not.
Once authenticated on a host, VCS grants users authorization to use VCS commands at a predetermined privilege level. The privilege level specifies that a VCS user can perform certain operations (read, write, or execute) on certain objects (systems, groups, or resources).
The halogin command stores the encrypted authentication information in the user’s local home directory. The user may enter subsequent commands without having to login and enter a password until the credential expires.
The Symantec Product Authentication Service utilities combined with the VCS interfaces (the command line and graphical user interfaces) use a hierarchy of brokers to certify VCS users and issue a credential. Short term credentials, called user credentials, last twenty-four hours. Long term credentials, called service credentials, last two years.
VCS user privilege levels include:

* Guest:
	Has read-only access to the configuration, that is, the capability to display and list information.
* Operator:
	Has read-execute access to the configuration, that is, the capability to perform operations to take objects online and offline
* Administrator:
	Has read-write-execute access to the configuration, that is, full access with the capability to change the configuration
Users need to set the following environment variables to enable the use of halogin in a secure environment. In a non-secure environment, only VCS_HOST need be set.
* VCS_HOST
	set to the name of the host where the VCS engine is running.
* VCS_DOMAIN
	set to the name of the domain to which the user belongs.
* VCS_DOMAINTYPE
	set to the type of the VxSS domain to which the user belongs: unixpwd, nt, nis, nisplus, or vx. If this variable is not set, the domain type defaults to "vx".

OPTIONS

username [password]
	Log in as username with the password password. The user must have set the appropriate environment variables, depending on whether the cluster runs in a secure or non-secure mode. If password is not supplied, halogin interactively prompts for it.
-endsession host
	Delete the halogin session credentials on host where the commands are run.
-endallsessions
	Delete halogin session credentials on all hosts.
-help	Display options available for halogin.

FILES

$HOME/.VRTSat - Directory where user credentials are stored (secure cluster environment only).
$HOME/.vcspwd - File containing remembered session logins.

man page of haconf

haconf - allow or prevent dynamic changes to the VCS configuration file

SYNOPSIS

haconf -makerw
haconf -dump [-makero]
haconf -help

AVAILABILITY

VRTSvcs

DESCRIPTION

The haconf command enables dynamic changes to a VCS cluster. This includes adding and deleting objects, adding, deleting and modifying attributes, and writing them back to disk.
The configuration file is read-only (by default) upon starting a VCS server on a system. If the VCS server exits without saving the configuration, the configuration is not stale. Use the haconf command to enable modifications to the configuration while VCS is running.

OPTIONS

-makerw	Change VCS to read-write mode, after which changes to the configuration can be made while VCS is running. The configuration must be written back to disk and made read-only by specifying the -dump and -makero options. Otherwise, when VCS stops and restarts later the configuration changes are not effective.If you define the value of BackupInterval cluster attribute, then VCS backs up the configuration files periodically as .autobackup files.
-dump [-makero]
	Write the configuration to disk. -makero changes the VCS mode to read-only.
-help	Display information about this command.

EXAMPLES

To dynamically add a new system to a group’s SystemList in the configuration, use the following commands:

     # haconf -makerw
     # hagrp -modify group1 SystemList -add sysa 1
     # haconf -dump -makero

man page of hauser

hauser - add, modify, delete, or display VCS users

SYNOPSIS

hauser -add username [-priv Administrator | Operator [-group group(s)]]
hauser -addpriv username Administrator | Operator | Guest [-group group(s)]
hauser -delpriv username Administrator | Operator | Guest [-group group(s)]
hauser -addpriv groupname AdministratorGroup | OperatorGroup [-group group(s)]
hauser -delpriv groupname AdministratorGroup | OperatorGroup [-group group(s)]
hauser -update username
hauser -delete username
hauser -display [username]
hauser -list
hauser -help

AVAILABILITY

VRTSvcs

DESCRIPTION

The hauser command adds users to the VCS configuration. After being added, users can monitor and administer VCS from the GUI. Before users can be added, the configuration must first be set to read-write mode. After changes have been made to a user account, the configuration should be reset to read-only mode. In secure clusters, where Symantec Product Authentication Service is configured (SecureClus==1), operating system users can be assigned to an operating system level user group and that group can be assigned VCS privileges. For example the OS group, OSusers1, can be assigned AdministratorGroup privileges for all groups or a specified set of groups.

OPTIONS

-add username [-priv Administrator | Operator [-group group(s)]]
	Add a user to the VCS configuration. The user can be added with privileges. For example, \(oqhauser -add tom -priv Administrator -group grp1\(cq would add "tom" as the Group Administrator for group grp1. If you configured the cluster to use Symantec Product Authentication Service for security, then you can also add a user with Guest privilege to the VCS configuration as follows: -add username [-priv Administrator | Operator | Guest [-group group(s)]]
-addpriv username Administrator | Operator | Guest [-group group(s)]
	Adds privileges to the user username. For example, \(oqhauser -addpriv tom Administrator -group grp1 grp2\(cq would make "tom" the Group Administrator for groups grp1 and grp2. \(oqhauser -addpriv harry Operator\(cq would make "harry" the Cluster Operator.
-delpriv username Administrator | Operator | Guest [-group group(s)]
	Deletes the specified privileges of the user username. For example, \(oqhauser -delpriv tom Administrator -group grp1\(cq would remove "tom" from the Group Administrator of group grp1.
-addpriv groupname AdministratorGroup | OperatorGroup [-group group(s)]
	Adds specified privileges (Group Administrator or Group Operator) to the group of operating system users, groupname.For example, \(oqhauser -addpriv orausers AdministratorGroup -group grp1\(cq adds the specified privileges (Group Administrator or Group Operator) to the group of operating system users,groupname.
-delpriv groupname AdministratorGroup | OperatorGroup [-group group(s)]
	Deletes the specified privileges (Group Administrator or Group Operator) from the group of operating system users, groupname.For example, \(oqhauser -delpriv orausers AdministratorGroup -group grp1\(cq removes the Group Administrator privileges for group grp1 from all users in the operating system group orausers.
-update username
	Prompt a change of password for the existing user. Not available if SecureClus==1.
-delete username
	Delete a user from the list of registered users.
-display [username]
	Displays a list of users and its privileges in a formatted output. If a user username is specified, it displays the privileges for that user.
-list	Displays a list of all users on the cluster.

man page of haagent

haagent - administer agents and processes that manage VCS resources

SYNOPSIS

haagent -start agent -sys system
haagent -stop agent [-force] -sys system                
haagent -display [agent(s)] [-attribute attribute(s)]
haagent -dumpffdc agent -sys system
haagent -list [conditional(s)]
haagent -value agent                    attr
haagent [-help [-list]]

AVAILABILITY

VRTSvcs

DESCRIPTION

The haagent command starts, stops, displays, and lists VCS agents. See NOTES for how to specify "-" and "%" characters in the command line.

OPTIONS

-start agent -sys system
	Manually start an agent on the specified system. This is required only if the agent is stopped. Otherwise, the VCS server automatically starts agents.
-stop agent [-force] -sys system
	Manually stop an agent on the specified system. Use the -force option to specify that the service groups continue to run. The -force option stops the agent even if the resources for the agent are online. You can use the -force option when you want to upgrade an agent without taking its resources offline.
-display [agent(s)] [-attribute attribute(s)]
	Display information about all agents or about a specified agent. Use the -attribute option to specify the display of a resource attribute. The command displays agent information for the local system if a system is not specified.
-dumpffdc agent -sys system
	The agent dumps the First Failure Data Capture (FFDC) logs for the specified agent to the /var/VRTSvcs/diag/agents/type folder on the specified system.If the agent encountered some problem and if the debug logging was not turned on, these FFDC logs can be used for root-cause analysis.
-list [conditional(s)]
	Displays a list of agents whose values match given conditional statement(s). Conditional statements can take three forms: Attribute=Value, Attribute!=Value, Attribute=~Value. Multiple conditional statements imply AND logic. If no conditional statement is specified, all agents in the cluster are listed.
-value agent attr
	The -value option provides the value of a single agent attribute. For example, "hatype -value Mount Running" displays the value of the Running attribute for the Mount agent. The -value option is used instead of the -display option when one specific attribute value is needed rather than a table of many attribute values.
[-help [-list]]
	Displays information about using haagent. The -list option provides list specific help.

NOTES

The -start and -stop options enable you to debug custom agents without having to start and stop the VCS server.
When using the command to specify or modify an attribute’s value that begins with a dash ("-"), precede the value with a percent sign ("%"). For example, specify -y as %-y. Likewise, precede a value that starts with a percent sign with another percent sign.