Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

cmrunnode(1m) [hpux man page]

cmrunnode(1m)															     cmrunnode(1m)

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)

Check Out this Related Man Page

cm(5)								File Formats Manual							     cm(5)

cm - cluster monitor for high availability clusters Remarks Cluster operations require the installation of the optional Serviceguard or Serviceguard Extension for RAC software, which is not included in the standard HP-UX operating system. DESCRIPTION
Serviceguard and Serviceguard Extension for RAC are high availability products which provide an environment such that after a failure of a node, services (applications) can be up and running again on another node within a very short amount of time. In addition, Serviceguard Extension for RAC is the enabling software for the Real Application Clusters (RAC). Working with the basic Serviceguard product, Service- guard Extension for Faster Failover allows configuration of clusters for optimized failover. Commands The following set of commands is used to configure a high availability cluster: cmquerycl(1M) cmmakepkg(1M) cmcheckconf(1M) cmapplyconf(1M) The following commands are used to run or halt a cluster: cmruncl(1M) cmhaltcl(1M) cmrunnode(1M) cmhaltnode(1M) cmviewcl(1M) Once a cluster is formed, the following commands are provided for manual operation on high availability packages: cmrunpkg(1M) cmhaltpkg(1M) cmmodpkg(1M) The following commands are used within a package control script to control the services and networks configured for a package: cmrunserv(1M) cmhaltserv(1M) cmmodnet(1M) A command is provided to aid in migrating from a SwitchOver/UX configuration to a Serviceguard cluster: cmmigrate(1M) This command is not applicable with Serviceguard Extension for RAC. SEE ALSO
Managing Serviceguard. Configuring RAC Clusters with Serviceguard Extension for RAC. Requires Optional Serviceguard Software cm(5)
Man Page

Featured Tech Videos