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
Bonding Ethernet interfaces
The Network> bond create and Network> bond remove operations involve bringing down the interface first and then bringing them back up. This may cause the SSH connections that are hosted over those interfaces to terminate. Use the physical console of the client rather than SSH when performing Network> bond create and Network> bond remove operations.
To display a bond
- To display a bond and the algorithm that is used to distribute traffic among the bonded interfaces, enter the following:
Network> bond show
To create a bond
- To create a bond between sets of two or more Ethernet interfaces on all Veritas Access cluster nodes, enter the following:
Network> bond create interfacelist mode option
interfacelist
Specifies a comma-separated list of public Ethernet interfaces to bond.
mode
Specifies how the bonded Ethernet interfaces divide the traffic.
option
Specifies a comma-separated option string.
Available only when the bond mode is 2 (balance-xor) or 4 (802.3ad)
xmit_hash_policy - specifies the transmit hash policy to use for slave selection in balance-xor and 802.3ad modes.
If the option is not specified correctly, you get an error.
You can specify a mode either as a number or a character string, as follows:
0 | balance-rr | This mode provides fault tolerance and load balancing. It transmits packets in order from the first available slave through the last. |
1 | active-backup | Only one slave in the bond is active. If the active slave fails, a different slave becomes active. To avoid confusing the switch, the bond's MAC address is externally visible on only one port (network adapter). |
2 | balance-xor | Transmits based on the selected transmit hash policy. The default policy is a simple. This mode provides load balancing and fault tolerance. |
3 | broadcast | Transmits everything on all slave interfaces and provides fault tolerance. |
4 | 802.3ad | Creates aggregation groups with the same speed and duplex settings. It uses all slaves in the active aggregator based on the 802.3ad specification. |
5 | balance-tlb | Provides channel bonding that does not require special switch support. The outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave. The current slave receives incoming traffic. If the receiving slave fails, another slave takes over its MAC address. |
6 | balance-alb | Includes balance-tlb plus Receive Load Balancing (RLB) for IPV4 traffic. This mode does not require any special switch support. ARP negotiation load balances the receive. |
To remove a bond
- To remove a bond from all of the nodes in a cluster, enter the following:
Network> bond remove bondname
where bondname is the name of the bond configuration.