6.1 Administering the Cluster Overview

6.1.1 How to Change the Cluster Name

If necessary, you can change the cluster name after initial installation.

1. Become superuser on a node in the cluster.

2. Enter the scsetup(1M) utility.

   # scsetup

   The Main Menu appears.

3. To change the cluster name, enter 6 (Other cluster properties).

   The Other Cluster Properties menu appears.

4. Make your selection from the menu and follow the onscreen instructions.

6.1.1.1 Example--Changing the Cluster Name

The following example shows the scconf(1M) command generated from the scsetup utility to change to the new cluster name, dromedary.

# scconf -c -C cluster=dromedary

6.1.2 How to Map Node ID to Node Name

During Sun Cluster installation, each node is automatically assigned a unique node ID number. The node ID number is assigned to a node in the order in which it joins the cluster for the first time; once assigned, the number cannot be changed. The node ID number is often used in error messages to identify which cluster node the message concerns. Use this procedure to determine the mapping between node IDs and node names.

You do not need to be superuser to list configuration information.

1. Use scconf(1M) to list the cluster configuration information.

   % scconf -pv | grep "Node ID"

6.1.2.1 Example--Mapping the Node ID to the Node Name

The following example shows the node ID assignments

% scconf -pv | grep "Node ID"
	(phys-schost-1) Node ID:																				1
	(phys-schost-2) Node ID:																				2
	(phys-schost-3) Node ID:																				3

6.1.3 How to Work With New Cluster Node Authentication

Sun Cluster enables you to determine if new nodes can add themselves to the cluster and with what type of authentication. You can permit any new node to join the cluster over the public network, deny new nodes from joining the cluster, or indicate a specific node that can join the cluster. New nodes can be authenticated by using either standard UNIX or Diffie-Hellman (DES) authentication. If you select DES authentication, you must also configure all necessary encryption keys before a node can join. See the keyserv(1M) and publickey(4) man pages for more information.

1. Become superuser on a node in the cluster.

2. Enter the scsetup(1M) utility.

   # scsetup

   The Main Menu appears.

3. To work with cluster authentication, enter 5 (New nodes).

   The New Nodes menu appears.

4. Make your selection from the menu and follow the onscreen instructions.

6.1.3.1 Examples--Preventing New Machines From Being Added to the Cluster

The following example shows the scconf(1M) command generated from the scsetup utility that would prevent new machines from being added to the cluster.

# scconf -a -T node=.

6.1.3.2 Examples--Permitting All New Machines to Be Added to the Cluster

The following example shows the scconf command generated from the scsetup utility that would enable all new machines to be added to the cluster.

# scconf -r -T all

6.1.3.3 Examples--Specifying a New Machine to Be Added to the Cluster

The following example shows the scconf command generated from the scsetup utility to enable a single new machine to be added to the cluster.

# scconf -a -T node=phys-schost-4

6.1.3.4 Examples--Setting the Authentication to Standard UNIX

The following example shows the scconf command generated from the scsetup utility to reset to standard UNIX authentication for new nodes joining the cluster.

# scconf -c -T authtype=unix

6.1.3.5 Examples--Setting the Authentication to DES

The following example shows the scconf command generated from the scsetup utility to use DES authentication for new nodes joining the cluster.

# scconf -c -T authtype=des

When using DES authentication, you need to also configure all necessary encryption keys before a node can join the cluster. See the keyserv(1M) and publickey(4) man pages for more information.

6.1.4 How to Reset the Time of Day in a Cluster

Sun Cluster uses the Network Time Protocol (NTP) to maintain time synchronization between cluster nodes. Adjustments in the cluster occur automatically as needed when nodes synchronize their time. See the Sun Cluster 3.0 Concepts document and the Network Time Protocol User's Guide for more information.

When using NTP, do not attempt to adjust the cluster time while the cluster is up and running. This includes using the date(1), rdate(1M), or xntpdate(1M) commands interactively or within cron(1M) scripts.

1. Become superuser on a node in the cluster.

2. Shut down the cluster.

   # scshutdown -g0 -y

3. Boot each node into non-cluster node.

   ok boot -x

4. On a single node, set the time of day by running the date(1) command.

   # date HHMMSS

5. On the other machines, synchronize the time to that node by running the rdate(1M) command.

   # rdate hostname

6. Boot each node to restart the cluster.

   # reboot

7. Verify that the change took place on all cluster nodes.

   On each node, run the date(1M) command.

   # date

6.1.5 How to Enter the OpenBoot PROM (OBP) on a Node

Use this procedure if you need to configure or change OpenBoot PROM settings.

1. Connect to the terminal concentrator port.

   # telnet tc_name tc_port_number

   tc_name

   Specifies the name of the terminal concentrator.

   tc_port_number

   Specifies the port number on the terminal concentrator. Port numbers are configuration dependent. Typically, ports 2 and 3 (5002 and 5003) are used for the first cluster installed at a site.

2. Shut down the cluster node gracefully by using the scswitch(1M) command to evacuate any resource or disk device groups and then shutdown(1M) to bring the node to the OBP prompt.

   # scswitch -S -h node # shutdown -g 0 -y

3. Send a break to the node.

   telnet> send brk

4. Execute the OpenBoot PROM commands.