Please enter search query.
Search <book_title>...
Cluster Server 7.4.2 Configuration and Upgrade Guide - Linux
Last Published:
2020-08-18
Product(s):
InfoScale & Storage Foundation (7.4.2)
Platform: 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
- Configuring a secure cluster node by node
- Completing the VCS configuration
- 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
- Section II. Automated configuration using response files
- Performing an automated VCS configuration
- Performing an automated I/O fencing configuration using response files
- Section III. Manual configuration
- Manually configuring VCS
- Configuring LLT manually
- Configuring VCS manually
- Configuring VCS in single node mode
- 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
- Configuring server-based fencing on the VCS cluster manually
- 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
- Performing a VCS upgrade using the installer
- Tasks to perform after upgrading 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
- Performing an automated VCS upgrade using response files
- 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
- Manually adding a node to a cluster
- Setting up the node to run in secure mode
- Configuring I/O fencing on the new node
- Adding a node using response files
- Removing a node from a VCS cluster
- Removing a node from a VCS cluster
- 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
- Manually configuring LLT over UDP using IPv6
- About configuring LLT over UDP multiport
- Appendix D. Configuring LLT over TCP
- Manually configuring LLT over TCP using IPv4
- Manually configuring LLT over TCP using IPv6
- Appendix E. Migrating LLT links from IPv4 to IPv6 or dual-stack
- Appendix F. 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
- Appendix G. Configuring the secure shell or the remote shell for communications
- Appendix H. Installation script options
- Appendix I. Troubleshooting VCS configuration
- Appendix J. Sample VCS cluster setup diagrams for CP server-based I/O fencing
- Appendix K. Upgrading the Steward process
Tuning LLT variables for RDMA links
On an LLT over RDMA network, the default RDMA receive-buffer size is 64K and the number of receive-buffers that can be allocated is 1000.
To tune the LLT variables for RDMA links
- Append the /etc/sysconfig/llt file with the following value.
LLT_MAXADVBUFS=4000
When you increase the number of receive-buffers to a maximum value of 4000 the IO performance improves, provided the cluster nodes have sufficient memory.
- If the typical IO size is lesser than the average IO size, you can avoid memory wastage by tuning down the receive buffer size to a minimum of 8K. By default, the receive buffer size is 64K.
Append the /etc/sysconfig/llt file with the following value.
LLT_ADVBUF_SIZE=8192
- Append the /etc/llttab file with the following values.
set-flow highwater:10000 set-flow lowwater:8000 set-flow window:5000 set-flow rporthighwater:10000 set-flow rportlowwater:8000
- Restart the SFCFS or SFCFSHA stack for changes to take effect.
To verify the LLT tunable values
- Check the LLT configuration.
# lltstat -c
LLT configuration information: node: 0 . . max advertised buffers: 4000 advertised buffer size: 8192