Cluster Server 7.4.2 Configuration and Upgrade Guide - 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
Migrating LLT links to IPv6 or dual-stack when LLT is configured over TCP using IPv4
Before you migrate from IPv4 to IPv6, ensure that the cluster is running with LLT configured over TCP using IPv4.
To dynamically migrate from IPv4 to IPv6 configuration:
- Make sure that the LLT link is operational.
# lltstat -nvv configured
- Make sure that the IPv6 address is plumbed on all the nodes and is pingable from the IPv6 interface addresses of the peer nodes.
- On one of the interfaces, add one non-TCP (UDP) IPv4 link.
LLT over TCP configuration allows only one TCP link. Therefore, you should add a non-TCP IPv4 link for the migration. Doing so ensures that the additional non-TCP link continues to be operational, while the other link is being migrated to IPv6.
Use the following command to add the LLT UDP link with the newly plumbed IPv4 address dynamically:
# lltconfig -t devtag -d device -b udp -s port [-m mtu] -I IPaddr -B bcast [-l] [-Q]
where,
devtag is different than existing devtag used in llttab
device is the interface name used for the IPv4 link
- Verify that the non-TCP IPv4 link is added properly and is operational.
# lltstat -l
# lltstat -nvv configured
- Disable the existing TCP IPv4 link.
# lltconfig -L disable -t linkTagName
- Unlink the disabled TCP IPv4 LLT link.
# lltconfig -u linkTagName
- Verify whether one of the high priority LLT links is now configured with non-TCP IPv4 address.
# lltstat -l
# lltstat -nvv configured
- Update
/etc/llttab
with set-addr for all peer nodes with the IPv6 addresses that to be used for the TCPv6 links. - Add the TCP LLT link with the newly plumbed IPv6 address dynamically.
# lltconfig -t devtag -d device -b tcp6 -s port [-m mtu] -I IPaddr [-B mcast] [-l] [-Q]
where,
devtag is same as the existing devtag of the TCP link used in llttab
device is the interface name used for the IPv6 link
- Update
/etc/llttab
with the latest link configurations.If the link configurations are not updated, the migration changes are lost after reboot.