Link Aggregation - Revision history

Leo: /* LACP remains disabled in Open vSwitch */

2022-09-28T23:30:51Z

LACP remains disabled in Open vSwitch

← Older revision		Revision as of 23:30, 28 September 2022
Line 235:		Line 235:
	\| lang = terminal		\| lang = terminal
	}}		}}
	Solution: The problem here is that the Intel X550T card is not supported by Open vSwitch. To confirm if this applies to you, run lspci:		''Solution'': The problem here is that the Intel X550T card is not supported by Open vSwitch. To confirm if this applies to you, run lspci:
	{{Highlight		{{Highlight
	\| code = # lspci{{!}}grep -i network		\| code = # lspci{{!}}grep -i network
	02:00.0 Ethernet controller: Intel Corporation ~~I350 Gigabit Network Connection~~ (rev 01)		03:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10G X550T (rev 01)
	02:00.3 Ethernet controller: Intel Corporation ~~I350 Gigabit Network Connection~~ (rev 01)		03:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10G X550T (rev 01)
	\| lang = terminal		\| lang = terminal
	}}		}}

Leo at 22:13, 28 September 2022

2022-09-28T22:13:21Z

← Older revision		Revision as of 22:13, 28 September 2022
Line 165:		Line 165:

	To bring a port down, run: <code>ovs-ofctl mod-port br0 bond0 down</code>		To bring a port down, run: <code>ovs-ofctl mod-port br0 bond0 down</code>

			==== LACP remains disabled in Open vSwitch ====
			After configuring a pair of interfaces into a bonded port in Open vSwitch, the port remains disabled. The bond status also shows that the <code>actor state</code> is <code>defaulted</code> and the <code>may_enable</code> parameter is <code>false</code>. The underlying network interfaces do show LACP packets, but it is not being negotiated.
			{{Highlight
			\| code = # ovs-appctl lacp/show
			---- bond0 ----
			status: active
			sys_id: 6c:b3:11:13:58:d8
			sys_priority: 65534
			aggregation key: 5
			lacp_time: slow

			member: enp3s0f0: defaulted attached
			port_id: 6
			port_priority: 65535
			may_enable: true

			actor sys_id: 6c:b3:11:13:58:d8
			actor sys_priority: 65534
			actor port_id: 6
			actor port_priority: 65535
			actor key: 5
			actor state: activity aggregation synchronized collecting distributing defaulted

			partner sys_id: 00:00:00:00:00:00
			partner sys_priority: 0
			partner port_id: 0
			partner port_priority: 0
			partner key: 0
			partner state:

			member: enp3s0f1: defaulted attached
			port_id: 5
			port_priority: 65535
			may_enable: true

			actor sys_id: 6c:b3:11:13:58:d8
			actor sys_priority: 65534
			actor port_id: 5
			actor port_priority: 65535
			actor key: 5
			actor state: activity aggregation synchronized collecting distributing defaulted

			partner sys_id: 00:00:00:00:00:00
			partner sys_priority: 0
			partner port_id: 0
			partner port_priority: 0
			partner key: 0
			partner state:

			# ovs-appctl bond/show bond0
			---- bond0 ----
			bond_mode: balance-tcp
			bond may use recirculation: no, Recirc-ID : -1
			bond-hash-basis: 0
			lb_output action: disabled, bond-id: -1
			updelay: 0 ms
			downdelay: 0 ms
			lacp_status: configured
			lacp_fallback_ab: true
			active-backup primary: <none>
			active member mac: 00:00:00:00:00:00(none)

			member enp3s0f0: disabled
			may_enable: false

			member enp3s0f1: disabled
			may_enable: false
			\| lang = terminal
			}}
			Solution: The problem here is that the Intel X550T card is not supported by Open vSwitch. To confirm if this applies to you, run lspci:
			{{Highlight
			\| code = # lspci{{!}}grep -i network
			02:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
			02:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
			\| lang = terminal
			}}
			If this is the case, your next best option is to use Linux's LACP implementation described above (using <code>nmcli</code> or network-scripts to set up bond0 with LACP) and then add the port to Open vSwitch to the bond0 device (<code>ovs-vsctl add-port nic0 bond0 vlan_mode=native-untagged</code>).

	== Troubleshooting ==		== Troubleshooting ==

