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
- Overview of tasks to configure VCS using the product installer
- Starting the software configuration
- Specifying systems for configuration
- Configuring the cluster name
- Configuring private heartbeat links
- Configuring the virtual IP of the cluster
- Configuring VCS in secure mode
- Setting up trust relationships for your VCS cluster
- Configuring a secure cluster node by node
- Adding VCS users
- Configuring SMTP email notification
- Configuring SNMP trap notification
- Configuring global clusters
- Completing the VCS configuration
- About the License Audit Tool
- 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
- Setting up non-SCSI-3 I/O fencing in virtual environments using installer
- Setting up majority-based I/O fencing using installer
- Enabling or disabling the preferred fencing policy
- Section II. Automated configuration using response files
- Performing an automated VCS configuration
- Performing an automated I/O fencing configuration using response files
- Configuring I/O fencing using response files
- Response file variables to configure disk-based I/O fencing
- Sample response file for configuring disk-based I/O fencing
- Response file variables to configure server-based I/O fencing
- Sample response file for configuring server-based I/O fencing
- Response file variables to configure non-SCSI-3 I/O fencing
- Sample response file for configuring non-SCSI-3 I/O fencing
- Response file variables to configure majority-based I/O fencing
- Sample response file for configuring majority-based I/O fencing
- Section III. Manual configuration
- Manually configuring VCS
- About configuring VCS manually
- Configuring LLT manually
- Configuring GAB manually
- Configuring VCS manually
- Configuring VCS in single node mode
- Starting LLT, GAB, and VCS after manual configuration
- About configuring cluster using VCS Cluster Configuration wizard
- Before configuring a VCS cluster using the VCS Cluster Configuration wizard
- Launching the VCS Cluster Configuration wizard
- Configuring a cluster by using the VCS cluster configuration wizard
- Adding a system to a VCS cluster
- 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
- Preparing the CP servers manually for use by the VCS cluster
- Generating the client key and certificates manually on the client nodes
- Configuring server-based fencing on the VCS cluster manually
- Configuring CoordPoint agent to monitor coordination points
- Verifying server-based I/O fencing configuration
- 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
- About upgrading to VCS 9.0
- About rolling upgrade
- Upgrading VCS in secure enterprise environments
- Supported upgrade paths
- Considerations for upgrading secure VCS 7.4.x clusters to VCS 9.0
- Considerations for upgrading VCS to 9.0 on systems configured with an Oracle resource
- Considerations for upgrading CP servers
- Considerations for upgrading CP clients
- Considerations for upgrading REST server
- Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
- Performing a VCS upgrade using the installer
- Before upgrading VCS using the script-based installer
- Upgrading VCS using the product installer
- Performing a rolling upgrade from 7.4.2 to 9.0 using the product installer
- Upgrading to 2048 bit key and SHA256 signature certificates
- Tasks to perform after upgrading to 2048 bit key and SHA256 signature certificates
- Deleting certificates of non-root users after upgrading to 2048 bit key and SHA256 signature certificates
- Re-establishing WAC communication in global clusters after upgrading to 2048 bit key and SHA256 signature certificates
- Re-establishing CP server and CP client communication after upgrading to 2048 bit key and SHA256 signature certificates
- Re-establishing trust with Steward after upgrading to 2048 bit key and SHA256 signature certificates
- Upgrading Steward 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
- Moving the service groups to the second subcluster
- Upgrading the operating system on the first subcluster
- Upgrading the first subcluster
- Preparing the second subcluster
- Activating the first subcluster
- Upgrading the operating system on the second subcluster
- Upgrading the second subcluster
- Finishing the phased upgrade
- 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
- Adding nodes using the VCS installer
- Manually adding a node to a cluster
- Setting up the hardware
- Installing the VCS software manually when adding a node
- Setting up the node to run in secure mode
- Configuring LLT and GAB when adding a node to the cluster
- Configuring I/O fencing on the new node
- Adding the node to the existing cluster
- Starting VCS and verifying the cluster
- Adding a node using response files
- Removing a node from a VCS cluster
- Removing a node from a VCS cluster
- Verifying the status of nodes and service groups
- Deleting the departing node from VCS configuration
- Modifying configuration files on each remaining node
- Removing the node configuration from the CP server
- Removing security credentials from the leaving node
- Unloading LLT and GAB and removing InfoScale Availability or Enterprise on the departing node
- 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
- Broadcast address in the /etc/llttab file
- The link command in the /etc/llttab file
- The set-addr command in the /etc/llttab file
- Selecting UDP ports
- Configuring the netmask for LLT
- Configuring the broadcast address for LLT
- Sample configuration: direct-attached links
- Sample configuration: links crossing IP routers
- Manually configuring LLT over UDP using IPv6
- LLT over UDP sample /etc/llttab
- About configuring LLT over UDP multiport
- Appendix D. Configuring LLT over TCP
- Using the TCP layer for LLT
- Manually configuring LLT over TCP using IPv4
- Broadcast address in the /etc/llttab file
- The link command in the /etc/llttab file
- The set-addr command in the /etc/llttab file
- Selecting TCP ports
- Configuring the netmask for LLT
- Configuring the broadcast address for LLT
- Sample configuration: direct-attached link
- Sample configuration: link crossing IP routers
- Manually configuring LLT over TCP using IPv6
- LLT over TCP sample /etc/llttab
- Appendix E. Migrating LLT links from IPv4 to IPv6 or dual-stack
- About migrating the LLT links from IPv4 to IPv6 or to a dual-stack network
- Review the current configuration
- Meet the prerequisites for migration
- Adding a new node to an existing cluster
- Migrating LLT links to IPv6 or dual-stack when LLT is configured over UDP using IPv4
- Migrating LLT links to IPv6 or dual-stack when LLT is configured over TCP using IPv4
- Appendix F. Using LLT over RDMA
- Using LLT over RDMA
- About RDMA over RoCE or InfiniBand networks in a clustering environment
- How LLT supports RDMA capability for faster interconnects between applications
- Using LLT over RDMA: supported use cases
- Configuring LLT over RDMA
- Choosing supported hardware for LLT over RDMA
- Installing RDMA, InfiniBand or Ethernet drivers and utilities
- Configuring RDMA over an Ethernet network
- Configuring RDMA over an InfiniBand network
- Tuning system performance
- Manually configuring LLT over RDMA
- LLT over RDMA sample /etc/llttab
- Verifying LLT configuration
- Troubleshooting LLT over RDMA
- IP addresses associated to the RDMA NICs do not automatically plumb on node restart
- Ping test fails for the IP addresses configured over InfiniBand interfaces
- After a node restart, by default the Mellanox card with Virtual Protocol Interconnect (VPI) gets configured in InfiniBand mode
- The LLT module fails to start
- Appendix G. Configuring the secure shell or the remote shell for communications
- About configuring secure shell or remote shell communication modes before installing products
- Manually configuring passwordless ssh
- Setting up ssh and rsh connection using the installer -comsetup command
- Setting up ssh and rsh connection using the pwdutil.pl utility
- Restarting the ssh session
- Enabling rsh for Linux
- Appendix H. Installation script options
- Appendix I. Troubleshooting VCS configuration
- Restarting the installer after a failed network connection
- Cannot launch the cluster view link
- Starting and stopping processes for the InfoScale products
- Installer cannot create UUID for the cluster
- LLT startup script displays errors
- The vxfentsthdw utility fails when SCSI TEST UNIT READY command fails
- The GAB program reports incorrect membership results with existing iptable rules
- Issues during fencing startup on VCS cluster nodes set up for server-based fencing
- Appendix J. Sample VCS cluster setup diagrams for CP server-based I/O fencing
- Appendix K. Upgrading the Steward process
Adding a system to a VCS cluster
Perform the following steps to add a system to a Cluster Server (VCS) cluster by using the VCS Cluster Configuration wizard.
The system from where you launch the wizard must be part of the cluster to which you want to add a new system.
To add a system to a VCS cluster
- Access the High Availability view (for any system belonging to the required cluster).
- Click Actions > Add System to VCS Cluster.
The VCS Cluster Configuration Wizard is launched.
- Review the information on the Welcome panel and click Next.
The Configuration Inputs panel appears, along with the cluster name, and a table of existing cluster systems.
- To add a system to the cluster, click Add System.
- In the Add System dialog box, specify the following details for the system that you want to add to the VCS cluster and click OK.
System Name or IP address
Specify the name or IP address of the system that you want to add to the VCS cluster.
User name
Specify the user account for the system.
Typically, this is the root user. The root user should have the necessary privileges.
Password
Specify the password for the user account you specified.
Use the specified user account on all systems
Select this check box to use the specified user account on all the cluster systems that have the same user name and password.
- On the Configuration Inputs panel, do one of the following actions:
To add another system to the cluster, click Add System and repeat step 4.
To modify the User name or Password for a cluster system, use the edit icon.
Click Next
- On the Network Details panel, specify the adapters for network communication (Low Latency Transport or LLT module of VCS) for the system. The wizard configures the VCS cluster communication links using these adapters. You must select a minimum of two adapters.
Note:
You cannot modify the existing type of cluster communication (LLT over Ethernet or LLT over UDP).
If the existing cluster uses LLT over Ethernet, select the adapter for each network communication link. You must select a different network adapter for each communication link.
If the existing cluster uses LLT over UDP, select the type of IP protocol (IPv4 or IPv6), and then specify the required details for each communication link.
Network Adapter
Select a network adapter for the communication links.
You must select a different network adapter for each communication link.
IP Address
Displays the IP address.
Port
Specify a unique port number for each link.
For IPv4 and IPv6, the port range is from 49152 to 65535.
A specified port for a link is used for all the cluster systems on that link.
Subnet mask (IPv4)
Displays the subnet mask details.
Prefix (IPv6)
Displays the prefix details.
By default, one of the links is configured as a low-priority link on a public network interface. The other link is configured as a high-priority link.
To change a high-priority link to a low-priority link, click Modify. In the Modify low-priority link dialog box, select the link and click OK.
Note:
Arctera recommends that you configure one of the links on a public network interface. You can assign the link on the public network interface as a low-priority link for minimal VCS cluster communication over the link.
- On the Configuration Summary panel, review the VCS Cluster Configuration Details.
- On the Implementation panel, the wizard creates the VCS cluster.
The wizard displays the status of the configuration task. After the configuration is complete, click Next.
If the configuration task fails, click Diagnostic information to check the details of the failure. Rectify the cause of the failure and run the wizard again to add the required system to the VCS cluster.
- On the Finish panel, click Finish to complete the wizard workflow.