cmgetconf(1m)cmgetconf(1m)NAMEcmgetconf - Get cluster or package configuration information
SYNOPSIScmgetconf [-v {0 | 1 | 2}] [[-K] -c cluster_name] [-p package_name]
[output_filename]
cmgetconf [-v {0 | 1 | 2}] [[-K] -c cluster_name] [-P dirname]
cmgetconf [-v {0 | 1 | 2}] [-K]
DESCRIPTIONcmgetconf obtains either the cluster configuration, not including the
package configuration, and with or without the volume group information
(-K option), or the specified package's configuration information (-p
option), and writes to either the output_filename file, or to stdout.
With the -P option, cmgetconf obtains the configuration information for
all packages and writes to the directory specified by dirname. This
command can be run whether the cluster is up or down. If -c , -p , or
-P are not specified, cmgetconf will obtain the local cluster's config‐
uration. Local cluster is the cluster containing the node where the
cmgetconf command is issued. If both cluster_name and package_name are
specified, the package must be configured in cluster_name, and only the
package configuration for package_name will be written to output_file‐
name or to stdout. The dirname parameter is required with the -P
option. If cluster_name is specified with the -P option, the configura‐
tion of all the packages configured in the cluster_name will be written
out to the directory specified by dirname. Each configured package
configuration will be written out to the the specified dirname in a
separate file named by appending the suffix .ascii to the name of the
package. The -K option prevents probing of volume groups, reducing the
time to get the cluster configuration file.
NOTE: When this command is run by an authorized user who is not the
superuser(UID=0), only those entries that match the user running the
command and the node where the command is run are displayed.
To view cluster or package information, a user must either be supe‐
ruser(UID=0), or have an access policy of MONITOR allowed in the clus‐
ter configuration file, or have an access policy of PACKAGE_ADMIN
allowed in one of the cluster package configuration files. See access
policy in cmquerycl (1) or cmmakepkg (1).
To modify the configuration of an existing cluster, the user needs to
have the cluster's corresponding configuration file. To get the cur‐
rent cluster's configuration file, run cmgetconf first. Once created,
the output_filename can be edited to add or delete nodes. The node
configuration information should be retrieved from the cmquerycl com‐
mand. Some cut and paste may be necessary.
To modify the configuration of an existing package, the user needs to
have the package's corresponding configuration file first. cmgetconf
can be used to produce the package configuration file, then edit it to
make the desired modifications, e.g. changing the list of nodes that
can run the package, changing the subnet, etc.
The modified configuration file can then be used in the cmapplyconf
command to update either the cluster configuration or the package con‐
figuration.
Options
cmgetconf supports the following options:
-v 0|1|2 Verbose output will be displayed. The -v option
applies only when cmgetconf is used to obtain package
configuration information. It is ignored if used to
obtain cluster configuration information.
0 (data_only mode) The package configuration file
will include only the configured attribute val‐
ues.
1 (headline mode) The package configuration file
will include the headline description and legal
value for each configured and configurable
attribute for the package.
2 (verbose mode) The package configuration file
will include the full description and legal
value for each configured and configurable
attribute for the package. This is the default.
-c cluster_name
Name of the cluster for which to query cluster infor‐
mation.
-K This option causes the probing of volume groups to be
skipped, reducing the time for the command to com‐
plete. This option is not available for Linux. Note
that if this option is used, cmgetconf will not add
the list of cluster-aware volume groups to the result‐
ing cluster configuration file. You must add the
cluster-aware volume groups to the cluster configura‐
tion file before running cmapplyconf, or use the -K
option of cmapplyconf when applying the generated con‐
figuration file. Failure to do so will result in all
volume groups in the cluster being unusable in pack‐
ages or for the cluster lock.
-p package_name
Name of an existing package for which to query package
information. This option is mutually exclusive to the
-P option.
-P This option will write all package's configuration
information to a specified output_filename. This
option is mutually exclusive to the -p option.
output_filename
If -c and/or -p options are specified, the name of the
file into which cmgetconf will copy cluster or package
configuration information. If this parameter is not
specified, the information will be directed to stdout.
If the -P option is specified, the name of the direc‐
tory into which cmgetconf will copy the configuration
information for all packages. This parameter is
required when -P option is specified.
RETURN VALUE
Upon completion, cmgetconf returns one of the following values:
0 Successful completion.
1 Command failed.
EXAMPLES
The high availability environment contains the cluster, clusterA , and
packages pkg1 and pkg2.
To generate the cluster configuration file for clusterA, and store the
information in clusterA.conf, do the following:
cmgetconf-c clusterA clusterA.conf
To generate the cluster configuration file for clusterA, skipping disk
probing, and store the information in clusterA.config, do the follow‐
ing:
cmgetconf-K -c clusterA clusterA.config
To generate the package configuration file for pkg1, and store the
information in pkg1.conf, do the following:
cmgetconf-c clusterA -p pkg1 pkg1.conf
To generate the package configuration files for all packages in the
cluster, and store the information in the directory /tmp/pkgconfig, do
the following:
mkdir /tmp/pkgconfig
cmgetconf-c clusterA -P /tmp/pkgconfig
The directory /tmp/pkgconfig will contain two files, pkg1.ascii and
pkg2.ascii.
AUTHORcmgetconf was developed by HP.
SEE ALSOcmcheckconf(1m), cmapplyconf(1m), cmdeleteconf(1m), cmquerycl(1m),
cmmakepkg(1m).
Requires Optional Serviceguard Software cmgetconf(1m)
