InfoScale™ 9.0 Storage Foundation Cluster File System High Availability Configuration and Upgrade Guide - Solaris

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: Solaris
  1. Section I. Introduction to SFCFSHA
    1. Introducing Storage Foundation Cluster File System High Availability
      1.  
        About this document
      2.  
        About Storage Foundation Cluster File System High Availability
      3.  
        About InfoScale Operations Manager
      4.  
        About I/O fencing
      5.  
        About Services and Operations Readiness Tools (SORT)
      6. About configuring SFCFSHA clusters for data integrity
        1.  
          About I/O fencing for SFCFSHA in virtual machines that do not support SCSI-3 PR
        2. About I/O fencing components
          1.  
            About data disks
          2.  
            About coordination points
          3.  
            About preferred fencing
  2. Section II. Configuration of SFCFSHA
    1. Preparing to configure
      1. I/O fencing requirements
        1.  
          Coordinator disk requirements for I/O fencing
        2.  
          CP server requirements
        3.  
          Non-SCSI-3 I/O fencing requirements
    2. Preparing to configure SFCFSHA clusters for data integrity
      1. About planning to configure I/O fencing
        1.  
          Typical SFCFSHA cluster configuration with server-based I/O fencing
        2.  
          Recommended CP server configurations
      2. Setting up the CP server
        1.  
          Planning your CP server setup
        2.  
          Installing the CP server using the installer
        3.  
          Configuring the CP server cluster in secure mode
        4.  
          Setting up shared storage for the CP server database
        5.  
          Configuring the CP server using the installer program
        6. Configuring the CP server manually
          1.  
            Configuring the CP server manually for HTTPS-based communication
          2.  
            Generating the key and certificates manually for the CP server
          3.  
            Completing the CP server configuration
        7.  
          Verifying the CP server configuration
    3. Configuring SFCFSHA
      1.  
        Overview of tasks to configure SFCFSHA using the product installer
      2.  
        Starting the software configuration
      3.  
        Specifying systems for configuration
      4.  
        Configuring the cluster name
      5.  
        Configuring private heartbeat links
      6.  
        Configuring the virtual IP of the cluster
      7.  
        Configuring SFCFSHA in secure mode
      8. Configuring a secure cluster node by node
        1.  
          Configuring the first node
        2.  
          Configuring the remaining nodes
        3.  
          Completing the secure cluster configuration
      9.  
        Adding VCS users
      10.  
        Configuring SMTP email notification
      11.  
        Configuring SNMP trap notification
      12.  
        Configuring global clusters
      13.  
        Completing the SFCFSHA configuration
      14.  
        About the License Audit Tool
      15. Verifying and updating licenses on the system
        1.  
          Checking licensing information on the system
        2.  
          Replacing a SFCFSHA keyless license with another keyless license
        3.  
          Replacing a SFCFSHA keyless license with a permanent license
      16.  
        Configuring SFDB
    4. Configuring SFCFSHA clusters for data integrity
      1. Setting up disk-based I/O fencing using installer
        1.  
          Configuring disk-based I/O fencing using installer
        2.  
          Initializing disks as VxVM disks
        3. Checking shared disks for I/O fencing
          1.  
            Verifying Array Support Library (ASL)
          2.  
            Verifying that the nodes have access to the same disk
          3.  
            Testing the disks using vxfentsthdw utility
        4.  
          Refreshing keys or registrations on the existing coordination points for disk-based fencing using the installer
      2. Setting up server-based I/O fencing using installer
        1.  
          Refreshing keys or registrations on the existing coordination points for server-based fencing using the installer
        2. Setting the order of existing coordination points for server-based fencing using the installer
          1.  
            About deciding the order of existing coordination points
          2.  
            Setting the order of existing coordination points using the installer
      3.  
        Setting up non-SCSI-3 I/O fencing in virtual environments using installer
      4.  
        Setting up majority-based I/O fencing using installer
      5.  
        Enabling or disabling the preferred fencing policy
    5. Performing an automated SFCFSHA configuration using response files
      1.  
        Configuring SFCFSHA using response files
      2.  
        Response file variables to configure SFCFSHA
      3.  
        Sample response file for SFCFSHA configuration
    6. Performing an automated I/O fencing configuration using response files
      1.  
        Configuring I/O fencing using response files
      2.  
        Response file variables to configure disk-based I/O fencing
      3.  
        Sample response file for configuring disk-based I/O fencing
      4. Configuring CP server using response files
        1.  
          Response file variables to configure CP server
        2.  
          Sample response file for configuring the CP server on single node VCS cluster
        3.  
          Sample response file for configuring the CP server on SFHA cluster
      5.  
        Response file variables to configure server-based I/O fencing
      6.  
        Sample response file for configuring server-based I/O fencing
      7.  
        Response file variables to configure non-SCSI-3 I/O fencing
      8.  
        Sample response file for configuring non-SCSI-3 I/O fencing
      9.  
        Response file variables to configure majority-based I/O fencing
      10.  
        Sample response file for configuring majority-based I/O fencing
    7. Manually configuring SFCFSHA clusters for data integrity
      1. Setting up disk-based I/O fencing manually
        1.  
          Identifying disks to use as coordinator disks
        2.  
          Setting up coordinator disk groups
        3.  
          Creating I/O fencing configuration files
        4.  
          Modifying VCS configuration to use I/O fencing
        5.  
          Verifying I/O fencing configuration
      2. Setting up server-based I/O fencing manually
        1.  
          Preparing the CP servers manually for use by the SFCFSHA cluster
        2.  
          Generating the client key and certificates manually on the client nodes
        3. Configuring server-based fencing on the SFCFSHA cluster manually
          1.  
            Sample vxfenmode file output for server-based fencing
        4.  
          Configuring CoordPoint agent to monitor coordination points
        5.  
          Verifying server-based I/O fencing configuration
      3. Setting up non-SCSI-3 fencing in virtual environments manually
        1.  
          Sample /etc/vxfenmode file for non-SCSI-3 fencing
      4. Setting up majority-based I/O fencing manually
        1.  
          Creating I/O fencing configuration files
        2.  
          Modifying VCS configuration to use I/O fencing
        3.  
          Verifying I/O fencing configuration
  3. Section III. Upgrade of SFCFSHA
    1. Planning to upgrade SFCFSHA
      1.  
        About the upgrade
      2.  
        Supported upgrade paths
      3.  
        Transitioning between the InfoScale products
      4.  
        Considerations for upgrading SFCFSHA to 9.0 on systems configured with an Oracle resource
      5. Preparing to upgrade SFCFSHA
        1.  
          Getting ready for the upgrade
        2.  
          Creating backups
        3. Pre-upgrade planning when VVR is configured
          1. Planning an upgrade from the previous VVR version
            1.  
              Planning and upgrading VVR to use IPv6 as connection protocol
          2.  
            Additional settings for using VVR in a localized environment
          3.  
            Considerations for upgrading SFCFSHA to 7.4 or later on systems with an ongoing or a paused replication
        4. Preparing to upgrade VVR when VCS agents are configured
          1. Freezing the service groups and stopping all the applications
            1.  
              Determining the nodes on which disk groups are online
          2.  
            Preparing for the upgrade when VCS agents are configured
        5.  
          Verifying that the file systems are clean
        6.  
          Upgrading the array support
      6.  
        Considerations for upgrading REST server
      7.  
        Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
    2. Performing a full upgrade of SFCFSHA using the installer
      1. Performing a full upgrade using the product installer
        1.  
          Ensuring the file systems are clean
        2.  
          Modifying the main.cf file
        3. Performing the upgrade
          1.  
            Updating the configuration and confirming startup
        4.  
          Upgrading the operating system
      2.  
        Upgrading SFDB
      3.  
        Upgrading language packages
    3. Performing a rolling upgrade of SFCFSHA
      1.  
        About rolling upgrade
      2.  
        About rolling upgrade with local zone on Solaris 11
      3.  
        Performing a rolling upgrade of SFCFSHA using the product installer
    4. Performing a phased upgrade of SFCFSHA
      1. About phased upgrade
        1.  
          Prerequisites for a phased upgrade
        2.  
          Planning for a phased upgrade
        3.  
          Phased upgrade limitations
        4.  
          Phased upgrade example
        5.  
          Phased upgrade example overview
      2. Performing a phased upgrade using the product installer
        1.  
          Moving the service groups to the second subcluster
        2.  
          Upgrading the operating system on the first subcluster
        3.  
          Upgrading the SFCFSHA stack on the first subcluster
        4.  
          Preparing the second subcluster
        5.  
          Activating the first subcluster
        6.  
          Upgrading the operating system on the second subcluster
        7.  
          Upgrading the second subcluster
        8.  
          Completing the phased upgrade
    5. Performing an automated SFCFSHA upgrade using response files
      1.  
        Upgrading SFCFSHA using response files
      2.  
        Response file variables to upgrade SFCFSHA
      3.  
        Sample response file for full upgrade of SFCFSHA
      4.  
        Sample response file for rolling upgrade of SFCFSHA
    6. Upgrading Volume Replicator
      1.  
        Upgrading Volume Replicator
      2. Upgrading VVR without disrupting replication
        1.  
          Upgrading VVR sites for InfoScale 7.3.1
        2.  
          Upgrading VVR sites with InfoScale 7.4 or later
        3.  
          Upgrading VVR sites in VCS control for InfoScale 7.3.1
        4.  
          Upgrading VVR sites in VCS control for InfoScale 7.4 or later
        5.  
          Post-upgrade tasks for VVR sites
    7. Upgrading VirtualStore
      1.  
        Supported upgrade paths
      2.  
        Upgrading SVS to SFCFSHA 9.0
    8. Upgrading SFCFSHA using Boot Environment upgrade
      1.  
        About ZFS Boot Environment (BE) upgrade
      2.  
        Supported upgrade paths for Boot Environment upgrade
      3. Performing Boot Environment upgrade on Solaris 11 systems
        1.  
          Creating a new Solaris 11 BE on the primary boot disk
        2.  
          Upgrading SFCFSHA using the installer for upgrading BE on Solaris 11
        3.  
          Completing the SFCFSHA upgrade on BE on Solaris 11
        4.  
          Verifying Solaris 11 BE upgrade
        5. Administering BEs on Solaris 11 systems
          1.  
            Reverting to the primary BE on a Solaris 11 system
      4.  
        About Live Upgrade in a Volume Replicator (VVR) environment
    9. Performing post-upgrade tasks
      1.  
        Resetting DAS disk names to include host name in FSS environments
      2.  
        CVM master node needs to assume the logowner role for VCS managed VVR resources
  4. Section IV. Post-configuration tasks
    1. Performing post configuration tasks
      1.  
        Changing root user into root role
      2.  
        Upgrading disk layout versions
      3.  
        Switching on Quotas
      4. About enabling LDAP authentication for clusters that run in secure mode
        1.  
          Enabling LDAP authentication for clusters that run in secure mode
      5. About configuring authentication for SFDB tools
        1.  
          Configuring vxdbd for SFDB tools authentication
  5. Section V. Configuration of disaster recovery environments
    1. Configuring disaster recovery environments
      1.  
        Disaster recovery options for SFCFSHA
      2.  
        About setting up a campus cluster for disaster recovery
      3.  
        About setting up a global cluster environment for SFCFSHA
      4.  
        About configuring a parallel global cluster using Volume Replicator (VVR) for replication
  6. Section VI. Adding and removing nodes
    1. Adding a node to SFCFSHA clusters
      1.  
        About adding a node to a cluster
      2.  
        Before adding a node to a cluster
      3.  
        Adding a node to a cluster using the Veritas InfoScale installer
      4. Adding the node to a cluster manually
        1.  
          Starting Veritas Volume Manager (VxVM) on the new node
        2.  
          Configuring cluster processes on the new node
        3. Setting up the node to run in secure mode
          1.  
            Configuring the authentication broker on node sys5
        4.  
          Starting fencing on the new node
        5.  
          After adding the new node
        6.  
          Configuring Cluster Volume Manager (CVM) and Cluster File System (CFS) on the new node
        7.  
          Configuring the ClusterService group for the new node
      5. Adding a node using response files
        1.  
          Response file variables to add a node to a SFCFSHA cluster
        2.  
          Sample response file for adding a node to a SFCFSHA cluster
      6. Configuring server-based fencing on the new node
        1.  
          Adding the new node to the vxfen service group
      7.  
        Adding nodes to a cluster that is using authentication for SFDB tools
      8.  
        Updating the Storage Foundation for Databases (SFDB) repository after adding a node
      9.  
        Sample configuration file for adding a node to the cluster
    2. Removing a node from SFCFSHA clusters
      1.  
        About removing a node from a cluster
      2.  
        Removing a node from a cluster
      3.  
        Modifying the VCS configuration files on existing nodes
      4.  
        Modifying the Cluster Volume Manager (CVM) configuration on the existing nodes to remove references to the deleted node
      5.  
        Removing the node configuration from the CP server
      6.  
        Removing security credentials from the leaving node
      7.  
        Updating the Storage Foundation for Databases (SFDB) repository after removing a node
      8.  
        Sample configuration file for removing a node from the cluster
  7. Section VII. Configuration and Upgrade reference
    1. Appendix A. Installation scripts
      1.  
        Installation script options
      2.  
        About using the postcheck option
    2. Appendix B. Configuration files
      1.  
        About the LLT and GAB configuration files
      2.  
        About the AMF configuration files
      3.  
        About I/O fencing configuration files
      4. Sample configuration files for CP server
        1.  
          Sample main.cf file for CP server hosted on a single node that runs VCS
        2.  
          Sample main.cf file for CP server hosted on a two-node SFHA cluster
        3.  
          Sample CP server configuration (/etc/vxcps.conf) file output
      5.  
        Packaging related SMF services on Solaris 11
    3. Appendix C. Configuring the secure shell or the remote shell for communications
      1.  
        About configuring secure shell or remote shell communication modes before installing products
      2.  
        Manually configuring passwordless ssh
      3.  
        Setting up ssh and rsh connection using the installer -comsetup command
      4.  
        Setting up ssh and rsh connection using the pwdutil.pl utility
      5.  
        Restarting the ssh session
      6.  
        Enabling and disabling rsh for Solaris
    4. Appendix D. High availability agent information
      1. About agents
        1.  
          VCS agents included within SFCFSHA
      2. Enabling and disabling intelligent resource monitoring for agents manually
        1.  
          Administering the AMF kernel driver
      3. CVMCluster agent
        1.  
          Entry points for CVMCluster agent
        2.  
          Attribute definition for CVMCluster agent
        3.  
          CVMCluster agent type definition
        4.  
          CVMCluster agent sample configuration
      4. CVMVxconfigd agent
        1.  
          Entry points for CVMVxconfigd agent
        2.  
          Attribute definition for CVMVxconfigd agent
        3.  
          CVMVxconfigd agent type definition
        4.  
          CVMVxconfigd agent sample configuration
      5. CVMVolDg agent
        1.  
          Entry points for CVMVolDg agent
        2.  
          Attribute definition for CVMVolDg agent
        3.  
          CVMVolDg agent type definition
        4.  
          CVMVolDg agent sample configuration
      6. CFSMount agent
        1.  
          Entry points for CFSMount agent
        2.  
          Attribute definition for CFSMount agent
        3.  
          CFSMount agent type definition
        4.  
          CFSMount agent sample configuration
      7. CFSfsckd agent
        1.  
          Entry points for CFSfsckd agent
        2.  
          Attribute definition for CFSfsckd agent
        3.  
          CFSfsckd agent type definition
        4.  
          CFSfsckd agent sample configuration
    5. Appendix E. Sample SFCFSHA cluster setup diagrams for CP server-based I/O fencing
      1. Configuration diagrams for setting up server-based I/O fencing
        1.  
          Two unique client clusters served by 3 CP servers
        2.  
          Client cluster served by highly available CPS and 2 SCSI-3 disks
        3.  
          Two node campus cluster served by remote CP server and 2 SCSI-3 disks
        4.  
          Multiple client clusters served by highly available CP server and 2 SCSI-3 disks
    6. Appendix F. Reconciling major/minor numbers for NFS shared disks
      1. Reconciling major/minor numbers for NFS shared disks
        1.  
          Checking major and minor numbers for disk partitions
        2.  
          Checking the major and minor number for VxVM volumes
    7. Appendix G. Configuring LLT over UDP
      1. Using the UDP layer for LLT
        1.  
          When to use LLT over UDP
      2. Manually configuring LLT over UDP using IPv4
        1.  
          Broadcast address in the /etc/llttab file
        2.  
          The link command in the /etc/llttab file
        3.  
          The set-addr command in the /etc/llttab file
        4.  
          Selecting UDP ports
        5.  
          Configuring the netmask for LLT
        6.  
          Configuring the broadcast address for LLT
        7.  
          Sample configuration: direct-attached links
        8.  
          Sample configuration: links crossing IP routers
      3. Using the UDP layer of IPv6 for LLT
        1.  
          When to use LLT over UDP
      4. Manually configuring LLT over UDP using IPv6
        1.  
          The link command in the /etc/llttab file
        2.  
          The set-addr command in the /etc/llttab file
        3.  
          Selecting UDP ports
        4.  
          Sample configuration: direct-attached links
        5.  
          Sample configuration: links crossing IP routers

