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
Enabling or disabling the preferred fencing policy
You can enable or disable the preferred fencing feature for your I/O fencing configuration.
You can enable preferred fencing to use system-based race policy, group-based race policy, or site-based policy. If you disable preferred fencing, the I/O fencing configuration uses the default count-based race policy.
Preferred fencing is not applicable to majority-based I/O fencing.
To enable preferred fencing for the I/O fencing configuration
- Make sure that the cluster is running with I/O fencing set up.
# vxfenadm -d
- Make sure that the cluster-level attribute UseFence has the value set to SCSI3.
# haclus -value UseFence
To enable system-based race policy, perform the following steps:
Make the VCS configuration writable.
# haconf -makerw
Set the value of the cluster-level attribute PreferredFencingPolicy as System.
# haclus -modify PreferredFencingPolicy System
Set the value of the system-level attribute FencingWeight for each node in the cluster.
For example, in a two-node cluster, where you want to assign sys1 five times more weight compared to sys2, run the following commands:
# hasys -modify sys1 FencingWeight 50 # hasys -modify sys2 FencingWeight 10
Save the VCS configuration.
# haconf -dump -makero
Verify fencing node weights using:
# vxfenconfig -a
To enable group-based race policy, perform the following steps:
Make the VCS configuration writable.
# haconf -makerw
Set the value of the cluster-level attribute PreferredFencingPolicy as Group.
# haclus -modify PreferredFencingPolicy Group
Set the value of the group-level attribute Priority for each service group.
For example, run the following command:
# hagrp -modify service_group Priority 1
Make sure that you assign a parent service group an equal or lower priority than its child service group. In case the parent and the child service groups are hosted in different subclusters, then the subcluster that hosts the child service group gets higher preference.
Save the VCS configuration.
# haconf -dump -makero
To enable site-based race policy, perform the following steps:
Make the VCS configuration writable.
# haconf -makerw
Set the value of the cluster-level attribute PreferredFencingPolicy as Site.
# haclus -modify PreferredFencingPolicy Site
Set the value of the site-level attribute Preference for each site.
For example, # hasite -modify Pune Preference 2
Save the VCS configuration.
# haconf -dump - makero
- To view the fencing node weights that are currently set in the fencing driver, run the following command:
# vxfenconfig -a
To disable preferred fencing for the I/O fencing configuration
- Make sure that the cluster is running with I/O fencing set up.
# vxfenadm -d
- Make sure that the cluster-level attribute UseFence has the value set to SCSI3.
# haclus -value UseFence
- To disable preferred fencing and use the default race policy, set the value of the cluster-level attribute PreferredFencingPolicy as Disabled.
# haconf -makerw # haclus -modify PreferredFencingPolicy Disabled # haconf -dump -makero