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
Configuring server-based fencing on the SFHA cluster manually
The configuration process for the client or SFHA cluster to use CP server as a coordination point requires editing the /etc/vxfenmode
file.
You need to edit this file to specify the following information for your configuration:
Fencing mode
Fencing mechanism
Fencing disk policy (if applicable to your I/O fencing configuration)
CP server or CP servers
Coordinator disk group (if applicable to your I/O fencing configuration)
Set the order of coordination points
Note:
Whenever coordinator disks are used as coordination points in your I/O fencing configuration, you must create a disk group (vxfencoorddg). You must specify this disk group in the /etc/vxfenmode
file.
The customized fencing framework also generates the /etc/vxfentab
file which has coordination points (all the CP servers and disks from disk group specified in /etc/vxfenmode
file).
To configure server-based fencing on the SFHA cluster manually
- Use a text editor to edit the following file on each node in the cluster:
/etc/sysconfig/vxfen
You must change the values of the VXFEN_START and the VXFEN_STOP environment variables to 1.
- Use a text editor to edit the
/etc/vxfenmode
file values to meet your configuration specifications.If your server-based fencing configuration uses a single highly available CP server as its only coordination point, make sure to add the single_cp=1 entry in the
/etc/vxfenmode
file.If you want the vxfen module to use a specific order of coordination points during a network partition scenario, set the vxfen_honor_cp_order value to be 1. By default, the parameter is disabled.
The following sample file output displays what the
/etc/vxfenmode
file contains: - After editing the
/etc/vxfenmode
file, run the vxfen init script to start fencing.For example:
For systemd environments with supported Linux distributions:
# systemctl start vxfen
For other supported Linux distributions:
# /etc/init.d/vxfen start