LACP on NAS sysnology RS1221RP+ and Meraki cisco MS410

[MinhTu]

LACP configuration between Sysnology NAS bond 4 port and MS410 01 port 25,26 stack MS410 port 25,26 . Error ""Port running LACP and LACP has disabled this port"" .  HOw to fix?

Thanks 

[RWelch]

Often speed and duplex are not identical when LACP fails.  That is where I'd look first (suggestion).

[MinhTu]

port on MS410 and NAS are both 1gb. Any further suggestions?

[RWelch]

Are they both set to AUTO or 1Gig (manual)?  Although Meraki typically recommends setting ALL ports to AUTO negotiate, some hardware might need to be set manually (forced).

And you marked your own response as Accept as Solution.  If it solved your issue, perfect.

[MinhTu]

Currently I am configuring it as auto, let me switch to manual configuration of 1gb and see if it works

[MinhTu]

It's still error ""Port running LACP and LACP has disabled this port"". 

[RWelch]

LACP tends to fail when both ends are NOT configured correctly.  I am not familiar with Sysnology unfortunately.  You can always check the link below to verify/confirm the Meraki side is set accordingly.

Link Aggregation and Load Balancing 

And you can use the SEARCH box at the top of this page and type LACP to see others who might have had the same issue/conundrum. 

[MinhTu]

thanks you sir.

[alemabrahao]

I believe you marked it as resolved by mistake.

@RWelch 's statements are correct, could you share the LACP configuration for both?

[MinhTu]

Oh no I still Not find solution. You have solution acceptable?

[MinhTu]

Oh no I still Not find solution. You have solution acceptable?

[alemabrahao]

 could you share the LACP configuration for both please?

[MinhTu]

Okay, on sysnology nas rs1221rp+ ,I bond 4 port 1gb, and on switch stack ms410 port 25 26 , I LACP on 4 port . But error lacp

[alemabrahao]

Could you share the LACP configuration (Screenshot) for both please?

[MinhTu]

Siêu , i Not sit on desktop. I will send for you later

[MinhTu]

You also have case the same me?

[alemabrahao]

Maybe it will help you.

https://www.youtube.com/watch?v=GbQvp4cVVFI

[MinhTu]

Are you here , i will share with you.

[BlakeRichardson]

@MinhTu I have the same problem with a RS2212 running DSM 6.3 connected to a MS130-24, I believe the issue is with the Synology and not the MS.

I wasn't able to resolve the problem. Your model of NAS has a PCIe expansion slot so why not install one of their Mgbit NIC's or SFP NIC? 

[PhilipDAth]

@BlakeRichardson , if you are bored, it would be interesting to re-test this on MS 17.2.1.  It had LACP improvements.  Important improvements.  Of special note, to get the "fixes" you must delete any existing LACP group and re-create it (on the Meraki side).

[BlakeRichardson]

Thanks I'll give this a try. 

[MinhTu]

HI, you tried , yet?

[NicolasRen]

Hello,

We are also facing this exact issue with a Synology NAS connected to MS225-24P. When we connect a second port of configured aggregate, with LACP on NAS side, the second port is instantly in blocking state by STP... We tried to upgrade in 17.2.1, but it's definitely the same.

Support case has been opened and the first answer is that there's a configuration problem on NAS side... 🙂

[MinhTu]

T_T , t opening with Support case , i still wating..

[NicolasRen]

Hi,

Support is telling me that there's a client's side issue ... x) We tried to capture packets during the connection process, as we are good seeing lacp packets. Also, we are trying to open a Synology case to get more chance to get a working aggregate 🙂

[MinhTu]

HI Mr. NicolasRen, I will waiting from you.

[MinhTu · Accepted solution]

Hi team, I resolved issue. LACP is working good .  Everyone can try "Hello, Thank you again for your cooperation and for all the information you’ve provided. As part of our continued internal investigation, we’ve identified a broader issue that aligns closely with the symptoms observed in your case. Specifically, the behavior seems to be related to the “Enforce LACP active” setting on the switch, which can result in some ports in an aggregation group becoming blocked. The “Enforce LACP active” option was previously not exposed in the Dashboard UI but had been enabled for your network from the backend. At this point, the option is currently enabled for your aggregation group. To resolve the issue, we kindly ask you to disable the “Enforce LACP active” setting. This can now be done directly via the new UI in the Dashboard. To enable the new view, click "Try new version" located in the upper right corner of the Dashboard interface. Once enabled, navigate to one of the ports in the affected aggregation group and choose the option to edit it. You should now see the toggle for “Enforce LACP active”, which can be disabled from there. Please give this a try and let me know whether the link begins operating correctly after the change. Looking forward to your reply and once again thank you for the cooperation."

[alemabrahao]

LACP mode configuration
Mode Active:
The mode places a port into an active negotiating state, in which the port initiates negotiations with other ports by sending LACP packets.

Mode On:
All static EtherChannels, that is, the port is not running LACP messaging but static bundling. With this mode, the switch or the other end switch will not recognize any problem with the EtherChannel and will not tell about the problem.

[NicolasRen]

Thanks MinhTu ! I asked my support contact to enable the feature, disabled the option on ports and aggregate is correctly up ! 🙂

By the way, switch is showing aggregate speed at 1G... So I'm planning some tests to see if we have bandwitdth.

I'll let you know...

[PhilipDAth]

>By the way, switch is showing aggregate speed at 1G... So I'm planning some tests to see if we have bandwitdth

ps. You often get MUCH better performance on a Synology if you max out the RAM, especially if you are using BTRFS.