Meraki

cmr · ‎Nov 15 2024

17.1.4 is the new stable firmware and I think the change should fix your issue.

cmr · ‎Nov 15 2024

CS firmware versions CS 17.1.4 changelog Important notes Factory-default VLAN range is now 1-995, instead of 1-1000 as in previous firmware versions. Resetting the device to factory settings will apply this new VLAN range. This version's IOS image is based on 17.12.3 CCO. Upgrades to this version will result in a full system reload. New feature highlights Client Analytics Device Uptime for MS390s EEE (Energy Efficient Ethernet) Support Multi-auth with support for guest/failed/critical RADIUS Caching Support for Multicast in Live Tool VLAN to SGT mapping Fixed issues Corrected a bug that prevented clients that only send UDP traffic from appearing in the client list Fixed a bug that caused some switch stacks to experience a configuration mismatch when making multiple consecutive port configuration changes Fixed an issue that caused some clients to experience packet loss for 60-200 seconds while a standby switch took over the active stack member role Resolved an issue that occasionally caused a loss of management plane connectivity when there were a large number of LLDP announcements Resolved an issue that prevented TCN packets from being correctly reported in Switch Port Packet Counters General known issues Meraki native switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 or other Catalyst switch unless the bundles are configured on the Catalyst side first. All Meraki native ports are configured in passive LACP mode so that loops do not occur between Meraki native switches (always present)

cmr · ‎Nov 15 2024

CS firmware versions CS 17.1.4 changelog Important notes Factory-default VLAN range is now 1-995, instead of 1-1000 as in previous firmware versions. Resetting the device to factory settings will apply this new VLAN range. This version's IOS image is based on 17.12.3 CCO. Upgrades to this version will result in a full system reload. New feature highlights Client Analytics Device Uptime for MS390s EEE (Energy Efficient Ethernet) Support Multi-auth with support for guest/failed/critical RADIUS Caching Support for Multicast in Live Tool VLAN to SGT mapping Fixed issues Corrected a bug that prevented clients that only send UDP traffic from appearing in the client list Fixed a bug that caused some switch stacks to experience a configuration mismatch when making multiple consecutive port configuration changes Fixed an issue that caused some clients to experience packet loss for 60-200 seconds while a standby switch took over the active stack member role Resolved an issue that occasionally caused a loss of management plane connectivity when there were a large number of LLDP announcements Resolved an issue that prevented TCN packets from being correctly reported in Switch Port Packet Counters General known issues Meraki native switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 or other Catalyst switch unless the bundles are configured on the Catalyst side first. All Meraki native ports are configured in passive LACP mode so that loops do not occur between Meraki native switches (always present)

cmr · ‎Nov 15 2024

Did you try transfers to the other spoke directly (set the temp MX64 up as a hub, or have them fully meshed) as well?

cmr · ‎Nov 14 2024

I'm guessing that you don't have a spare MX that you could try at another spoke site (even a home broadband connection would do for testing)? If not, could Cisco lend you one, this might well be an option, or if you got another MX68 it could then become a warm spare at the spoke once testing has been completed.

cmr · ‎Nov 14 2024

Have you tried replacing the patch lead between the MX68 and the MS120?

cmr · ‎Nov 14 2024

What about the spoke, or are they all having the same issue?

cmr · ‎Nov 14 2024

Adding to what @KarstenI said, if the syslog server is offline then the message will most likely be lost.

cmr · ‎Nov 14 2024

🎉🎉 Welcome back @PhilipDAth 🎉🎉 The new Cisco Meraki cloud managed ultra wide monitor* *Only available with annual subscription...🤔

cmr · ‎Nov 14 2024

I'd does seem mad that IOS-XE still doesn't have some intelligence here.

cmr · ‎Nov 13 2024

Doesn't everyone count in base 9?

cmr · ‎Nov 13 2024

It is announced here: Wireless Update: Magnetized AP Summary Roll Out! - The Meraki Community My initial thoughts are: Font too big on current clients, I now need to scroll left to right One of my SSIDs appears as 0 instead of the name for all clients AP historical health has gone to be replaced with mesh stats when no meshing on this network Graphic for ports looks just odd! Back to the old for now!

cmr · ‎Nov 13 2024

Go on, live a little (and maybe die a lot), you only live once! I've been running in on a test C9300L for a couple of weeks and it does seem generally stable.

cmr · ‎Nov 13 2024

Interesting, I've used it for sites issuing a few hundred concurrent IPs, but I can see if there are thousands of clients that it might not be a good idea.

cmr · ‎Nov 13 2024

Welcome @JonColes, glad to have you here, what Meraki devices do you generally use these days?

cmr · ‎Nov 13 2024

If you set the same static settings on a PC connected to the internet link, does it work and can it reach the Meraki cloud?

cmr · ‎Nov 13 2024

On another note, have you enjoyed the shorter boot/reboot times, at least 2 minutes quicker for either by my measurement 😎 Or are you on CS firmware?

cmr · ‎Nov 13 2024

@GIdenJoe whilst I agree that the path you had to follow seems far from sensible, I would not want the default to be that you had to have to provision VLANs on each Meraki switch. Part of the allure of Meraki is that a lot of it just works and I think although that would be easy for the likes of you and me, it wouldn't be great for the generalists that perform a lot of Meraki management. I do think however it could be an organisation/network wide setting that could be toggled in the same way that inbound L3 rules and others are enabled/disabled. The feature could be called "Switch VLAN auto creation" and be able to be disabled.

cmr · ‎Nov 13 2024

Any curly haired data engineers 😉

cmr · ‎Nov 13 2024

@GIdenJoe I've had a case open for a week or so now about the second issue, for me it seems to only occur when there is a C9300L in the network, with the MS220s, MX75 and MRs/CWs it works fine. What switches do you have in the network(s) that have this issue?

cmr · ‎Nov 12 2024

@frosten5117 indeed, I do wish it said excluded rather than reserved, it is very confusing.

cmr · ‎Nov 12 2024

If they have all those devices, the modem won't be in bridge mode, it'll be in routed mode, but (non Spectrum specific) that shouldn't be a problem.

cmr · ‎Nov 12 2024

If you are going through the firewall, why don't you use that as the DHCP server?

cmr · ‎Nov 12 2024

MT14 and MT15 can detect excessive noise, I have installed these in server rooms. They can also detect small particles when powered by a USB-C adapter, so might cover the smoke requirement, but they are not fire certified.

cmr · ‎Nov 12 2024

Welcome @ChrisHead, if you are looking for any assistance, feel free to ask here, we have a good team of experts from all fields! What Meraki devices have you been using and what are you looking at getting?

About cmr

cmr

Community Record

Badges