MS 425 ISSUES WITH CROSS-STACK LACP

InfraTI-Meraki
Conversationalist

MS 425 ISSUES WITH CROSS-STACK LACP

I have a scenario where, at the access layer, we have 25 MS 125 switches; each switch is connected with two fibers, one to each switch in the SW-CORE stack, forming a Port-channel with 20G speed.

Screenshot_82.png

The SW-CORE stack is composed of two MS425-32 switches running MS version 16.8.

The problem is that when any switch in the stack is powered off, whether it's the active switch or a member switch, it seems transparent to the endpoints (tested with ICMP, pinging another machine on the same VLAN but on different access switches, i.e., traffic passes through the SW-CORE stack). However, when we power on any of these switches, whether it's the active or member switch, it causes a downtime of about 5 minutes (this downtime only occurs when the switch that was turned off is powered on again, whether it's the active or member switch).


I have opened a case with Meraki, but it hasn't been helpful. We escalated the case, and the engineer mentioned that Meraki does not support Stateful Switch Over (SSO) like the Catalyst switches and that there would indeed be downtime when a switch is powered back on.

In my research, I found two bugs that have been fixed:

Cross-stack LACP bundles experiencing a switch reboot will cause the remaining online port to experience an outage of up to 30 seconds. The same is seen again when the switch comes back online (present since MS 10), fixed in 16.1.

A stack containing more than 10 LACP bundles may encounter a brief network loop when a stack member is rebooted (present since MS 15), fixed in 16.8.

My switch infrastructure is composed of two MS425-32 switches in the CORE layer stack and 25 MS125 access switches, all running MS version 16.8.


Has anyone faced a similar issue?

5 Replies 5
cmr
Kind of a big deal
Kind of a big deal

Have you set the MS425s to have the lowest Bridge Priority under the STP configuration on the Switch/Settings page?  i.e. Cabin as below: 

 

cmr_0-1729070380952.png

 

If my answer solves your problem please click Accept as Solution so others can benefit from it.
InfraTI-Meraki
Conversationalist

Yes, the STP root has already been defined, and all the switches recognize it as the root.

PhilipDAth
Kind of a big deal
Kind of a big deal

I assume you are using flexible stacking between the MS425s?

https://documentation.meraki.com/MS/Stacking/Switch_Stacks#Understanding_Flexible_Stacking

 

I would also try upgrading to 16.9, as this is the current stable firmware release.

InfraTI-Meraki
Conversationalist

I am currently using two 40GB ports on each MS425 switch to form the stack.

Yellow_Tang
Here to help

Oh man,.. I've been fighting with LACP since 15.21.1.  Tell me, when your LACP links seem to be working properly, do you randomly have STP take them down?  Also, do you have intermittent traffic issues, some devices seem inaccessible from one device but not another on the same switch, then suddenly the issue resolves itself?

 

My upgrade today to 16.9 seems to have made LACP worse than 15.21.1 because it used to feel like just Cross Stack LACP was an issue, now LACP between two single switches is also giving me fits.  I've disabled one link in the LACP group for all of our 66 switches for now until I can figure this out.  With the link disabled everything is working perfecty.

 

James

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels