Community discussions

MikroTik App
 
localhost
just joined
Topic Author
Posts: 6
Joined: Sat Apr 17, 2010 10:26 am

Bonding 802.3ad issue

Sun Jan 19, 2020 9:02 pm

Hello,

we have 2x 2x1Ge bondings with 802.3ad. When we add them to same bridge there is packet loss.
In combination when one is 802.3ad and other active/backup there is no packet loss.
We are using 6.46.1, same issue was present on 6.45.X.
 
Zacharias
Forum Guru
Forum Guru
Posts: 3459
Joined: Tue Dec 12, 2017 12:58 am
Location: Greece

Re: Bonding 802.3ad issue

Sun Jan 19, 2020 10:16 pm

Can we see the bonding and bridge port configs ?
 
User avatar
StubArea51
Trainer
Trainer
Posts: 1739
Joined: Fri Aug 10, 2012 6:46 am
Location: stubarea51.net
Contact:

Re: Bonding 802.3ad issue

Sun Jan 19, 2020 10:37 pm

What type of links are you connecting to the ports in the bridge? copper/fiber/RF?
 
Zacharias
Forum Guru
Forum Guru
Posts: 3459
Joined: Tue Dec 12, 2017 12:58 am
Location: Greece

Re: Bonding 802.3ad issue

Sun Jan 19, 2020 11:30 pm

What type of links are you connecting to the ports in the bridge? copper/fiber/RF?
If i understood correctly the OP says that there are 2 Bondings inside the same Bridge. If those 2 Bondings inside the same Bridge are 802.3ad there is packet loss, when different there is no packet loss.. so why should the Layer1 connectivity be the problem ?
 
localhost
just joined
Topic Author
Posts: 6
Joined: Sat Apr 17, 2010 10:26 am

Re: Bonding 802.3ad issue

Sun Jan 19, 2020 11:35 pm

/interface bonding> print
Flags: X - disabled, R - running
0 R name="bonding1" mtu=1500 mac-address=74:4D:28:9B:35:05 forced-mac-address=74:4D:28:9B:35:05 arp=enabled arp-timeout=auto slaves=ether1_SERVER1_#1,ether2_SERVER1_#2
mode=802.3ad primary=none link-monitoring=mii arp-interval=100ms arp-ip-targets="" mii-interval=100ms down-delay=0ms up-delay=0ms lacp-rate=1sec
transmit-hash-policy=layer-3-and-4 min-links=0

1 R name="bonding2" mtu=1500 mac-address=74:4D:28:9B:35:07 forced-mac-address=74:4D:28:9B:35:07 arp=enabled arp-timeout=auto slaves=ether3_SERVER2_#1,ether4_SERVER2_#2
mode=active-backup primary=ether3_SERVER2_#1 link-monitoring=mii arp-interval=100ms arp-ip-targets="" mii-interval=100ms down-delay=0ms up-delay=0ms lacp-rate=1sec
transmit-hash-policy=layer-3-and-4 min-links=0

/interface bonding> print
Flags: X - disabled, R - running
0 R name="bonding1" mtu=1500 mac-address=74:4D:28:9B:35:05 forced-mac-address=74:4D:28:9B:35:05 arp=enabled arp-timeout=auto slaves=ether1_SERVER1_#1,ether2_SERVER1_#2
mode=802.3ad primary=none link-monitoring=mii arp-interval=100ms arp-ip-targets="" mii-interval=100ms down-delay=0ms up-delay=0ms lacp-rate=1sec
transmit-hash-policy=layer-3-and-4 min-links=0

1 R name="bonding2" mtu=1500 mac-address=74:4D:28:9B:35:07 forced-mac-address=74:4D:28:9B:35:07 arp=enabled arp-timeout=auto slaves=ether3_SERVER2_#1,ether4_SERVER2_#2
mode=active-backup primary=ether3_SERVER2_#1 link-monitoring=mii arp-interval=100ms arp-ip-targets="" mii-interval=100ms down-delay=0ms up-delay=0ms lacp-rate=1sec
transmit-hash-policy=layer-3-and-4 min-links=0

This is config and there is no packet loss. But bonding2 is working in active/backup mode and there is no packet loss with this configuration but we are not able to have 4Gbps in total.
These are copper ports, and L1 isn't a problem because when bonding2 is in "active-backup" everything is OK.
 
Zacharias
Forum Guru
Forum Guru
Posts: 3459
Joined: Tue Dec 12, 2017 12:58 am
Location: Greece

