Veritas Access Installation Guide

Last Published:
Product(s): Access (7.4)
Platform: Linux
  1. Introducing Veritas Access
    1.  
      About Veritas Access
  2. Licensing in Veritas Access
    1.  
      About Veritas Access product licensing
  3. System requirements
    1.  
      Important release information
    2. System requirements
      1. Linux requirements
        1.  
          Operating system RPM installation requirements and operating system patching
        2.  
          Kernel RPMs that are required to be installed with exact predefined RPM versions
        3.  
          OL kernel RPMs that are required to be installed with exact predefined RPM versions
        4.  
          Required operating system RPMs for OL 7.3
        5.  
          Required operating system RPMs for OL 7.4
        6.  
          Required operating system RPMs for RHEL 7.3
        7.  
          Required operating system RPMs for RHEL 7.4
      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.  
        Supported NetBackup versions
      6.  
        Supported OpenStack versions
      7.  
        Supported Oracle versions and host operating systems
      8.  
        Supported 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
  4. Preparing to install Veritas Access
    1.  
      Overview of the installation process
    2.  
      Hardware requirements for the nodes
    3.  
      Connecting the network hardware
    4. About obtaining IP addresses
      1.  
        About calculating IP address requirements
      2.  
        Reducing the number of IP addresses required at installation time
    5.  
      About checking the storage configuration
  5. 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
  6. 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 operating system on the target Veritas Access cluster
      3.  
        Installing the Oracle Linux operating system on the target Veritas Access cluster
    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
  7. 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
  8. 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
  9. Upgrading Veritas Access and operating system
    1.  
      Upgrading the operating system and Veritas Access
  10. Upgrading Veritas Access using a rolling upgrade
    1.  
      About the rolling upgrades
    2.  
      Supported rolling upgrade paths for upgrades on RHEL and Oracle Linux
    3.  
      Performing a rolling upgrade using the installer
  11. Uninstalling Veritas Access
    1.  
      Before you uninstall Veritas Access
    2. Uninstalling Veritas Access using the installer
      1.  
        Removing Veritas Access 7.4 RPMs
      2.  
        Running uninstall from the Veritas Access 7.4 disc
  12. Appendix A. Installation reference
    1.  
      Installation script options
  13. Appendix B. Configuring the secure shell for communications
    1.  
      Manually configuring passwordless SSH
    2.  
      Setting up the SSH and the RSH connections
  14. 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

Installing and configuring the Veritas Access software on the cluster

To install and configure the cluster

Note:

