Team configuration in CentOS 7

Team configuration in CentOS 7

Bonding vs Team

You have encountered many pitfalls when configuring bonding on CentOS7. After reading RedHat's official blog, I realized that CentOS7 introduced team driver.

Before CentOS7, the system provided bonding driver for Link aggregation. In fact, bonding is applicable to most applications. The Bonding driver architecture is fully controlled and managed by the kernel space.

What is Team driver? The team driver does not intend to copy the bonding driver. In fact, it is designed to implement bonding with a set of different designs and different methods. It is more flexible and efficient. The following is the feature and performance Comparison between Bonding and Teaming:

 

Performance

From the official comparison data provided by redhat, team driver is better than bonding driver in terms of feature and performance. How stable is the team driver? Waiting for testing.

For the existing bonding configuration, if you want to switch from bonding driver to team driver, redhat is quite user-friendly and provides a bond2team command line tool.

Team Configuration

According to the rhel7 networking guide pdf provided by redhat, the configuration is still detailed.

The nmtui text interface tool is used for configuration (NIC configuration file will be generated directly). This tool can also configure bonding. I tried bond1, and ifup takes effect every time, systemctlrestart network.

Type nmtui in the command line. The home page is as follows:

You cannot select mode When configuring the team. This is too much ...! The default value is mode0.

Bond2team comes in handy. Haha!

In this directory, you can view the related mode configuration.

Use team to configure mode 1

[Root @ compute-6 network-scripts] # vim ifcfg-team0 # edit the ifcfg-team0, modify the corresponding pitfall,
DEVICE = team0
DEVICETYPE = "Team"
BOOTPROTO = none # dhcp is generated and changed to static. Otherwise, the ip address cannot start.
DEFROUTE = yes
20174_failure_fatal = no
IPV6INIT = yes
IPV6_AUTOCONF = yes
Required 6_defroute = yes
20176_failure_fatal = no
NAME = team0
UUID = 7a9afef2-4aba-463d-a2d5-59fcc1dc885c
ONBOOT = yes
TEAM_CONFIG = "{" runner ": {" name ":" activebackup "}," link_watch ": {" name ":" ethtool "}}" # Add TEAM_CONFIG content
IPADDR = 172.16.100.6
PREFIX = 24
GATEWAY = 172.16.100.254
PEERDNS = yes
PEERROUTES = yes
IPV6_PEERDNS = yes
20176_peerroutes = yes
Service network restart # restart the network

To check the team status, you need to install the teamd package.

After the machine is restarted, team0 cannot start. I don't know what's going on yet?

Reference

Http://rhelblog.redhat.com/2014/06/23/team-driver/