Chapter 9. Configuring network teams using the web console
Learn how network bonding works, what are the differences between network teams and network bonds, and what are the possibilities of configuration in the web console.
Additionally you can find guidelines for:
- Adding a new network team
- Adding new interfaces to an existing network team
- Removing interfaces from an existing network team
- Removing a network team
Network teaming is deprecated in Red Hat Enterprise Linux 9. Consider using the network bonding driver as an alternative. For details, see Configuring network bonding.
Prerequisites
The RHEL web console installed and enabled.
For details, see Installing the web console.
9.1. Understanding network teaming
Network teaming is a feature that combines or aggregates network interfaces to provide a logical interface with higher throughput or redundancy.
Network teaming uses a kernel driver to implement fast handling of packet flows, as well as user-space libraries and services for other tasks. This way, network teaming is an easily extensible and scalable solution for load-balancing and redundancy requirements.
Certain network teaming features, such as the fail-over mechanism, do not support direct cable connections without a network switch. For further details, see Is bonding supported with direct connection using crossover cables?
9.2. Comparison of network teaming and bonding features
Learn about the features supported in network teams and network bonds:
| Feature | Network bond | Network team |
|---|---|---|
| Broadcast Tx policy | Yes | Yes |
| Round-robin Tx policy | Yes | Yes |
| Active-backup Tx policy | Yes | Yes |
| LACP (802.3ad) support | Yes (active only) | Yes |
| Hash-based Tx policy | Yes | Yes |
| User can set hash function | No | Yes |
| Tx load-balancing support (TLB) | Yes | Yes |
| LACP hash port select | Yes | Yes |
| Load-balancing for LACP support | No | Yes |
| Ethtool link monitoring | Yes | Yes |
| ARP link monitoring | Yes | Yes |
| NS/NA (IPv6) link monitoring | No | Yes |
| Ports up/down delays | Yes | Yes |
| Port priorities and stickiness (“primary” option enhancement) | No | Yes |
| Separate per-port link monitoring setup | No | Yes |
| Multiple link monitoring setup | Limited | Yes |
| Lockless Tx/Rx path | No (rwlock) | Yes (RCU) |
| VLAN support | Yes | Yes |
| User-space runtime control | Limited | Yes |
| Logic in user-space | No | Yes |
| Extensibility | Hard | Easy |
| Modular design | No | Yes |
| Performance overhead | Low | Very low |
| D-Bus interface | No | Yes |
| Multiple device stacking | Yes | Yes |
| Zero config using LLDP | No | (in planning) |
| NetworkManager support | Yes | Yes |
9.3. Adding a new team using the web console
Configure a new active backup network team on two or more network interfaces using the web console.
Prerequisites
- Two or more network cards installed on the server.
- The network cards are connected to a switch.
Procedure
Log in to the web console.
For details, see Logging in to the web console
- Go to the Networking tab.
- Click the Add Team button.
In the Team Settings area, configure parameters for the new team:
- Add a name for your team device to the Name field.
- In the Ports field, select all network interfaces you want to add to the team.
- In the Runner drop down menu, select the runner.
In the Link Watch drop down menu select a link watcher.
- If you select Ethtool, additionally, set a link up delay and a link down delay.
- If you select ARP Ping or NSNA Ping, additionally, set a ping interval and ping target.
Click Apply
Verification steps
Go to the Networking tab and check if the Sending and Receiving columns in the Interfaces table display a network activity.
Additional resources
9.4. Adding new interfaces to the team using the web console
Network teams can include multiple interfaces and it is possible to add or remove any of them at any time. The following section describes how to add a new network interface to an existing team.
Prerequisites
- A network team with is configured.
Procedure
Log in to the web console.
For details, see Logging in to the web console.
- Switch to the Networking tab.
- In the Interfaces table, click on the team you want to configure.
- In the team settings window, scroll down to the Ports table.
- Click on the icon.
Select the interface you wish to add from the drop down list.
The RHEL web console adds the interface to the team.
9.5. Removing or disabling an interface from the team using the web console
Network teams can include multiple interfaces. If you need to change a device, you can remove or disable particular interfaces from the network team, which will work together with the rest of active interfaces.
There are two options how to stop using an interface included in a team:
- Removing the interface from the team
- Temporarily disabling the interface. The interface then stays a part of the team, but the team will not use it until you enable it again.
Prerequisites
- A network team with multiple interfaces exists on the host.
Procedure
Log in to the RHEL web console.
For details, see Logging in to the web console.
- Switch to the Networking tab.
- Click the team you want to configure.
- In the team settings window, scroll down to the table of ports (interfaces).
Select an interface and remove or disable it.
- Switch the button to Off to disable the interface.
Click the icon to remove the interface.
Based on your choice, the web console either removes or disables the interface. If you remove the interface, it will be available in Networking as a standalone interface.
9.6. Removing or disabling a team using the web console
Remove or disable a network team using the web console. If you only disable the team, interfaces in the team will stay in it but the team will not be used for network traffic.
Prerequisites
- A network team is configured on the host.
Procedure
Log in to the web console.
For details, see Logging in to the web console.
- Switch to the Networking tab.
- Click the team you wish to remove or disable.
Remove or disable the selected team.
- You can remove the team by clicking the button.
You can disable the team by moving the switch to a disabled position.
Verification steps
- If you removed the team, go to Networking, and verify that all the interfaces from your team are now listed as standalone interfaces.