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 6.8
- Required operating system RPMs for OL 7.3
- Required operating system RPMs for OL 7.4
- Required operating system RPMs for RHEL 6.6
- Required operating system RPMs for RHEL 6.7
- Required operating system RPMs for RHEL 6.8
- 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 NIC bonding and NIC exclusion
- 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. Troubleshooting the LTR upgrade
- Appendix C. Configuring the secure shell for communications
Configuring LLT over RDMA for Veritas Access
During the Veritas Access installation, the installer automatically configures LLT over RDMA if there are InfiniBand NICs on the cluster nodes, unless the InfiniBand NICs are excluded.
This section describes the required hardware and configuration for LLT to support RDMA for Veritas Access. The high-level steps to configure LLT over RDMA are as follows:
1. Choose NICs, network switches, and cables that support RDMA.
Table: RDMA-enabled hardware
Hardware | Supported types | Reference |
|---|---|---|
Network card | Mellanox-based Host Channel Adapters (HCAs) (VPI, ConnectX, ConnectX-2 and 3) | For detailed installation information, refer to the hardware vendor documentation. |
Network switch | Mellanox, InfiniBand switches Ethernet switches must be Data Center Bridging (DCB) capable | For detailed installation information, refer to the hardware vendor documentation. |
Cables | Copper and Optical Cables, InfiniBand cables | For detailed installation information, refer to the hardware vendor documentation. |
2. Connect the first two non-excluded InfiniBand NICs as private NICs.
Note:
Cross-links connection is not supported for private NICs in an RDMA environment.
3. Make sure that the required packages to enable RDMA, InfiniBand drivers, and utilities are installed with the base operating system. Or they can be installed from the yum repository.
Table: Drivers and utilities required for RDMA, InfiniBand, or an Ethernet network
Packages | Drivers and utilities |
|---|---|
Device drivers for RDMA operations |
|
OpenSM-related package |
|
InfiniBand troubleshooting and performance tests |
|
libibverbs packages for InfiniBand operations |
|