Veritas Access Installation Guide

To install and configure the cluster

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 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. In case the OS RPMs' dependencies are not sorted, then the Redhat subscription manager user id and password is 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 
   3260 iSCSI Port
   4001 Mountd (NFS) 
   4045 NLM (NFS)       
   4379 CTDB Port 
   445 CIFS TCP Service
   51001,51002 RDMA 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 automatically configures the RDMA environment on the cluster nodes if there are InfiniBand NICs.
7. The installer asks the following information to configure the cluster:

   Enter the cluster name: [q,?]
   Enter the public IP starting address: [b,q,?]
   Enter the netmask for the public IP address: [b,q,?] (255.255.240.0)
   Enter the number of VIPs per interface: [b,q,?] (0)
   Enter the virtual IP starting address: [b,q,?]
   Enter the default gateway IP address: [b,q,?]
   Enter the DNS IP address: [b,q,?] (10.182.128.34)
   Enter the DNS domain name: [b,q,?] (engba.veritas.com)
   Enter the console virtual IP address: [b,q,?]
   Do you want to use the separate console port? [y,n,q,b,?] (n)

   Note:

   Cluster names should be DNS-compatible. DNS-compliant bucket names should conform to the following naming conventions. Bucket names must be at least three and no more than 63 characters long. Allowed characters in a cluster name are 'a-z, 0-9, -' lowercase letters, numbers, and hyphens. Cluster name must start with a lowercase letter and must end with a lowercase letter or a number. Any other character is invalid. A bucket name should not be an IP address. A period ('.') is not recommended in a bucket name because of an SSL issue, and including a period in a bucket name is not supported. Also, if a separate console port is chosen, the first public NIC is chosen to work exclusively as a console port.

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

9. The installer detects the network devices. The installer asks if you want to configure NIC bonding or exclude NICs.

   Do you want to configure NIC bonding or exclude NICs or configure 
   VLAN tagging? [y,n,q] (n)

   If you do not want to configure NIC bonding or exclude NICs, enter n. Go to step To install and configure the cluster .

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

   See Excluding a NIC.

   See Creating a new NIC bond.

   See Adding a VLAN device on a particular NIC.

10. 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        Hostname                         New Hostname
    ============================================================
    192.168.10.1  oldhostname01.example.com  newhostname01.example.com 
    192.168.10.2  oldhostname02.example.com  newhostname02.example.com 
    
    System        Gateway IP   DNS IP         Domain name
    ================================================================
    192.168.10.1  192.168.10.3 192.168.10.0  hostname.example.com 
    192.168.10.2  192.168.10.3 192.168.10.0  hostname.example.com
    
    System        NIC name(previous name)  Physical IP
    ====================================================
    192.168.10.1  pubeth0(eth10)           192.168.10.5
    192.168.10.1  pubeth1(eth11)           192.168.10.6
    192.168.10.2  pubeth0(eth10)           192.168.10.7
    192.168.10.2  pubeth1(eth11)           192.168.10.8
    
    Virtual IP
    =========================================================
    192.168.10.10  192.168.10.11 192.168.10.12 192.168.10.13
    
    System        NIC name(previous name)
    ======================================
    192.168.10.1  priveth0(eth8)
    192.168.10.1  priveth1(eth9)
    192.168.10.2  priveth0(eth8)
    192.168.10.2  priveth1(eth9)
    
    Is this information correct? [y,n,q] (y)

11. The installer renames the NICs and host name, and assigns the IPs for the systems after the confirmation. 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.

12. If you are installing the ISO image on any node of the cluster (not the driver node), your session will get disconnected due to the network configuration. Re-login using the IP address prompted by the installer to resume installation.

    The system is performing network configuration tasks. The current
    session will be temporarily disconnected. Re-login with 10.209.193.248
    to resume installation.

13. The installer prompts to ask 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. If you plan to use both shared disks and local disks in your cluster, we recommend that you do not configure I/O fencing with the installer. Go to step To install and configure the cluster .

    To configure I/O fencing, enter y.

    See Configuring I/O fencing.

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