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
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.
The driver node platform can be: RHEL 7, SLES 11 SP2, or SLES 11 SP3.
The following table provides the information about Veritas Access installation support from the cluster node and the driver node with different types of network devices.
Network device type | Driver Node | Cluster Node |
|---|---|---|
Normal network device | Yes | Yes |
Create a bond device through installer and add NIC in bond through which installation is started. | Yes | No |
Create a bond device on NIC other than the NIC through which installation is started. | Yes | Yes |
Create a VLAN through installer on the NIC other than the NIC through which installation is started. | No | Yes |
Create a VLAN through installer on NIC through which installation is started. | No | No |
Exclude NIC from which installation started. | No | No |
Create a bond and a VLAN over bond device on NIC other than the NIC through which installation is started. | No | Yes |
Preconfigured bond as public and Installation from other NIC. | Yes | Yes |
Create a bond through installer and select it as private connection. | No | No |
Create VLAN through installer and select it as private connection. | No | No |
Install with public NIC and pre-existing public bond. | Yes | Yes |