Cluster Server 7.4.2 Configuration and Upgrade Guide - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.2)
Platform: Linux
  1. Section I. Configuring Cluster Server using the script-based installer
    1. I/O fencing requirements
      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 VCS clusters for data integrity
      1. About planning to configure I/O fencing
        1.  
          Typical VCS cluster configuration with disk-based I/O fencing
        2.  
        3.  
          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.  
          Setting up shared storage for the CP server database
        4.  
          Configuring the CP server using the installer program
        5. 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
        6. 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
        7.  
          Verifying the CP server configuration
    3. Configuring VCS
      1.  
        Overview of tasks to configure VCS 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 VCS in secure mode
      8.  
        Setting up trust relationships for your VCS cluster
      9. Configuring a secure cluster node by node
        1.  
          Configuring the first node
        2.  
          Configuring the remaining nodes
        3.  
          Completing the secure cluster configuration
      10.  
        Adding VCS users
      11.  
        Configuring SMTP email notification
      12.  
        Configuring SNMP trap notification
      13.  
        Configuring global clusters
      14. Completing the VCS configuration
        1.  
          Verifying the NIC configuration
      15.  
        About Veritas License Audit Tool
      16. Verifying and updating licenses on the system
        1.  
          Checking licensing information on the system
        2.  
          Replacing a VCS keyless license with another keyless license
        3.  
          Replacing a VCS keyless license with a permanent license
    4. Configuring VCS clusters for data integrity
      1. Setting up disk-based I/O fencing using installer
        1.  
          Initializing disks as VxVM disks
        2.  
          Configuring disk-based I/O fencing using installer
        3.  
          Refreshing keys or registrations on the existing coordination points for disk-based fencing using the installer
        4. 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
      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
  2. Section II. Automated configuration using response files
    1. Performing an automated VCS configuration
      1.  
        Configuring VCS using response files
      2.  
        Response file variables to configure VCS
      3.  
        Sample response file for configuring Cluster Server
    2. 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.  
        Response file variables to configure server-based I/O fencing
      5.  
        Sample response file for configuring server-based I/O fencing
      6.  
        Response file variables to configure non-SCSI-3 I/O fencing
      7.  
        Sample response file for configuring non-SCSI-3 I/O fencing
      8.  
        Response file variables to configure majority-based I/O fencing
      9.  
        Sample response file for configuring majority-based I/O fencing
  3. Section III. Manual configuration
    1. Manually configuring VCS
      1.  
        About configuring VCS manually
      2. Configuring LLT manually
        1.  
          Setting up /etc/llthosts for a manual installation
        2.  
          Setting up /etc/llttab for a manual installation
        3.  
          About LLT directives in /etc/llttab file
        4.  
          Additional considerations for LLT for a manual installation
      3.  
        Configuring GAB manually
      4. Configuring VCS manually
        1.  
          Configuring the cluster UUID when creating a cluster manually
      5. Configuring VCS in single node mode
        1. Disabling LLT, GAB, and I/O fencing on a single node cluster
          1.  
            Disabling LLT, GAB, and I/O fencing
        2.  
          Enabling LLT, GAB, and I/O fencing
      6.  
        Starting LLT, GAB, and VCS after manual configuration
      7.  
        About configuring cluster using VCS Cluster Configuration wizard
      8.  
        Before configuring a VCS cluster using the VCS Cluster Configuration wizard
      9.  
        Launching the VCS Cluster Configuration wizard
      10.  
        Configuring a cluster by using the VCS cluster configuration wizard
      11.  
        Adding a system to a VCS cluster
      12. Modifying the VCS configuration
        1.  
          Configuring the ClusterService group
    2. Manually configuring the 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 VCS cluster
        2.  
          Generating the client key and certificates manually on the client nodes
        3. Configuring server-based fencing on the VCS 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
        4.  
          Sample /etc/vxfenmode file for majority-based fencing
  4. Section IV. Upgrading VCS
    1. Planning to upgrade VCS
      1.  
        About upgrading to VCS 7.4.2
      2.  
        Upgrading VCS in secure enterprise environments
      3.  
        Supported upgrade paths
      4.  
        Considerations for upgrading secure VCS 6.x clusters to VCS 7.4.2
      5.  
        Considerations for upgrading VCS to 7.4.2 on systems configured with an Oracle resource
      6.  
        Considerations for upgrading CP servers
      7.  
        Considerations for upgrading CP clients
      8.  
        Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
    2. Performing a VCS upgrade using the installer
      1.  
        Before upgrading VCS using the script-based installer
      2.  
        Upgrading VCS using the product installer
      3.  
        Upgrading to 2048 bit key and SHA256 signature certificates
      4. Tasks to perform after upgrading to 2048 bit key and SHA256 signature certificates
        1.  
          Deleting certificates of non-root users after upgrading to 2048 bit key and SHA256 signature certificates
        2.  
          Re-establishing WAC communication in global clusters after upgrading to 2048 bit key and SHA256 signature certificates
        3.  
          Re-establishing CP server and CP client communication after upgrading to 2048 bit key and SHA256 signature certificates
        4.  
          Re-establishing trust with Steward after upgrading to 2048 bit key and SHA256 signature certificates
      5.  
        Upgrading Steward to 2048 bit key and SHA256 signature certificates
    3. Performing an online upgrade
      1.  
        Limitations of online upgrade
      2.  
        Upgrading VCS online using the installer
    4. Performing a phased upgrade of VCS
      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 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.  
          Finishing the phased upgrade
    5. Performing an automated VCS upgrade using response files
      1.  
        Upgrading VCS using response files
      2.  
        Response file variables to upgrade VCS
      3.  
        Sample response file for full upgrade of VCS
  5. Section V. Adding and removing cluster nodes
    1. Adding a node to a single-node cluster
      1. Adding a node to a single-node cluster
        1. Setting up a node to join the single-node cluster
          1.  
            Installing VxVM or VxFS if necessary
        2.  
          Installing and configuring Ethernet cards for private network
        3.  
          Configuring the shared storage
        4.  
          Bringing up the existing node
        5.  
          Creating configuration files
        6.  
          Starting LLT and GAB
        7.  
          Reconfiguring VCS on the existing node
        8.  
          Verifying configuration on both nodes
    2. Adding a node to a multi-node VCS cluster
      1.  
        Adding nodes using the VCS installer
      2. Manually adding a node to a cluster
        1.  
          Setting up the hardware
        2.  
          Installing the VCS software manually when adding a node
        3. Setting up the node to run in secure mode
          1.  
            Configuring the authentication broker on node sys5
        4.  
          Configuring LLT and GAB when adding a node to the cluster
        5. Configuring I/O fencing on the new node
          1.  
            Preparing to configure I/O fencing on the new node
          2. Configuring server-based fencing on the new node
            1.  
              Adding the new node to the vxfen service group
          3.  
            Starting I/O fencing on the new node
        6.  
          Adding the node to the existing cluster
        7.  
          Starting VCS and verifying the cluster
        8. Adding a node using response files
          1.  
            Response file variables to add a node to a VCS cluster
          2.  
            Sample response file for adding a node to a VCS cluster
    3. Removing a node from a VCS cluster
      1. Removing a node from a VCS cluster
        1.  
          Verifying the status of nodes and service groups
        2.  
          Deleting the departing node from VCS configuration
        3.  
          Modifying configuration files on each remaining node
        4.  
          Removing the node configuration from the CP server
        5.  
          Removing security credentials from the leaving node
        6.  
          Unloading LLT and GAB and removing Veritas InfoScale Availability or Enterprise on the departing node
  6. Section VI. Installation reference
    1. Appendix A. Services and ports
      1.  
        About InfoScale Enterprise services and ports
    2. Appendix B. Configuration files
      1.  
        About the LLT and GAB configuration files
      2.  
        About the AMF configuration files
      3. About the VCS configuration files
        1.  
          Sample main.cf file for VCS clusters
        2.  
          Sample main.cf file for global clusters
      4.  
        About I/O fencing configuration files
      5. 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
      6. Tuning LLT variables for FSS environments
        1.  
          Tuning LLT variables for RDMA links
        2.  
          Tuning LLT variables for Ethernet links
        3. Configuring parallel ports for I/O shipping
          1.  
            To tune the LLT variables for I/O shipping
    3. Appendix C. 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. 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
      4.  
        LLT over UDP sample /etc/llttab
      5. About configuring LLT over UDP multiport
        1.  
          Manually configuring LLT over UDP multiport
        2.  
          Enabling LLT ports in firewall
        3.  
          Disabling the UDP multiport feature
    4. Appendix D. Configuring LLT over TCP
      1.  
        Using the TCP layer for LLT
      2. Manually configuring LLT over TCP 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 TCP ports
        5.  
          Configuring the netmask for LLT
        6.  
          Configuring the broadcast address for LLT
        7.  
          Sample configuration: direct-attached link
        8.  
          Sample configuration: link crossing IP routers
      3. Manually configuring LLT over TCP using IPv6
        1.  
          The link command in the /etc/llttab file
        2.  
          The set-addr command in the /etc/llttab file
        3.  
          Selecting TCP ports
        4.  
          Sample configuration: direct-attached links
        5.  
          Sample configuration: links crossing IP routers
      4.  
        LLT over TCP sample /etc/llttab
    5. Appendix E. Migrating LLT links from IPv4 to IPv6 or dual-stack
      1.  
        About migrating the LLT links from IPv4 to IPv6 or to a dual-stack network
      2.  
        Review the current configuration
      3.  
        Meet the prerequisites for migration
      4.  
        Adding a new node to an existing cluster
      5.  
        Migrating LLT links to IPv6 or dual-stack when LLT is configured over UDP using IPv4
      6.  
        Migrating LLT links to IPv6 or dual-stack when LLT is configured over TCP using IPv4
    6. Appendix F. Using LLT over RDMA
      1.  
        Using LLT over RDMA
      2.  
        About RDMA over RoCE or InfiniBand networks in a clustering environment
      3.  
        How LLT supports RDMA capability for faster interconnects between applications
      4.  
        Using LLT over RDMA: supported use cases
      5. Configuring LLT over RDMA
        1.  
          Choosing supported hardware for LLT over RDMA
        2.  
          Installing RDMA, InfiniBand or Ethernet drivers and utilities
        3. Configuring RDMA over an Ethernet network
          1.  
            Enable RDMA over Converged Ethernet (RoCE)
          2.  
            Configuring RDMA and Ethernet drivers
          3.  
            Configuring IP addresses over Ethernet Interfaces
        4. Configuring RDMA over an InfiniBand network
          1.  
            Configuring RDMA and InfiniBand drivers
          2.  
            Configuring the OpenSM service
          3.  
            Configuring IP addresses over InfiniBand Interfaces
        5. Tuning system performance
          1.  
            Tuning the CPU frequency
          2.  
            Tuning the boot parameter settings
        6. Manually configuring LLT over RDMA
          1.  
            Broadcast address in the /etc/llttab file
          2.  
            The link command in the /etc/llttab file
          3.  
            Selecting UDP ports
          4.  
            Configuring the netmask for LLT
          5.  
            Sample configuration: direct-attached links
        7.  
          LLT over RDMA sample /etc/llttab
        8.  
          Verifying LLT configuration
      6. Troubleshooting LLT over RDMA
        1.  
          IP addresses associated to the RDMA NICs do not automatically plumb on node restart
        2.  
          Ping test fails for the IP addresses configured over InfiniBand interfaces
        3.  
          After a node restart, by default the Mellanox card with Virtual Protocol Interconnect (VPI) gets configured in InfiniBand mode
        4.  
          The LLT module fails to start
    7. Appendix G. 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 rsh for Linux
    8. Appendix H. Installation script options
      1.  
        Installation script options
    9. Appendix I. Troubleshooting VCS configuration
      1.  
        Restarting the installer after a failed network connection
      2.  
        Cannot launch the cluster view link
      3.  
        Starting and stopping processes for the Veritas InfoScale products
      4.  
        Installer cannot create UUID for the cluster
      5.  
        LLT startup script displays errors
      6.  
        The vxfentsthdw utility fails when SCSI TEST UNIT READY command fails
      7.  
        The GAB program reports incorrect membership results with existing iptable rules
      8.  
        Issues during fencing startup on VCS cluster nodes set up for server-based fencing
    10. Appendix J. Sample VCS 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
    11. Appendix K. Upgrading the Steward process
      1.  
        Upgrading the Steward process

