Please enter search query.
Search <book_title>...
Cluster Server 7.3.1 Configuration and Upgrade Guide - Solaris
Last Published:
2019-04-17
Product(s):
InfoScale & Storage Foundation (7.3.1)
Platform: 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
Starting LLT, GAB, and VCS after manual configuration
After you have configured LLT, GAB, and VCS, use the following procedures to start LLT, GAB, and VCS.
- On each node, run the following command to start LLT:
# svcadm enable llt
If LLT is configured correctly on each node, the console output resembles:
Jun 26 19:04:24 sys1 kernel: [1571667.550527] LLT INFO V-14-1-10009 LLT 6.0.100.000-SBLD Protocol available
- On each node, run the following command to verify that LLT is running:
# /sbin/lltconfig LLT is running
- On each node, run the following command to start GAB:
# svcadm enable gab
If GAB is configured correctly on each node, the console output resembles:
Jun 26 19:10:34 sys1 kernel: [1572037.501731] GAB INFO V-15-1-20021 GAB 6.0.100.000-SBLD available
- On each node, run the following command to verify that GAB is running:
# /sbin/gabconfig -a GAB Port Memberships =================================== Port a gen a36e0003 membership 01
- On each node, type:
# svcadm enable vcs
If VCS is configured correctly on each node, the console output resembles:
Apr 5 14:52:02 sys1 gab: GAB:20036: Port h gen 3972a201 membership 01
To start VCS as single node
- Run the following command:
# svcadm enable vcs-onenode