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

| Previous Contents Index Next
3. Chapter 1 # Using Cluster Administration Tools and Configuration Files The Foundation Services provide tools and configuration files to administer your cluster environment. Throughout this document, references to a cluster imply the use of a cluster running the Foundation Services. For a description of the cluster environment, see "Cluster Model" in the Netra High Availability Suite Foundation Services 2.1 6/03 Overview. This chapter contains the following sections: Adding Tools to Your Path Using Foundation Services Tools for Cluster Administration Using Solaris Tools for Cluster Administration Using Foundation Services Configuration Files in the Cluster Environment Using Solaris Configuration Files in the Cluster Environment ## Adding Tools to Your Path The Foundation Services tools are located in `/opt/SUNWcgha/sbin`. To include these directories in your path, add them to your `/etc/profile` file. To use some of the Foundation Services tools, you must log in as superuser. To know whether you need to log in as superuser, see the man page of the Foundation Services tool. To add the man pages to your path, see "To Access Man Pages on the Master-Eligible Nodes" in the Netra High Availability Suite Foundation Services 2.1 6/03 Custom Installation Guide. ### To Add the Foundation Services Tools to Your Path Log in to a peer node as superuser. Open the `/etc/profile` file in a text editor. Add the following lines to the file:
       PATH=/opt/SUNWcgha/sbin:$PATH
       export PATH
Save the `/etc/profile` file, and exit the text editor and the shell session. Test the success of this procedure by running a Foundation Services tool at the prompt in a new shell session. For a list of the tools and a reference to their corresponding man pages, see Table 1-1. ## Using Foundation Services Tools for Cluster Administration The following table lists the Foundation Services tools you can use for cluster administration. The table describes the purpose of the tools and provides links to their man pages. To add the man pages to your path, see "To Access Man Pages on the Master-Eligible Nodes" in the Netra High Availability Suite Foundation Services 2.1 6/03 Custom Installation Guide. Table 1-1 Foundation Services Cluster Administration Tools
Tool | Description
--- | ---
`nhadm`(1M) | Verifies cluster configuration, using the following commands: `nhadm check` `nhadm check installation` `nhadm check configuration` `nhadm check starting` Creates the file required for patching shared packages, using the following command: `nhadm confshare` Displays information about node configuration, using the following command: `nhadm display` Copies files fom the master node to the vice-master node. Files listed can be passed as an argument or listed in the data-file file. `nhadm [`-d` data-file] copy [file]` Lists differences between specified nonreplicated files on the master node and vice-master node, using the following command: `nhadm synccheck` Stores differences between specified nonreplicated files on the master node and vice-master node, using the following command: `nhadm syncgen` Lists all possible error messages returned by the `nhadm` command: `nhadm -z`
`nhcmmqualif`(1M) | Qualifies a node as the master node if the node is master-eligible, and if the cluster has no master node.
`nhcmmrole`(1M) | Gets the role of the node. A node can have the following roles: MASTER VICEMASTER IN_CLUSTER OUT_OF_CLUSTER For more information about roles, see the Netra High Availability Suite Foundation Services 2.1 6/03 Glossary.
`nhcmmstat`(1M) | Analyzes the state of a node, using the following commands: `info` `local` `master` `mynode` `potential` `vice` Analyzes the state of a group of nodes, using the following commands: `all` `count` Forces a reload of the `cluster_nodes_table` configuration, using the following command: `reload` Triggers a switchover, using the following command: `so` Qualifies a node, using the following command: `squalif` Exits, using the following commands: `exit` `quit` Displays help information, using the following command: `help`
`nhcrfsadm`(1M) | Authorizes or refuses permission to start replication of the master node to the vice-master node.
`nhenablesync`(1M) | Triggers disk synchronization.
`nhpmdadm`(1M) | Administrates the Daemon Monitor. For more information about the Daemon Monitor, see the `nhpmd`(1M) man page.
## Using Solaris Tools for Cluster Administration The following table lists Solaris tools that you can use for cluster administration. The table describes the purpose of the tools and provides links to their man pages. To add the man pages to your path, see "To Access Man Pages on the Master-Eligible Nodes" in the Netra High Availability Suite Foundation Services 2.1 6/03 Custom Installation Guide. Table 1-2 Solaris Tools Used for Cluster Administration
Tool | Description
--- | ---
`boot`(1M) | Boots a specific node. For an example of using the `boot` command, see To Restart a Cluster.
`format`(1M) | Formats, labels, repairs, and analyzes disks on your system. For more information about using the `format` utility on a cluster, see Using the `format` Utility to Display and Modify the Configuration of a Disk Partition.
`ifconfig`(1M) | Checks and sets a network interface configuration, as described in To Obtain Configuration Information About the Network Interfaces of a Node.
`init`(1M) | Creates processes from information stored in the `/etc/inittab` file. This command can be used to reboot a node. For example, see To Restart the Foundation Services.
`mount`(1M) | Mounts a file system. For an example of using the `mount` command, see To Increase the Size of a Mirrored Data Partition on a Virtual Disk.
`netstat`(1M) | Shows the network status as described in Examining the Routes on a Node.
`patchadd`(1M) | Adds a patch, as described in Chapter 7, Patching Software on the Cluster.
`pgrep`(1) | Finds processes by name and other attributes. For an example of using the `pgrep` command, see To Verify That an `nhcmmd` Daemon Is Running on Each Peer Node.
`pkill`(1M) | Kills processes. For an example of using the `pkill` command, see To Replace Ethernet Cards on a Diskless Node With the DHCP Static Boot Policy.
`ps`(1) | Lists processes. For a list of monitored daemons, see the `nhpmd`(1M) man page.
`reboot`(1M) | Do not use this command. The `reboot` command does not take into account the order in which daemons are to be stopped or started. Incorrect use of the `reboot` command can cause data loss on the master node and error messages on the vice-master node. To reboot a master-eligible node running the Foundation Services, use the `init` command.
`route`(1M) | Adds or removes a route, as described in Examining the Routes on a Node.
`truss`(1) | Traces system calls and signals. For information about using this command, see Stopping and Restarting Daemon Monitoring.
`ufsdump`(1M) | Backs up an entire file system or selected files within a file system. For an example of using this command, see To Increase the Size of a Mirrored Data Partition on a Virtual Disk.
`ufsrestore`(1M) | Restores files from backup media created with the `ufsdump` command. For an example of using this command, see To Increase the Size of a Mirrored Data Partition on a Virtual Disk.
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems