InfoScale™ 9.0 Storage Foundation Cluster File System High Availability Configuration and Upgrade Guide - AIX
- Section I. Introduction to SFCFSHA
- Introducing Storage Foundation Cluster File System High Availability
- Section II. Configuration of SFCFSHA
- Preparing to configure
- Preparing to configure SFCFSHA clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring the CP server manually
- Configuring SFCFSHA
- Configuring a secure cluster node by node
- Verifying and updating licenses on the system
- Configuring SFCFSHA clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Performing an automated SFCFSHA configuration using response files
- Performing an automated I/O fencing configuration using response files
- Configuring CP server using response files
- Manually configuring SFCFSHA 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 SFCFSHA cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Section III. Upgrade of SFCFSHA
- Planning to upgrade SFCFSHA
- Preparing to upgrade SFCFSHA
- Upgrading the operating system
- Performing a full upgrade of SFCFSHA using the installer
- Performing a rolling upgrade of SFCFSHA
- Performing a phased upgrade of SFCFSHA
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated SFCFSHA upgrade using response files
- Upgrading Volume Replicator
- Performing post-upgrade tasks
- Planning to upgrade SFCFSHA
- Section IV. Post-configuration tasks
- Section V. Configuration of disaster recovery environments
- Section VI. Adding and removing nodes
- Adding a node to SFCFSHA clusters
- Adding the node to a cluster manually
- Setting up the node to run in secure mode
- Adding a node using response files
- Configuring server-based fencing on the new node
- Removing a node from SFCFSHA clusters
- Adding a node to SFCFSHA clusters
- Section VII. Configuration and Upgrade reference
- Appendix A. Support for AIX Live Update
- Appendix B. Installation scripts
- Appendix C. Configuration files
- Appendix D. Configuring the secure shell or the remote shell for communications
- Appendix E. High availability agent information
- Appendix F. Sample SFCFSHA cluster setup diagrams for CP server-based I/O fencing
- Appendix G. Changing NFS server major numbers for VxVM volumes
- Appendix H. 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
Modifying VCS configuration to use I/O fencing
After you configure I/O fencing, add the UseFence = SCSI3 cluster attribute to the VCS configuration file /etc/VRTSvcs/conf/config/main.cf.
If you reset this attribute to UseFence = None, VCS does not make use of I/O fencing abilities while failing over service groups. However, I/O fencing needs to be disabled separately.
To modify VCS configuration to enable I/O fencing
- Save the existing configuration:
# haconf -dump -makero
- Stop VCS on all nodes:
# hastop -all
- To ensure High Availability has stopped cleanly, run gabconfig -a.
In the output of the commans, check that Port h is not present.
- If the I/O fencing driver vxfen is already running, stop the I/O fencing driver.
# /etc/init.d/vxfen.rc stop
- Make a backup of the main.cf file on all the nodes:
# cd /etc/VRTSvcs/conf/config # cp main.cf main.orig
- On one node, use vi or another text editor to edit the main.cf file. To modify the list of cluster attributes, add the UseFence attribute and assign its value as SCSI3.
cluster clus1( UserNames = { admin = "cDRpdxPmHpzS." } Administrators = { admin } HacliUserLevel = COMMANDROOT CounterInterval = 5 UseFence = SCSI3 )
For fencing configuration in any mode except the disabled mode, the value of the cluster-level attribute UseFence is set to SCSI3.
- Save and close the file.
- Verify the syntax of the file /etc/VRTSvcs/conf/config/main.cf:
# hacf -verify /etc/VRTSvcs/conf/config
- Using rcp or another utility, copy the VCS configuration file from a node (for example, sys1) to the remaining cluster nodes.
For example, on each remaining node, enter:
# rcp sys1:/etc/VRTSvcs/conf/config/main.cf \ /etc/VRTSvcs/conf/config
Start the I/O fencing driver and VCS. Perform the following steps on each node:
Start the I/O fencing driver.
The vxfen startup script also invokes the vxfenconfig command, which configures the vxfen driver.
# /etc/init.d/vxfen.rc start
Start VCS on the node where main.cf is modified.
# /opt/VRTS/bin/hastart
Start VCS on all other nodes once VCS on first node reaches RUNNING state.
# /opt/VRTS/bin/hastart