Veritas Access Installation Guide
- Licensing in Veritas Access
- System requirements
- System requirements
- Linux requirements
- Network and firewall requirements
- Preparing to install Veritas Access
- Deploying virtual machines in VMware ESXi for Veritas Access installation
- Installing and configuring a cluster
- 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
- Automating Veritas Access installation and configuration using response files
- Displaying and adding nodes to a cluster
- Upgrading the operating system and Veritas Access
- Performing 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.
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 use the cluster in mixed mode by configuring both IPv4 and IPv6 IPs, you have to disable the IPv6 IP auto-assignment.
To configure a static IPv6 address
- Modify the
vim /etc/sysconfig/network-scripts/ifcfg-ens161
network 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.