Veritas Access Installation Guide

Last Published:
Product(s): Access (7.4.2)
Platform: Linux
  1. Licensing in Veritas Access
    1.  
      About Veritas Access product licensing
    2.  
      Per-TB licensing model
    3.  
      TB-Per-Core licensing model
    4.  
      Per-Core licensing model
    5.  
      Add-on license for using Veritas Data Deduplication
    6.  
      Notes and functional enforcements for licensing
  2. System requirements
    1.  
      Important release information
    2. System requirements
      1. Linux requirements
        1.  
          Required operating system RPMs and patches
        2.  
          Required kernel RPMs
        3.  
          Required Oracle Linux kernel RPMs
        4.  
          Required operating system RPMs for OL 7.4
        5.  
          Required operating system RPMs for OL 7.5
        6.  
          Required operating system RPMs for RHEL 7.4
        7.  
          Required operating system RPMs for RHEL 7.5
      2.  
        Software requirements for installing Veritas Access in a VMware ESXi environment
      3.  
        Hardware requirements for installing Veritas Access virtual machines
      4.  
        Management Server Web browser support
      5.  
        Required NetBackup versions
      6.  
        Required OpenStack versions
      7.  
        Required Oracle versions and host operating systems
      8.  
        Required IP version 6 Internet standard protocol
    3. Network and firewall requirements
      1.  
        NetBackup ports
      2.  
        OpenDedup ports and disabling the iptable rules
      3.  
        CIFS protocols and firewall ports
    4.  
      Maximum configuration limits
  3. Preparing to install Veritas Access
    1.  
      Overview of the installation process
    2.  
      Hardware requirements for the nodes
    3. About using LLT over the RDMA network for Veritas Access
      1.  
        RDMA over InfiniBand networks in the Veritas Access clustering environment
      2.  
        How LLT supports RDMA for faster interconnections between applications
      3.  
        Configuring LLT over RDMA for Veritas Access
      4.  
        How the Veritas Access installer configures LLT over RDMA
      5.  
        LLT over RDMA sample /etc/llttab
    4.  
      Connecting the network hardware
    5. About obtaining IP addresses
      1.  
        About calculating IP address requirements
      2.  
        Reducing the number of IP addresses required at installation time
    6.  
      About checking the storage configuration
  4. Deploying virtual machines in VMware ESXi for Veritas Access installation
    1.  
      Setting up networking in VMware ESXi
    2.  
      Creating a datastore for the boot disk and LUNs
    3.  
      Creating a virtual machine for Veritas Access installation
  5. Installing and configuring a cluster
    1.  
      Installation overview
    2.  
      Summary of the installation steps
    3.  
      Before you install
    4. Installing the operating system on each node of the cluster
      1.  
        About the driver node
      2.  
        Installing the RHEL operating system on the target Veritas Access cluster
      3. Installing the Oracle Linux operating system on the target Veritas Access cluster
        1.  
          Setting up the Oracle Linux yum server repository
    5. Installing Veritas Access on the target cluster nodes
      1.  
        Installing and configuring the Veritas Access software on the cluster
      2.  
        Veritas Access Graphical User Interface
    6. About managing the NICs, bonds, and VLAN devices
      1.  
        Selecting the public NICs
      2.  
        Selecting the private NICs
      3.  
        Excluding a NIC
      4.  
        Including a NIC
      5.  
        Creating a NIC bond
      6.  
        Removing a NIC bond
      7.  
        Removing a NIC from the bond list
    7. About VLAN tagging
      1.  
        Creating a VLAN device
      2.  
        Removing a VLAN device
      3.  
        Limitations of VLAN Tagging
    8.  
      Replacing an Ethernet interface card
    9.  
      Configuring I/O fencing
    10.  
      About configuring Veritas NetBackup
    11.  
      About enabling kdump during an Veritas Access configuration
    12.  
      Reconfiguring the Veritas Access cluster name and network
    13.  
      Configuring a KMS server on the Veritas Access cluster
  6. Automating Veritas Access installation and configuration using response files
    1.  
      About response files
    2.  
      Performing a silent Veritas Access installation
    3.  
      Response file variables to install and configure Veritas Access
    4.  
      Sample response file for Veritas Access installation and configuration
  7. Displaying and adding nodes to a cluster
    1.  
      About the Veritas Access installation states and conditions
    2.  
      Displaying the nodes in the cluster
    3.  
      Before adding new nodes in the cluster
    4.  
      Adding a node to the cluster
    5.  
      Adding a node in mixed mode environment
    6.  
      Deleting a node from the cluster
    7.  
      Shutting down the cluster nodes
  8. Upgrading the operating system and Veritas Access
    1.  
      Supported upgrade paths for upgrades on RHEL
    2.  
      Upgrading the operating system and Veritas Access
  9. Performing a rolling upgrade
    1.  
      About rolling upgrade
    2.  
      Performing a rolling upgrade using the installer
  10. Uninstalling Veritas Access
    1.  
      Before you uninstall Veritas Access
    2. Uninstalling Veritas Access using the installer
      1.  
        Removing Veritas Access 7.4.2 RPMs
      2.  
        Running uninstall from the Veritas Access 7.4.2 disc
  11. Appendix A. Installation reference
    1.  
      Installation script options
  12. Appendix B. Configuring the secure shell for communications
    1.  
      Manually configuring passwordless secure shell (ssh)
    2.  
      Setting up ssh and rsh connections using the pwdutil.pl utility
  13. Appendix C. Manual deployment of Veritas Access
    1.  
      Deploying Veritas Access manually on a two-node cluster in a non-SSH environment
    2.  
      Enabling internal sudo user communication in Veritas Access

Reconfiguring the Veritas Access cluster name and network

After you install and configure Veritas Access, you can reconfigure the cluster name and network, if required.

Before you reconfigure the cluster, you must enable the support user for the nodes because the root user access authority is not allowed. The support user default password is veritas. However, you can change the password after you log on the first time.

To reconfigure the Veritas Access cluster name and network

  1. Log on to the host console using the support user name and password.
  2. Take all the service groups offline by running the hastop -all command.

    Enter the following command: 

    /opt/VRTS/install/installaccess -updateparameter
  3. Enter the private IPs of the systems.
    172.16.0.3 172.16.0.4

    Note:

    Only the private IPs of the systems must be entered. Public IPs should not be used here.

  4. Enter the cluster name and network information.
    Enter the cluster name: 
Enter the public IP starting address: 
Enter the netmask for the public IP address:
Enter the number of VIPs per interface:
Enter the virtual IP starting address:
Enter the default gateway IP address:
Enter the DNS IP address:
Enter the DNS domain name:
Enter the console virtual IP address:
Do you want to use the separate console port? [y,n,q] (n):
Do you want to configure the Network Time Protocol(NTP) server to 
synchronize the system clocks? [y,n,q] (n) y:
Enter the Network Time Protocol server:

    The installer confirms that the information that you entered is correct. The configuration is completed and the new cluster and IPs are configured on the cluster.

    The installer displays the location of the log and summary files. If required, view the files to confirm the configuration status.

    Note:

    The cluster name can contain only alpha characters, numbers, or underscores. The cluster name must start with a letter of the alphabet and can have a length of maximum 15 characters. Also, if a separate console port is chosen, the first public NIC is chosen to work exclusively as a console port.

    Note:

    If your cluster has DAS disks, limit the cluster name to 10 characters.

    After formatting the DAS disks, do not change the cluster name.