During the installation, the installer log is located at /var/tmp.

  1. Enter one of the following commands to start the installation.
    # ./installaccess node1_ip node2_ip

    Where node1_ip and node2_ip are the public physical IP addresses that are already assigned to the target cluster nodes to install Veritas Access over SSH.

    These are the current IPs assigned to the nodes for the installation communication.

    The example is used to install two nodes. To install another target node cluster, add node3_ip to the command line that is used in this step.

  2. The installer checks for the operating system dependencies and automatically installs the required OS RPMs. If the OS RPMs' dependencies are not sorted, the RedHat subscription manager user ID and password are required.
  3. The installer installs the Veritas Access RPMs.
  4. Choose the licensing method. Answer the licensing questions and follow the prompts.
    1)  Enter a valid perpetual or subscription license key file
    2)  Register with evaluation mode and complete system licensing later
    
    How would you like to license the systems? [1-2,q,?] (2)
  5. The installer displays the firewall ports to be opened after the configuration, and asks if you want to open them:
    Veritas Access needs to open the following ports:
    111 Rpcbind (NFS)
    11211 Memcached Port
    123 NTP Service
    139 CIFS Service
    14161 GUI
    161 SNMP Service
    2049 NFS Service
    21 FTP Port
    22 SSH Service
    25 SMTP Port
    30000:40000 FTP Passive Port Range
    3172,3173 Server View Ports
    4001 Mountd (NFS)
    4045 NLM (NFS)
    4379 CTDB Port
    445 CIFS TCP Service
    514 Syslog Service
    53 DNS Service
    5634 VIOM
    56987 Replication Service
    756,757,755 Statd (NFS)
    8088 REST Server
    8143 Object Access Gateway
    8144 Object Access Admin Gateway
    Do you want to proceed? [y,n,q] (y)
    
  6. The installer asks the following information to configure the cluster:
    Enter the cluster name: [q,?] 
    Do you want to rename the hosts' name like vac_01, vac_02? [y,n,q,b,?] (n) 
    Enter the public IP starting address or : [b,q,?] 
    Enter the netmask for the public IP address: [b,q,?] (255.255.255.0)
    Enter the number of VIPs per interface: [b,q,?] (0) 1
    Enter the virtual IP starting address: [b,q,?]  
    Enter the default gateway IP address: [b,q,?]  
    Enter the DNS IP address: [b,q,?] (10.0.2.3)
    Enter the DNS domain name: [b,q,?] (community.veritas.com)
    Enter the console virtual IP address: [b,q,?]  
    Do you want to use the separate console port? [y,n,q,b,?] (n)
    Enter the private IP starting address: [b,q,?] (172.16.0.3)
    

    Note:

    Cluster names should be DNS-compatible. Cluster name must be at least three characters and no more than 10 characters long. Allowed characters in a cluster name are 'a-z, 0-9, -' lowercase letters, numbers, and hyphens. Any other character is invalid. Also, if a separate console port is chosen, the first public NIC is chosen to work exclusively as a console port.

  7. The installer asks if you want to configure the Network Time Protocol (NTP) server.
    Do you want to configure the Network Time Protocol(NTP) server to 
    synchronize the system clocks? [y,n,q]  y
    Enter the Network Time Protocol server: [q,?]

    If you enter y, you can type in your NTP server. If you enter n, the NTP server is not configured.

  8. Installer asks to confirm the entered cluster information.

    The installer detects the network devices, checks the network device's connectivity with the gateway, and displays information about it.

    Checking network configuration .................................... Done
    Detecting network devices ......................................... Done
    Checking network connection ....................................... Done
     
    Detecting network devices completed successfully.
     
    Common NICs on all systems:
    
    NIC       Type       Properties     Public
    ===========================================
    ens161    Physical   -              N
    ens192    Physical   -              Y
    ens193    Physical   -              Y
    ens224    Physical   -              Y
    ens256    Physical   -              N 
     
    For the 'Public' field of the NIC:
        Y: means the NIC can connect to the public gateway, and can be selected as
    public NIC.
        N: means the NIC cannot connect to the public gateway, and can be selected
    as private NIC.
        -: means the NIC was not tested if connect to the public gateway.
        blank: means this NIC is excluded or not selectable.
    

    To configure Veritas Access networking, you need to exclude the unused NICs, and to include at least one public NIC, and one private NIC. It is recommended to have two public NICs and two private NICs, and the selected private NICs on all systems should be interconnected.

    If you do want to configure NIC bonding or exclude NICs, enter y.

    If you do not want to configure NIC bonding or exclude NICs, enter n.

    See Excluding a NIC.

    See Creating a NIC bond.

    See Creating a VLAN device .

  9. You need to select one of the options from the following for the installation:
    • Manually select NIC

    • Configure NIC bonding

    • Configure VLAN through installer

    Do you want to manually select NICs, or configure NIC bonding or VLAN tagging? [y,n,q] (n) 
    Enter n : If you want installer to do auto network configuration for the cluster
    Enter y : If you want to select public and private NICs manually, configure NIC bonding
              or to create VLAN using installer.

    The installer performs the public and private NIC detection tests on each node of the cluster. If physical or virtual IPs that are entered are less than the required IPs for the cluster configuration, the installer asks you to add the required IPs.

  10. Verify that the network configuration details such as the new IP addresses, host name, and other details are correct.
  11. The installer prompts to verify the network configuration.

    Verify that the configuration information such as the new IP addresses, host name, and other details are correct.

    Configuration checklist:
    
    System        Public NIC	Physical IP
    ============= ========== =============
    192.168.10.10 ens192		   192.168.10.20
    192.168.10.10 ens224		   192.168.10.21
    192.168.10.10 ens193		   192.168.10.22
    192.168.10.11 ens192		   192.168.10.23
    192.168.10.11 ens224		   192.168.10.24
    192.168.10.11 ens193		   192.168.10.25
    
    System        Private NIC
    ============= ===========
    192.168.10.10 ens161
    192.168.10.10 ens256
    192.168.10.11 ens161
    192.168.10.11 ens256
    
    Virtual IP
    =======================================================================
    192.168.10.30 192.168.10.31 192.168.10.32 192.168.10.33 ...(6 in total)
    
    Console IP
    =============
    192.168.10.50
    
    Gateway IP   DNS IP       Domain name
    ============ ============ ===================
    192.168.10.1 192.168.10.2 vxindia.veritas.com
    
    Is this information correct? [y,n,q,b,?] (y)
    
  12. After you confirm the network configuration details, the installer renames the host name if you have chosen to rename it and assigns the IPs for the systems. The installer also checks the Low Latency Transport (LLT) link status and automatically selects them.

    Note:

    The installer does not check the LLT link status if the InfiniBand NICs are chosen as private NICs.

  13. Installer performs the Veritas Access service group configuration.
  14. The installer prompts if you want to configure I/O fencing during the installation.
    Do you want to configure I/O Fencing in enabled mode? [y,n,q,?] (y)

    If you do not want to configure I/O fencing, enter n.

    To configure I/O fencing, enter y.

    See Configuring I/O fencing.

  15. The installer automatically restarts the cluster nodes to enables the Kdump function for each node.
  16. Check the log file to confirm the installation and configuration. Logs can be found in /opt/VRTS/install/logs/.

Note:

After the installation, connect to the Veritas Access console using the console IP address you assigned earlier, then log on using the default user name master and the default password master.