Re: Bonding 802.3ad issue

Sun Jan 19, 2020 11:42 pm

Layer 2 and 3 should be used with 802.3ad and not Layer 3 and 4...
https://wiki.mikrotik.com/wiki/Manual:I ... ng#802.3ad
Also, did you check the CPU usage when you use 2 802.3ad inside the Bridge ?
 
EdPa
MikroTik Support
MikroTik Support
Posts: 278
Joined: Fri Sep 15, 2017 10:05 am
Location: Riga
Contact:

Re: Bonding 802.3ad issue

Mon Jan 20, 2020 8:56 am

In the latest beta version, we included fixes regarding neighbor discovery, STP and active-backup bonding. If the packet loss is periodic (every minute) and you have some backup/alternate STP paths, try to disable the neighbor discovery on these devices or try out the beta version.

What's new in 6.47beta19 (2020-Jan-09 08:08):
*) discovery - do not send discovery packets on inactive bonding slave interfaces;
*) discovery - do not send discovery packets on interfaces that are blocked by STP;
 
User avatar
StubArea51
Trainer
Trainer
Posts: 1739
Joined: Fri Aug 10, 2012 6:46 am
Location: stubarea51.net
Contact:

Re: Bonding 802.3ad issue

Mon Jan 20, 2020 8:37 pm

What type of links are you connecting to the ports in the bridge? copper/fiber/RF?
If i understood correctly the OP says that there are 2 Bondings inside the same Bridge. If those 2 Bondings inside the same Bridge are 802.3ad there is packet loss, when different there is no packet loss.. so why should the Layer1 connectivity be the problem ?

Because you're making an assumption that it's only Layer 1. If two RF links are plugged in for example, it's not purely L1 but L2 as well. If the latency is significantly different on the two links, we've seen issues with LACP PDUs arriving far enough apart that causes the bonding in the channel to flap which can lead to packet loss.

The same would be true if one of the links was fiber or copper and the other was RF.
 
Zacharias
Forum Guru
Forum Guru
Posts: 3459
Joined: Tue Dec 12, 2017 12:58 am
Location: Greece

Re: Bonding 802.3ad issue

Mon Jan 20, 2020 10:24 pm

@IPANetEngineer what is layer1 or not is not an assumption, is a fact... also everything begins from layer1... can you go on layer2 without passing layer1?
So i dont really catch your point here...

I still believe you talk about 1 bonding...
bonding in the channel to flap
although the OP talks about 2 different bondings...
How can those 2 different bondings interfere with each other ?
 
localhost
just joined
Topic Author
Posts: 6
Joined: Sat Apr 17, 2010 10:26 am

Re: Bonding 802.3ad issue

Tue Jan 21, 2020 12:23 am

Layer 2 and 3 should be used with 802.3ad and not Layer 3 and 4...
https://wiki.mikrotik.com/wiki/Manual:I ... ng#802.3ad
Also, did you check the CPU usage when you use 2 802.3ad inside the Bridge ?
Thanks Zacharias.
I will try this in week or two when I will be able to offload services.
 
ppeetoom
just joined
Posts: 1
Joined: Fri Jul 23, 2021 5:33 pm

Re: Bonding 802.3ad issue

Fri Jul 23, 2021 5:50 pm

Model RB3011UiAS
Firmware Type ipq8060
Current Firmware 6.48.3
Upgrade Firmware 6.48.3

Actually having exactly the same problem. Configuring two 802.3ad bonds in one bridge gives packet loss on both bonds. Have tried the following (all give the same results):

- changing hash policy on one or both from layer-3+4 to layer-2+3
- disabling one interface in one or both bonds
- played with slow of fast LACP rate

What actually fixes the problem is changing one bond to anything but 802.3ad. I have mine running stable on one bond balanced-xor (3+4) and the other 802.3ad (3+4)

So something strange is going on here.
 
Zacharias
Forum Guru
Forum Guru
Posts: 3459
Joined: Tue Dec 12, 2017 12:58 am
Location: Greece

Re: Bonding 802.3ad issue

Mon Jul 26, 2021 9:27 pm

Only CRS3xx devices support 802.3ad on hardware Level..
So am not sure if the Problem is software related to the devices that do not support LACP on hardware level... Maybe high CPU ?

I Only use 802.3ad on CRS3xx devices and i ve not seen any problems...

Who is online

Users browsing this forum: 4l4R1, iustin, lurker888, NetHorror, smirgo and 90 guests