Overview of Administering the Cluster
This section describes how to perform administrative tasks for the entire
global cluster or zone cluster. The following table lists these administrative
tasks and the associated procedures. You generally perform cluster
administrative tasks in the global zone. To administer a zone cluster, at least
one machine that will host the zone cluster must be up in cluster mode. All zone
cluster nodes are not required to be up and running; Oracle Solaris Cluster replays any
configuration changes when the node that is currently out of the cluster rejoins
the cluster.
Note -
By default, power management is disabled so that it does not
interfere with the cluster. If you enable power management for a single-node
cluster, the cluster is still running but it can become unavailable for a few
seconds. The power management feature attempts to shut down the node, but it
does not succeed.
In this chapter, phys-schost# reflects a global-cluster
prompt. The clzonecluster interactive shell prompt is
clzc:schost>.
Table 17 Task List: Administering the Cluster
|
|
Add or remove a node from a cluster
|
|
Change the name of the cluster
|
|
List node IDs and their corresponding node names
|
|
Permit or deny new nodes to add themselves to the cluster
|
|
Change the time for a cluster by using the NTP
|
|
Shut down a node to the OpenBoot PROM ok prompt on a
SPARC based system or to the Press any key to continue
message in a GRUB menu on an x86 based system
|
|
Add or change the private hostname
|
You can also use the Oracle Solaris Cluster Manager browser interface to add a logical
hostname to a global cluster or a zone cluster. Click Tasks, then click Logical
Hostname to start the wizard. For Oracle Solaris Cluster Manager log-in instructions, see How to Access Oracle Solaris Cluster Manager.
|
Put a cluster node in maintenance state
|
|
Rename a Node
|
|
Bring a cluster node out of maintenance state
|
|
Uninstall cluster software from a cluster node
|
|
Add and manage an SNMP Event MIB
|
|
Configure load limits for each node
|
|
Move a zone cluster; prepare a zone cluster for applications, remove a
zone cluster
|
|
|