Community discussions

MikroTik App
 
dooh
just joined
Topic Author
Posts: 14
Joined: Fri May 19, 2023 9:55 pm

bonding on CCR2216 not working/crashing the router

Fri May 19, 2023 10:06 pm

Hi there,

I am new to Mikrotik, been using Force10, Cisco, HP and lately Dell, Extreme Networks CER2024 and Ruckus ICX switches. On all of the examples a LACP port-channel works as expected.
On Mikrotik, it seems not, a bonding between SFP28-1, SFP28-2 and a DELL switch does not get in running state except if I reboot the switch, and any other modification by this point will bring the bonding down.
The other issue that I have (already opened a ticket) is when I disable both interfaces in the bond then the bond, the router crashes, web page no longer displays settings, from CLI almost any commands time out.

My bonding on the CCR2216 looks like:
/interface bonding
add mode=802.3ad name=bonding1 slaves=sfp28-1,sfp28-2 transmit-hash-policy=layer-3-and-4
and
[admin@CCR1] > interface/bonding/print
Flags: X - disabled; R - running
 0    name="bonding1" mtu=1500 mac-address=DA:EB:BD:5C:6E:76 arp=enabled arp-timeout=auto slaves=sfp28-1,sfp28-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=30secs transmit-hash-policy=layer-3-and-4 min-links=0
[admin@CCR1] >
and on the Dell:
core-stack#show running-config interface te1/0/24

channel-group 24 mode active
switchport access vlan 24

core-stack#show running-config interface te2/0/24

channel-group 24 mode active
switchport access vlan 24

core-stack#show running-config interface po24

description "CCR1"
switchport access vlan 24

core-stack#show lacp tengigabitethernet 1/0/24

port Te1/0/24 LACP parameters:
Actor:
      system priority:              1
      port Admin key:               0
      port oper key:                841
      port oper priority:           1
      port oper timeout:            LONG
      port Admin timeout:           LONG
      LACP Activity:                ACTIVE
      Aggregation:                  AGGREGATABLE
      synchronization:              FALSE
      collecting:                   FALSE
      distributing:                 FALSE
      expired:                      FALSE
Partner:
      port Admin key:               0
      port oper key:                0
      port Admin priority:          0
      port oper priority:           0
      port Oper timeout:            LONG
      LACP Activity:                ACTIVE
      Aggregation:                  AGGREGATABLE
      synchronization:              TRUE
      collecting:                   FALSE
      distributing:                 FALSE
      expired:                      FALSE
port Te1/0/24 LACP Statistics:
      LACP PDUs send:               2429
      LACP PDUs received:           1541

core-stack#show lacp tengigabitethernet 2/0/24

port Te2/0/24 LACP parameters:
Actor:
      system priority:              1
      port Admin key:               0
      port oper key:                841
      port oper priority:           1
      port oper timeout:            LONG
      port Admin timeout:           LONG
      LACP Activity:                ACTIVE
      Aggregation:                  AGGREGATABLE
      synchronization:              FALSE
      collecting:                   FALSE
      distributing:                 FALSE
      expired:                      FALSE
Partner:
      port Admin key:               0
      port oper key:                0
      port Admin priority:          0
      port oper priority:           0
      port Oper timeout:            LONG
      LACP Activity:                ACTIVE
      Aggregation:                  AGGREGATABLE
      synchronization:              TRUE
      collecting:                   FALSE
      distributing:                 FALSE
      expired:                      FALSE
port Te2/0/24 LACP Statistics:
      LACP PDUs send:               2433
      LACP PDUs received:           1541

core-stack#
I have seen bugs on almost any equipment I used, my first encounter with Force10 was when setting up ssh keys, the L3 switch would reboot, so nothing new. But I cannot see any similar issues on the internet and on the forum so, I am doing something wrong or?
Last edited by dooh on Sat Jun 03, 2023 1:45 pm, edited 2 times in total.
 
LunaticRv
newbie
Posts: 40
Joined: Mon Dec 31, 2018 8:50 am

