Show Table of Contents
8.2. Understanding the Default Behavior of Master and Slave Interfaces
When controlling teamed port interfaces using the
NetworkManager daemon, and especially when fault finding, keep the following in mind:
- Starting the master interface does not automatically start the port interfaces.
- Starting a port interface always starts the master interface.
- Stopping the master interface also stops the port interfaces.
- A master without ports can start static
IPconnections. - A master without ports waits for ports when starting
DHCPconnections. - A master with a
DHCPconnection waiting for ports completes when a port with a carrier is added. - A master with a
DHCPconnection waiting for ports continues waiting when a port without a carrier is added.
Warning
The use of direct cable connections without network switches is not supported for teaming. The failover mechanisms described here will not work as expected without the presence of network switches. See the Red Hat Knowledgebase article Why is bonding not supported with direct connection using crossover cables? for more information.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.