MS130 switches causing UDLD errors

[redsector]

I have a few MS130-8X switches and they are causing UDLD-errors at the port of the connected switch. Anybody here with the same issue? The uplink goes to an MS120 switch. The MS120 reports UDLD error on the port where the MS130 is connected.

[redsector]

It‘s a mess. How long do my clients have to wait?

[CoreyDavoll1]

That's a great question. My network refresh project is pretty much on hold until this is resolved.

[AdamB-ANZ]

I guess it hadn't resolved the issues

[CoreyDavoll1]

After a few settings changes that did not fix the issue. Support is now saying that there is a fix in the MS17 code. Waiting on details since the published beta still lists the control plane bug as a known issue

[redsector]

16.9 didn´t help a lot. Its concerning spanning-tree connections and aggregates. As a standalone switch it´s no problem.

[AdamB-ANZ]

in the change log it appears 17.1.1 may have the fix.

Ms130 known issues

• In rare circumstances MS130s may experience management plane congestion that results in UDLD alerts and STP transitions

[redsector]

not fixed. Still a known issue.

[CoreyDavoll1]

I applied the MS17 code on Thursday night. My SE said that there are some fixes in the beta but they haven't fixed all the triggers yet.

In my site that has a MS350 at the core and 2 MS130's (MS350->MS130-01->MS130-02->MS350), the firmware seems to have corrected the issue.

However, at another site that has a C9300 and 5 MS130's (C9300->MS130-01->MS130-02->MS130-03->MS130-04->MS130-05->C9300) it just made it worst so I downgraded back to 16.9

[redsector]

Yes seems to be a problem incteracting betwen Meraki origin and Cisco Catalyst origin. Maybe.

[CoreyDavoll1]

Well, my site that has a MS350 at the core and 2 MS130's that's on the beta MS17 code had the UDLD issue again. It was stable for a week. Guess I'll wait for the next release.

[redsector]

Still UDLD-errors.

the newest beta-firmware still has this issue in "rare" circumstances 😂. Here on each place where MS130 are installed on different networks and places. Everywhere!

Switch firmware versions MS 17.1.1 changelog

Ms130 known issues

• In rare circumstances MS130s may experience management plane congestion that results in UDLD alerts and STP transitions

[CoreyDavoll1]

My support tech replied back to me with "On our internal thread, our escalations team stated that they expected these issues to be resolved in the latest 17 beta firmware. The reason it's listed like this in release notes is that it's still in its verification stage as being "fixed"."

So I'll probably have it pushed and see what happens.

[chris674]

That's great to hear. Also awesome that you've had Meraki TAC at least acknowledging it's a problem on their end. My TAC guy is way less engaged and is certain it's a fiber issue on our end, which it's not. I upgraded to 16.9 at the site where I'm having these issues. What's curious is I have one switch dropping a lot (more so with 16.9) on fiber, I have another on fiber that is dropping but maybe once a week. I have another switch at that site that's a copper uplink, which is fine. All MS130R switches (their new "ruggedized" switch). Fingers crossed 17.1.1 resolves this, it's driving me nuts. Though looks like compared to other posters, one problematic switch isn't huge. Stopping a whole project for this really should open up Meraki's eyes when it comes to QA testing of their firmware.

[CoreyDavoll1]

Well they did try to blame the cables and ports before they fessed up to the issue. I'm still seeing the issue on 17.1.1 so they haven't fixed everything yet. One site that has an MS350 and MS130's seems to be better than when it was on 16.9 but not 100% yet. When I updated my 130's at another site to 17.1.1 that are connected to a C9300 with CS16.8, the issue got worse.

[AdamB-ANZ]

Well at least it has now been identified and acknowledged. This only occurs with the MS130 model for me.