Cluster Server 7.3.1 Configuration and Upgrade Guide - Solaris
- Section I. Configuring Cluster Server using the script-based installer
- I/O fencing requirements
- Preparing to configure VCS clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring VCS
- Configuring a secure cluster node by node
- Verifying and updating licenses on the system
- Configuring VCS clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Section II. Automated configuration using response files
- Performing an automated VCS configuration
- Performing an automated I/O fencing configuration using response files
- Section III. Manual configuration
- Manually configuring VCS
- Configuring LLT manually
- Configuring VCS manually
- Configuring VCS in single node mode
- Modifying the VCS configuration
- Manually configuring the clusters for data integrity
- Setting up disk-based I/O fencing manually
- Setting up server-based I/O fencing manually
- Configuring server-based fencing on the VCS cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Manually configuring VCS
- Section IV. Upgrading VCS
- Planning to upgrade VCS
- Performing a VCS upgrade using the installer
- Tasks to perform after upgrading to 2048 bit key and SHA256 signature certificates
- Performing an online upgrade
- Performing a rolling upgrade of VCS
- Performing a phased upgrade of VCS
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated VCS upgrade using response files
- Upgrading VCS using Live Upgrade and Boot Environment upgrade
- Planning to upgrade VCS
- Section V. Adding and removing cluster nodes
- Adding a node to a single-node cluster
- Adding a node to a single-node cluster
- Adding a node to a multi-node VCS cluster
- Manually adding a node to a cluster
- Setting up the node to run in secure mode
- Configuring I/O fencing on the new node
- Adding a node using response files
- Removing a node from a VCS cluster
- Removing a node from a VCS cluster
- Removing a node from a VCS cluster
- Adding a node to a single-node cluster
- Section VI. Installation reference
- Appendix A. Services and ports
- Appendix B. Configuration files
- Appendix C. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Manually configuring LLT over UDP using IPv6
- Appendix D. Configuring the secure shell or the remote shell for communications
- Appendix E. Installation script options
- Appendix F. Troubleshooting VCS configuration
- Appendix G. Sample VCS cluster setup diagrams for CP server-based I/O fencing
- Appendix H. Reconciling major/minor numbers for NFS shared disks
- Appendix I. Upgrading the Steward process
Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
Beginning with version 6.1, you can easily install or upgrade your systems directly to a base, maintenance, patch level or a combination of multiple patches and packages together in one step using Install Bundles. With Install Bundles, the installer has the ability to merge so that customers can install or upgrade directly to maintenance or patch levels in one execution. The various scripts, packages, and patch components are merged, and multiple releases are installed together as if they are one combined release. You do not have to perform two or more install actions to install or upgrade systems to maintenance levels or patch levels.
Releases are divided into the following categories:
Table: Release Levels
Level | Content | Form factor | Applies to | Release types | Download location |
---|---|---|---|---|---|
Base | Features | packages | All products | Major, minor, Service Pack (SP), Platform Release (PR) | FileConnect |
Maintenance | Fixes, new features | packages | All products | Maintenance Release (MR), Rolling Patch (RP) | Veritas Services and Operations Readiness Tools (SORT) |
Patch | Fixes | packages | Single product | P-Patch, Private Patch, Public patch | SORT, Support site |
When you install or upgrade using Install Bundles:
Veritas InfoScale products are discovered and assigned as a single version to the maintenance level. Each system can also have one or more patches applied.
Base releases are accessible from FileConnect that requires customer serial numbers. Maintenance and patch releases can be automatically downloaded from SORT.
Patches can be installed using automated installers from the 6.0.1 version or later.
Patches can now be detected to prevent upgrade conflict. Patch releases are not offered as a combined release. They are only available from Veritas Technical Support on a need basis.
You can use the -base_path and -patch_path options to import installation code from multiple releases. You can find packages and patches from different media paths, and merge package and patch definitions for multiple releases. You can use these options to use new task and phase functionality to correctly perform required operations for each release component. You can install the packages and patches in defined phases using these options, which helps you when you want to perform a single start or stop process and perform pre and post operations for all level in a single operation.
Four possible methods of integration exist. All commands must be executed from the highest base or maintenance level install script.
In the example below:
7.3.1 is the base version
7.3.1.1 is the maintenance version
7.3.1.1.100 is the patch version for 7.3.1.1
7.3.1.0.100 is the patch version for 7.3.1
Base + maintenance:
This integration method can be used when you install or upgrade from a lower version to 7.3.1.1.
Enter the following command:
# installmr -base_path <path_to_base>
Base + patch:
This integration method can be used when you install or upgrade from a lower version to 7.3.1.0.100.
Enter the following command:
# installer -patch_path <path_to_patch>
Maintenance + patch:
This integration method can be used when you upgrade from version 7.3.1 to 7.3.1.1.100.
Enter the following command:
# installmr -patch_path <path_to_patch>
Base + maintenance + patch:
This integration method can be used when you install or upgrade from a lower version to 7.3.1.1.100.
Enter the following command:
# installmr -base_path <path_to_base> -patch_path <path_to_patch>
Note:
From the 6.1 or later release, you can add a maximum of five patches using -patch_path <path_to_patch> -patch2_path <path_to_patch> ... -patch5_path <path_to_patch>