InfoScale™ 9.0 Storage Foundation and High Availability Configuration and Upgrade Guide - 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
Installation script options
Table: Available command line options shows command line options for the installation script. For an initial install or upgrade, options are not usually required. The installation script options apply to all InfoScale product scripts, except where otherwise noted.
Table: Available command line options
Command Line Option | Function |
---|---|
-addnode | Adds a node to a high availability cluster. |
-ai | The -ai option is supported on Solaris 11 only, and is used to generate Automated Installation manifest. This can be used by Solaris Automated Installation Server to install the InfoScale product, along with the Solaris 11 operation system. |
-allpkgs | Displays all packages required for the specified product. The packages are listed in correct installation order. The output can be used to create scripts for command line installs, or for installations over a network. |
-comcleanup | The -comcleanup option removes the secure shell or remote shell configuration added by installer on the systems. The option is only required when installation routines that performed auto-configuration of the shell are abruptly terminated. |
-comsetup | The -comsetup option is used to set up the ssh or rsh communication between systems without requests for passwords or passphrases. |
-configcps | The -configcps option is used to configure CP server on a running system or cluster. |
-configure | Configures the product after installation. |
-disable_dmp_native_support | Disables Dynamic Multi-pathing support for the native LVM volume groups and ZFS pools during upgrade. Retaining Dynamic Multi-pathing support for the native LVM volume groups and ZFS pools during upgrade increases package upgrade time depending on the number of LUNs and native LVM volume groups and ZFS pools configured on the system. |
-fencing | Configures I/O fencing in a running cluster. |
-fips | The -fips option is used to enable or disable security with fips mode on a running VCS cluster. It could only be used together with -security or -securityonenode option. |
- hostfile full_path_to_file | Specifies the location of a file that contains a list of hostnames on which to install. |
-install | Used to install products on system |
-online_upgrade | Used to perform online upgrade. Using this option, the installer upgrades the whole cluster and also supports customer's application zero down time during the upgrade procedure. Now this option only supports VCS and ApplicationHA. |
-patch_path | Defines the path of a patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed . |
-patch2_path | Defines the path of a second patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed. |
-patch3_path | Defines the path of a third patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed. |
-patch4_path | Defines the path of a fourth patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed. |
-patch5_path | Defines the path of a fifth patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed. |
- keyfile ssh_key_file | Specifies a key file for secure shell (SSH) installs. This option passes -I ssh_key_file to every SSH invocation. |
-license | Registers or updates product licenses on the specified systems. |
- logpath log_path | Specifies a directory other than /opt/VRTS/install/logs as the location where installer log files, summary files, and response files are saved. |
-noipc | Disables the installer from making outbound networking calls to Services and Operations Readiness Tool (SORT) in order to automatically obtain patch and release information updates. |
-nolic | Allows installation of product packages without entering a license key. Licensed features cannot be configured, started, or used when this option is specified. |
-pkgtable | Displays product's packages in correct installation order by group. |
- postcheck | Checks for different HA and file system-related processes, the availability of different ports, and the availability of cluster-related service groups. |
-precheck | Performs a preinstallation check to determine if systems meet all installation requirements. Arctera recommends doing a precheck before installing a product. |
-prod | Specifies the product for operations. |
-component | Specifies the component for operations. |
-redirect | Displays progress details without showing the progress bar. |
-require | Specifies an installer patch file. |
- responsefile response_file | Automates installation and configuration by using system and configuration information stored in a specified file instead of prompting for information. The response_file must be a full path name. You must edit the response file to use it for subsequent installations. Variable field definitions are defined within the file. |
-rolling_upgrade | Starts a rolling upgrade. Using this option, the installer detects the rolling upgrade status on cluster systems automatically without the need to specify rolling upgrade phase 1 or phase 2 explicitly. |
-rollingupgrade_phase1 | The -rollingupgrade_phase1 option is used to perform rolling upgrade Phase-I. In the phase, the product kernel packages get upgraded to the latest version. |
-rollingupgrade_phase2 | The -rollingupgrade_phase2 option is used to perform rolling upgrade Phase-II. In the phase, VCS and other agent packages upgrade to the latest version. Product kernel drivers are rolling-upgraded to the latest protocol version. |
- rootpath root_path | Specifies an alternative root directory on which to install packages. On Solaris operating systems, -rootpath passes -R path to pkgadd command. |
-rsh | Specify this option when you want to use RSH and RCP for communication between systems instead of the default SSH and SCP. See About configuring secure shell or remote shell communication modes before installing products. |
-security | The -security option is used to convert a running VCS cluster between secure and non-secure modes of operation. |
-securityonenode | The -securityonenode option is used to configure a secure cluster node by node. |
-securitytrust | The -securitytrust option is used to setup trust with another broker. |
- serial | Specifies that the installation script performs install, uninstall, start, and stop operations on each system in a serial fashion. If this option is not specified, these operations are performed simultaneously on all systems. |
-settunables | Specify this option when you want to set tunable parameters after you install and configure a product. You may need to restart processes of the product for the tunable parameter values to take effect. You must use this option together with the -tunablesfile option. |
-start | Starts the daemons and processes for the specified product. |
-stop | Stops the daemons and processes for the specified product. |
-timeout | The -timeout option is used to specify the number of seconds that the script should wait for each command to complete before timing out. Setting the -timeout option overrides the default value of 1200 seconds. Setting the -timeout option to 0 prevents the script from timing out. The -timeout option does not work with the -serial option |
- tmppath tmp_path | Specifies a directory other than /opt/VRTStmp as the working directory for the installation scripts. This destination is where initial logging is performed and where packages are copied on remote systems before installation. |
-tunables | Lists all supported tunables and create a tunables file template. |
-tunables_file tunables_file | Specify this option when you specify a tunables file. The tunables file should include tunable parameters. |
-uninstall | This option is used to uninstall the products from systems |
-upgrade | Specifies that an existing version of the product exists and you plan to upgrade it. |
-version | Checks and reports the installed products and their versions. Identifies the installed and missing packages and patches where applicable for the product. Provides a summary that includes the count of the installed and any missing packages and patches where applicable. Lists the installed patches, patches, and available updates for the installed product if an Internet connection is available. |