Veritas Access Installation Guide
- Introducing Veritas Access
- Licensing in Veritas Access
- System requirements
- Important release information
- System requirements
- Linux requirements
- Operating system RPM installation requirements and operating system patching
- Kernel RPMs that are required to be installed with exact predefined RPM versions
- OL kernel RPMs that are required to be installed with exact predefined RPM versions
- Required operating system RPMs for OL 7.4
- Required operating system RPMs for RHEL 7.3
- Required operating system RPMs for RHEL 7.4
- Software requirements for installing Veritas Access in a VMware ESXi environment
- Hardware requirements for installing Veritas Access virtual machines
- Management Server Web browser support
- Supported NetBackup versions
- Supported OpenStack versions
- Supported Oracle versions and host operating systems
- Supported IP version 6 Internet standard protocol
- Linux requirements
- Network and firewall requirements
- Maximum configuration limits
- Preparing to install Veritas Access
- Deploying virtual machines in VMware ESXi for Veritas Access installation
- Installing and configuring a cluster
- Installation overview
- Summary of the installation steps
- Before you install
- Installing the operating system on each node of the cluster
- Installing Veritas Access on the target cluster nodes
- About managing the NICs, bonds, and VLAN devices
- About VLAN tagging
- Replacing an Ethernet interface card
- Configuring I/O fencing
- About configuring Veritas NetBackup
- About enabling kdump during an Veritas Access configuration
- Reconfiguring the Veritas Access cluster name and network
- Configuring a KMS server on the Veritas Access cluster
- Automating Veritas Access installation and configuration using response files
- Displaying and adding nodes to a cluster
- Upgrading Veritas Access and operating system
- Upgrading Veritas Access using a rolling upgrade
- Uninstalling Veritas Access
- Appendix A. Installation reference
- Appendix B. Configuring the secure shell for communications
- Appendix C. Manual deployment of Veritas Access
Installing Veritas Access on the target cluster nodes
Before you install Veritas Access on the target cluster nodes, you must allocate enough IP addresses for the cluster. You can install up to a 20-node cluster.
Installing the cluster is a one-time activity. It takes about 40 minutes to install a two-node cluster. Installation times may vary depending on your configuration and the number of nodes.
See About obtaining IP addresses.
If you want to install the Veritas Access cluster with IPv6 IP addresses, you need to configure a static IPv6 address on the driver node and on all the nodes of the cluster. You need to make sure that the IPv6 IP auto-assignment is disabled on all nodes of the cluster. You can then use the IPv6 IPs to install Veritas Access on the cluster nodes.
If you want to configure the cluster in an IPv6 environment or plan to use the cluster in mixed mode that is, configure both IPv4 and IPv6 IPs, you need to disable the IPv6 IP auto-assignment.
To disable the IPv6 IP auto-assignment, add the following entries in the
/etc/sysctl.conffile for all network interfaces of the node.net.ipv6.conf.<network interface name>.autoconf=0 net.ipv6.conf.<network interface name>.accept_ra=0 net.ipv6.conf.<network interface name>.accept_ra_defrtr=0
To configure a static IPv6 address
- Modify the
vim /etc/sysconfig/network-scripts/ifcfg-ens161network interface file by using the following:IPV6INIT="yes" IPV6_AUTOCONF="no" IPV6ADDR=2001:128:f0a2:900a::121/64
- Restart the network service by using thesystemctl restart network command.