InfoScale™ 9.0 Storage Foundation Cluster File System High Availability Configuration and Upgrade Guide - Linux
- 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
- Completing the SFCFSHA configuration
- 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
- 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 SFCFSHA using YUM
- Upgrading Volume Replicator
- Upgrading VirtualStore
- 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. Installation scripts
- Appendix B. Configuration files
- Appendix C. Configuring the secure shell or the remote shell for communications
- Appendix D. High availability agent information
- Appendix E. Sample SFCFSHA 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 IP addresses over InfiniBand Interfaces
Perform the following steps to configure IP addresses over the network interfaces which you plan to configure under LLT. These interfaces must not be aggregated interfaces.
- Configure IP addresses using Linux ifconfig command. Make sure that the IP address for each link must be from a different subnet.
Typical private IP addresses that you can use are: 192.168.12.1, 192.168.12.2, 192.168.12.3 and so on.
- Run the InfiniBand ping test between nodes to ensure that there is InfiniBand level connectivity between nodes.
On one node, start the ibping server.
# ibping -S
On the node, get the GUID of an InfiniBand interface that you need to ping from another node.
# ibstat
CA 'mlx4_0' Number of ports: 2 -- Port 1: State: Active --- Port GUID: 0x0002c90300a02af1 Link layer: InfiniBand
Ping the peer node by using its GUID.
# ibping -G 0x0002c90300a02af1
Where, 0x0002c90300a02af1 is the GUID of the server.
- Configure IP addresses automatically after restart by creating a new configuration file or by modifying the existing file.
On RHEL, modify the
/etc/sysconfig/network-scripts/
directory by modifying theifcfg-ibX
(InfiniBand) configuration file.On SUSE, modify the
/etc/sysconfig/network/
by modifying theifcfg-ibX
(InfiniBand) configuration file.
For example, for an Infiniband interface ib0, create ifcfg-ib0 file with values for the following parameters. DEVICE=ib0 BOOTPROTO=static IPADDR=192.168.27.1 NETMASK=255.255.255.0 NETWORK=192.168.27.0 BROADCAST=192.168.27.255 NM_CONTROLLED=no # This line ensures IPs are plumbed correctly after bootup and the Network manager does not interfere with the interfaces ONBOOT=yes STARTMODE='auto' # This line is only for SUSE