Storage Foundation and High Availability 7.4.2 Configuration and Upgrade Guide - AIX
- Section I. Introduction to SFHA
- Introducing Storage Foundation and High Availability
- 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
- Response file variables to configure server-based I/O fencing
- 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
- Performing post-upgrade tasks
- Post-upgrade tasks when VCS agents for VVR are configured
- 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. Support for AIX Live Update
- Appendix B. Installation scripts
- Appendix C. SFHA services and ports
- Appendix D. Configuration files
- Appendix E. Configuring the secure shell or the remote shell for communications
- Appendix F. Sample SFHA cluster setup diagrams for CP server-based I/O fencing
- Appendix G. Changing NFS server major numbers for VxVM volumes
- Appendix H. 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
Response file variables to upgrade SFHA
Table: Response file variables for upgrading SFHA lists the response file variables that you can define to configure SFHA.
Table: Response file variables for upgrading SFHA
Variable | Description |
---|---|
CFG{accepteula} | Specifies whether you agree with the EULA.pdf file on the media. List or scalar: scalar Optional or required: required |
CFG{systems} | List of systems on which the product is to be installed or uninstalled. List or scalar: list Optional or required: required |
CFG{upgrade} | Upgrades all filesets installed. List or scalar: list Optional or required: required |
CFG{keys}{keyless} CFG{keys}{licensefile} | CFG{keys}{keyless} gives a list of keyless keys to be registered on the system. CFG{keys}{licensefile} gives the absolute file path to the permanent license key to be registered on the system. List or scalar: list Optional or required: required |
CFG{opt}{keyfile} | Defines the location of an ssh keyfile that is used to communicate with all remote systems. List or scalar: scalar Optional or required: optional |
CFG{opt}{tmppath} | Defines the location where a working directory is created to store temporary files and the filesets that are needed during the install. The default location is /opt/VRTStmp. List or scalar: scalar Optional or required: optional |
CFG{opt}{logpath} | Mentions the location where the log files are to be copied. The default location is /opt/VRTS/install/logs. List or scalar: scalar Optional or required: optional |
$CFG{edgeserver_host} | Use this parameter to configure the edge server. Enter telemetry.veritas.com to use the Veritas Cloud Receiver, which is a preconfigured, cloud-based edge server deployed by Veritas. Optional or required: required Note: An edge server is used to collect licensing and platform related information from InfoScale products as part of the Veritas Product Improvement Program. The information collected helps identify how customers deploy and use the product, and enables Veritas to manage customer licenses more efficiently. |
$CFG{edgeserver_port} | Use this parameter to configure the port number of the edge server. Enter 443, which is the port number used by the Veritas Cloud Receiver. Optional or required: required Note: An edge server is used to collect licensing and platform related information from InfoScale products as part of the Veritas Product Improvement Program. The information collected helps identify how customers deploy and use the product, and enables Veritas to manage customer licenses more efficiently. |
CFG{opt}{disable_dmp_native_support} | If it is set to 1, Dynamic Multi-pathing support for the native LVM volume groups and ZFS pools is disabled after upgrade. Retaining Dynamic Multi-pathing support for the native LVM volume groups and ZFS pools during upgrade increases fileset upgrade time depending on the number of LUNs and native LVM volume groups and ZFS pools configured on the system. List or scalar: scalar Optional or required: optional |
CFG{opt}{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 . List or scalar: scalar Optional or required: optional |
CFG{opt}{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. List or scalar: scalar Optional or required: optional |
CFG{opt}{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. List or scalar: scalar Optional or required: optional |
CFG{opt}{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. List or scalar: scalar Optional or required: optional |
CFG{opt}{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. List or scalar: scalar Optional or required: optional |
CFG{rootsecusrgrps} | Defines if the user chooses to grant read access to the cluster only for root and other users/usergroups which are granted explicit privileges on VCS objects. List or scalar: scalar Optional or required: optional |
CFG{secusrgrps} | Defines the usergroup names that are granted read access to the cluster. List or scalar: scalar Optional or required: optional |