10.7 About Network Interface Teaming

10.7.1 Configuring Network Interface Teaming
10.7.2 Adding Ports to and Removing Ports from a Team
10.7.3 Changing the Configuration of a Port in a Team
10.7.4 Removing a Team
10.7.5 Displaying Information About Teams

Note

Network interface teaming requires Unbreakable Enterprise Kernel Release 3 (UEK R3) Quarterly Update 7 or later.

Network interface teaming is similar to network interface bonding and provides a way of implementing link aggregation that is relatively maintenance-free, as well as being simpler to modify, expand, and debug as compared with bonding.

A lightweight kernel driver implements teaming and the teamd daemon implements load-balancing and failover schemes termed runners. The following standard runners are defined:

activebackup

Monitors the link for changes and selects the active port that is used to send packets.

broadcast

Sends packets on all member ports.

lacp

Provides load balancing by implementing the Link Aggregation Control Protocol 802.3ad on the member ports.

loadbalance

In passive mode, uses the BPF hash function to select the port that is used to send packets.

In active mode, uses a balancing algorithm to distribute outgoing packets over the available ports.

random

Selects a port at random to send each outgoing packet.

Note

UEK R3 does not currently support this runner mode.

roundrobin

Transmits packets over the available ports in a round-robin fashion.

For specialized applications, you can create customized runners that teamd can interpret. The teamdctl command allows you to control the operation of teamd.

For more information, see the teamd.conf(5) manual page.