InfoScale™ 9.0 Storage Foundation Cluster File System High Availability Configuration and Upgrade Guide - AIX
- Section I. Introduction to SFCFSHA
- Introducing Storage Foundation Cluster File System High Availability
- Section II. Configuration of SFCFSHA
- Preparing to configure
- Preparing to configure SFCFSHA clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring the CP server manually
- Configuring SFCFSHA
- Configuring a secure cluster node by node
- Verifying and updating licenses on the system
- Configuring SFCFSHA clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Performing an automated SFCFSHA configuration using response files
- Performing an automated I/O fencing configuration using response files
- Configuring CP server using response files
- Manually configuring SFCFSHA 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 SFCFSHA cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Section III. Upgrade of SFCFSHA
- Planning to upgrade SFCFSHA
- Preparing to upgrade SFCFSHA
- Upgrading the operating system
- Performing a full upgrade of SFCFSHA using the installer
- Performing a rolling upgrade of SFCFSHA
- Performing a phased upgrade of SFCFSHA
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated SFCFSHA upgrade using response files
- Upgrading Volume Replicator
- Performing post-upgrade tasks
- Planning to upgrade SFCFSHA
- Section IV. Post-configuration tasks
- Section V. Configuration of disaster recovery environments
- Section VI. Adding and removing nodes
- Adding a node to SFCFSHA clusters
- Adding the node to a cluster manually
- Setting up the node to run in secure mode
- Adding a node using response files
- Configuring server-based fencing on the new node
- Removing a node from SFCFSHA clusters
- Adding a node to SFCFSHA clusters
- Section VII. Configuration and Upgrade reference
- Appendix A. Support for AIX Live Update
- Appendix B. Installation scripts
- Appendix C. Configuration files
- Appendix D. Configuring the secure shell or the remote shell for communications
- Appendix E. High availability agent information
- Appendix F. Sample SFCFSHA cluster setup diagrams for CP server-based I/O fencing
- Appendix G. Changing NFS server major numbers for VxVM volumes
- Appendix H. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Using the UDP layer of IPv6 for LLT
- Manually configuring LLT over UDP using IPv6
Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
Beginning with version 7.3.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, filesets, 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 | filesets | All products | Major, minor, Service Pack (SP), Platform Release (PR) | FileConnect |
Maintenance | Fixes, new features | filesets | All products | Maintenance Release (MR), Rolling Patch (RP) | Services and Operations Readiness Tools (SORT) |
Patch | Fixes | filesets | Single product | P-Patch, Private Patch, Public patch | SORT, Support site |
When you install or upgrade using Install Bundles:
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.
Patches can now be detected to prevent upgrade conflict. Patch releases are not offered as a combined release. They are only available from Arctera 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 filesets and patches from different media paths, and merge fileset 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 filesets 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:
9.0 is the base version
9.0.1 is the maintenance version
9.0.1.1000 is the patch version for 9.0.1
9.0.0.1000 is the patch version for 9.0
Base + maintenance:
This integration method can be used when you install or upgrade from a lower version to 9.0.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 9.0.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 9.0 to 9.0.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 9.0.1.100.
Enter the following command:
# installmr -base_path <path_to_base> -patch_path <path_to_patch>
Note:
You can add a maximum of five patches using -patch_path <path_to_patch> -patch2_path <path_to_patch> ... -patch5_path <path_to_patch>