I think, that this has still not been corrected in the release notes. ... View more

I don't know and Meraki doesn't know as well (I suppose that this has not been fixed): https://community.meraki.com/t5/Switching/MS-16-7-1-Changelog-questions/m-p/223084  ... View more

A side comment from me, here: "I thought it was ok when I saw on front view the 1st switch getting Fixed White LED, but few second after it became fixed orange like all others. I waited 3 minutes and nothing change the first one did not came back to fixed white." you might have been hit by this known issue: Connecting a stacking cable to a stack that is online may result in a stack member going offline (present since MS 12) A freshly booted device, that comes up is in my opinion a stacking cable connection, and I saw this behavior more than once - in a stack with more than 2 devices, rebooting one device or a replug of stacking cable might break things. ... View more

Yes, when updating or I think when rebooting the devices to be more specific. But on a daily basis I'm not having any issues, so what you are experiencing is very weird. Have you contacted support? Can you share all settings from the ports on both sides here? Maybe there is something that you are just missing? ... View more

It's on the MS425 (my core), I don't have MS390's, I have MS225 downstream. What I mean is that I would disable all redundant links towards given downstream switches from the MS425 perspective. If I have a LACP connection to some downstream switch (or downstream stack) consisting of 2 ports, I would manually disable one of them and leave only one running (if I would have 5, I would disable 4 and leave one running). So basically, what I'm doing is killing all redundancy in my network during upgrades, just in case. And since I'm doing this only on the core switches, if something is going wrong I can easily turn the ports back on (not disabling these links on both sides). In a perfect world, lets say you have 2 core switches, both of them having connections to all downstream switches (LACP, 2 ports, each ending up in one of the cores), then it would mean that you just need to disable all ports on one of the core switches (assuming you have them stacked, the stack you leave enabled) - that's what I'm doing more/less.   If you read the release notes for the firmwares you will see that there is a lot going on around switches creating loops during reboots on LACP ports and so on. Its my way of preventing these since some firmware versions ago.   BTW, maybe this known issue is hitting you? Switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 or other Catalyst switches unless the bundles are configured on the MS390/Catalyst switches first. All non-catalyst ports are configured in passive LACP mode so that loops do not occur between Meraki switches (always present)   Sorry for the lengthy post and repeating myself, just ask if you have any doubts 🙂 And by any means - that is not what Meraki would suggest, its only my way of working around the issues that I kinda got used to during the years. ... View more

You can say this one out loud, it's been around for way too long. ... View more

From my experience, adding or removing switches to a Meraki stack never caused a reboot, which you would get with classic Cisco Catalyst switches, BUT, if you are passing the magic 2 switches in a stack, things will get weird, here is a known issue: Connecting a stacking cable to a stack that is online may result in a stack member going offline (present since MS 12)   If you connect a stacking cable in a at least 3 member stack you might notice one of the switches going offline (I would say I got that 75% of the cases, so each time I do this I assume this will happen). Most of the time, disconnecting and reconnecting a stacking cable helps, but sometimes this will fix one switch (bring it online), but break another (going offline). This is really a guessing game, so if the switches are very crucial and you can spare a max 5min downtime, then just try connecting them, if one goes offline, power cycle them all at once and you will be good.. If you are adding only a 2nd switch and creating a 2 switch stack, you can play with everything running as long as the config is alright (I know, not recommended by Cisco, but that is my experience). ... View more

It is bad, never had issues with a quick replacement (once the HW has been qualified for replacement, which is a whole different story). But the diagnostics, software part, unless its a obvious issue is bad most of the times and you feel that you are wasting a lot of time. Example: https://community.meraki.com/t5/Switching/MS-16-7-1-Changelog-questions/m-p/223038/highlight/true#M15816 ... View more