Response file variables to configure SFCFSHA

Table: Response file variables specific to configuring SFCFSHA lists the response file variables that you can define to configure SFCFSHA.

Table: Response file variables specific to configuring SFCFSHA

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 SFCFSHA.

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 SFCFSHA90 for SFCFSHA.

(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 specified logpath location.

(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 SFCFSHA cluster lists the response file variables that specify the required information to configure a basic SFCFSHA cluster.

Table: Response file variables specific to configuring a basic SFCFSHA 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 SFCFSHA 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#}

{"system"}

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.

You must enclose the system name within double quotes.

(Required)

CFG{vcs_lltlinklowpri#}

{"system"}

Scalar

Defines a low priority heartbeat link. Typically, lltlinklowpri is used on a public network link to provide an additional layer of communication.

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<n>_address}

{<sys1>}

Scalar

Stores the IP address (IPv4 or IPv6) that the heartbeat link uses on node1.

You can have four heartbeat links and <n> for this response file variable can take values 1 to 4 for the respective heartbeat links.

(Required)

CFG

{vcs_udplinklowpri<n>_address}

{<sys1>}

Scalar

Stores the IP address (IPv4 or IPv6) that the low priority heartbeat link uses on node1.

You can have four low priority heartbeat links and <n> for this response file variable can take values 1 to 4 for the respective low priority heartbeat links.

(Required)

CFG{vcs_udplink<n>_port}

{<sys1>}

Scalar

Stores the UDP port (16-bit integer value) that the heartbeat link uses on node1.

You can have four heartbeat links and <n> for this response file variable can take values 1 to 4 for the respective heartbeat links.

(Required)

CFG{vcs_udplinklowpri<n>_port}

{<sys1>}

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 <n> for this response file variable can take values 1 to 4 for the respective low priority heartbeat links.

(Required)

CFG{vcs_udplink<n>_netmask}

{<sys1>}

Scalar

Stores the netmask (prefix for IPv6) that the heartbeat link uses on node1.

You can have four heartbeat links and <n> for this response file variable can take values 1 to 4 for the respective heartbeat links.

(Required)

CFG{vcs_udplinklowpri<n>_netmask}

{<sys1>}

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 <n> 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 SFCFSHA cluster lists the response file variables that specify the required information to configure virtual IP for SFCFSHA cluster.

Table: Response file variables specific to configuring virtual IP for SFCFSHA cluster

Variable

List or Scalar

Description

CFG{vcs_csgnic}

{system}

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.

(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 SFCFSHA cluster in secure mode lists the response file variables that specify the required information to configure the SFCFSHA cluster in secure mode.

Table: Response file variables specific to configuring SFCFSHA 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 SFCFSHA global clusters lists the response file variables that specify the required information to configure SFCFSHA global clusters.

Table: Response file variables specific to configuring SFCFSHA global clusters

Variable

List or Scalar

Description

CFG{vcs_gconic}

{system}

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.

(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)