Cluster Server 7.4.1 Configuration and Upgrade Guide - Solaris
- Section I. Configuring Cluster Server using the script-based installer
- I/O fencing requirements
- Preparing to configure VCS clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring VCS
- Overview of tasks to configure VCS using the product installer
- Starting the software configuration
- Specifying systems for configuration
- Configuring the cluster name
- Configuring private heartbeat links
- Configuring the virtual IP of the cluster
- Configuring VCS in secure mode
- Setting up trust relationships for your VCS cluster
- Configuring a secure cluster node by node
- Adding VCS users
- Configuring SMTP email notification
- Configuring SNMP trap notification
- Configuring global clusters
- Completing the VCS configuration
- About Veritas License Audit Tool
- Verifying and updating licenses on the system
- Configuring VCS clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Setting up non-SCSI-3 I/O fencing in virtual environments using installer
- Setting up majority-based I/O fencing using installer
- Enabling or disabling the preferred fencing policy
- Section II. Automated configuration using response files
- Performing an automated VCS configuration
- Performing an automated I/O fencing configuration using response files
- Configuring I/O fencing using response files
- Response file variables to configure disk-based I/O fencing
- Sample response file for configuring disk-based I/O fencing
- Response file variables to configure server-based I/O fencing
- Sample response file for configuring server-based I/O fencing
- Response file variables to configure non-SCSI-3 I/O fencing
- Sample response file for configuring non-SCSI-3 I/O fencing
- Response file variables to configure majority-based I/O fencing
- Sample response file for configuring majority-based I/O fencing
- Section III. Manual configuration
- Manually configuring VCS
- About configuring VCS manually
- Configuring LLT manually
- Configuring GAB manually
- Configuring VCS manually
- Configuring VCS in single node mode
- Starting LLT, GAB, and VCS after manual configuration
- About configuring cluster using VCS Cluster Configuration wizard
- Before configuring a VCS cluster using the VCS Cluster Configuration wizard
- Launching the VCS Cluster Configuration wizard
- Configuring a cluster by using the VCS cluster configuration wizard
- Adding a system to a VCS cluster
- Modifying the VCS configuration
- Manually configuring the clusters for data integrity
- Setting up disk-based I/O fencing manually
- Setting up server-based I/O fencing manually
- Preparing the CP servers manually for use by the VCS cluster
- Generating the client key and certificates manually on the client nodes
- Configuring server-based fencing on the VCS cluster manually
- Configuring CoordPoint agent to monitor coordination points
- Verifying server-based I/O fencing configuration
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Manually configuring VCS
- Section IV. Upgrading VCS
- Planning to upgrade VCS
- About upgrading to VCS 7.4.1
- Upgrading VCS in secure enterprise environments
- Supported upgrade paths
- Considerations for upgrading secure VCS 6.x clusters to VCS 7.4.1
- Considerations for upgrading VCS to 7.4.1 on systems configured with an Oracle resource
- Considerations for upgrading secure VCS clusters to VCS 7.4.1
- Considerations for upgrading CP servers
- Considerations for upgrading CP clients
- Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
- Performing a VCS upgrade using the installer
- Before upgrading VCS using the script-based installer
- Upgrading VCS using the product installer
- Upgrading to 2048 bit key and SHA256 signature certificates
- Tasks to perform after upgrading to 2048 bit key and SHA256 signature certificates
- Deleting certificates of non-root users after upgrading to 2048 bit key and SHA256 signature certificates
- Re-establishing WAC communication in global clusters after upgrading to 2048 bit key and SHA256 signature certificates
- Re-establishing CP server and CP client communication after upgrading to 2048 bit key and SHA256 signature certificates
- Re-establishing trust with Steward after upgrading to 2048 bit key and SHA256 signature certificates
- Upgrading Steward to 2048 bit key and SHA256 signature certificates
- Performing an online upgrade
- Performing a phased upgrade of VCS
- About phased upgrade
- Performing a phased upgrade using the product installer
- Moving the service groups to the second subcluster
- Upgrading the operating system on the first subcluster
- Upgrading the first subcluster
- Preparing the second subcluster
- Activating the first subcluster
- Upgrading the operating system on the second subcluster
- Upgrading the second subcluster
- Finishing the phased upgrade
- Performing an automated VCS upgrade using response files
- Upgrading VCS using Live Upgrade and Boot Environment upgrade
- Planning to upgrade VCS
- Section V. Adding and removing cluster nodes
- Adding a node to a single-node cluster
- Adding a node to a single-node cluster
- Adding a node to a multi-node VCS cluster
- Adding nodes using the VCS installer
- Manually adding a node to a cluster
- Setting up the hardware
- Installing the VCS software manually when adding a node
- Setting up the node to run in secure mode
- Configuring LLT and GAB when adding a node to the cluster
- Configuring I/O fencing on the new node
- Adding the node to the existing cluster
- Starting VCS and verifying the cluster
- Adding a node using response files
- Removing a node from a VCS cluster
- Removing a node from a VCS cluster
- Verifying the status of nodes and service groups
- Deleting the departing node from VCS configuration
- Modifying configuration files on each remaining node
- Removing the node configuration from the CP server
- Removing security credentials from the leaving node
- Unloading LLT and GAB and removing Veritas InfoScale Availability or Enterprise on the departing node
- Removing a node from a VCS cluster
- Adding a node to a single-node cluster
- Section VI. Installation reference
- Appendix A. Services and ports
- Appendix B. Configuration files
- Appendix C. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Broadcast address in the /etc/llttab file
- The link command in the /etc/llttab file
- The set-addr command in the /etc/llttab file
- Selecting UDP ports
- Configuring the netmask for LLT
- Configuring the broadcast address for LLT
- Sample configuration: direct-attached links
- Sample configuration: links crossing IP routers
- Manually configuring LLT over UDP using IPv6
- LLT over UDP sample /etc/llttab
- Appendix D. Migrating LLT links from IPv4 to IPv6 or dual-stack
- Appendix E. 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 and disabling rsh for Solaris
- Appendix F. Installation script options
- Appendix G. Troubleshooting VCS configuration
- Restarting the installer after a failed network connection
- Cannot launch the cluster view link
- Starting and stopping processes for the Veritas InfoScale products
- Installer cannot create UUID for the cluster
- LLT startup script displays errors
- The vxfentsthdw utility fails when SCSI TEST UNIT READY command fails
- Issues during fencing startup on VCS cluster nodes set up for server-based fencing
- Appendix H. Sample VCS cluster setup diagrams for CP server-based I/O fencing
- Appendix I. Reconciling major/minor numbers for NFS shared disks
- Appendix J. Upgrading the Steward process
Response file variables to configure VCS
Table: Response file variables specific to configuring VCS lists the response file variables that you can define to configure VCS.
Table: Response file variables specific to configuring VCS
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 VCS. |
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 VCS741 for VCS. (Required) |
CFG{keys}{keyless} CFG{keys}{license} | List | CFG{keys}{keyless} gives a list of keyless keys to be registered on the system. CFG{keys}{license} gives a list of user defined keys to be registered on the system. (Optional) |
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 AVAILABILITY741 for Veritas InfoScale Availability. (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 Veritas website. The value 0 indicates that the installation logs are not uploaded to the Veritas 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 VCS cluster lists the response file variables that specify the required information to configure a basic VCS cluster.
Table: Response file variables specific to configuring a basic VCS 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 VCS 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) |
Table: Response file variables specific to configuring virtual IP for VCS cluster lists the response file variables that specify the required information to configure virtual IP for VCS cluster.
Table: Response file variables specific to configuring virtual IP for VCS 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 VCS cluster in secure mode lists the response file variables that specify the required information to configure the VCS cluster in secure mode.
Table: Response file variables specific to configuring VCS 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.
|
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 VCS global clusters lists the response file variables that specify the required information to configure VCS global clusters.
Table: Response file variables specific to configuring VCS 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) |