An administrator wants to configure a new3-node PowerHA 7 cluster for 3 instances of an application. Each node will host an instance under normal production mode. The administrator wants a node failover to be based on which cluster node has the most free real memory available. Which standard or user-defined dynamic node priority (DNP) attribute can be used to accomplish this?
After migrating to PowerHA 7 and restarting the cluster for the first time, the following error is reported:
Starting Cluster Services on node: Jessica
This may take a few minutes. Please wait...
Jessica: cl_rshhad exit code = 13, see cspoc.log and/or clcomd.log for more information
What is the most common cause of this error?
A PowerHA 7 cluster is running on two fully virtualized LPARs. An administrator simulates a network failure on the cluster by running the "ifconfig enX down" command on all network interfaces on one node. The resource group moved, and clstat shows the cluster as stable on both nodes. What prevented the resource group from being active on both nodes?
An administrator has a 2-node cluster and has chosen the C-SPOC option to bring a resource group offline. The resource group was stable on the primary node prior taking resource offline, however it has gone into an error state. The administrator corrects the error and issues the clruncmd to continue cluster processing. What will happen to the resource group?
An administrator performed a DARE operation in their cluster configuration. During this operation one of the cluster nodes halted. The node halt was an isolated problem, however, as a result the DARE operation did not complete. When the failed node was re-integrated to the cluster, the following error was received when trying to perform the DARE operation again: cldare: A lock for a Dynamic Reconfiguration event has been detected. Which action will resolve the problem?