Leo at 01:23, 10 February 2022

2022-02-10T01:23:09Z

@@ Line 48: / Line 48: @@
 |}
 You can see the current bonding status by reading {{code|/proc/net/bonding/bond0}}:
 {{highlight

Leo: /* Open vSwitch */

2022-02-08T01:50:11Z

Open vSwitch

← Older revision		Revision as of 01:50, 8 February 2022
Line 105:		Line 105:
	\| lang = terminal		\| lang = terminal
	}}		}}

	~~==== Supported modes ====~~
	~~{\| class="wikitable"~~
	~~!bond_mode~~
	~~!Description~~
	\|-
	~~\|active-backup~~
	\|
	\|-
	~~\|balance-slb~~
	\|
	\|-
	~~\|balance-tcp~~
	\|
	\|}

	==== LACP options ====		==== LACP options ====
Line 129:		Line 114:
	\|<code>lacp</code>		\|<code>lacp</code>
	\|		\|
	* active - ports can initiate LACP negotiations		* <code>active</code> - ports can initiate LACP negotiations
	* passive - ports can participate in LACP negotiations if initiated by the switch		* <code>passive</code> - ports can participate in LACP negotiations if initiated by the switch
	* off - do not use LACP (default)		* <code>off</code> - do not use LACP (default)
	\|-		\|-
	\|<code>bond_mode</code>		\|<code>bond_mode</code>
	\|		\|
	* balance-slb - Balances traffic based on source MAC address and output VLAN		* <code>balance-slb</code> - Balances traffic based on source MAC address and output VLAN
	* active-backup - Uses one member and fails over to a backup member (default)		* <code>active-backup</code> - Uses one member and fails over to a backup member (default)
	* balance-tcp - Requires 802.3ad / LACP enabled. Balances traffic based on l3/l4 information (Eg. IP addresses or ports).		* <code>balance-tcp</code> - Requires 802.3ad / LACP enabled. Balances traffic based on l3/l4 information (Eg. IP addresses or ports).
	\|-		\|-
	\|<code>other_config:bond-detect-mode</code>		\|<code>other_config:bond-detect-mode</code>
	\|		\|
	* carrier - check by the link's carrier status		* <code>carrier</code> - check by the link's carrier status
	* miimon - check by polling each interface's MII		* <code>miimon</code> - check by polling each interface's MII
	\|-		\|-
	\|<code>other_config:bond-miimon-interval</code>		\|<code>other_config:bond-miimon-interval</code>
Line 155:		Line 140:
	\|<code>other_config:lacp-fallback-ab</code>		\|<code>other_config:lacp-fallback-ab</code>
	\|		\|
	* true - allows Open vSwitch to fallback to active-backup mode if the switch does not support LACP		* <code>true</code> - allows Open vSwitch to fallback to active-backup mode if the switch does not support LACP
	* false - the bond will be disabled if LACP is not supported by the switch.		* <code>false</code> - the bond will be disabled if LACP is not supported by the switch (default).
	\|}		\|}
	To check on the status of your bond, run: <code>ovs-appctl lacp/show</code>		To check on the status of your bond, run: <code>ovs-appctl lacp/show</code>

Leo at 01:33, 8 February 2022

2022-02-08T01:33:44Z

@@ Line 1: / Line 1: @@
 Link Aggregation joins two or more network interfaces together. Depending on the configuration, you can increase bandwidth, throughput, performance and redundancy.
 ==Linux==
