Please enter search query.
Search <book_title>...
Cluster Server 7.4.2 Configuration and Upgrade Guide - Linux
Last Published:
2020-08-18
Product(s):
InfoScale & Storage Foundation (7.4.2)
Platform: 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
Sample main.cf file for CP server hosted on a single node that runs VCS
The following is an example of a single CP server node main.cf.
For this CP server single node main.cf, note the following values:
Cluster name: cps1
Node name: cps1
include "types.cf" include "/opt/VRTScps/bin/Quorum/QuorumTypes.cf" // cluster name: cps1 // CP server: cps1 cluster cps1 ( UserNames = { admin = bMNfMHmJNiNNlVNhMK, haris = fopKojNvpHouNn, "cps1.example.com@root@vx" = aj, "root@cps1.example.com" = hq } Administrators = { admin, haris, "cps1.example.com@root@vx", "root@cps1.example.com" } SecureClus = 1 HacliUserLevel = COMMANDROOT ) system cps1 ( ) group CPSSG ( SystemList = { cps1 = 0 } AutoStartList = { cps1 } ) IP cpsvip1 ( Critical = 0 Device @cps1 = eth0 Address = "10.209.3.1" NetMask = "255.255.252.0" ) IP cpsvip2 ( Critical = 0 Device @cps1 = eth1 Address = "10.209.3.2" NetMask = "255.255.252.0" ) NIC cpsnic1 ( Critical = 0 Device @cps1 = eth0 PingOptimize = 0 NetworkHosts @cps1 = { "10.209.3.10" } ) NIC cpsnic2 ( Critical = 0 Device @cps1 = eth1 PingOptimize = 0 ) Process vxcpserv ( PathName = "/opt/VRTScps/bin/vxcpserv" ConfInterval = 30 RestartLimit = 3 ) Quorum quorum ( QuorumResources = { cpsvip1, cpsvip2 } ) cpsvip1 requires cpsnic1 cpsvip2 requires cpsnic2 vxcpserv requires quorum // resource dependency tree // // group CPSSG // { // IP cpsvip1 // { // NIC cpsnic1 // } // IP cpsvip2 // { // NIC cpsnic2 // } // Process vxcpserv // { // Quorum quorum // } // }