Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Storage Foundation Cluster File System High Availability Configuration and Upgrade Guide - Solaris
Last Published:
2025-04-21
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: Solaris
- Section I. Introduction to SFCFSHA
- Introducing Storage Foundation Cluster File System High Availability
- Section II. Configuration of SFCFSHA
- Preparing to configure
- Preparing to configure SFCFSHA clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring the CP server manually
- Configuring SFCFSHA
- Configuring a secure cluster node by node
- Verifying and updating licenses on the system
- Configuring SFCFSHA clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Performing an automated SFCFSHA configuration using response files
- Performing an automated I/O fencing configuration using response files
- Configuring CP server using response files
- Manually configuring SFCFSHA 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 SFCFSHA cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Section III. Upgrade of SFCFSHA
- Planning to upgrade SFCFSHA
- Preparing to upgrade SFCFSHA
- Performing a full upgrade of SFCFSHA using the installer
- Performing a rolling upgrade of SFCFSHA
- Performing a phased upgrade of SFCFSHA
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated SFCFSHA upgrade using response files
- Upgrading Volume Replicator
- Upgrading VirtualStore
- Upgrading SFCFSHA using Boot Environment upgrade
- Performing post-upgrade tasks
- Planning to upgrade SFCFSHA
- Section IV. Post-configuration tasks
- Section V. Configuration of disaster recovery environments
- Section VI. Adding and removing nodes
- Adding a node to SFCFSHA clusters
- Adding the node to a cluster manually
- Setting up the node to run in secure mode
- Adding a node using response files
- Configuring server-based fencing on the new node
- Removing a node from SFCFSHA clusters
- Adding a node to SFCFSHA clusters
- Section VII. Configuration and Upgrade reference
- Appendix A. Installation scripts
- Appendix B. Configuration files
- Appendix C. Configuring the secure shell or the remote shell for communications
- Appendix D. High availability agent information
- Appendix E. Sample SFCFSHA cluster setup diagrams for CP server-based I/O fencing
- Appendix F. Reconciling major/minor numbers for NFS shared disks
- Appendix G. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Using the UDP layer of IPv6 for LLT
- Manually configuring LLT over UDP using IPv6
Adding nodes to a cluster that is using authentication for SFDB tools
To add a node to a cluster that is using authentication for SFDB tools, perform the following steps as the root user
- Export authentication data from a node in the cluster that has already been authorized, by using the -o export_broker_config option of the sfae_auth_op command.
Use the -f option to provide a file name in which the exported data is to be stored.
# /opt/VRTS/bin/sfae_auth_op \ -o export_broker_config -f exported-data
- Copy the exported file to the new node by using any available copy mechanism such as scp or rcp.
- Import the authentication data on the new node by using the -o import_broker_config option of the sfae_auth_op command.
Use the -f option to provide the name of the file copied in Step 2.
# /opt/VRTS/bin/sfae_auth_op \ -o import_broker_config -f exported-data Setting up AT Importing broker configuration Starting SFAE AT broker
- Stop the vxdbd daemon on the new node.
# /opt/VRTS/bin/sfae_config disable vxdbd has been disabled and the daemon has been stopped.
- Enable authentication by setting the AUTHENTICATION key to yes in the
/etc/vx/vxdbed/admin.properties
configuration file.If
/etc/vx/vxdbed/admin.properties
does not exist, then use cp /opt/VRTSdbed/bin/admin.properties.example /etc/vx/vxdbed/admin.properties - Start the vxdbd daemon.
# /opt/VRTS/bin/sfae_config enable vxdbd has been enabled and the daemon has been started. It will start automatically on reboot.
The new node is now authenticated to interact with the cluster to run SFDB commands.