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 support for InfoScale upgrade using YUM
InfoScale (9.0 onwards) provides an additional method to upgrade the product using the Yellowdog Updater Modified (YUM) tool. This method does not require the use of the InfoScale Common Product Installer (CPI). The YUM upgrade method is designed to accommodate minor OS version upgrades as well as application upgrades.
This method employs a single-node reboot to finalize the upgrade process, thus eliminating application downtime and the need to evacuate the Cluster Server (VCS) resource, if applicable.
Consider the following requirements and limitations before you use YUM to upgrade InfoScale:
The YUM upgrade method is available on the RHEL platform only.
With InfoScale 9.0, the method supports upgrades from InfoScale 8.x to 9.x only.
With InfoScale 9.0.2, the method supports upgrades from InfoScale 7.4.x to 9.x. Specifically, you can upgrade from the 7.4.1.3100, 7.4.1.3300 (additional patch for RHEL 8.7), and 7.4.2.5600 patches through 9.x.
The method supports rolling upgrades or full upgrades.
The method does not support rollback operations like yum history rollback and yum history undo.
The method is compatible with YUM and DNF commands, both. Dandified YUM (DNF) is a successor to YUM and employs a similar command structure.
In the pre-reboot phase, where you have run the yum update command but have not yet rebooted the node, InfoScale continues to work as the previous version. The features and functionality of the upgraded InfoScale version are not available until the node has rebooted successfully.
The pre-reboot phase may also enforce other restrictions. For example, in InfoScale storage environments, you cannot update the VxVM tunables.
During the pre-reboot phase, if the following services are not running before you run the yum update command, make sure that you do not start them before the node reboots:
veki
vxfs
vxglmservice
vxgmsservice
vxodm
During the execution of the yum update command, any scheduled Secure File System (SecureFS) jobs and File Replicator (VFR) jobs are temporarily skipped. After the command completes its execution successfully, the jobs resume and run as per the configured schedule.