InfoScale™ 9.0 Storage Foundation and High Availability Configuration and Upgrade Guide - Linux
- Section I. Introduction to SFHA
- Section II. Configuration of SFHA
- Preparing to configure
- Preparing to configure SFHA clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring the CP server manually
- Configuring CP server using response files
- Configuring SFHA
- Configuring Storage Foundation High Availability using the installer
- Configuring a secure cluster node by node
- Completing the SFHA configuration
- Verifying and updating licenses on the system
- Configuring Storage Foundation High Availability using the installer
- Configuring SFHA clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Manually configuring SFHA 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 SFHA cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Performing an automated SFHA configuration using response files
- Performing an automated I/O fencing configuration using response files
- Section III. Upgrade of SFHA
- Planning to upgrade SFHA
- Preparing to upgrade SFHA
- Upgrading Storage Foundation and High Availability
- Performing a rolling upgrade of SFHA
- Performing a phased upgrade of SFHA
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated SFHA upgrade using response files
- Upgrading SFHA using YUM
- Performing post-upgrade tasks
- Post-upgrade tasks when VCS agents for VVR are configured
- About enabling LDAP authentication for clusters that run in secure mode
- Planning to upgrade SFHA
- Section IV. Post-installation tasks
- Section V. Adding and removing nodes
- Adding a node to SFHA clusters
- Adding the node to a cluster manually
- Adding a node using response files
- Configuring server-based fencing on the new node
- Removing a node from SFHA clusters
- Removing a node from a SFHA cluster
- Removing a node from a SFHA cluster
- Adding a node to SFHA clusters
- Section VI. Configuration and upgrade reference
- Appendix A. Installation scripts
- Appendix B. SFHA services and ports
- Appendix C. Configuration files
- Appendix D. Configuring the secure shell or the remote shell for communications
- Appendix E. Sample SFHA cluster setup diagrams for CP server-based I/O fencing
- Appendix F. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Using the UDP layer of IPv6 for LLT
- Manually configuring LLT over UDP using IPv6
- About configuring LLT over UDP multiport
- Appendix G. 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
Refreshing keys or registrations on the existing coordination points for server-based fencing using the installer
You must refresh registrations on the coordination points in the following scenarios:
When the CoordPoint agent notifies VCS about the loss of registration on any of the existing coordination points.
A planned refresh of registrations on coordination points when the cluster is online without having an application downtime on the cluster.
Registration loss might occur because of an accidental array restart, corruption of keys, or some other reason. If the coordination points lose registrations of the cluster nodes, the cluster might panic when a network partition occurs.
Warning:
Refreshing keys might cause the cluster to panic if a node leaves membership before the coordination points refresh is complete.
To refresh registrations on existing coordination points for server-based I/O fencing using the installer
- Start the installer with the -fencing option.
# /opt/VRTS/install/installer -fencing
The installer starts with a copyright message and verifies the cluster information.
Note the location of log files that you can access if there is a problem with the configuration process.
- Confirm that you want to proceed with the I/O fencing configuration at the prompt.
The program checks that the local node running the script can communicate with the remote nodes and checks whether SFHA 9.0 is configured properly.
- Review the I/O fencing configuration options that the program presents. Type the number corresponding to the option that suggests to refresh registrations or keys on the existing coordination points.
Select the fencing mechanism to be configured in this Application Cluster [1-7,q] 6
- Ensure that the
/etc/vxfentab
file contains the same coordination point servers that are currently used by the fencing module.Also, ensure that the disk group mentioned in the
/etc/vxfendg
file contains the same disks that are currently used by the fencing module as coordination disks. - Verify the coordination points.
For example, Total number of coordination points being used: 3 Coordination Point Server ([VIP or FQHN]:Port): 1. 10.198.94.146 ([10.198.94.146]:443) 2. 10.198.94.144 ([10.198.94.144]:443) SCSI-3 disks: 1. emc_clariion0_61 Disk Group name for the disks in customized fencing: vxfencoorddg Disk policy used for customized fencing: dmp
- Is this information correct? [y,n,q] (y)
Updating client cluster information on Coordination Point Server IPaddress
Successfully completed the vxfenswap operation
The keys on the coordination disks are refreshed.
- Do you want to send the information about this installation to us to help improve installation in the future? [y,n,q,?] (y).
- Do you want to view the summary file? [y,n,q] (n).