About the LLT and GAB configuration files

Low Latency Transport (LLT) and Group Membership and Atomic Broadcast (GAB) are VCS communication services. LLT requires /etc/llthosts and /etc/llttab files. GAB requires /etc/gabtab file.

Table: LLT configuration files lists the LLT configuration files and the information that these files contain.

Table: LLT configuration files

File

Description

/etc/sysconfig/llt

This file stores the start and stop environment variables for LLT:

  • LLT_START - Defines the startup behavior for the LLT module after a system reboot. Valid values include:

    1 - Indicates that LLT is enabled to start up.

    0 - Indicates that LLT is disabled to start up.

  • LLT_STOP - Defines the shutdown behavior for the LLT module during a system shutdown. Valid values include:

    1 - Indicates that LLT is enabled to shut down.

    0 - Indicates that LLT is disabled to shut down.

The installer sets the value of these variables to 1 at the end of VCS configuration.

If you manually configured VCS, make sure you set the values of these environment variables to 1.

Assign the buffer pool memory for RDMA operations:

  • LLT_BUFPOOL_MAXMEM - Maximum assigned memory that LLT can use for the LLT buffer pool. This buffer pool is used to allocate memory for RDMA operations and packet allocation, which are delivered to the LLT clients.

    The default value is calculated based on the total system memory, the minimum value is 1GB, and the maximum value is 10GB. You must specify the value in GB.