Re: bonding on CCR2216 not working/crashing the router

Sat May 20, 2023 4:14 pm

I don't think transmit hash policy layer 3 and layer 4 supported on LACP. Maybe try changing it to layer 2 and layer 3?
 
dooh
just joined
Topic Author
Posts: 14
Joined: Fri May 19, 2023 9:55 pm

Re: bonding on CCR2216 not working/crashing the router

Tue May 23, 2023 11:36 pm

Hi,

Thanks for the reply. It does not work. It only works if i reboot the switch. As I have tested, the crash regarding deleting the bond it is unrelated to the switch, it happens with interfaces that are not even connected.

Flags: X - disabled; R - running
 0    name="bonding1" mtu=1500 mac-address=0A:0A:AD:61:B3:AC arp=enabled arp-timeout=auto slaves=sfp28-1,sfp28-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=30secs transmit-hash-policy=layer-2 min-links=0
Later Edit:

After reboot looks like:
[admin@CCR1] > interface/bonding/print
Flags: X - disabled; R - running
 0  R name="bonding1" mtu=1500 mac-address=48:A9:8A:CA:68:E8 arp=enabled arp-timeout=auto slaves=sfp28-1,sfp28-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=30secs transmit-hash-policy=layer-2 min-links=1
[admin@CCR1] > interface/print
Flags: R - RUNNING; S - SLAVE
Columns: NAME, TYPE, ACTUAL-MTU, L2MTU, MAX-L2MTU, MAC-ADDRESS
 #    NAME               TYPE    ACTUAL-MTU  L2MTU  MAX-L2MTU  MAC-ADDRESS
 9 RS sfp28-1            ether         1500   1584       9570  48:A9:8A:CA:68:E8
10 RS sfp28-2            ether         1500   1584       9570  48:A9:8A:CA:68:E9
21 R  bonding1           bond          1500   1584             48:A9:8A:CA:68:E8
 
dooh
just joined
Topic Author
Posts: 14
Joined: Fri May 19, 2023 9:55 pm

Re: bonding on CCR2216 not working/crashing the router

Sat May 27, 2023 5:09 pm

Keep testing, when using just one interface within the bond, the bond can be manipulated/deleted but still does not get in running state.
Is this device so rarely used that I am not getting any help and neither response to the tickets?
 
LunaticRv
newbie
Posts: 40
Joined: Mon Dec 31, 2018 8:50 am

Re: bonding on CCR2216 not working/crashing the router

Mon May 29, 2023 9:36 am

I am using it with CRS518 and Huawei57XX series with bonding (802.3ad mode) and never had issues besides unbalanced traffic sometimes even with 30 gbps traffic.
 
User avatar
chechito
Forum Guru
Forum Guru
Posts: 2989
Joined: Sun Aug 24, 2014 3:14 am
Location: Bogota Colombia
Contact:

Re: bonding on CCR2216 not working/crashing the router

Mon May 29, 2023 6:12 pm

Keep testing, when using just one interface within the bond, the bond can be manipulated/deleted but still does not get in running state.
Is this device so rarely used that I am not getting any help and neither response to the tickets?


you must configure using Bridge Vlan Filtering style of configuration

https://help.mikrotik.com/docs/display/ ... NFiltering

then you can use the bonding interface as a port in the bridge, obtaining hardware offload of the bonding using the integrated Switch ASIC, dont include the ethernet management port in the bridge

be aware you need to have only one bridge to achieve hardware offload correctly
 
dooh
just joined
Topic Author
Posts: 14
Joined: Fri May 19, 2023 9:55 pm

Re: bonding on CCR2216 not working/crashing the router  [SOLVED]

Sat Jun 03, 2023 1:45 pm

Got response from Mikrotik a few days ago, it is something related to VRF, they will release a fix.
For now the workaround is that the slaves remain in main VRF and the bond in the custom VRF.

Thank you all, lets say this is SOLVED

Who is online

Users browsing this forum: adimihaix, Bing [Bot], Qalderu and 74 guests