Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Storage Foundation and High Availability Configuration and Upgrade Guide - Solaris
Last Published:
2025-04-18
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: Solaris
- Section I. Introduction to SFHA
- Section II. Configuration of SFHA
- Preparing to configure
- Preparing to configure SFHA clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring the CP server manually
- Configuring CP server using response files
- Configuring SFHA
- Configuring Storage Foundation High Availability using the installer
- Configuring a secure cluster node by node
- Verifying and updating licenses on the system
- Configuring Storage Foundation High Availability using the installer
- Configuring SFHA clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Manually configuring SFHA 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 SFHA cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Performing an automated SFHA configuration using response files
- Performing an automated I/O fencing configuration using response files
- Section III. Upgrade of SFHA
- Planning to upgrade SFHA
- Preparing to upgrade SFHA
- Upgrading Storage Foundation and High Availability
- Performing a rolling upgrade of SFHA
- Performing a phased upgrade of SFHA
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated SFHA upgrade using response files
- Upgrading SFHA using Boot Environment upgrade
- Performing post-upgrade tasks
- Post-upgrade tasks when VCS agents for VVR are configured
- Upgrading the Array Support Library
- About enabling LDAP authentication for clusters that run in secure mode
- Planning to upgrade SFHA
- Section IV. Post-installation tasks
- Section V. Adding and removing nodes
- Adding a node to SFHA clusters
- Adding the node to a cluster manually
- Adding a node using response files
- Configuring server-based fencing on the new node
- Removing a node from SFHA clusters
- Removing a node from a SFHA cluster
- Removing a node from a SFHA cluster
- Adding a node to SFHA clusters
- Section VI. Configuration and upgrade reference
- Appendix A. Installation scripts
- Appendix B. SFHA services and ports
- Appendix C. Configuration files
- Appendix D. Configuring the secure shell or the remote shell for communications
- Appendix E. Sample SFHA 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
Verifying Solaris 11 BE upgrade
To ensure that BE upgrade has completed successfully, verify that all the nodes have booted from the alternate BE and joined the cluster.
To verify that BE upgrade is completed successfully
- Verify that the alternate BE is active.
# beadm list
If the alternate BE fails to be active, you can revert to the primary BE.
- In a cluster environment, make sure that all the GAB ports are up. Note that different ports appear for different products.
# gabconfig -a Port a gen c03c01 membership 0 Port h gen c03c03 membership 0
- Perform other verification as required to ensure that the new BE is configured correctly.
If you have set AutoStart to 0 for the service group containing zone resource earlier, perform the following steps:
Verify whether the zpool on which the root file system of the zone is residing is imported
# zpool list
If not imported, online the zpool resource.
Attach the zone.
# zoneadm -z <zone> attach
Reset AutoStart to 1 for the service group containing zone resource.
# hagrp -modify <group> AutoStart 1
If you have installed VRTSvxfs
or VRTSodm
packages inside the zones, you need to manually upgrade these packages inside the zone.