Cluster Server 7.4.2 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
- 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
Starting LLT, GAB, and VCS after manual configuration
After you have configured LLT, GAB, and VCS, use the following procedures to start LLT, GAB, and VCS.
- On each node, run the following command to start LLT:
For RHEL 7, SLES 12, and supported RHEL distributions:
# systemctl start llt
For earlier versions of RHEL, SLES, and supported RHEL distributions:
# /etc/init.d/llt start
If LLT is configured correctly on each node, the console output resembles:
Loading LLT Driver... Starting LLT: LLT: loading module... Loaded kernel_version on kernel kernel_version LLT: configuring module where, kernel_version is the kernel version of the Linux operating system
- On each node, run the following command to verify that LLT is running:
# /sbin/lltconfig LLT is running
- On each node, run the following command to start GAB:
For RHEL 7, SLES 12, and supported RHEL distributions:
# systemctl start gab
For earlier versions of RHEL, SLES, and supported RHEL distributions:
# /etc/init.d/gab start
If GAB is configured correctly on each node, the console output resembles:
GAB: Starting GAB: Starting Done
- On each node, run the following command to verify that GAB is running:
# /sbin/gabconfig -a GAB Port Memberships =================================== Port a gen a36e0003 membership 01
- On each node, type:
For RHEL 7, SLES 12, and supported RHEL distributions:
# systemctl start vcs
For earlier versions of RHEL, SLES, and supported RHEL distributions:
# /etc/init.d/vcs start
If VCS is configured correctly on each node, the engine log file at
/var/VRTSvcs/log/engine_A.log
resembles:VCS NOTICE V-16-1-10619 'HAD' starting on: sys1 VCS NOTICE V-16-1-10620 Waiting for local cluster configuration status VCS NOTICE V-16-1-10625 Local cluster configuration valid VCS NOTICE V-16-1-11034 Registering for cluster membership VCS NOTICE V-16-1-11035 Waiting for cluster membership GAB INFO V-15-1-20036 Port h gen 265f06 membership ;1 GAB INFO V-15-1-20038 Port h gen 265f06 k_jeopardy 0 GAB INFO V-15-1-20040 Port h gen 265f06 visible 0 VCS INFO V-16-1-10077 Received new cluster membership VCS NOTICE V-16-1-10082 System (sys1) is in Regular Membership - Membership: 0x2 VCS NOTICE V-16-1-10073 Building from local configuration VCS NOTICE V-16-1-10066 Entering RUNNING state GAB INFO V-15-1-20036 Port h gen 265f07 membership 01 VCS INFO V-16-1-10077 Received new cluster membership VCS NOTICE V-16-1-10082 System (sys2) is in Regular Membership - Membership: 0x3