Please enter search query.
Search <book_title>...
Veritas Access Installation Guide
Last Published:
2018-07-27
Product(s):
Access (7.3.1)
Platform: Linux
- Introducing Veritas Access
- Licensing in Veritas Access
- System requirements
- System requirements
- Linux 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 NIC bonding and NIC exclusion
- About VLAN Tagging
- 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. Troubleshooting the LTR upgrade
- Appendix C. Configuring the secure shell for communications
About the driver node
If you do not plan to install Veritas Access from the console of the nodes in the cluster (the local management console of your nodes), you need another server that is not a target node in the Veritas Access cluster to use in the Veritas Access installation. This server is called the driver node.
When you run the Veritas Access installation script, the Veritas Access installer helps set up the ssh connection between the driver node and the target Veritas Access cluster nodes.
Note:
Installation may fail if it is triggered from one of the node in the cluster. Therefore, installation must be triggered from the driver node.
The driver node platform can be: RHEL 7, RHEL 6, SLES 11 SP2, or SLES 11 SP3.