Sun Microsystems, Inc.
spacerspacer
spacer www.sun.com docs.sun.com |
spacer
black dot
 
 
7.  Administering the Cluster Administering the Cluster Overview How to Work With New Cluster Node Authentication  Previous   Contents   Next 
   
 

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=.

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

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

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

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

Note - 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.


ProcedureHow 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.1 10/03 Concepts Guide document and the Network Time Protocol User's Guide for more information.


Caution! Caution - 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 xntpd(1M) commands interactively or within cron(1M) scripts.


  1. Become superuser on any node in the cluster.

  2. Shut down the cluster to the OBP prompt.
    # 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

ProcedureHow 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 -g0 -y -i0


    Caution! Caution - Do not use send brk on a cluster console to shut down a cluster node. If you use send brk and then type go at the OBP prompt to reboot, the node will panic. This functionality is not supported within a cluster.


  3. Execute the OBP commands.

ProcedureHow to Change the Private Hostname

Use this procedure to change the private hostname of a cluster node after installation has been completed.

Default private hostnames are assigned during initial cluster installation. The default private hostname takes the form clusternode<nodeid>-priv, for example: clusternode3-priv. You should only change a private hostname if the name is already in use in the domain.


Caution! Caution - Do not attempt to assign IP addresses to new private hostnames. The clustering software assigns them.


  1. Disable, on all nodes in the cluster, any Data Service resources or other applications that might cache private hostnames.
    # scswitch -n -j resource1, resource2

    Include the following in the applications you disable.

    • HA-DNS and HA-NFS services, if configured.

    • Any application which has been custom configured to use the private hostname.

    • Any application which is being used by clients over the private interconnect.

    See the scswitch(1M) man page and theSun Cluster 3.1 Data Service Planning and Administration Guide for information about using the scswitch command.

  2. Bring down the Network Time Protocol (NTP) daemon on each node of the cluster.

    See the xntpd(1M) man page for more information about the NTP daemon.
    # /etc/init.d/xntpd stop

  3. Run the scsetup(1M) utility to change the private hostname of the appropriate node.

    It is only necessary to do this from one of the nodes in the cluster.


    Note - When selecting a new private hostname, be sure the name is unique to the cluster node.


  4. Select 5, Private Hostnames, from the Main Menu.

  5. Select 1, Change a Private Hostname, from the Private Hostnames Menu.

    Answer the questions when prompted. You will be asked the name of the node whose private hostname is being changed (clusternode<nodeid>-priv), and the new private hostname.

  6. Flush the name service cache.

    Do this on each node in the cluster. This prevents the cluster applications and data services from trying to access the old private hostname.
    # nscd -i hosts

  7. Edit the ntp.conf file on each node to change the private hostname to the new one.

    Use whatever editing tool you prefer.

    If this is done at install time, also remember to remove names for nodes which are configured; the default template comes pre-configured with eight nodes. Typically, the ntp.conf file will be identical on each cluster node.

  8. Verify that you can successfully ping the new private hostname from all cluster nodes.

  9. Restart the NTP daemon.

    Do this on each node of the cluster.
    # /etc/init.d/xntpd start

  10. Enable all Data Service resources and other applications that were disabled in Step 1.
    # scswitch -e -j resource1, resource2

    See the scswitch(1M) man page and theSun Cluster 3.1 Data Service Planning and Administration Guide for information about using the scswitch command.

 
 
 
  Previous   Contents   Next