Cluster Server 7.3.1 Configuration and Upgrade Guide - Solaris
- 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
- 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 rolling upgrade of VCS
- 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
- Upgrading VCS using Live Upgrade and Boot Environment upgrade
- 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
- Appendix D. Configuring the secure shell or the remote shell for communications
- Appendix E. Installation script options
- Appendix F. Troubleshooting VCS configuration
- Appendix G. Sample VCS cluster setup diagrams for CP server-based I/O fencing
- Appendix H. Reconciling major/minor numbers for NFS shared disks
- Appendix I. Upgrading the Steward process
Configuring private heartbeat links
After configuring the cluster name, configure the private heartbeat links that LLT uses.
VCS provides the option to use LLT over Ethernet or LLT over UDP (User Datagram Protocol). Veritas recommends that you configure heartbeat links that use LLT over Ethernet for high performance, unless hardware requirements force you to use LLT over UDP. If you want to configure LLT over UDP, make sure you meet the prerequisites.
You must not configure LLT heartbeat using the links that are part of aggregated links. For example, link1, link2 can be aggregated to create an aggregated link, aggr1. You can use aggr1 as a heartbeat link, but you must not use either link1 or link2 as heartbeat links.
See Using the UDP layer for LLT.
The following procedure helps you configure LLT heartbeat links.
To configure private heartbeat links
Choose one of the following options at the installer prompt based on whether you want to configure LLT over Ethernet or LLT over UDP.
Option 1: Configure the heartbeat links using LLT over Ethernet (answer installer questions)
Enter the heartbeat link details at the installer prompt to configure LLT over Ethernet.
Skip to step 2.
Option 2: Configure the heartbeat links using LLT over UDP (answer installer questions)
Make sure that each NIC you want to use as heartbeat link has an IP address configured. Enter the heartbeat link details at the installer prompt to configure LLT over UDP. If you had not already configured IP addresses to the NICs, the installer provides you an option to detect the IP address for a given NIC.
Skip to step 3.
Option 3: Automatically detect configuration for LLT over Ethernet
Allow the installer to automatically detect the heartbeat link details to configure LLT over Ethernet. The installer tries to detect all connected links between all systems.
Skip to step 5.
Note:
Option 3 is not available when the configuration is a single node configuration.
- If you chose option 1, enter the network interface card details for the private heartbeat links.
The installer discovers and lists the network interface cards.
Answer the installer prompts. The following example shows different NICs based on architecture:
For Solaris SPARC:
You must not enter the network interface card that is used for the public network (typically net0.)
Enter the NIC for the first private heartbeat link on sys1: [b,q,?] net1 Would you like to configure a second private heartbeat link? [y,n,q,b,?] (y) Enter the NIC for the second private heartbeat link on sys1: [b,q,?] net2 Would you like to configure a third private heartbeat link? [y,n,q,b,?](n)
Do you want to configure an additional low priority heartbeat link? [y,n,q,b,?] (n)
For Solaris x64:
You must not enter the network interface card that is used for the public network (typically e1000g0.)
Enter the NIC for the first private heartbeat link on sys1: [b,q,?] e1000g1 Would you like to configure a second private heartbeat link? [y,n,q,b,?] (y) Enter the NIC for the second private heartbeat link on sys1: [b,q,?] e1000g2 Would you like to configure a third private heartbeat link? [y,n,q,b,?](n)
- If you chose option 2, enter the NIC details for the private heartbeat links. This step uses examples such as private_NIC1 or private_NIC2 to refer to the available names of the NICs.
Enter the NIC for the first private heartbeat link on sys1: [b,q,?] private_NIC1 Some configured IP addresses have been found on the NIC private_NIC1 in sys1, Do you want to choose one for the first private heartbeat link? [y,n,q,?] (y) Please select one IP address: 1) 192.168.0.1/24 2) 192.168.1.233/24 b) Back to previous menu Please select one IP address: [1-2,b,q,?] (1) Enter the UDP port for the first private heartbeat link on sys1: [b,q,?] (50000) Enter the NIC for the second private heartbeat link on sys1: [b,q,?] private_NIC2 Some configured IP addresses have been found on the NIC private_NIC2 in sys1, Do you want to choose one for the second private heartbeat link? [y,n,q,?] (y) Please select one IP address: 1) 192.168.1.1/24 2) 192.168.2.233/24 b) Back to previous menu Please select one IP address: [1-2,b,q,?] (1) 1 Enter the UDP port for the second private heartbeat link on sys1: [b,q,?] (50001) Would you like to configure a third private heartbeat link? [y,n,q,b,?] (n) Do you want to configure an additional low-priority heartbeat link? [y,n,q,b,?] (n) y Enter the NIC for the low-priority heartbeat link on sys1: [b,q,?] private_NIC0 Some configured IP addresses have been found on the NIC private_NIC0 in sys1, Do you want to choose one for the low-priority heartbeat link? [y,n,q,?] (y) Please select one IP address: 1) 10.200.59.233/22 2) 192.168.3.1/22 b) Back to previous menu Please select one IP address: [1-2,b,q,?] (1) 2 Enter the UDP port for the low-priority heartbeat link on sys1: [b,q,?] (50010)
- Choose whether to use the same NIC details to configure private heartbeat links on other systems.
Are you using the same NICs for private heartbeat links on all systems? [y,n,q,b,?] (y)
If you want to use the NIC details that you entered for sys1, make sure the same NICs are available on each system. Then, enter y at the prompt.
For LLT over UDP, if you want to use the same NICs on other systems, you still must enter unique IP addresses on each NIC for other systems.
If the NIC device names are different on some of the systems, enter n. Provide the NIC details for each system as the program prompts.
- If you chose option 3 , the installer detects NICs on each system and network links, and sets link priority.
If the installer fails to detect heartbeat links or fails to find any high-priority links, then choose option 1 or option 2 to manually configure the heartbeat links.
See step 2 for option 1, or step 3 for option 2, or step 5 for option 3.
- Enter a unique cluster ID:
Enter a unique cluster ID number between 0-65535: [b,q,?] (60842)
The cluster cannot be configured if the cluster ID 60842 is in use by another cluster. Installer performs a check to determine if the cluster ID is duplicate. The check takes less than a minute to complete.
Would you like to check if the cluster ID is in use by another cluster? [y,n,q] (y)
- Verify and confirm the information that the installer summarizes.