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
Performing the upgrade
If you plan to upgrade the operating system, perform the following steps:
Note:
On a Cross replication VVR or CVR environment, full upgrade is not supported. Perform a rolling upgrade.
To upgrade the operating system
- Rename the
/etc/llttab
file to prevent LLT from starting automatically when the node starts:# mv /etc/llttab /etc/llttab.save
- Create
install-db
file to prevent VxVM daemons or processes from starting automatically when the node starts.# touch /etc/vx/reconfig.d/state.d/install-db
- Upgrade the operating system on all nodes in the cluster.
For instructions, see the operating system documentation.
- If you upgraded the operating system, restart the nodes if required:
# shutdown -r now
- After the system restarts, rename the
/etc/llttab
file to its original name:# mv /etc/llttab.save /etc/llttab
- Enable VxVM to start after system restarts.
# rm /etc/vx/reconfig.d/state.d/install-db
To perform the upgrade
- Log in as superuser.
- Insert the appropriate media disc into your system's DVD-ROM drive.
- If volume management software is running on your system, the software disc automatically mounts as /mnt/cdrom.
If volume management software is not available to mount the CD-ROM, you must mount it manually, enter:
# mkdir -p /mnt/cdrom # mount -V cdrfs -o ro /dev/cd0 /mnt/cdrom
- Change to the top-level directory on the disc:
# cd /mnt/cdrom
- Verify there are no VxFS file systems mounted on the nodes being upgraded:
# mount | grep vxfs
- Unconfigure the lmx module on all nodes in the cluster.
# /etc/init.d/lmx.rc stop
- Start the upgrade from any node in the cluster. Enter the following command, and then press y to upgrade the cluster configuration.
# ./installer -upgrade
- You are prompted to enter the system names (in the following example, "sys1" and "sys2") on which the software is to be upgraded. Enter the system name or names and then press Return.
Enter the system names separated by spaces: [q, ?] sys1 sys2
- During the initial system check, the installer verifies that communication between systems has been set up.
If the installer hangs or asks for a login password, you have the option to let the installer configure SSH or RSH communications between the systems. If you choose to allow this configuration, select the communication type and provide the root passwords for each system.
- At the prompt, specify whether you accept the terms of the End User License Agreement (EULA).
Do you agree with the terms of the End User License Agreement as specified in the EULA/en/EULA_ENTERPRISE_Ux_9.0.pdf file present on media? [y,n,q,?] y
- The installer displays the following question before the installer stops the product processes if the current cluster is secured and version is prior to 6.2.:
Do you want to grant read access to everyone? [y,n,q,?]
To grant read access to all authenticated users, type y.
To grant usergroup specific permissions, type n.
Do you want to provide any usergroups that you would like to grant read access?[y,n,q,?]
To specify usergroups and grant them read access, type y
To grant read access only to root users, type n. The installer grants read access read access to the root users.
Note:
Separate the usergroup names with spaces. To grant read access to a usergroup on a specific node, specify usergroup as <usergroup>@<node_name>. You can also specify usergroups here and create them later.