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
Removing a NIC bond
An administrator can remove a bond that has been already created.
To remove a NIC bond
- During the Veritas Access installation, the installer prompts you to enter your selection. Enter 5 to remove an existing bond.
Veritas Access 7.3.1 Install 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 =============================================== eth0 0000:02:01.0 (physical NIC) N eth1 0000:02:02.0 (physical NIC) N eth2 0000:02:03.0 (Slave of bond0) N eth3 0000:02:04.0 (Slave of bond0) N eth4 0000:02:05.0 (Slave of bond2) N eth5 0000:02:06.0 (Slave of bond1) N eth6 0000:02:07.0 (Slave of bond1) N eth7 0000:02:08.0 (Slave of bond2) 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] 5 - The installer prompts you to select the bond which you want to remove. Enter your choice.
1) bond0 2) bond1 3) bond2 b) Back to previous menu Choose bonds: [1-3,b,q] 3 Deleting NIC bonding bond2 succeeded Press [Enter] to continue:
- The installer prompts you to select the NIC option that you want to configure in the cluster. Enter 5 if you want to remove another bond . Or you can enter 7 to save your configurations and continue with the installation of Veritas Access.
Veritas Access 7.3.1 Install 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 =============================================== eth0 0000:02:01.0 (physical NIC) N eth1 0000:02:02.0 (physical NIC) N 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 (Slave of bond1) N eth6 0000:02:07.0 (Slave of bond1) 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]