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
- 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
Excluding a NIC
When you install Veritas Access on a cluster, you may want to use some of the NICs for other storage purposes. You can use the Exclude a NIC functionality to exclude some NICs that you do not want to use for Veritas Access.
Note:
The NIC bonding/NIC exclusion configuration options support both a single NIC or bond, and multiple NICs or bonds.
To exclude a NIC
- During Veritas Access installation, the installer asks if you want to configure NIC bonding or exclude NICs. Enter y if you want to exclude a NIC.
Do you want to configure NIC bonding or exclude NICs or configure VLAN tagging? [y,n,q] (n)
- The installer prompts you to enter your selection. Enter 1 to exclude a NIC.
Veritas Access 7.3.1 Configure Program 10.200.114.45 10.200.114.46 NIC bonding/NIC exclusion configuration NIC bonding supports only public NICs. Make sure the NICs you choose are connected to public network. NIC PCI ID bond status If excluded ============================================= eth2 0000:02:03.0 (physical NIC) N eth3 0000:02:04.0 (physical NIC) N eth4 0000:02:05.0 (physical NIC) N eth5 0000:02:06.0 (physical NIC) N eth6 0000:02:07.0 (physical NIC) N eth7 0000:02:08.0 (physical NIC) N 1) Exclude NICs 2) Include NICs 3) Create a new bond 4) Add NICs to a bond 5) Remove bonds 6) Remove NICs from the bond list 7) Create VLAN device 8) Delete VLAN device 9) Save and Continue Select the NIC option to be configured in this cluster: [1-9,q] 1 - The installer prompts you to select the NIC that you want to exclude. Enter your choice.
Choose NICs for exclusion 1) eth2 0000:02:03.0 (physical NIC) 2) eth3 0000:02:04.0 (physical NIC) 3) eth4 0000:02:05.0 (physical NIC) 4) eth5 0000:02:06.0 (physical NIC) 5) eth6 0000:02:07.0 (physical NIC) 6) eth7 0000:02:08.0 (physical NIC) 7) Exclude NICs per node b) Back to previous menu Choose NICs: [1-7,b,q] 1 2(1,2) - The installer goes back to the previous menu. You can choose another NIC for exclusion. Enter 1 to exclude another NIC. Or you can save your configurations and continue with the installation of Veritas Access.
If you want to save your configurations, enter 9 :
Veritas Access 7.3.1 Configure Program 10.200.114.45 10.200.114.46 NIC bonding/NIC exclusion configuration NIC bonding supports only public NICs. Make sure the NICs you choose are connected to public network. NIC PCI ID bond status If excluded ============================================= eth2 0000:02:03.0 (physical NIC) Y eth3 0000:02:04.0 (physical NIC) Y eth4 0000:02:05.0 (physical NIC) N eth5 0000:02:06.0 (physical NIC) N eth6 0000:02:07.0 (physical NIC) N eth7 0000:02:08.0 (physical NIC) N 1) Exclude NICs 2) Include NICs 3) Create a new bond 4) Add NICs to a bond 5) Remove bonds 6) Remove NICs from the bond list 7) Create VLAN device 8) Delete VLAN device 9) Save and Continue Select the NIC option to be configured in this cluster: [1-9,q] 9 - If you want to exclude NICs per node, in Step To exclude a NIC enter 7. The NICs with inconsistent PCI IDs are listed:
Choose NICs for exclusion 1) eth2 0000:02:03.0 (physical NIC) 2) eth3 0000:02:04.0 (physical NIC) 3) eth4 0000:02:05.0 (physical NIC) 4) eth5 0000:02:06.0 (physical NIC) 5) eth6 0000:02:07.0 (physical NIC) 6) eth7 0000:02:08.0 (physical NIC) 7) Exclude NICs per node b) Back to previous menu Choose NICs: [1-7,b,q] 7 Choose items: [1-1,b,q] 1 1 0000:02:00.0 (10.198.95.214) 2 0000:02:01.0 (10.198.95.214) 3 0000:02:06.0 (10.198.95.212) 4 0000:02:09.0 (10.198.95.214) 5 0000:02:14.0 (10.198.95.212) 6 0000:02:15.0 (10.198.95.212) b) Back to previous menu Choose NICs: [1-6,b,q] 1 2 3 4 5 6
Note:
NIC exclusion function is supported on InfiniBand NICs, but all the NICs with the same PCI ID are excluded during the exclusion operation. See About using LLT over the RDMA network for Veritas Access.