cmcheckconf man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

cmcheckconf(1m)						       cmcheckconf(1m)

NAME
       cmcheckconf  -  check  high  availability  cluster configuration and/or
       package configuration files

SYNOPSIS
       cmcheckconf [-v] [[-k|-K] -C cluster_ascii_file]
       [[-p pkg_reference_file] | [-P pkg_ascii_file]...]

DESCRIPTION
       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, the cmcheckconf command will compare the config‐
       uration 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 not	neces‐
       sary  to	 halt  either  the  cluster  or any of the packages to run the
       cmcheckconf command.

       Only a superuser, whose effective user ID is zero (see id  (1)  and  su
       (1)), can verify the configuration.

       cmcheckconf  verifies  any  configured  external script program in each
       pkg_ascii_file for the package run and halt function by calling it with
       a  "validate"  parameter.  A  non-zero  return  value from any external
       script program will cause the command to fail.

       If the cluster_ascii_file specifies a quorum server as the cluster tie-
       breaker service, the quorum server must be running and all nodes in the
       cluster configuration must be authorized to access it. If more than one
       IP  address  is specified for the quorum server, the quorum server must
       be reachable from all configured nodes through all  the	IP  addresses.
       Otherwise the cmcheckconf command will fail.

       If the cluster_ascii_file specifies the lock lun devices as the cluster
       tie breaking service, all nodes must be	accessing  the	same  physical
       device. The lock lun device file must be a block device file. The clus‐
       ter must be down before you can modify a cluster tie-breaking service.

   Options
       cmcheckconf supports the following options:

	      -v	Verbose output will be displayed.

	      -k	Using the -k option means that cmcheckconf only checks
			disk  connectivity  to	the  LVM volume group that are
			identified in the ASCII file.  This  option  does  not
			exist  on  Linux.  Omitting the -k option (the default
			behavior) means that cmcheckconf tests the  connectiv‐
			ity of all LVM volume groups on all the cluster nodes.
			Using -k can result in significantly faster  operation
			of  the	 command.  -k must be used with -C and can not
			be used with -K

	      -K	Using the -K option means that cmcheckconf only checks
			disk  connectivity for cluster lock volume groups. For
			all other LVM volume groups no	connectivity  will  be
			checked.  This	option does not exist on Linux.	 Omit‐
			ting the -K option (the default behavior)  means  that
			cmcheckconf  tests  the connectivity of all LVM volume
			groups on all the cluster nodes. Using -K  can	result
			in  significantly faster operation of the command.  -K
			can be used only when cluster  is  already  configured
			and is used with -C -K can not be used with -k.

	      -C cluster_ascii_file
			Name  of the cluster ASCII file to use.	 This file can
			be created by either the cmquerycl command  or	cmget‐
			conf  command.	 See  cmquerycl(1m)  or cmgetconf(1m).
			This is a required parameter if the cluster has	 never
			been  configured  before.  If not specified, the local
			cluster configuration is used.

	      -P pkg_ascii_file...
			Name of the package configuration file(s) to  use.   A
			package	 configuration template file can be created by
			using the cmmakepkg command and must be customized  to
			include	 specific  information	for  the package.  See
			cmmakepkg(1m).	A configuration file for  an  existing
			package	 can  be generated by using the cmgetconf com‐
			mand. See cmgetconf(1m).  Once a package configuration
			file  is  generated  from  the	existing configuration
			using cmgetconf, it can be  modified  to  reflect  the
			desired changes for that package.  The package config‐
			uration file will be scanned for the purpose of	 vali‐
			dation.

	      -p  pkg_reference_file
			Name of the file containing a list of package configu‐
			ration file(s) to be used.  This file may be necessary
			if  the number of pkg_ascii_file names given with mul‐
			tiple -P options do not fit on the command line.  This
			option cannot be used with the -P option.

RETURN VALUE
       Upon completion, cmcheckconf returns one of the following values:

	       0   Successful completion.
	       1   Command failed.

EXAMPLES
       The  high availability environment contains an ASCII cluster configura‐
       tion file, and two packages, pkg1 and pkg2, specified  in  ASCII	 files
       pkg1.config and pkg1.config.

       To  verify  the cluster configuration and package files, do the follow‐
       ing:

	      cmcheckconf -C clusterA.config -P pkg1.config -P pkg2.config

       To verify the cluster configuration while restricting the  connectivity
       check to the volume groups specified in the clusterA.config file,

	      cmcheckconf -k -C clusterA.config -P pkg1.config -P pkg2.config

       To  verify the cluster configuration while restricting the connectivity
       check to the cluster lock volume groups,

	      cmcheckconf -K -C clusterA.config -P pkg1.config -P pkg2.config

       To specify a long list of package configuration files do the following:

	      cmcheckconf -C clusterA.config -p myfile

       where myfile contains:

	      pkg1.config
	      pkg2.config
	      pkg3.config

       The cluster is up and running, with both packages pkg1, pkg2 running as
       well.   The package configuration file pkg1.config contains the changes
       to the package pkg1.  To verify the package configuration changes  made
       for pkg1, do the following:

		     cmcheckconf -P pkg1.config

AUTHOR
       cmcheckconf was developed by HP.

SEE ALSO
       cmapplyconf(1m),	   cmdeleteconf(1m),   cmgetconf(1m),	cmmakepkg(1m),
       cmquerycl(1m).

		    Requires Optional Serviceguard Software    cmcheckconf(1m)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net