Define the number of RDMA queue pairs per LLT link

  • LLT_RDMA_QPS - Maximum number of RDMA queue pairs per LLT link. You can change the value of this parameter in the /etc/sysconfig/llt file. The default value is 4. However, you can extend this value to maximum 8 queue pairs per LLT link.

Enable or disable the adaptive window feature:

  • For performance reason, the adaptive window feature (LLT_ENABLE_AWINDOW ) is enabled by default for 5 (cfs) and port 24(cvm). You can disable the adaptive window feature by manually changing the value of the LLT_ENABLE_AWINDOW parameter to zero.

    To enable adaptive window for ports other than 5 and 24, add the port numbers in LLT_AW_PORT_LIST separated by comma. For example: LLT_AW_PORT_LIST=: '"5,24,0,1,5,14"'.

    If you want to disable the adaptive window feature for any of the ports, remove that specific port from this parameter. Example: LLT_AW_PORT_LIST='"5"'

Configure LLT over TCP

  • When you configure LLT over the Transmission Control Protocol (TCP) layer for clusters using wide-area networks and routers, you can use the LLT_TCP_CONNS parameter to control the number of TCP connections that can be established between peer nodes. The default value of this parameter is 8 connections. However, you can extend this value to maximum 64 connections.

/etc/llthosts

