Storage Foundation and High Availability 7.4.2 Configuration and Upgrade Guide - AIX
- Section I. Introduction to SFHA
- Introducing Storage Foundation and High Availability
- Section II. Configuration of SFHA
- Preparing to configure
- Preparing to configure SFHA clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring the CP server manually
- Configuring CP server using response files
- Configuring SFHA
- Configuring Storage Foundation High Availability using the installer
- Configuring a secure cluster node by node
- Verifying and updating licenses on the system
- Configuring Storage Foundation High Availability using the installer
- Configuring SFHA clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Manually configuring SFHA 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 SFHA cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Performing an automated SFHA configuration using response files
- Performing an automated I/O fencing configuration using response files
- Response file variables to configure server-based I/O fencing
- Section III. Upgrade of SFHA
- Planning to upgrade SFHA
- Preparing to upgrade SFHA
- Upgrading Storage Foundation and High Availability
- Performing a rolling upgrade of SFHA
- Performing a phased upgrade of SFHA
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated SFHA upgrade using response files
- Performing post-upgrade tasks
- Post-upgrade tasks when VCS agents for VVR are configured
- About enabling LDAP authentication for clusters that run in secure mode
- Planning to upgrade SFHA
- Section IV. Post-installation tasks
- Section V. Adding and removing nodes
- Adding a node to SFHA clusters
- Adding the node to a cluster manually
- Adding a node using response files
- Configuring server-based fencing on the new node
- Removing a node from SFHA clusters
- Removing a node from a SFHA cluster
- Removing a node from a SFHA cluster
- Adding a node to SFHA clusters
- Section VI. Configuration and upgrade reference
- Appendix A. Support for AIX Live Update
- Appendix B. Installation scripts
- Appendix C. SFHA services and ports
- Appendix D. Configuration files
- Appendix E. Configuring the secure shell or the remote shell for communications
- Appendix F. Sample SFHA 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
Finishing the phased upgrade
Complete the following procedure to complete the upgrade.
To finish the upgrade
- Verify that the cluster UUID is the same on the nodes in the second subcluster and the first subcluster. Run the following command to display the cluster UUID:
# /opt/VRTSvcs/bin/uuidconfig.pl -clus -display node1 [node2 ...]
If the cluster UUID differs, manually copy the cluster UUID from a node in the first subcluster to the nodes in the second subcluster. For example:
# /opt/VRTSvcs/bin/uuidconfig.pl [-rsh] -clus -copy -from_sys node01 -to_sys node03 node04
- Reboot the node03 and node04 in the second subcluster.
# /usr/sbin/shutdown -r
The nodes in the second subcluster join the nodes in the first subcluster.
- In the
/etc/default/llt
file, change the value of the LLT_START attribute.In the
/etc/default/gab
file, change the value of the GAB_START attribute.In the
/etc/default/vxfen
file, change the value of the VXFEN_START attribute.In the
/etc/default/vcs
file, change the value of the VCS_START attribute.LLT_START = 1 GAB_START = 1 VXFEN_START =1 VCS_START =1
- Start LLT and GAB.
# /etc/init.d/llt.rc start
# /etc/init.d/gab.rc start
- Seed node03 and node04 in the second subcluster.
# gabconfig -x
- On the second half of the cluster, start SFHA:
# cd /opt/VRTS/install
# ./installer -start sys3 sys4
- Check to see if SFHA and High Availability and its components are up.
# gabconfig -a GAB Port Memberships =============================================================== Port a gen nxxxnn membership 0123 Port b gen nxxxnn membership 0123 Port h gen nxxxnn membership 0123
- Run an hastatus -sum command to determine the status of the nodes, service groups, and cluster.
# hastatus -sum -- SYSTEM STATE -- System State Frozen A node01 RUNNING 0 A node02 RUNNING 0 A node03 RUNNING 0 A node04 RUNNING 0 -- GROUP STATE -- Group System Probed AutoDisabled State B sg1 node01 Y N ONLINE B sg1 node02 Y N ONLINE B sg1 node03 Y N ONLINE B sg1 node04 Y N ONLINE B sg2 node01 Y N ONLINE B sg2 node02 Y N ONLINE B sg2 node03 Y N ONLINE B sg2 node04 Y N ONLINE B sg3 node01 Y N ONLINE B sg3 node02 Y N OFFLINE B sg3 node03 Y N OFFLINE B sg3 node04 Y N OFFLINE B sg4 node01 Y N OFFLINE B sg4 node02 Y N ONLINE B sg4 node03 Y N OFFLINE B sg4 node04 Y N OFFLINE
- After the upgrade is complete, start the VxVM volumes (for each disk group) and mount the VxFS file systems.
In this example, you have performed a phased upgrade of SFHA. The service groups were down when you took them offline on node03 and node04, to the time SFHA brought them online on node01 or node02.
Note:
If you want to upgrade the application clusters that use CP server based fencing to version 6.1 and later, make sure that you first upgrade VCS or SFHA on the CP server systems to version 6.1 and later. And then, from 7.0.1 onwards, CP server supports only HTTPS based communication with its clients and IPM-based communication is no longer supported. CP server needs to be reconfigured if you upgrade the CP server with IPM-based CP server configured.