Community discussions

MikroTik App
 
n0xlf
just joined
Topic Author
Posts: 14
Joined: Thu Nov 08, 2012 7:16 pm

CRS312 bonding problem (fw bug?)

Sat Sep 04, 2021 11:23 pm

Running 6.49beta54 on a CRS312 and can not get a 2 port 10G bond working, to the point that I believe it may be a firmware bug.

The bond is 802.3ad, layer 3+4, 9000 byte frames, 2x10G ports going to a Fedora 34 server. I always end up with one port showing "inactive" on the Mikrotik side and often end up with no connectivity at all until I randomly enable/disable the 2 port members. I have tried the following (and probably more that I can't remember):

  • Layer 2
  • 1500 byte frames
  • Disabling mii
  • Taking the bond out of any bridge

I have an additional 2x1G bond running to a UniFi switch with no issues.

The Mikrotik slave monitoring only shows the key (33) and no partner info, with flags A-GS-F-

The "F" flag is certainly a clue but I don't know what would be causing it:
F - defaulted (link is using defaulted partner information, indicated that no LACPDU has been received from the partner)

Info from the Linux side (failures shown are from testing):
Ethernet Channel Bonding Driver: v5.13.13-200.fc34.x86_64

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer3+4 (1)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Peer Notification Delay (ms): 0

802.3ad info
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: 82:af:2b:ec:cf:1c
Active Aggregator Info:
        Aggregator ID: 1
        Number of ports: 2
        Actor Key: 15
        Partner Key: 33
        Partner Mac Address: 74:4d:28:d2:3e:a0

Slave Interface: eno1np0
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 29
Permanent HW addr: 00:25:90:5f:99:ec
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: monitoring
Partner Churn State: monitoring
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
    system priority: 65535
    system mac address: 82:af:2b:ec:cf:1c
    port key: 15
    port priority: 255
    port number: 1
    port state: 5
details partner lacp pdu:
    system priority: 65535
    system mac address: 74:4d:28:d2:3e:a0
    oper key: 33
    port priority: 255
    port number: 1
    port state: 69

Slave Interface: eno2np1
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 28
Permanent HW addr: 00:25:90:5f:99:ed
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: monitoring
Partner Churn State: monitoring
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
    system priority: 65535
    system mac address: 82:af:2b:ec:cf:1c
    port key: 15
    port priority: 255
    port number: 2
    port state: 5
details partner lacp pdu:
    system priority: 65535
    system mac address: 74:4d:28:d2:3e:a0
    oper key: 33
    port priority: 255
    port number: 2
    port state: 69

Any thoughts?
 
n0xlf
just joined
Topic Author
Posts: 14
Joined: Thu Nov 08, 2012 7:16 pm

Re: CRS312 bonding problem (fw bug?)

Sat Sep 04, 2021 11:44 pm

Sometimes you just need to post about things to get your mind flowing again - The "F" flag lead me to this bug:
https://github.com/systemd/systemd/issues/15208

Which apparently still exists - problem solved with the fix mentioned in that thread!!

I'll leave this post up for others who may search and find it useful..

Who is online

Users browsing this forum: No registered users and 73 guests