Veritas Access Installation Guide
- Introducing Veritas Access
- Licensing in Veritas Access
- System requirements
- System requirements
- Linux requirements
- Linux requirements
- Network and firewall requirements
- Preparing to install Veritas Access
- Deploying virtual machines in VMware ESXi for Veritas Access installation
- Installing and configuring a cluster
- 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
- 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
About NIC bonding and NIC exclusion
When you install Veritas Access on a cluster, you can perform the following operations using the NICs:
Exclude a NIC
See Excluding a NIC.
Include a NIC
See Including a NIC.
Create a new NIC bond and add a NIC to a bond
Remove a bond
See Removing a NIC bond.
Remove a NIC from the bond list
Add a VLAN device on a particular NIC
Note:
The NIC bonding and NIC exclusion configuration options support both a single NIC or bond, and multiple NICs or bonds.
Note:
When using the NIC exclusion feature, you can exclude any NIC on the first node. But if you want to exclude any NIC on the other nodes, you can choose to exclude NICs per node.
See Excluding a NIC.
Note:
If you want to use the NIC bonding feature, make sure that the PCI IDs of the slave bond NICs of the first node is the same as the PCI IDs of the slave bond NICs of the other nodes.