|
|||
|
 |
|
  |
|
  |
|
| |||||||||||||||||||||||
Examples--Preventing New Machines From Being Added to the ClusterThe following example shows the scconf command generated from the scsetup utility that would prevent new machines from being added to the cluster.
Examples--Permitting All New Machines to Be Added to the ClusterThe following example shows the scconf command generated from the scsetup utility that would enable all new machines to be added to the cluster.
Examples--Specifying a New Machine to Be Added to the ClusterThe following example shows the scconf command generated from the scsetup utility to enable a single new machine to be added to the cluster.
Examples--Setting the Authentication to Standard UNIXThe following example shows the scconf command generated from the scsetup utility to reset to standard UNIX authentication for new nodes joining the cluster.
Examples--Setting the Authentication to DESThe following example shows the scconf command generated from the scsetup utility to use DES authentication for new nodes joining the cluster.
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.
|
# scshutdown -g0 -y |
Verify that the node is showing the ok prompt or the Select (b)oot or (i)nterpreter prompt on the Current Boot Parameters screen.
Boot the node in non-cluster mode by using the boot(1M) or the b
command with the -x option. SPARC: ok boot -x
x86:
<<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/
sd@0,0:a
Boot args:
Type b [file-name] [boot-flags] <ENTER> to boot with options
or i <ENTER> to enter boot interpreter
or <ENTER> to boot with defaults
<<< timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b -x |
On a single node, set the time of day by running the date
command.# date HHMM.SS
On the other machines, synchronize the time to that node by running
the rdate(1M)
command.# rdate hostname
Boot each node to restart the cluster.# reboot
Verify that the change took place on all cluster nodes.
On each node, run the date command.
# date |
SPARC: How to Enter the OpenBoot PROM (OBP) on a NodeUse this procedure if you need to configure or change OpenBoot PROM settings.
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. |
Shut down the cluster node gracefully by using the scswitch(1M) command to
evacuate any resource or disk device groups and then shutdown.# scswitch -S -h node[,...]
# shutdown -g0 -y -i0
Caution - Do not use send brk on a cluster console
to shut down a cluster node.
Execute the OBP commands.
How to Change the Private HostnameUse 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 - Do not attempt to assign IP addresses to new private hostnames.
The clustering software assigns them.
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 the Sun Cluster Data Services Planning and Administration Guide for Solaris OS for information about using the scswitch command.
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/initd./xntpd.cluster stop |
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.
Select 5, Private Hostnames, from the Main Menu.
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.
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 |
Edit the ntp.conf.cluster 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 sixteen nodes. Typically, the ntp.conf.cluster file will be identical on each cluster node.
Verify that you can successfully ping the new private hostname from all cluster nodes.
Restart the NTP daemon.
Do this on each node of the cluster.
# /etc/initd./xntpd.cluster start |
Enable all Data Service resources and other applications that were disabled
in Step 1.# scswitch -e -j resource1, resource2
See the scswitch man page and the Sun Cluster Data Services Planning and Administration Guide for Solaris OS for information about using the scswitch command.
 Previous Contents Index Next  |