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
Unloading LLT and GAB and removing Veritas InfoScale Availability or Enterprise on the departing node
Perform the tasks on the node that is departing the cluster.
You can use script-based installer to uninstall Veritas InfoScale Availability or Enterprise on the departing node or perform the following manual steps.
If you have configured VCS as part of the InfoScale products, you may have to delete other dependent packages before you can delete all of the following ones.
To unconfigure and unload LLT and GAB and remove InfoScale Availability or Enterprise
- If you had configured I/O fencing in enabled mode, then stop I/O fencing.
# svcadm disable -s vxfen
- Unconfigure GAB and LLT:
# /sbin/gabconfig -U # /sbin/lltconfig -U
Unload the GAB and LLT modules from the kernel.
Determine the kernel module IDs:
# modinfo | grep gab # modinfo | grep llt
The module IDs are in the left-hand column of the output.
Unload the module from the kernel:
# modunload -i gab_id # modunload -i llt_id
- Disable the startup files to prevent LLT, GAB, or InfoScale Availability or Enterprise from starting up:
# /usr/sbin/svcadm disable -s vcs # /usr/sbin/svcadm disable -s gab # /usr/sbin/svcadm disable -s llt
- To determine the packages to remove, enter:
# pkginfo | grep VRTS
- To permanently remove the InfoScale Availability or Enterprise packages from the system, use the pkg uninstall command. Start by removing the following packages, which may have been optionally installed, in the order shown below.
On Solaris 11:
# pkg uninstall VRTSvcsea # pkg uninstall VRTSvcswiz # pkg uninstall VRTSvbs # pkg uninstall VRTSsfmh # pkg uninstall VRTSvcsag # pkg uninstall VRTScps # pkg uninstall VRTSvcs # pkg uninstall VRTSamf # pkg uninstall VRTSvxfen # pkg uninstall VRTSgab # pkg uninstall VRTSllt # pkg uninstall VRTSspt # pkg uninstall VRTSsfcpi # pkg uninstall VRTSperl # pkg uninstall VRTSvlic
- Remove the LLT and GAB configuration files.
# rm /etc/llttab # rm /etc/gabtab # rm /etc/llthosts
- Remove the language packages and patches.