The file llthosts is a database that contains one entry per system. This file links the LLT system ID (in the first column) with the LLT host name. This file must be identical on each node in the cluster. A mismatch of the contents of the file can cause indeterminate behavior in the cluster.

For example, the file /etc/llthosts contains the entries that resemble:

    0      sys1
    1      sys2

/etc/llttab

The file llttab contains the information that is derived during installation and used by the utility lltconfig(1M). After installation, this file lists the LLT network links that correspond to the specific system.

For example, the file /etc/llttab contains the entries that resemble:

    set-node sys1
    set-cluster 2
    link eth1 eth1 - ether - -
    link eth2 eth2 - ether - -

If you use aggregated interfaces, then the file contains the aggregated interface name instead of the eth-MAC_address.

    set-node sys1
    set-cluster 2
    link eth1 eth-00:04:23:AC:12:C4 - ether - -
    link eth2 eth-00:04:23:AC:12:C5 - ether - -

The first line identifies the system. The second line identifies the cluster (that is, the cluster ID you entered during installation). The next two lines begin with the link command. These lines identify the two network cards that the LLT protocol uses.

If you configured a low priority link under LLT, the file also includes a "link-lowpri" line.

Refer to the llttab(4) manual page for details about how the LLT configuration may be modified. The manual page describes the ordering of the directives in the llttab file.

Table: GAB configuration files lists the GAB configuration files and the information that these files contain.

Table: GAB configuration files

File

Description

/etc/sysconfig/gab

This file stores the start and stop environment variables for GAB:

  • GAB_START - Defines the startup behavior for the GAB module after a system reboot. Valid values include:

    1 - Indicates that GAB is enabled to start up.

    0 - Indicates that GAB is disabled to start up.

  • GAB_STOP - Defines the shutdown behavior for the GAB module during a system shutdown. Valid values include:

    1 - Indicates that GAB is enabled to shut down.

    0 - Indicates that GAB is disabled to shut down.

The installer sets the value of these variables to 1 at the end of VCS configuration.

If you manually configured VCS, make sure you set the values of these environment variables to 1.

/etc/gabtab

After you install VCS, the file /etc/gabtab contains a gabconfig(1) command that configures the GAB driver for use.

The file /etc/gabtab contains a line that resembles:

    /sbin/gabconfig -c -nN

The -c option configures the driver for use. The -nN specifies that the cluster is not formed until at least N nodes are ready to form the cluster. Veritas recommends that you set N to be the total number of nodes in the cluster.

Note:

Veritas does not recommend the use of the -c -x option for /sbin/gabconfig. Using -c -x can lead to a split-brain condition. Use the -c option for /sbin/gabconfig to avoid a split-brain condition.