Chapter 8. Configure Network Teaming
8.1. Understanding Network Teaming
bonding. The term Network Teaming has been chosen to refer to this new implementation of the concept. The existing bonding driver is unaffected, Network Teaming is offered as an alternative and does not replace bonding in Red Hat Enterprise Linux 7.
teamd, which uses the
libteamlibrary is also available. One instance of
teamdcan control one instance of the Team driver. The daemon implements the load-balancing and active-backup logic, such as round-robin, by using additional code referred to as “runners”. By separating the code in this way, the Network Teaming implementation presents an easily extensible and scalable solution for load-balancing and redundancy requirements. For example, custom runners can be relatively easily written to implement new logic through
teamd, and even
teamdis optional, users can write their own application to use libteam.
teamdusing D-bus. teamdctl provides a D-Bus wrapper around the
teamdD-Bus API. By default,
teamdlistens and communicates using Unix Domain Sockets but still monitors D-Bus. This is to ensure that
teamdcan be used in environments where D-Bus is not present or not yet loaded. For example, when booting over
teamdlinks, D-Bus would not yet be loaded. The teamdctl utility can be used during run time to read the configuration, the state of link-watchers, check and change the state of ports, add and remove ports, and to change ports between active and backup states.
libteamuser-space library does not directly interact with the API, but uses libnl or teamnl to interact with the driver API.
portis also known as
Portis preferred when using
slaveis used when using NetworkManager to refer to interfaces which create a team.