- Sun Cluster 3.0 Series: Guide to Installation—Part 2
- Major Resources
- Sun Cluster 3.0 Software
- Install SC 3.0 On First Cluster Node—Without Reboot
- Identify the Device ID (DID) on the First Cluster Node
- Verify DID is Available on Each Additional Cluster Node)
- Install SC 3.0 Patches on the First Cluster Node
- Verify the Install Mode is Enabled
- Install SC 3.0 on Additional Cluster Nodes— Without Reboot
- Install SC 3.0 Patches on Additional Cluster Nodes
- Establish the SC 3.0 Quorum Device - First Cluster Node Only
- Configure Additional Public Network Adapters - NAFO
- Configure ntp.conf on Each Cluster Node
- Verify /etc/nsswitch Entries
- Update Private Interconnect Addresses on All Cluster Nodes
- Add Diagnostic Toolkit
Section 2.4: Install SC 3.0 Patches on the First Cluster Node
At this time, continue to install all required Sun Cluster 3.0 U3 patches on the first cluster node. This node should already be in single-user mode. In this section, after verifying patches have been applied, you will reboot the first cluster node, placing it back into multi-user mode.
For local (manual) installations, obtain all required SC 3.0 U3 patches (Solaris 8 OE). We recommend accessing SunSolveSM Online. To do this, go to http://sunsolve.Sun.com and click the Patches option on the left side column. Next, select PatchPro, followed by SunCluster, and specify all installed cluster components to generate a list of Sun Cluster Patches.
SunSolve is a contract service from Sun Enterprise Services. It is a good idea to subscribe to this service, especially if you are running a production server.
Key Practice: Create a /PATCHES directory on a dedicated Management Server to store all patches. This enables centralized patch management. For example, the Sun BluePrints™ BPLAB hardware has been configured with a 'master' JumpStart server, which will serve all software binaries and patches, and act as the repository.
Key Practice: Refer to the individual patch README files to review any installation prerequisites before installing patches.
At this time, recall that the SC 3.0 U3 patches were copied to the local /opt directory, and are accessible in single-user mode. Complete the SC 3.0 U3 patch installation on the first cluster node only. Enter the following, on clustnode1:
root@clustnode1# cd /opt/PATCHES/CLUSTER3.0U3 root@clustnode1# patchadd 110648-22 Checking installed patches......
Verify the first patch installs, successfully. Then on the first cluster node, add the next patch:
root@clustnode1# patchadd 111554-09 Checking installed patches......
Verify that all required patches install successfully. Some patches might already be installed, or might fail to install at this time.
Verify that any errors reported did not result in corrupt or missing packages required by the SC 3.0 software.
Review the list of installed patches by entering the following command into the first cluster node:
root@clustnode1# /usr/sbin/patchadd -p
Key Practice: Verify that all patches have been installed correctly by reviewing the patch installation logs, and resolve any installation errors or failures.
After all required patches have been installed successfully, reboot the first cluster node:
root@clustnode1# init 6
The console window displays numerous messages indicating the status of the cluster.
During the reboot process, observe the console window for cluster messages appearing during the kernel and cluster initialization. Verify messages are displayed that indicate the first cluster node is "Booting as part of a cluster," along with additional "NOTICE: CMM: .." messages. At this time, you may ignore WARNING messages that instruct you to load the SunPlex Manager, or Apache software. These packages will be added in the future.