Meraki

cmr

Sounds lovely - GUI only does X, CLI only does Y...

cmr

@RWelch this is the discussion I was about to link your question to...

cmr

I have only used them in C9300s (where they work fine), I have some MS130s I could try the 1Gb ones with, but I think you already have the 10Gb ones working in MS225s, so that wouldn't prove anything. Either way as mentioned above they aren't supported in MS switches for some reason...

cmr · Re: A new candidate wireless firmware is now available on Tue, 27 Jan 2026

Wireless firmware versions MR 32.1.6 changelog Important note MR45/55 APs are not supported on MR 32.x.x and will instead upgrade to the backup version (MR 31.1.8) if they are in networks configured for MR 32.x.x versions, and thus, new features will not be available. Enhancement Enable class 2 PoE (7W) output when AP is supplied with PoE+ (802.3at) power budget for CW9172H (https://documentation.meraki.com/Wireless/Product_Information/Overviews_and_Datasheets/CW9172H_Datasheet) Bug fixes General stability, performance, and experience improvements APs not using configured SGT tag (Wi-Fi 6, 6e, Wi-Fi 7) RADSec authentication stuck (Wi-Fi 6, 6e, Wi-Fi 7) Wi-Fi calling not working (Wi-Fi 6, 6e, Wi-Fi 7) WebEx DeskPro connectivity issues (Wi-Fi 6, 6e, Wi-Fi 7) APs previously on 1 Gbps suddenly negotiating at 100mbps after a few hours (Wi-Fi 6, 6e)

cmr

Yes all APs can use the co-term license and all use the same license, so you can swap existing ones to the new devices.

cmr

I feared as much, I have a lot of device configured 9300s on 17.15.4 and thought perhaps I'd missed an in place upgrade somehow. Hopefully it's coming soon!

cmr

Where you are migrating from device configured to cloud configured, does it now allow you to keep the configuration, or are you reconfiguring them?

cmr

Use Cloudflare Zero Trust. It reliably breaks AnyDesk regardless of configuration 😉

cmr

Congratulations all, I can't emphasise how friendly and helpful this Cisco Meraki community is, very refreshing!

cmr

I have it on a 9300L but again, only limited features. It does have a port channel though 🎉

cmr

Switch firmware versions MS 18.1.5.1 changelog Important notes This firmware release only includes updates for MS150 switches. All other MS switches on MS 18.1.5.1 will run firmware identical to MS 18.1.3.1. New feature highlights Group Policy ACL on MS130 & MS150 Maximum MAC support in MAC Allowlists 802.1x limited access mode with pre-auth GPACL Local Status Page connectivity diagnostics enhancements Layer 2 multicast live tool Traffic Mirroring: RSPAN & VLAN Based SPAN Fixed issues Ms150 fixed issues Resolved an issue that resulted in some MS150 switches setting a port into a discarding state after a stack member reboot Fixed a bug that caused some clients to experience reduced upload speeds while connected to an MS150 switch that was connected to an MX68 gateway Fixed a bug that sometimes caused MS150 switches in stack configurations to experience unicast traffic floods Resolved an issue that sometimes caused MS150 switches in stack configurations to fail to learn the default gateway’s correct MAC address, which resulted in packet loss for clients on those VLANs Known issues General known issues MS130 and MS150 switches may not properly display IPv6 RA packets in dashboard packet captures In rare circumstances switches may experience uplink instability when IPv6 link-local addresses are enabled. If this issue is encountered it can be resolved by enabling IPv6 RA Guard to block ICMPv6 neighbor discovery messages. MR access points may be incorrectly assigned to the Default profile instead of the preconfigured Access Point profile when initially connected to a switch port that uses Smartport Automation Some clients may fail to authenticate and resolve DHCP in voice VLANs Ms120 known issues Switches may fail to provide PoE power to legacy access points (always present) Cable tests may report incorrect cable lengths Ms130 known issues MS130X mGig ports may fail to establish a link when both sides are forced to 100 Mbps full-duplex. If either side of the connection uses auto-negotiation the link will be established normally Switches may incorrectly remove or update SGT tags when no policy or VLAN mapping is defined. Until a firmware fix is available, correct SGT tags can be preserved by defining a policy for the SGT group in Adaptive Policies, and binding the SGT group to a VLAN using VLAN profiles. Ms150 known issues When a stacking cable is disconnected from MS150 switches in stack configurations the disconnected port will incorrectly continue to be marked as connected while the still-connected stacking port will incorrectly be marked as disconnected MS150 switches may intermittently negotiate USB-C Ethernet adapters at 10 Mbps half-duplex instead of the expected speed for the switchport, requiring a physical reseat to correct the issue. In some circumstances MS150 switches in stack configurations may fail to blocking redundant links, resulting in looped packets Ms350x known issues Switches may experience an unexpected reboot (present since MS 15) Ms355 known issues Switches in stack configuration may experience some ports failing to reconnect after a firmware upgrade Ms410 known issues Some MS410 switches may encounter alerts for fan failures that will eventually self-resolve Ms425 known issues In rare circumstances MS425 switches may encounter a software crash that results in a reboot In rare circumstances MS425 switches in stack configurations may encounter a software crash that results in a reboot

cmr · Re: A new candidate switch firmware is now available on Mon, 26 Jan 2026

Switch firmware versions MS 18.1.5.1 changelog Important notes This firmware release only includes updates for MS150 switches. All other MS switches on MS 18.1.5.1 will run firmware identical to MS 18.1.3.1. New feature highlights Group Policy ACL on MS130 & MS150 Maximum MAC support in MAC Allowlists 802.1x limited access mode with pre-auth GPACL Local Status Page connectivity diagnostics enhancements Layer 2 multicast live tool Traffic Mirroring: RSPAN & VLAN Based SPAN Fixed issues Ms150 fixed issues Resolved an issue that resulted in some MS150 switches setting a port into a discarding state after a stack member reboot Fixed a bug that caused some clients to experience reduced upload speeds while connected to an MS150 switch that was connected to an MX68 gateway Fixed a bug that sometimes caused MS150 switches in stack configurations to experience unicast traffic floods Resolved an issue that sometimes caused MS150 switches in stack configurations to fail to learn the default gateway’s correct MAC address, which resulted in packet loss for clients on those VLANs Known issues General known issues MS130 and MS150 switches may not properly display IPv6 RA packets in dashboard packet captures In rare circumstances switches may experience uplink instability when IPv6 link-local addresses are enabled. If this issue is encountered it can be resolved by enabling IPv6 RA Guard to block ICMPv6 neighbor discovery messages. MR access points may be incorrectly assigned to the Default profile instead of the preconfigured Access Point profile when initially connected to a switch port that uses Smartport Automation Some clients may fail to authenticate and resolve DHCP in voice VLANs Ms120 known issues Switches may fail to provide PoE power to legacy access points (always present) Cable tests may report incorrect cable lengths Ms130 known issues MS130X mGig ports may fail to establish a link when both sides are forced to 100 Mbps full-duplex. If either side of the connection uses auto-negotiation the link will be established normally Switches may incorrectly remove or update SGT tags when no policy or VLAN mapping is defined. Until a firmware fix is available, correct SGT tags can be preserved by defining a policy for the SGT group in Adaptive Policies, and binding the SGT group to a VLAN using VLAN profiles. Ms150 known issues When a stacking cable is disconnected from MS150 switches in stack configurations the disconnected port will incorrectly continue to be marked as connected while the still-connected stacking port will incorrectly be marked as disconnected MS150 switches may intermittently negotiate USB-C Ethernet adapters at 10 Mbps half-duplex instead of the expected speed for the switchport, requiring a physical reseat to correct the issue. In some circumstances MS150 switches in stack configurations may fail to blocking redundant links, resulting in looped packets Ms350x known issues Switches may experience an unexpected reboot (present since MS 15) Ms355 known issues Switches in stack configuration may experience some ports failing to reconnect after a firmware upgrade Ms410 known issues Some MS410 switches may encounter alerts for fan failures that will eventually self-resolve Ms425 known issues In rare circumstances MS425 switches may encounter a software crash that results in a reboot In rare circumstances MS425 switches in stack configurations may encounter a software crash that results in a reboot

cmr

The part about half way down about replacements is I think what you need: Replace existing APs AP Zero Touch Deployment relies on the CDP / LLDP information to automatically map a new AP to an existing AP that it is replacing. Because of this, ensure that new AP is connected to the same switch and switch port as the existing AP it is replacing. If the CDP / LLDP information matches between APs, the new AP will automatically have its settings pre-populated during the workflow.

cmr

@Snika there is a new AP zero touch feature that you might want to use. It has to be enabled under Organisation / Early Access. The documentation is here: AP Zero Touch Deployment - Cisco Meraki Documentation

cmr

Thank you @AmyReyes and a special congratulations to our new recruit @JamesT91.. Well done everyone 🎊

cmr

Thank you @spaladug, any chance the first posted bug can be looked at?

cmr

I saw that earlier and thought it must just be some premium white space at the top of the page, I forgot it was supposed to have real value!

cmr

Yes it does, no choice of anything else!

cmr

I have used unique client identifier most of the time recently and found it to work okay.

cmr

It can be changed, the box appears behind the current item in the GUI so you cannot see it. Click on the pencil next to the Ip to open the box that shows DHCP in the first row and the VLAN in the second row (if the current IP is DHCP). This will change the twistie from pointing down to pointing up. Then press the down arrow on the keyboard twice, followed by the return key. You will now see that the top box says static and the fields you need all appear.

cmr

Camera firmware versions MV 7.2 changelog Bug fixes Resolved an issue on MV84 series cameras where a short recording disruption could occur immediately after a firmware upgrade Resolved an issue where privacy windows might not appear on the video stream when using Standard video quality settings on MV84X General Improvements to video recording stability on MV84X Improvements to Image Quality for MV84X Notice When configured for this version, MV21 & MV71 cameras will run MV4.15 MV7.2 is the last supported firmware branch for MV12, MV2, MV22, MV32, MV52 and MV72 series. Future updates for these models will be limited to maintenance and security patches

cmr · Re: A new beta camera firmware is now available on Tue, 13 Jan 2026

Camera firmware versions MV 7.2 changelog Bug fixes Resolved an issue on MV84 series cameras where a short recording disruption could occur immediately after a firmware upgrade Resolved an issue where privacy windows might not appear on the video stream when using Standard video quality settings on MV84X General Improvements to video recording stability on MV84X Improvements to Image Quality for MV84X Notice When configured for this version, MV21 & MV71 cameras will run MV4.15 MV7.2 is the last supported firmware branch for MV12, MV2, MV22, MV32, MV52 and MV72 series. Future updates for these models will be limited to maintenance and security patches

cmr

My goal in 2026 is to simplify the networks I manage, all too often we use features because they are there and not because they give us the secure reliable networks that we need! I aim to use the relatively new automation tools to help with maintaining this once it is properly set up.

cmr

You should be okay with that model and those users, but I do see your utilisation going quite high. I do believe that you can get support to monitor the real time load in the morning peak as that may be somewhat higher than the averages shown on the dashboard.

cmr

To me it sounds like the MX could be getting overloaded. What model is it and how many users do you have? So they authenticate on premises or to the cloud / over the WAN?

About cmr

cmr

Community Record

Badges