-There is a bonding kernel module which can bond multiple network interfaces (so-called slaves) into a virtual bonded network interface. There are a few modes that are supported:
+Link aggregation on Linux is available using either the Linux kernel ethernet bonding driver, the Linux Team driver (which runs the link validation, LACP implementation, etc. in user space), or some other application such as Open vSwitch.
 {| class="wikitable"
 !Type
 !Description
 |-
-|mode=0, mode=balance-rr
+|0
-|Round Robin policy and is the default mode.
+|balance-rr
 |-
-|mode=1, mode=active-backup
+|1
 |Only one slave is active at one time. All slave interfaces will share the same MAC address.
 |-
-|mode=3, mode=broadcast
+|2
 |Everything is transmitted on all slave interfaces
 |-
-|mode=4, mode=802.3ad
+|4
-|Dynamic Link Aggregation mode, also known as LACP, on a switch that supports IEEE 802.3ad dynamic link.
+|802.3ad
 |-
-|mode=5, mode=balance-tlb
+|5
 |Adaptive transmit load balancing. Outgoing traffic is distributed based on load on each slave.
 |-
-|mode=6, mode=balance-alb
+|6
 |Adaptive load balancing.
 |}
 You can see the current bonding status by reading {{code|/proc/net/bonding/bond0}}:
-{{highlight|lang=terminal|code=
+{{highlight
-# cat /proc/net/bonding/bond0
+| lang = terminal
 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
@@ Line 72: / Line 95: @@
 Slave queue ID: 0
 }}
 == Troubleshooting ==

Leo: /* See Also */

2020-08-13T18:19:13Z

See Also

← Older revision		Revision as of 18:19, 13 August 2020
Line 1:		Line 1:
	Link Aggregation joins two or more network interfaces together. Depending on the configuration, you can increase bandwidth, throughput, performance and redundancy.		Link Aggregation joins two or more network interfaces together. Depending on the configuration, you can increase bandwidth, throughput, performance and redundancy.

	== Linux ==		==Linux==
	There is a bonding kernel module which can bond multiple network interfaces (so-called slaves) into a virtual bonded network interface. There are a few modes that are supported:		There is a bonding kernel module which can bond multiple network interfaces (so-called slaves) into a virtual bonded network interface. There are a few modes that are supported:

	{\| class="wikitable"		{\| class="wikitable"
	! Type		!Type
	! Description		!Description
	\|-		\|-
	\| mode=0, mode=balance-rr		\|mode=0, mode=balance-rr
	\| Round Robin policy and is the default mode.		\|Round Robin policy and is the default mode.
	\|-		\|-
	\| mode=1, mode=active-backup		\|mode=1, mode=active-backup
	\| Only one slave is active at one time. All slave interfaces will share the same MAC address.		\|Only one slave is active at one time. All slave interfaces will share the same MAC address.
	\|-		\|-
	\| mode=3, mode=broadcast		\|mode=3, mode=broadcast
	\| Everything is transmitted on all slave interfaces		\|Everything is transmitted on all slave interfaces
	\|-		\|-
	\| mode=4, mode=802.3ad		\|mode=4, mode=802.3ad
	\| Dynamic Link Aggregation mode, also known as LACP, on a switch that supports IEEE 802.3ad dynamic link.		\|Dynamic Link Aggregation mode, also known as LACP, on a switch that supports IEEE 802.3ad dynamic link.
	\|-		\|-
	\| mode=5, mode=balance-tlb		\|mode=5, mode=balance-tlb
	\| Adaptive transmit load balancing. Outgoing traffic is distributed based on load on each slave.		\|Adaptive transmit load balancing. Outgoing traffic is distributed based on load on each slave.
	\|-		\|-
	\| mode=6, mode=balance-alb		\|mode=6, mode=balance-alb
	\| Adaptive load balancing.		\|Adaptive load balancing.
	\|}		\|}

Line 73:		Line 73:
	}}		}}

	== ~~See Also~~ ==		== Troubleshooting ==
	* https://en.wikipedia.org/wiki/Link_aggregation
	* http://www.linuxhorizon.ro/bonding.html
	* https://wiki.debian.org/Bonding
	* https://www.interserver.net/tips/kb/network-bonding-types-network-bonding/

	{{Navbox Linux}}[[Category:Linux]]		=== Bond link keeps on randomly dying ===
			I have a bond0 interface that randomly stops communicating with another device on the infiniband network. Here's some duct tape to toggle the active slave down and up which causes the bond to pick another active slave which in doing so fixes the network issues (at least temporarily). I run this script every 5 minutes via cronjob.
			{{Highlight
			\| code = #!/bin/bash

			function fix_fail (){
			echo Fixing a bad connection
			ActiveIb=$(cat /proc/net/bonding/bond0 {{!}}grep -i "Currently Active" {{!}} awk '{print $4}')
			/sbin/ifconfig $ActiveIb down
			/sbin/ifconfig $ActiveIb up
			}

			ping -W 2 -c 5 ems1-ib {{!}}{{!}} fix_fail
			\| lang = bash
			}}

			==See Also==

			*https://en.wikipedia.org/wiki/Link_aggregation
			*http://www.linuxhorizon.ro/bonding.html
			*https://wiki.debian.org/Bonding
			*https://www.interserver.net/tips/kb/network-bonding-types-network-bonding/

			{{Navbox Linux}}
			[[Category:Linux]]
	[[Category:Networking]]		[[Category:Networking]]

