Response file variables to upgrade VCS

Last published : Jun 11, 2026
Table: Response file variables specific to upgrading VCS lists the response file variables that you can define to upgrade VCS.

Table: Response file variables specific to upgrading VCS

Variable List or Scalar Description
CFG{opt}{upgrade} Scalar Upgrades VCS filesets.
(Required)
CFG{accepteula} Scalar Specifies whether you agree with EULA.pdf on the media.
(Required)
CFG{systems} List List of systems on which the product is to be upgraded.
(Required)
CFG{defaultaccess} Scalar (optional) Defines if the user chooses to grant read access for VCS cluster information to everyone.
CFG{key} Scalar (optional) Stores the keyless key you want to register.
CFG{vcs_allowcomms} Scalar Indicates whether or not to start LLT and GAB when you set up a single-node cluster. The value can be 0 (do not start) or 1 (start).
(Required)
CFG{opt}{keyfile} Scalar Defines the location of an ssh keyfile that is used to communicate with all remote systems.
(Optional)
CFG{opt}{pkgpath} Scalar Defines a location, typically an NFS mount, from which all remote systems can install product filesets. The location must be accessible from all target systems.
(Optional)
CFG{opt}{tmppath} Scalar 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 /var/tmp.
(Optional)
CFG{secusrgrps} List Defines the user groups which get read access to the cluster.
(Optional)
CFG{opt}{logpath} Scalar Mentions the location where the log files are to be copied. The default location is /opt/VRTS/install/logs.
Note: The installer copies the response files and summary files also to the specifiedlogpathlocation.
(Optional)
CFG{opt}{rsh} Scalar Defines that rsh must be used instead of ssh as the communication method between systems.
(Optional)
CFG{opt}{online_upgrade} Scalar Set the value to 1 for online upgrades.