cmrunnode(1m) [hpux man page]

cmrunnode(1m)															     cmrunnode(1m)

NAME

       cmrunnode - run a node in a high availability cluster

SYNOPSIS

       cmrunnode [-v] [node_name...]  [-t | -w none]

DESCRIPTION

       cmrunnode  causes  a node to start its cluster daemon to join the existing cluster.  This command verifies the network configuration before
       causing the node to start its cluster daemon.

       To start a cluster on one of its nodes, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the clus-
       ter configuration file. See access policy in cmquerycl(1m).

       Starting  a node will not cause any active packages to be moved to the new node.  However, if a package is DOWN, has its switching enabled,
       and is able to run on the new node, that package will automatically run there.

       If node_name is not specified, the cluster daemon will be started on the local node and will join the existing cluster.

   Options
       cmrunnode supports the following options:

	      -v   Verbose output will be displayed.

	      -t   Test only. Provide an assessment of the package placement without affecting the current state of the nodes or packages. The	-w
		   option is not required with the -t option as -t does not validate network connectivity, but assumes that all the nodes can meet
		   any external dependencies such as EMS resources, package subnets, and storage.

	      node_name...
		   Start the cluster daemon on the specified node(s).

	      -w none
		   By default network probing is performed to check that the network connectivity is the same as when the cluster was  configured.
		   Any	anomalies are reported before the cluster daemons are started. The -w none option disables this probing. The option should
		   only be used if this network configuration is known to be correct from a recent check.

RETURN VALUE

       cmrunnode returns the following value:

	       0   Successful completion.
	       1   Command failed.

EXAMPLES

       Run the cluster daemon on the current node:

	      cmrunnode

       Run the cluster daemons on node1 and node2:

	      cmrunnode node1 node2

AUTHOR

       cmrunnode was developed by HP.

SEE ALSO

       cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmruncl(1m), cmviewcl(1m), cmeval(1m).

						      Requires Optional Serviceguard Software					     cmrunnode(1m)

cmdeleteconf(1m)														  cmdeleteconf(1m)

NAME

       cmdeleteconf - Delete either the cluster or the package configuration

SYNOPSIS

       cmdeleteconf [-f] [-v] [-c cluster_name] [[-p package_name]...]

DESCRIPTION

       cmdeleteconf  deletes either the entire cluster configuration, including all its packages, or only the specified package configuration.	If
       neither cluster_name nor package_name is specified, cmdeleteconf will delete the local cluster's configuration and all  its  packages.	If
       the  local node's cluster configuration is outdated, cmdeleteconf without any argument will only delete the local node's configuration.	If
       only the package_name is specified, the configuration of package_name in the local cluster is deleted.	If  both  cluster_name	and  pack-
       age_name  are  specified, the package must be configured in the cluster_name, and only the package package_name will be deleted.  cmdelete-
       conf with only cluster_name specified will delete the entire cluster configuration on all the nodes in the cluster, regardless of the  con-
       figuration version.  The local cluster is the cluster that the node running the cmdeleteconf command belongs to.

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

       To delete the cluster configuration, halt the cluster first.  To delete a package configuration you must halt the package first, but you do
       not need to halt the cluster (it may remain up or be brought down).  To delete the package VxVM-CVM-pkg (HP-UX only), you must first delete
       all packages with STORAGE_GROUP defined.

       While  deleting	the cluster, if any of the cluster nodes are powered down, the user can choose to continue deleting the configuration.	In
       this case, the cluster configuration on the down node will remain in place and, therefore, be out of sync with the rest of the cluster.	If
       the powered-down node ever comes up, the user should execute the cmdeleteconf command with no argument on that node to clean up the config-
       uration before doing any other Serviceguard command.

   Options
       cmdeleteconf supports the following options:

	      -f	Force the deletion of either the cluster configuration or the package configuration.

	      -v	Verbose output will be displayed.

	      -c cluster_name
			Name of the cluster to delete. The cluster must be halted already, if intending to delete the cluster.

	      -p package_name
			Name of an existing package to delete from the cluster.  The package must be halted already.   There  should  not  be  any
			packages in the cluster with STORAGE_GROUP defined before having a package_name of VxVM-CVM-pkg (HP-UX only).

RETURN VALUE

       Upon completion, cmdeleteconf returns one of the following values:

	       0   Successful completion.
	       1   Command failed.

EXAMPLES

       The high availability environment contains the cluster, clusterA , and a package, pkg1.

       To delete package pkg1 in clusterA, do the following:

	      cmdeleteconf -f -c clusterA -p pkg1

       To delete the cluster clusterA and all its packages, do the following:

	      cmdeleteconf -f -c clusterA

AUTHOR

       cmdeleteconf was developed by HP.

SEE ALSO

       cmcheckconf(1m), cmapplyconf(1m), cmgetconf(1m), cmmakepkg(1m), cmquerycl(1m).

						      Requires Optional Serviceguard Software					  cmdeleteconf(1m)