Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Configuring an FTP server
- Using Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
About bonding Ethernet interfaces
Bonding associates a set of two or more Ethernet interfaces with one IP address. The association improves network performance on each Veritas Access cluster node by increasing the potential bandwidth available on an IP address beyond the limits of a single Ethernet interface. Bonding also provides redundancy for higher availability.
For example, you can bond two 1-gigabit Ethernet interfaces together to provide up to 2 gigabits per second of throughput to a single IP address. Moreover, if one of the interfaces fails, communication continues using the single Ethernet interface.
When you create a bond, you need to specify a bonding mode. In addition, for the following bonding modes: 802.3ad, balance-rr, balance-xor, broadcast, balance-tlb, and balance-alb, make sure that the base network interface driver is configured correctly for the bond type. For type 802.3ad, the switch must be configured for link aggregation.
Consult your vendor-specific documentation for port aggregation and switch set up. You can use the -s option in the Linux ethtool command to check if the base driver supports the link speed retrieval option. The balance-alb bond mode type works only if the underlying interface network driver enables you to set a link address.
Note:
An added IPv6 address may go into a TENTATIVE state while bonding Ethernet interfaces with balance-rr, balance-xor, or broadcast bond modes. While bonding with those modes, Veritas Access requires the switch to balance incoming traffic across the ports, and not deliver looped back packets or duplicates. To work around this issue, enable EtherChannel on your switch, or avoid using these bond modes.
Table: Bonding mode
Index | Bonding mode | Fault tolerance | Load balancing | Switch setup | Ethtool/base driver support |
---|---|---|---|---|---|
0 | balance-rr | yes | yes | yes | no |
1 | active-backup | yes | no | no | no |
2 | balance-xor | yes | yes | yes | no |
3 | broadcast | yes | no | yes | no |
4 | 802.3ad | yes | yes | yes | yes (to retrieve speed) |
5 | balance-tlb | yes | yes | no | yes (to retrieve speed) |
6 | balance-alb | yes | yes | no | yes (to retrieve speed) |
Note:
When you create or remove a bond, SSH connections with Ethernet interfaces involved in that bond may be dropped. When the operation is complete, you must restore the SSH connections.