Storage Foundation 7.4.2 Configuration and Upgrade Guide - AIX
- Section I. Introduction and configuration of Storage Foundation
- Section II. Upgrade of Storage Foundation
- Planning to upgrade Storage Foundation
- About the upgrade
- Supported upgrade paths
- Preparing to upgrade SF
- Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
- Upgrading Storage Foundation
- Performing an automated SF upgrade using response files
- Performing post-upgrade tasks
- Planning to upgrade Storage Foundation
- Section III. Post configuration tasks
- Section IV. Configuration and Upgrade reference
- Appendix A. Support for AIX Live Update
- Appendix B. Installation scripts
- Appendix C. Configuring the secure shell or the remote shell for communications
- About configuring secure shell or remote shell communication modes before installing products
- Manually configuring passwordless ssh
- Setting up ssh and rsh connection using the installer -comsetup command
- Setting up ssh and rsh connection using the pwdutil.pl utility
- Restarting the ssh session
- Enabling rsh for AIX
- Appendix D. Changing NFS server major numbers for VxVM volumes
Response file variables to upgrade SF
Table: Response file variables for upgrading SF lists the response file variables that you can define to configure SF.
Table: Response file variables for upgrading SF
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 |