I have a very old support case where we noticed behavior that in the end turned out to be: Connecting a stacking cable to a stack that is online may result in a stack member going offline (present since MS 12. I told support in the ticket (around August 2023), that for me the issues we noticed are most likely the bug described in the changelog (citing the one above). In December 2023 I got a reply: Our software engineering team has now marked this issue as resolved as they have not been able to reproduce the issue in-house on earlier MS 16 firmware. As a next step could you please upgrade the switches to the latest stable version MS 16.7 and test whether the issue still occurs on this version?   Cool, isn't it? Maybe I should get paid to do a trip to Meraki lab and show them how you cause this - you just look at a stack of at least 3 switches, you disconnect one end, of one stacking cable (everything will be still running ok) and then you connect that one back and wait for one of the switches to go offline. Their support is very disappointing most of the times. ... View more

Thought that it would be worth to add this one here since the changelog seems to have some mistakes: https://community.meraki.com/t5/Switching/MS-16-7-1-Changelog-questions/m-p/222916  ... View more

Yeah, its confusing, also if you use that for Uplink/Downlik ports without setting them manually first (lets say a brand new switch with the standard trunk + native vlan 1 setup on all ports) - the dashboard will start complaining about vlan mismatch on trunk ports (its checking against the manual setup, not the current one affected by port profiles). I would expect them to test things way more before deploying them tbh. ... View more

Assuming you are setting up the 802.1x using GPO and certificates to authenticate. Check if you have the root certificate picked in the GPO, AFAIR this was a must have for Win11. Also check this reddit thread, as there are multiple options: https://www.reddit.com/r/sysadmin/comments/xr7kaa/8021x_authentication_broken_after_windows_11/ ... View more

They lose local logs which are crucial if you run into weird problems - whatever went into the dashboard, will stay there obviously, but its only what you see in it (not much of value).   I had a few times issues that would turn the whole network unusable and in the end I rebooted the devices and everything went back to normal (matter of ~5 minutes). When I created a case after that - 99% of the time support would say that the switches loose all logs and if I run into issues I should call support so they can grab the logs and then eventually reboot the devices (which means hanging in the support queue in extreme cases up to 20-30min.) ... View more

I noticed a few days ago that the DHCP Servers page changed to the upgraded one in my env (now it has settings for v4, v6, and also RA guard). Sounds like a very suspicious coincidence to me? Double check the settings over there (switching -> monitor -> dhcp servers & arp). Tried rebooting the MS250? Is it only one switch or a stack with L3? ... View more

I'm using these: https://gbcphotonics.com/en/qsfp-plus-40g/1443-qsfp-lx4.html   it is 40Gbit since its on my MS425-32, but never had issues with them. ... View more

this one is old 😄 ... View more

Totally get you with the MESH network, but the author never mentioned using a Meraki Mesh in the first place. Wireless bridge is what he said but I see that the whole discussion went into the Mesh direction, which I also hardly doubt that it would work. A classic wireless bridge would be one of the ways to go in my opinion. ... View more

I don't see why this wouldn't work, it doesn't matter if you use fiber, LAN or radio, its the (R)STP protocol that finds loops in the network and disables redundant paths. If you set up a wireless link that will pass through all L2 traffic and disable any STP on them, then all STP packets will go via the links, they will act as cables. So the switches will "think" that they are connected directly and will suspend one of the 4 ports that take part in the communication and if one of the connections break, the other one will take over. ... View more

No worries! I hoped you just know something more than in then notes, too bad 😅 ... View more

@cmr do you know anything in particular about the "stacking, LACP fixes"? I can only see fixes being mentioned for the "DHCP relay and cable test" in the changelog, everything else is known issues... ... View more

Sorry, I somehow missed the part where you wrote about the fiber type above. Then I suppose there is something in the SFPs or the fiber, that it can't negotiate higher speeds. Without proper tests it will be hard to tell. You could switch around patch cables, SFP ports and modules if you have an option to check different paths. You have any option to test the SFP on a smaller distance in the cabinet? I sometimes even create loops from one SFP port to the other with a short patch cable, for a second, just to see if things work, if they negotiate proper speeds, so I know that both SFPs and patch cables have no obvious problems... ... View more

You need to find out what type of fiber is used and if its OK, the distance you said max 150m. If its an old infrastructure then this might be explaining the issues (like OM2). https://documentation.meraki.com/General_Administration/Cross-Platform_Content/SFP_and_Stacking_Accessories?file ... View more

How does the port config look like on both sides? I understand you don't get an uplink LED on these ports? What is the distance, what are the SFP models? ... View more

Because its a fairly new thing. Old networks will have the "Sample all interfaces" option chosen, only new networks will have the default option picked 🙂 ... View more

Exactly, @KarstenI here you have everything explained: https://documentation.meraki.com/MS/Monitoring_and_Reporting/MS_Client_Sampling_on_Uplink_Configuration the new, default setting is way better, no client jumping between interfaces. ... View more