Leo: Added categories

2020-06-14T23:44:34Z

Added categories

← Older revision		Revision as of 23:44, 14 June 2020
Line 78:		Line 78:
	* https://wiki.debian.org/Bonding		* https://wiki.debian.org/Bonding
	* https://www.interserver.net/tips/kb/network-bonding-types-network-bonding/		* https://www.interserver.net/tips/kb/network-bonding-types-network-bonding/

			{{Navbox Linux}}[[Category:Linux]]
			[[Category:Networking]]

Leo at 21:35, 5 May 2020

2020-05-05T21:35:13Z

← Older revision		Revision as of 21:35, 5 May 2020
Line 1:		Line 1:
	~~Network bonding~~ joins two or more network interfaces together~~, also known as link aggregation~~. Depending on the configuration, you can increase bandwidth, throughput, performance and redundancy.		Link Aggregation joins two or more network interfaces together. Depending on the configuration, you can increase bandwidth, throughput, performance and redundancy.

	== Linux ==		== Linux ==
	There is a bonding kernel module which can bond multiple network interfaces into a virtual bonded network interface. There are a few modes that are supported:		There is a bonding kernel module which can bond multiple network interfaces (so-called slaves) into a virtual bonded network interface. There are a few modes that are supported:

	{\| class="wikitable"		{\| class="wikitable"
Line 18:		Line 18:
	\|-		\|-
	\| mode=4, mode=802.3ad		\| mode=4, mode=802.3ad
	\| Dynamic Link Aggregation mode on a switch that supports IEEE 802.3ad dynamic link.		\| Dynamic Link Aggregation mode, also known as LACP, on a switch that supports IEEE 802.3ad dynamic link.
	\|-		\|-
	\| mode=5, mode=balance-tlb		\| mode=5, mode=balance-tlb
Line 74:		Line 74:

	== See Also ==		== See Also ==
			* https://en.wikipedia.org/wiki/Link_aggregation
	* http://www.linuxhorizon.ro/bonding.html		* http://www.linuxhorizon.ro/bonding.html
	* https://wiki.debian.org/Bonding		* https://wiki.debian.org/Bonding
	* https://www.interserver.net/tips/kb/network-bonding-types-network-bonding/		* https://www.interserver.net/tips/kb/network-bonding-types-network-bonding/

Leo: Leo moved page Network Bonding to Link Aggregation

2020-05-05T21:33:19Z

Leo moved page Network Bonding to Link Aggregation

← Older revision		Revision as of 21:33, 5 May 2020
(No difference)

Leo: /* See Also */

2020-05-05T20:26:33Z

← Older revision		Revision as of 20:26, 5 May 2020
Line 74:		Line 74:

	== See Also ==		== See Also ==
			* http://www.linuxhorizon.ro/bonding.html
			* https://wiki.debian.org/Bonding
	* https://www.interserver.net/tips/kb/network-bonding-types-network-bonding/		* https://www.interserver.net/tips/kb/network-bonding-types-network-bonding/
	* https://wiki.debian.org/Bonding