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
Creating a new NIC bond
An administrator can create a bond NIC interface from a given list of public NIC interfaces during Veritas Access installation. This feature allows an administrator to save a number of physical IP addresses that are used for installation and post-installation bond creation.
The bond interface feature is available for network interface card (NIC) bonding of public interfaces only. Bonding of private interfaces is not supported.
You cannot bond InfiniBand NICs since the PCI IDs are identical. See About using LLT over the RDMA network for Veritas Access.
You can create a bond interface for public NICs only if the PCI IDs of the public NICs are correspondingly same among the nodes.
If you do not want to create a bond interface, continue with the installation.
To create a bond
- During the Veritas Access installation, the installer asks if you want to configure NIC bonding or exclude NICs. Enter y if you want to configure a NIC bond.
Do you want to configure NIC bonding or exclude NICs? [y,n,q] (n) y
- The installer prompts you to enter your selection. Enter 3 to create a new bond.
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) Save and Continue Select the NIC option to be configured in this Cluster: [1-7,q] 3 - The installer prompts you to select the bond mode of the new bond. Enter your choice.
Configure the mode for the NIC bonding: 1) balance-rr 2) active-backup 3) balance-xor 4) broadcast 5) 802.3ad b) Back to previous menu Select the mode of bond: [1-5,b,q] 3 bond0 is created. Press [Enter] to continue - If you choose 3 or 5, the installer prompts you to choose the bond option for the bond mode:
1) layer2 2) layer3+4 3) default Select the bonding option: [1-3,b,q] 1
- The installer prompts you to select the NIC option that you want to configure in the cluster.
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) Save and Continue Select the NIC option to be configured in this Cluster: [1-7,q] 4 - The installer prompts you to select the NIC.
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) b) Back to previous menu Choose NICs: [1-6,b,q] 1
- The installer prompts you to choose a bond name to which you want to add the NIC.
1) bond0 b) Back to previous menu Choose a bond: [1-1,b,q] 1 Adding 0000:02:03.0 to bond0 was successful Press [Enter] to continue:
- The installer prompts you to select the NIC option that you want to configure in the cluster.
Enter 4 if you want to add another NIC to the bond . Or you can enter 7 to save your configurations and continue with the installation of Veritas Access.
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 (Slave of bond0) N eth3 0000:02:04.0 (Slave of bond0) 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) Save and Continue Select the NIC option to be configured in this Cluster: [1-7,q] 7