Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- 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
- Using Access Appliance as an Object Store server
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Section VI. Monitoring and troubleshooting
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Configuring event notifications and audit logs
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring episodic replication
- 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 Access Appliance 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, Access Appliance 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.