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

| Previous Contents Index Next
2. Chapter 6 # Starting and Stopping Services, Nodes, and Clusters This chapter describes how to stop and start the Foundation Services, a node, or a cluster. This chapter contains the following sections: Stopping and Restarting the Foundation Services Stopping and Restarting Daemon Monitoring Shutting Down and Restarting a Node Shutting Down and Restarting a Cluster Triggering a Switchover Recovering a Cluster ## Stopping and Restarting the Foundation Services Maintenance on a peer node can disrupt communication between this node and services and applications running on other peer nodes. During maintenance, you must isolate a node from the cluster by starting the node without the Foundation Services. After maintenance, reintegrate the node into the cluster by restarting the Foundation Services. ### To Start a Node Without the Foundation Services Log in as superuser to the node on which you want to stop the Foundation Services. Create the `not_configured` file on the node:
       # touch /etc/opt/SUNWcgha/not_configured
3. Reboot the node:
       # init 6
4. The node restarts without the Foundation Services running. If the node is the master node, this procedure causes a failover. Verify that the Foundation Services are not running
       # pgrep -x nhcrfsd
3. If the Foundation Services have been stopped, no process identifier should be displayed for the `nhcrfsd` daemon. ### To Restart the Foundation Services Use this procedure to restart the Foundation Services on a node after performing the procedure in To Start a Node Without the Foundation Services. Log in as superuser to the node on which you want to restart the Foundation Services. Check that the `/etc/opt/SUNWcgha/not_configured` file is not present. If the `/etc/opt/SUNWcgha/not_configured` file is present, delete it. Reboot the node:
       # init 6
4. Verify the configuration of the node:
       # nhadm check configuration
5. If the node is configured correctly, the `nhadm` command does not encounter any errors. For information about the `nhadm` command, see the `nhadm`(1M) man page. Verify that the services have started correctly:
       # nhadm check starting
3. If the Foundation Services have started correctly, the `nhadm` command does not encounter any errors. ## Stopping and Restarting Daemon Monitoring Sometimes you need to stop Daemon Monitoring to investigate why a monitored daemon has failed. This section describes how to stop and restart Daemon Monitoring. For information about the causes of daemon failure at startup and runtime, see the Netra High Availability Suite Foundation Services 2.1 6/03 Troubleshooting Guide. ### To Stop Daemon Monitoring Note - Use this procedure with extreme caution. Incorrect editing of the `/etc/inittab` file can lead to major problems on your cluster. This procedure stops the Daemon Monitoring. On reboot, the Daemon Monitoring is not automatically restarted. Log in as superuser to the node on which you want to stop the `nhpmd` daemon. Open the `/etc/inittab` file in a text editor. Delete the string `.HA` from the `rc2.HA` and `rc3.HA` entries shown here.
       s2:23:wait:/sbin/rc2.HA	>/dev/msglog 2<>/dev/msglog </dev/console
       s3:3:wait:/sbin/rc3.HA	>/dev/msglog 2<>/dev/msglog </dev/console
5. This converts these entries back to the original Solaris `rc2` and `rc3` entries. Save and close the `/etc/inittab` file. Reboot the node.
       # init 6
3. The Foundation Services start, and the Solaris and Foundation Services daemons that were monitored are no longer monitored. ### To Restart Daemon Monitoring Note - Use this procedure with extreme caution. Incorrect editing of the `/etc/inittab` file can lead to major problems on your cluster. If Daemon Monitoring was stopped using To Stop Daemon Monitoring, restart Daemon Monitoring as follows: Log in to the node on which you want to restart the Daemon Monitoring. Open the `/etc/inittab` file in a text editor. Paste the string `.HA` in the `rc2` and `rc3` entries of the `/etc/inittab` file. The entries should be as follows:
       s2:23:wait:/sbin/rc2.HA	>/dev/msglog 2<>/dev/msglog </dev/console
       s3:3:wait:/sbin/rc3.HA	>/dev/msglog 2<>/dev/msglog </dev/console
Use the `sync` command, as described in the `sync`(1M) man page. Reboot the node. The Foundation Services start and are monitored by the Daemon Monitor.
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems