Comandos básicos hp-service guard

COMANDOS SERVICE GUARD…….07/06/2012.

Table A-1 Serviceguard Commands
Command Description
cfscluster • Configure or unconfigure SG-CFS-pkg, the system multi-node package used for clusters that use the Veritas Cluster File System.
• Start or stop the CVM package for the CFS.
• Get the status of the SG-CFS-pkg package.
Requires selected HP Serviceguard Storage Management Suite Bundle.cfsdgadm • Display the status of CFS disk groups.
• Add shared disk groups to a Veritas Cluster File System CFS cluster configuration, or remove existing CFS disk groups from the configuration.
Serviceguard automatically creates the multi-node package SG-CFS-DG-id# to regulate the disk groups. This package has a dependency on the SG-CFS-pkg created by cfscluster command.
• Activate orde-activate the shared disk groups, clusterwide or on specified node(s).
Requires selected HP Serviceguard Storage Management Suite Bundle.
The cmgetpkgenv command, below, displays information about the environment.
cfsmntadm Add, delete, modify, or set policy on mounted filesystems in a Veritas Cluster File System (CFS) cluster.
Requires selected HP Serviceguard Storage Management Suite Bundle.cfsmount
cfsumount Mount or unmount a Veritas Cluster File System.
The cmgetpkgenv command, below, displays status.
Requires selected HP Serviceguard Storage Management Suite Bundle.
cmapplyconf Verify and apply Serviceguard cluster configuration and package configuration files.
cmapplyconf verifies the cluster configuration and package configuration specified in the cluster_ascii_file and theassociated pkg_ascii_file(s), creates or updates the binary configuration file, called cmclconfig, and distributes it to all nodes. This binary configuration file contains the cluster configuration information as well as package configuration information for all packages specified. This file, which is used by the cluster daemons to manage the entire cluster and package environment, is kept in the/etc/cmcluster directory.
If changes to either the cluster configuration or to any of the package configuration files are needed, first update the appropriate ASCII file(s) (cluster or package), then validate the changes using the cmcheckconf command and then use cmapplyconf again to verify and redistribute the binary file to all nodes. The cluster and package configuration can be modified only whenthe cluster is down. The cluster ASCII file only needs to be specified if configuring the cluster for the first time, or if adding or deleting nodes to the cluster. The package ASCII file only needs to be specified if the package is being added, or if the package configuration is being modified.
cmapplyconf (continued) Run cmgetconf to get either the cluster configuration file or packageconfiguration file whenever changes to the existing configuration are required.
Note that cmapplyconf will verify and distribute cluster configuration or package files. It will not cause the cluster daemon to start or be removed from the cluster configuration. The same kind of processing will apply to the package configuration to determine whether to add or delete package nodes, package subnet, etc. Allpackage configuration changes require the package to be halted.
cmcheckconf Check high availability cluster configuration and/or package configuration files.
cmcheckconf verifies the cluster configuration as specified by the cluster_ascii_file and/or the package configuration files specified by each pkg_ascii_file in the command. If the cluster has already been configured previously, thecmcheckconf command will compare the configuration in the cluster_ascii_file against the previously configuration information stored in the binary configuration file and validates the changes. The same rules apply to the pkg_ascii_file. It is necessary to halt the cluster to run the cmcheckconf command.
cmdeleteconf Delete either the cluster or the package configuration.

cmdeleteconf deletes...