How to Uninstall Sun Cluster Software to Correct Installation Problems
Perform this procedure if the installed node cannot join the cluster, or if you need to correct configuration information, for example, the transport adapters.
Note - If the node has already joined the cluster and is no longer in installation mode (see Step 12 of How to Perform Postinstallation Setup), do not perform this procedure. Instead, go to "How to Uninstall Sun Cluster Software From a Cluster Node" in "Adding and Removing a Cluster Node" in Sun Cluster 3.1 10/03 System Administration Guide.
Attempt to reinstall the node.
You can correct certain failed installations simply by repeating Sun Cluster software installation on the node. If you have already tried to reinstall the node without success, proceed to Step 2 to uninstall Sun Cluster software from the node.
Become superuser on an active cluster member other than the node that you are uninstalling.
From the active cluster member, add the node that you intend to uninstall to the cluster node-authentication list.
# /usr/cluster/bin/scconf -a -T node=nodename
-a Add
-T Specifies authentication options
node=nodename Specifies the name of the node to add to the authentication list
Alternately, you can use the scsetup(1M) utility. See "How to Add a Cluster Node to the Authorized Node List" in "Adding and Removing a Cluster Node" in Sun Cluster 3.1 10/03 System Administration Guide for procedures.
Become superuser on the node you intend to uninstall.
Reboot the node into noncluster mode.
# shutdown -g0 -y -i0 ok boot -x
Uninstall the node.
Run the scinstall command from a directory that does not contain any files that are delivered by the Sun Cluster packages.
# cd / # /usr/cluster/bin/scinstall -r
See the scinstall(1 M) man page for more information.
Reinstall Sun Cluster software on the node.
Refer to Table 2-1 for the list of all installation tasks and the order in which to perform the tasks.
Configuring the Cluster
The following table lists the tasks to perform to configure your cluster. Before you start to perform these tasks, ensure that you completed the following tasks.
Cluster framework installation as described in Installing the Software
Volume manager installation and configuration as described in Installing and Configuring Solstice DiskSuite/Solaris Volume Manager Software or Installing and Configuring VxVM Software
Table 2-4 Task Map: Configuring the Cluster
Task | Instructions |
|---|---|
Create and mount cluster file systems. | |
Configure IP Network Multipathing groups. | How to Configure Internet Protocol (IP) Network Multipathing Groups |
(Optional) Change a node's private hostname. | |
Create or modify the NTP configuration file. | |
(Optional) Install the Sun Cluster module to Sun Management Center software. | Installing the Sun Cluster Module for Sun Management Center Sun Management Center documentation |
Install third-party applications and configure the applications, data services, and resource groups. | Sun Cluster 3.1 Data Service Planning and Administration Guide Third-party application documentation |
How to Add Cluster File Systems
Perform this procedure for each cluster file system that you add.
Caution - Any data on the disks is destroyed when you create a file system. Be sure you specify the correct disk device name. If you specify the wrong device name, you erase data that you might not intend to delete.
If you used SunPlex Manager to install data services, SunPlex Manager might have already created one or more cluster file systems.
Ensure that volume-manager software is installed and configured.
For volume-manager installation procedures, see Installing and Configuring Solstice DiskSuite/Solaris Volume Manager Software or Installing and Configuring VxVM Software.
Become superuser on any node in the cluster.
Tip - For faster file-system creation, become superuser on the current primary of the global device for which you create a file system.
Create a file system.
For a VxFS file system, follow procedures that are provided in your VxFS documentation.
For a UFS file system, use the newfs(1M) command.
# newfs raw-disk-device
The following table shows examples of names for the raw-disk-device argument. Note that naming conventions differ for each volume manager.
Volume Manager
Sample Disk Device Name
Description
Solstice DiskSuite/Solaris Volume Manager
/dev/md/oracle/rdsk/d1
Raw disk device d1 within the oracle diskset
VERITAS Volume Manager
/dev/vx/rdsk/oradg/vol01
Raw disk device vol01 within the oradg disk group
None
/dev/global/rdsk/d1s3
Raw disk device d1s3
On each node in the cluster, create a mount-point directory for the cluster file system.
A mount point is required on each node, even if the cluster file system is not accessed on that node.
Tip - For ease of administration, create the mount point in the /global/device-group directory. This location enables you to easily distinguish cluster file systems, which are globally available, from local file systems.
# mkdir -p /global/device-group/mountpoint
device-group Name of the directory that corresponds to the name of the device group that contains the device
mountpoint Name of the directory on which to mount the cluster file system
On each node in the cluster, add an entry to the /etc/vfstab file for the mount point.
See the vfstab(4) man page for details.
Use the following required mount options.
Note - Logging is required for all cluster file systems.
Solaris UFS logging - Use the global,logging mount options. For use by Oracle Parallel Server/Real Application Clusters RDBMS data files, log files, and control files, also use the forcedirectio mount option. See the mount_ufs(1M) man page for more information about UFS mount options.
Note - The syncdir mount option is not required for UFS cluster file systems.
If you specify syncdir, you are guaranteed POSIX-compliant file system behavior for the write() system call. If a write() succeeds, then this mount option ensures that sufficient space is on the disk.
If you do not specify syncdir, the same behavior occurs that is seen with UFS file systems. When you do not specify syncdir, performance of writes that allocate disk blocks, such as when appending data to a file, can significantly improve. However, in some cases, without syncdir you would not discover an out-of-space condition (ENOSPC) until you close a file.
You see ENOSPC on close only during a very short time after a failover. With syncdir (and POSIX behavior), the out-of-space condition would be discovered before the close.
Solstice DiskSuite trans metadevice or Solaris Volume Manager transactional volume - Use the global mount option only. Do not use the logging mount option.
Note - Solaris Volume Managertransactional-volume logging (formerly Solstice DiskSuite trans-metadevice logging) is scheduled to be removed from the Solaris operating environment in an upcoming Solaris release. Solaris UFS logging provides the same capabilities but superior performance, as well as lower system administration requirements and overhead.
See your Solstice DiskSuite documentation for information about setting up trans metadevices, or see your Solaris Volume Manager documentation for information about setting up transactional volumes.
VxFS logging - Use the global, log mount options. See the VxFS mount_vxfs man page and "Administering Cluster File Systems Overview" in Sun Cluster 3.1 10/03 System Administration Guide for more information about VxFS mount options.
To automatically mount the cluster file system, set the mount at boot field to yes.
Ensure that, for each cluster file system, the information in its /etc/vfstab entry is identical on each node.
Ensure that the entries in each node's /etc/vfstab file list devices in the same order.
Check the boot order dependencies of the file systems.
For example, consider the scenario where phys-schost-1 mounts disk device d0 on /global/oracle, and phys-schost-2 mounts disk device d1 on /global/oracle/logs. With this configuration, phys-schost-2 can boot and mount /global/oracle/logs only after phys-schost-1 boots and mounts /global/oracle.
On any node in the cluster, verify that mount points exist. Also verify that /etc/vfstab file entries are correct on all nodes of the cluster.
# sccheck
If no errors occur, nothing is returned.
From any node in the cluster, mount the cluster file system.
# mount /global/device-group/mountpoint
Note - For VERITAS File System (VxFS), mount the file system from the current master of device-group to ensure that the file system mounts successfully. In addition, unmount a VxFS file system from the current master of device-group to ensure that the file system unmounts successfully.
On each node of the cluster, verify that the cluster file system is mounted.
You can use either the df(1M) or mount(1M) command to list mounted file systems.
Note - To manage a VxFS cluster file system in a Sun Cluster environment, run administrative commands only from the primary node on which the VxFS cluster file system is mounted.
Configure IP Network Multipathing groups.
Go to How to Configure Internet Protocol (IP) Network Multipathing Groups.