InfoScale™ 9.0 Storage Foundation Cluster File System High Availability Configuration and Upgrade Guide - 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
Administering the AMF kernel driver
Review the following procedures to start, stop, or unload the AMF kernel driver.
To start the AMF kernel driver
- Set the value of the AMF_START variable to 1 in the following file, if the value is not already 1:
# /etc/default/amf
- Start the AMF kernel driver. Run the following command:
# svcadm enable amf
To stop the AMF kernel driver
- Set the value of the AMF_STOP variable to 1 in the following file, if the value is not already 1:
# /etc/default/amf
- Stop the AMF kernel driver. Run the following command:
# svcadm disable amf
To unload the AMF kernel driver
If agent downtime is not a concern, use the following steps to unload the AMF kernel driver:
Stop the agents that are registered with the AMF kernel driver.
The amfstat command output lists the agents that are registered with AMF under the Registered Reapers section.
See the amfstat manual page.
On Solaris 11, set the value of the AMF_DISABLE variable to 1 in the following file (before stopping the AMF kernel driver):
# /etc/default/amf
Note:
Reset the AMF_DISABLE variable in the /etc/default/amf file before starting AMF kernel driver.
Stop the AMF kernel driver.
Start the agents.
If you want minimum downtime of the agents, use the following steps to unload the AMF kernel driver:
Run the following command to disable the AMF driver even if agents are still registered with it.
# amfconfig -Uof
On Solaris 11, set the value of the AMF_DISABLE variable to 1 in the following file (before stopping the AMF kernel driver):
# /etc/default/amf
Note:
Reset the AMF_DISABLE variable in the /etc/default/amf file before starting AMF kernel driver.
Stop the AMF kernel driver.