InfoScale™ 9.0 Cluster Server Configuration and Upgrade Guide - Linux
- 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
- Completing the VCS configuration
- 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 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 YUM
- 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
- About configuring LLT over UDP multiport
- Appendix D. Configuring LLT over TCP
- Manually configuring LLT over TCP using IPv4
- Manually configuring LLT over TCP using IPv6
- Appendix E. Migrating LLT links from IPv4 to IPv6 or dual-stack
- Appendix F. Using LLT over RDMA
- Configuring LLT over RDMA
- Configuring RDMA over an Ethernet network
- Configuring RDMA over an InfiniBand network
- Tuning system performance
- Manually configuring LLT over RDMA
- Troubleshooting LLT over RDMA
- Appendix G. Configuring the secure shell or the remote shell for communications
- Appendix H. Installation script options
- Appendix I. Troubleshooting VCS configuration
- Appendix J. Sample VCS cluster setup diagrams for CP server-based I/O fencing
- Appendix K. Upgrading the Steward process
About VCS upgrade support using YUM
VCS version 9.0 introduces support for a new upgrade method using the Yellow-Dog Updater Modified (YUM) tool. This method is designed to work along with the operating system (OS) minor version upgrades and application upgrades. The YUM upgrade method uses a single node reboot to complete the upgrade process, with no application downtime or a need to evacuate the Cluster Server (VCS) resource, if applicable.
The YUM upgrade method is an additional way to upgrade VCS. This method does not require the use of the VCS installer. The other upgrade methods, for example with the Common Product Installer (CPI), continue to be supported.
Consider the following requirements and limitations before you use YUM to upgrade VCS:
YUM support for VCS upgrade is available on the RHEL platform only.
Upgrades are supported for VCS version 8.x to 9.x only.
Upgrades for older VCS versions (7.4.x onward) are not supported using the YUM tool.
Rollback (yum history rollback and yum history undo) is not supported.
Rolling or full upgrades are supported with this method.
The Dandified YUM (DNF) is a successor to YUM and uses a similar command structure. The upgrade process that is described here works with both YUM and the DNF commands.
In a pre-reboot phase where you have run the yum update command but have not yet rebooted the node, VCS continues to work as the previous version. New features and functionality of the upgraded VCS version are not available.
The pre-reboot phase may also enforce other restrictions. For example, you cannot update the VxVM tunables.
If the following services are not running before you run the yum update command, then ensure that you do not restart these services before a node reboot (during the pre-reboot phase):
vxfs service
vxodm service
vxgms service
vxglm service
veki service
All Secure File System (SecureFS) and VFR scheduled jobs are skipped for the time duration that it takes for the yum update command to complete. After the update process is complete, the jobs resume and run as per the configured schedule.