From Fedora Project Wiki
< Features
| Line 24: | Line 24: | ||
=== Benefit to Fedora === | === Benefit to Fedora === | ||
Team Driver provides userspace driven NIC Teaming. In addition to that there are some new features in Team Driver that are not available in bonding. For example: | |||
* load balancing for LACP | |||
* separate per-port link monitoring setup | |||
* port priorities and stickiness | |||
* IPv6 Neighbor Solicitation/Neighbor Advertisement link monitoring | |||
NetworkManager is the default network configuration service in Fedora. | |||
=== Scope === | === Scope === | ||
Revision as of 09:56, 20 February 2013
Team driver support in NetworkManager
Summary
Owner
- Name: Pavel Šimerda
- Email: psimerda at redhat.com
- Name: Jiří Pírko
- Email: jpirko at redhat.com
Current status
- Targeted release: Fedora 20
- Last updated: 2013-02-20
- Percentage of completion: 0%
Detailed description
The purpose of the Team driver is to provide a mechanism to team multiple NICs (ports) into one logical one (teamdev) at L2 layer. The process is called "channel bonding", "Ethernet bonding", "channel teaming", "link aggregation", etc.
The teaming kernel driver (see Features/TeamDriver) supersedes bonding but NetworkManager still supports only the legacy bonding driver (see Features/NetworkManagerBonding).
Benefit to Fedora
Team Driver provides userspace driven NIC Teaming. In addition to that there are some new features in Team Driver that are not available in bonding. For example:
- load balancing for LACP
- separate per-port link monitoring setup
- port priorities and stickiness
- IPv6 Neighbor Solicitation/Neighbor Advertisement link monitoring
NetworkManager is the default network configuration service in Fedora.