sun.com | docs.sun.com | How To Buy | My Sun | Worldwide Sites |  |

| Previous Contents Index Next
2. ### To Verify That the Reliable Boot Service Is Running Log in to the master node. Determine whether an `in.dhcpd` daemon is running on the node:
       # pgrep -x in.dhcpd
2. If a process identifier is returned, the daemon is running. If a process identifier is not returned, the daemon is not running. To investigate the cause of daemon failure, see the Netra High Availability Suite Foundation Services 2.1 6/03 Troubleshooting Guide. ## Verifying That a Cluster Is Configured Correctly A cluster must meet the criteria outlined in Defining Minimum Criteria for a Cluster Running Highly Available Services. The following procedures describe how to verify that a cluster is configured correctly. ### To Verify That a Cluster Is Configured Correctly Log in to a peer node as superuser. Type:
       # nhadm check
   1. The `nhadm` tool tests whether the Foundation Services and its prerequisite products are installed and configured correctly. If the `nhadm` command encounters an error, it displays a message in the console window. If you receive an error message, perform the following steps: Identify the problem area, diagnose, and correct the problem. For an explanation of the error messages displayed by `nhadm`, type:
          # nhadm -z
3. Rerun the `nhadm check` command, diagnosing and correcting any further errors until all tests pass. For more information, see the `nhadm`(1M) man page. ## Reacting to a Failover When a master node fails over to the vice-master node, a fault has occurred. Even though your cluster has recovered, the fault that caused the failover could have serious implications for the future performance of your cluster. You must treat a failover seriously. After a failover, perform the following procedure. ### To React to a Failover Log in to the failed master node as superuser. Examine the system log files for information about the cause of the failover. For information about log files, see Chapter 2, Accessing and Maintaining Log Files. Verify that the failed master node has been elected as the vice-master node:
       # nhcmmstat -c vice
5. If there is a vice-master node in the cluster, `nhcmmstat` prints information to the console window about the vice-master role. If there is no vice-master node, `nhcmmstat` sends an error code. If there is no vice-master node, investigate why the failed master node is not capable of taking the vice-master role. For information, see the Netra High Availability Suite Foundation Services 2.1 6/03 Troubleshooting Guide. Ensure that you have a valid cluster as described in Defining Minimum Criteria for a Cluster Running Highly Available Services. Run the `nhadm check` command to verify that the node is correctly configured.
       # nhadm check
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems