8.2. Understanding the Default Behavior of Controller and Port Interfaces
When controlling teamed port interfaces using the
NetworkManager daemon, and especially when fault finding, keep the following in mind:
- Starting the controller interface does not automatically start the port interfaces.
- Starting a port interface always starts the controller interface.
- Stopping the controller interface also stops the port interfaces.
- A controller without ports can start static
IPconnections. - A controller without ports waits for ports when starting
DHCPconnections. - A controller with a
DHCPconnection waiting for ports completes when a port with a carrier is added. - A controller 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.
