From Fedora Project Wiki
Line 31: Line 31:
* IPv6 Neighbor Solicitation/Neighbor Advertisement link monitoring
* IPv6 Neighbor Solicitation/Neighbor Advertisement link monitoring


NetworkManager is the default network configuration service in Fedora.
NetworkManager has the ambition of replacing network scripts in the future and the team driver is already supported there. Therefore this is more of a must than a benefit.


=== Scope ===
=== Scope ===

Revision as of 09:59, 20 February 2013

Team driver support in NetworkManager

Summary

Owner

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 has the ambition of replacing network scripts in the future and the team driver is already supported there. Therefore this is more of a must than a benefit.

Scope

How to test

User experience

Dependencies

Contingency plan

Documentation

Release notes

Comments and discussions

See Talk:Features/NetworkManagerTeaming