|
|
Sponsored Content
Operating Systems
HP-UX
MC ServiceGaurd
Post 4927 by alwayslearningunix on Friday 3rd of August 2001 05:23:39 PM
08-03-2001
MC ServiceGuard is still at the forefront of HP-UX's high availability software, it has been developed to the point where (providing hardware behaves itself) it can provide 99.999% availability when spreading a service across two service guarded machines.
It's quite a sophisticated product, providing a double heartbeat between nodes to monitor machine availability in a cluster and has a whole host of cluster wide and node specific configurable parameters - HP's course covers 5 days. It works from the entry level A class server through to the top end Superdome, as well as on workstations (although the reasoning behind it's application there would be somewhat baffling).
The product does not pretend to create fault tolerant machines, I think fault tolerance in the strict sense of the word is something yet to be attained on servers, and the domain of the mainframe - but it does guarantee high availibilty and with most service level agreements providing for scheduled maintenence downtime a high availability cluster that is service guarded can provide a near fault tolerant environment by allowing services to be flipped from node to node as the sectrions of the cluster is worked on for maintenance.
It's a great product, I would recommend learning it. I am on the course next week
Regards.
It's quite a sophisticated product, providing a double heartbeat between nodes to monitor machine availability in a cluster and has a whole host of cluster wide and node specific configurable parameters - HP's course covers 5 days. It works from the entry level A class server through to the top end Superdome, as well as on workstations (although the reasoning behind it's application there would be somewhat baffling).
The product does not pretend to create fault tolerant machines, I think fault tolerance in the strict sense of the word is something yet to be attained on servers, and the domain of the mainframe - but it does guarantee high availibilty and with most service level agreements providing for scheduled maintenence downtime a high availability cluster that is service guarded can provide a near fault tolerant environment by allowing services to be flipped from node to node as the sectrions of the cluster is worked on for maintenance.
It's a great product, I would recommend learning it. I am on the course next week
Regards.
|
|
LEARN ABOUT HPUX
cmruncl
cmruncl(1m) cmruncl(1m) NAME
cmruncl - run a high availability cluster SYNOPSIS
cmruncl [-f] [-v] [-n node_name...] [-t | -w none] DESCRIPTION
cmruncl causes all nodes in a configured cluster or all nodes specified to start their cluster daemons and form a new cluster. To start a cluster, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configuration file. See access policy in cmquerycl(1m). This command should only be run when the cluster is not active on any of the configured nodes. This command verifies the network configu- ration before causing the nodes to start their cluster daemons. If a cluster is already running on a subset of the nodes, the cmrunnode command should be used to start the remaining nodes and force them to join the existing cluster. If node_name is not specified, the cluster daemons will be started on all the nodes in the cluster. All nodes in the cluster must be available for the cluster to start unless a subset of nodes is specified. Options cmruncl supports the following options: -f Force cluster startup without warning message and continuation prompt that are printed with the -n option. -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. -n node_name... Start the cluster daemon on the specified subset of node(s). -w none By default network probing is performed to check that the network connectivity is the same as when the cluster was config- ured. 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 cmruncl returns the following value: 0 Successful completion. 1 Command failed. EXAMPLES
Run the cluster daemon: cmruncl Run the cluster daemons on node1 and node2: cmruncl -n node1 -n node2 AUTHOR
cmruncl was developed by HP. SEE ALSO
cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m). Requires Optional Serviceguard Software cmruncl(1m)