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
Setting up non-SCSI-3 fencing in virtual environments manually
To manually set up I/O fencing in a non-SCSI-3 PR compliant setup
- Configure I/O fencing either in majority-based fencing mode with no coordination points or in server-based fencing mode only with CP servers as coordination points.
- Make sure that the VCS cluster is online and check that the fencing mode is customized mode or majority mode.
# vxfenadm -d
- Make sure that the cluster attribute UseFence is set to SCSI-3.
# haclus -value UseFence
- On each node, edit the /etc/vxenviron file as follows:
data_disk_fencing=off
On each node, edit the /kernel/drv/vxfen.conf file as follows:
vxfen_vxfnd_tmt=25
- On each node, edit the /etc/vxfenmode file as follows:
loser_exit_delay=55 vxfen_script_timeout=25
Refer to the sample /etc/vxfenmode file.
On each node, set the value of the LLT sendhbcap timer parameter value as follows:
Run the following command:
lltconfig -T sendhbcap:3000
Add the following line to the /etc/llttab file so that the changes remain persistent after any reboot:
set-timer senhbcap:3000
On any one node, edit the VCS configuration file as follows:
Make the VCS configuration file writable:
# haconf -makerw
For each resource of the type DiskGroup, set the value of the MonitorReservation attribute to 0 and the value of the Reservation attribute to NONE.
# hares -modify <dg_resource> MonitorReservation 0
# hares -modify <dg_resource> Reservation "NONE"
Run the following command to verify the value:
# hares -list Type=DiskGroup MonitorReservation!=0
# hares -list Type=DiskGroup Reservation!="NONE"
The command should not list any resources.
Modify the default value of the Reservation attribute at type-level.
# haattr -default DiskGroup Reservation "NONE"
Make the VCS configuration file read-only
# haconf -dump -makero
- Make sure that the UseFence attribute in the VCS configuration file main.cf is set to SCSI-3.
To make these VxFEN changes take effect, stop and restart VxFEN and the dependent modules
On each node, run the following command to stop VCS:
# svcadm disable -t vcs
After VCS takes all services offline, run the following command to stop VxFEN:
# svcadm disable -t vxfen
On each node, run the following commands to restart VxFEN and VCS:
# svcadm enable vxfen