Response file variables to configure SFHA

Last published : Sep 28, 2026
Table: Response file variables specific to configuring SFHA lists the response file variables that you can define to configure SFHA.

Table: Response file variables specific to configuring SFHA

Variable List or Scalar Description
CFG{opt}{configure} Scalar Performs the configuration if the packages are already installed.
(Required)
Set the value to 1 to configure SFHA.
CFG{accepteula} Scalar Specifies whether you agree with EULA.pdf on the media.
(Required)
CFG{activecomponent} List Defines the component to be
configured.
The value is SFHA90 for SFHA.
(Required)
CFG{systems} List List of systems on which the product is to be configured.
(Required)
CFG{prod} Scalar Defines the product for operations.
The value is ENTERPRISE90 for Arctera InfoScale Enterprise.
(Required)
CFG{opt}{keyfile} Scalar Defines the location of an ssh keyfile that is used to communicate with all remote systems.
(Optional)
CFG{opt}{rsh} Scalar Defines that rsh must be used instead of ssh as the communication method between systems.
(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{uploadlogs} Scalar Defines a Boolean value 0 or 1.
The value 1 indicates that the installation logs are uploaded to the Arctera website.
The value 0 indicates that the installation logs are not uploaded to the Arctera website.
(Optional)
Note that some optional variables make it necessary to define other optional variables. For example, all the variables that are related to the cluster service group (csgnic, csgvip, and csgnetmask) must be defined if any are defined. The same is true for the SMTP notification (smtpserver, smtprecp, and smtprsev), the SNMP trap notification (snmpport, snmpcons, and snmpcsev), and the Global Cluster Option (gconic, gcovip, and gconetmask).
Table: Response file variables specific to configuring a basic SFHA cluster lists the response file variables that specify the required information to configure a basic SFHA cluster.
Table: Response file variables specific to configuring a basic SFHA cluster
Variable List or Scalar Description
CFG{donotreconfigurevcs} Scalar Defines if you need to re-configure VCS.
(Optional)
CFG{donotreconfigurefencing} Scalar Defines if you need to re-configure fencing.
(Optional)
CFG{vcs_clusterid} Scalar An integer between 0 and 65535 that uniquely identifies the cluster.
(Required)
CFG{vcs_clustername} Scalar Defines the name of the cluster.
(Required)
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{fencingenabled} Scalar In a SFHA configuration, defines if fencing is enabled.
Valid values are 0 or 1.
(Required)
Table: Response file variables specific to configuring private LLT over Ethernet lists the response file variables that specify the required information to configure LLT over Ethernet.
Table: Response file variables specific to configuring private LLT over Ethernet
Variable List or Scalar Description
CFG{vcs_lltlink#} Scalar Defines the NIC to be used for a private heartbeat link on each system. At least two LLT links are required per system (lltlink1 and lltlink2). You can configure up to four LLT links.
{"system"} You must enclose the system name within double quotes.
(Required)
CFG{vcs_lltlinklowpri#} Scalar Defines a low priority heartbeat link. Typically, lltlinklowpri is used on a public network link to provide an additional layer of communication.
{"system"} If you use different media speed for the private NICs, you can configure the NICs with lesser speed as low-priority links to enhance LLT
performance. For example, lltlinklowpri1, lltlinklowpri2, and so on.
You must enclose the system name within double quotes.
(Optional)
Table: Response file variables specific to configuring LLT over UDP lists the response file variables that specify the required information to configure LLT over UDP.
Table: Response file variables specific to configuring LLT over UDP
Variable List or Scalar Description
CFG{lltoverudp}=1 Scalar Indicates whether to configure heartbeat link using LLT over UDP.
(Required)
CFG{vcs_udplink_address} Scalar Stores the IP address (IPv4 or IPv6) that the heartbeat link uses on node1.
{} You can have four heartbeat links and for this response file variable can take values 1 to 4 for the respective heartbeat links.
(Required)
CFG Scalar Stores the IP address (IPv4 or IPv6) that the low priority heartbeat link uses on node1.
{vcs_udplinklowpri_address} You can have four low priority heartbeat links and for this response file variable can take values 1 to 4 for the respective low priority heartbeat links.
{} (Required)
CFG{vcs_udplink_port} Scalar Stores the UDP port (16-bit integer value) that the heartbeat link uses on node1.
{} You can have four heartbeat links and for this response file variable can take values 1 to 4 for the respective heartbeat links.
(Required)
CFG{vcs_udplinklowpri_port} Scalar Stores the UDP port (16-bit integer value) that the low priority heartbeat link uses on node1.
{} You can have four low priority heartbeat links and for this response file variable can take values 1 to 4 for the respective low priority heartbeat links.
(Required)
CFG{vcs_udplink_netmask} Scalar Stores the netmask (prefix for IPv6) that the heartbeat link uses on node1.
{} You can have four heartbeat links and for this response file variable can take values 1 to 4 for the respective heartbeat links.
(Required)
CFG{vcs_udplinklowpri_netmask} Scalar Stores the netmask (prefix for IPv6) that the low priority heartbeat link uses on node1.
{} You can have four low priority heartbeat links and for this response file variable can take values 1 to 4 for the respective low priority heartbeat links.
(Required)
CFG{clientid} Scalar Defines the Azure user client id to create AzureAuthRes .
CFG{subscriptionid} Scalar Defines the Azure user subscription id to create AzureAuthRes .
CFG{tenantid} Scalar Defines the Azure user tenant id to create AzureAuthRes .
CFG{secretkey} Scalar Defines the Azure user encoded secret key to create AzureAuthRes .
Table: Response file variables specific to configuring virtual IP for SFHA cluster lists the response file variables that specify the required information to configure virtual IP for SFHA cluster.
Table: Response file variables specific to configuring virtual IP for SFHA cluster
Variable List or Scalar Description
CFG{vcs_csgnic} Scalar Defines the NIC device to use on a system. You can enter 'all' as a system value if the same NIC is used on all systems.
{system} (Optional)
CFG{vcs_csgvip} Scalar Defines the virtual IP address for the cluster.
(Optional)
CFG{vcs_csgnetmask} Scalar Defines the Netmask of the virtual IP address for the cluster.
(Optional)
Table: Response file variables specific to configuring SFHA cluster in secure mode lists the response file variables that specify the required information to configure the SFHA cluster in secure mode.
Table: Response file variables specific to configuring SFHA cluster in secure mode
Variable List or Scalar Description
CFG{vcs_eat_security} Scalar Specifies if the cluster is in secure enabled mode or not.
CFG{opt}{securityonenode} Scalar Specifies that the securityonenode option is being used.
CFG{securityonenode_menu} Scalar Specifies the menu option to choose to configure the secure cluster one at a time.
- 1 - Configure the first node
- 2 - Configure the other node
CFG{secusrgrps} List Defines the user groups which get read
access to the cluster.
List or scalar: list
Optional or required: optional
CFG{rootsecusrgrps} Scalar Defines the read access to the cluster only for root and other users or user groups which are granted explicit privileges in VCS objects.
(Optional)
CFG{security_conf_dir} Scalar Specifies the directory where the configuration files are placed.
CFG{opt}{security} Scalar Specifies that the security option is being used.
CFG{defaultaccess} Scalar Defines if the user chooses to grant read access to
everyone.
Optional or required: optional
CFG{vcs_eat_security_fips} Scalar Specifies that the enabled security is FIPS compliant.
Table: Response file variables specific to configuring VCS users lists the response file variables that specify the required information to configure VCS users.
Table: Response file variables specific to configuring VCS users
Variable List or Scalar Description
CFG{vcs_userenpw} List List of encoded passwords for VCS users
The value in the list can be "Administrators Operators Guests"
Note: The order of the values for the vcs_userenpw list must match the order of the values in the vcs_username list.
(Optional)
CFG{vcs_username} List List of names of VCS users
(Optional)
CFG{vcs_userpriv} List List of privileges for VCS users
Note: The order of the values for the vcs_userpriv list must match the order of the values in the vcs_username list.
(Optional)
Table: Response file variables specific to configuring VCS notifications using SMTP lists the response file variables that specify the required information to configure VCS notifications using SMTP.
Table: Response file variables specific to configuring VCS notifications using SMTP
Variable List or Scalar Description
CFG{vcs_smtpserver} Scalar Defines the domain-based hostname (example: smtp.example.com) of the SMTP server to be used for web notification.
(Optional)
CFG{vcs_smtprecp} List List of full email addresses (example: user@example.com) of SMTP recipients.
(Optional)
CFG{vcs_smtprsev} List Defines the minimum severity level of messages (Information, Warning, Error, SevereError) that listed SMTP recipients are to receive. Note that the ordering of severity levels must match that of the addresses of SMTP recipients.
(Optional)
Table: Response file variables specific to configuring VCS notifications using SNMP lists the response file variables that specify the required information to configure VCS notifications using SNMP.
Table: Response file variables specific to configuring VCS notifications using SNMP
Variable List or Scalar Description
CFG{vcs_snmpport} Scalar Defines the SNMP trap daemon port (default=162).
(Optional)
CFG{vcs_snmpcons} List List of SNMP console system names
(Optional)
CFG{vcs_snmpcsev} List Defines the minimum severity level of messages (Information, Warning, Error, SevereError) that listed SNMP consoles are to receive. Note that the ordering of severity levels must match that of the SNMP console system names.
(Optional)
Table: Response file variables specific to configuring SFHA global clusters lists the response file variables that specify the required information to configure SFHA global clusters.
Table: Response file variables specific to configuring SFHA global clusters
Variable List or Scalar Description
CFG{vcs_gconic} Scalar Defines the NIC for the Virtual IP that the Global Cluster Option uses. You can enter 'all' as a system value if the same NIC is used on all systems.
{system} (Optional)
CFG{vcs_gcovip} Scalar Defines the virtual IP address to that the Global Cluster Option uses.
(Optional)
CFG{vcs_gconetmask} Scalar Defines the Netmask of the virtual IP address that the Global Cluster Option uses.
(Optional)