linux_wiki:use_network_teaming_or_bonding_to_configure_aggregated_network_links_between_two_red_hat_enterprise_linux_systems

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
linux_wiki:use_network_teaming_or_bonding_to_configure_aggregated_network_links_between_two_red_hat_enterprise_linux_systems [2016/10/10 14:15]
billdozor 		linux_wiki:use_network_teaming_or_bonding_to_configure_aggregated_network_links_between_two_red_hat_enterprise_linux_systems [2018/05/29 22:07]
billdozor
Line 15: Line 15:
 ---- ----
  
 +====== Help ======
  
 +Finding help in this section.
 +  * nmcli examples<code bash>man nmcli-examples</code>
 +  * Team 'runner' config examples<code bash>/usr/share/doc/teamd-1.17/example_configs/</code>
 +
 +----
  
 ====== Team Creation ====== ====== Team Creation ======
Line 27: Line 33:
 Each VM should end up with 3 total interfaces: Each VM should end up with 3 total interfaces:
   * Main Management NIC: 192.168.1.x (server1=150 and server2=151)   * Main Management NIC: 192.168.1.x (server1=150 and server2=151)
-  * Additional NIC for slave1: 10.0.0.x +  * Additional NIC for team-slave: Can be bridged or private 
-  * Additional NIC for slave2: 10.0.0.x+  * Additional NIC for team-slave: Can be bridged or private
  
 \\ \\
Line 56: Line 62:
 yum install teamd yum install teamd
 </code> </code>
- 
-\\ 
-**Example configs** located at: /usr/share/doc/teamd-*/example_configs 
  
 \\ \\
Line 70: Line 73:
 ===== Interface Teaming ===== ===== Interface Teaming =====
  
-Create a new team connection+**On each VM**; Create a new team connection
 <code bash> <code bash>
 nmcli con add type team ifname team0 config '{"runner": {"name": "loadbalance"}}' nmcli con add type team ifname team0 config '{"runner": {"name": "loadbalance"}}'
 </code> </code>
-  * This creates a connection with a name of "team-team0" using device "team0". (type is pre-pended, since no con-name was specified)+  * Connection name is auto-created by combining type and ifname. (team-<ifname>) 
 +    * If you really want to, you can define the con-name during creation
   * Other team "name" types that can be passed in the JSON for runner configuration (man teamd.conf):   * Other team "name" types that can be passed in the JSON for runner configuration (man teamd.conf):
     * broadcast -> transmit packets via all ports     * broadcast -> transmit packets via all ports
Line 81: Line 85:
     * loadbalance -> balance between ports     * loadbalance -> balance between ports
     * lacp -> 802.3ad LACP protocol     * lacp -> 802.3ad LACP protocol
-  * Example JSON configs are available at: /usr/share/doc/teamd-1.17/example_configs/+  * **Example JSON configs** are available at: 
 +    * /usr/share/doc/teamd-1.17/example_configs/ 
 +    * man teamd.conf -> "EXAMPLES" section at the bottom
  
 \\ \\
 Assign a static address to the virtual team0 interface Assign a static address to the virtual team0 interface
-<code bash> +  * server1 team<code bash>nmcli con mod team-team0 ipv4.method manual ipv4.addresses 10.0.0.10/24</code> 
-nmcli con mod team-team0 ipv4.method manual ipv4.addresses 10.1.2.3/24 +  * server2 team<code bash>nmcli con mod team-team0 ipv4.method manual ipv4.addresses 10.0.0.20/24</code>
-</code>+
  
 \\ \\
-Add two **unconfigured** interfaces (enp0s8 and enp0s9) to the virtual team0 interface+**On each VM**; Add two **unconfigured** interfaces (enp0s8 and enp0s9) to the virtual team0 interface
 <code bash> <code bash>
-nmcli con add type team-slave con-name team0-port1 ifname enp0s8 master team0 +nmcli con add type team-slave ifname enp0s8 master team0 
-nmcli con add type team-slave con-name team0-port2 ifname enp0s9 master team0+nmcli con add type team-slave ifname enp0s9 master team0
 </code> </code>
 +  * Connection name is auto-created by combining type and ifname. (team-slave-<ifname>)
 +    * If you really want to, you can define the con-name during creation
   * If the interfaces have any previous configuration, you may get errors when attempting to set the connections to "up" later on. ("Error: Connection activation failed: Active connection removed before it was initialized")   * If the interfaces have any previous configuration, you may get errors when attempting to set the connections to "up" later on. ("Error: Connection activation failed: Active connection removed before it was initialized")
     * Remove configurations: nmcli con delete <con-name>     * Remove configurations: nmcli con delete <con-name>
  
 \\ \\
-Configure ports and team as up+**On each VM**; Configure ports and team as up
 <code bash> <code bash>
-nmcli con up team0-port1 +nmcli con up team-slave-enp0s8 
-nmcli con up team0-port2+nmcli con up team-slave-enp0s9
 nmcli con up team-team0 nmcli con up team-team0
 </code> </code>
  
 \\ \\
-View team status+View team status (by team device name)
 <code bash> <code bash>
 teamdctl team0 state teamdctl team0 state
 </code> </code>
 +
 +\\
 +**Team Config Command Examples**<code bash>man nmcli-examples</code>
 +
 +----
 +
 +===== Interface Bonding =====
 +
 +If you run into issues with teaming not working correctly, you can always set up a bonded connection in order to achieve the objective on the exam.
 +
 +This is straight from 'man nmcli-examples':<code bash>nmcli con add type bond ifname mybond0 mode active-backup
 +nmcli con add type ethernet ifname eth1 master mybond0
 +nmcli con add type ethernet ifname eth2 master mybond0</code>
  
 ---- ----
  
  • linux_wiki/use_network_teaming_or_bonding_to_configure_aggregated_network_links_between_two_red_hat_enterprise_linux_systems.txt
  • Last modified: 2019/05/25 23:50
  • (external edit)