Meraki

cmr

Excellent detailed report @-Rafal- I have a 9300L that stopped accepting config changes after trying to change from L2 with DHCP management to L3 with SVIs. Should like it might be similar to one of your issues.

cmr

I wish I could give you more Kudos @PhilipDAth for asking Gemini about ChatGPT, that's brilliant! 😎😂👌

cmr

You can add custom traffic, but it is only CIDRs i.e. 123.234.123.0/24

cmr

Best wishes for a smooth transition 🙏

cmr

I was actually trying to set the management IP to 'static' with it using an SVI to see if I got the same Bad IPv4 alert that I have on some 9300Xs that were upgraded from CS 17.2.3 using scenario 4a. They are working perfectly (apart from the big warning triangle) and looking at the cloud CLI they are configured correctly with the VLAN set for the management interface etc. However that VLAN in the GUI doesn't have the preferred box ticked... Perhaps another cloud to switch communication error...

cmr

I tried this today on a 9300L and it just doesn't work. The GUI looks good, the switch is all green, but the management IP stays on the old DHCP address. If I go to the cloud CLI I can see that the two SVIs don't actually get created on the switch and in fact since trying this, nothing else I change (port access VLAN, port shutdown etc.) reflects on the cloud CLI. However the ports do open and shut... Something is very wrong with the cloud to switch communication...

cmr

@alemabrahao I believe that is the CS rules. In IOS-XE the management traffic uses one of the SVIs as it's IP.

cmr

What switch models and firmware are you running? I've seen it before where the devices dropped off the client table, but still worked due to to internet usage and there could be a bug for them falling out of the arp table, but we'd need to know more to be sure.

cmr

As explained in my other post, you have to use the management VLAN for the default route out and therefore it needs to be part of the main routing design. This will change in the future, but for now it is the only option. In my case I changed the management interface to be on the transit VLAN to the firewalls and everything worked, apart from the warning alert mentioned in the other post.

cmr

I have an open case with support where a switch stack was configured to be in the recommended scenario 4a whilst running the latest cs firmware. In case you aren't familiar with the scenarios, 4a is where the management interface is using a static IP address and is on the same VLAN as the one that goes to the internet, in other words the traffic does not have to route through the device you are configuring. In my case there are about 20 SVIs on the stack as it is a core. After the upgrade, all of the network operates correctly, but there is a warning about a bad IPv4 address on the management interface. The only options are static (that is set) which just points you towards the L3 config of the stack, and DHCP which allows you to choose a VLAN. I think the answer is to change to DHCP (which it isn't really doing as there is no longer a separate management IP) as the switch does think it is using DHCP despite the configured static IP that was there before the upgrade. However support are completely confused and keep telling me to configure the management interface statically, even though I have shown them that you cannot and the documentation explains how it does not exist any more...

cmr

@albealt not at all. With native IOS-XE the Meraki management interface doesn't exist as a separate interface any more (for the moment). It uses the SVI of the VLAN that you choose it to be on.

cmr

Thank you 🎉

cmr

How can you go below zero? 😉😈

cmr

The organisation firmware summary seems to not be pulling the correct data: As when you go to schedule upgrades you see:

cmr

I'm not sure why the features are listed again at then end in other with references that look like they might be fix numbers... Also, one of the MS150 known issues says fixed - again hopefully this will be clarified.

cmr

Switches - MS software versions MS 18.1.6 changelog 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 General fixed issues Fixed an issue affecting SGT tag configuration when a corresponding policy or VLAN mapping is not present Resolved an issue that sometimes caused incorrect profile assignment when using Smartport Automations Fixed an issue that caused some clients to fail to authenticate and resolve DHCP in voice VLANs Fixed a bug that sometimes caused ports connected to 100Mbps devices on MS210, MS225 and MS250 switches to fail to pass traffic Ms130 fixed issues Resolved an issue that sometimes caused MS130 switches to fail to pass traffic until the switch was rebooted Ms150 fixed issues Resolved an issue that caused ports to fail to show their accurate connection status when a stacking cable was disconnected or reconnected Fixed a bug that sometimes caused MS150 switches to experience spikes of sdma_tx errors and lose connectivity until they were rebooted Fixed a bug that occasionally caused ports to flap, which caused clients to experience DHCP and other connectivity issues General known issues 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. MS130 and MS150 switches may not properly display IPv6 RA packets in dashboard packet captures Some switches may experience multicast packet loss when storm control is enabled Some MS130 switches may fail to provide PoE after upgrading from factory firmware to MS 18.1.6 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 Ms150 known issues 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. MS150 switches may produce a flood of unicast traffic when their uplink is using a LAG and is connected to a C9300X Resolved an issue that caused some MS150 switches in stack configurations to incorrectly flood unknown multicast traffic while the setting was disabled 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 Other New Feature Highlights • MS-21883: Group Policy ACL on MS130 & MS150 • MS-21889: Maximum MAC support in MAC Allowlists • MS-21885: 802.1x limited access mode with pre-auth GPACL • MS-28340: Local Status Page connectivity diagnostics enhancements • MS-23684: Layer 2 multicast live tool • MS-24285: Traffic Mirroring: RSPAN & VLAN Based SPAN

cmr · Re: A new candidate switch firmware is now available on Thu, 12 Mar 2026

This is listed as an MS150 known issue - but perhaps it is fixed? Resolved an issue that caused some MS150 switches in stack configurations to incorrectly flood unknown multicast traffic while the setting was disabled

cmr · Re: A new candidate switch firmware is now available on Thu, 12 Mar 2026

Switches - MS software versions MS 18.1.6 changelog 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 General fixed issues Fixed an issue affecting SGT tag configuration when a corresponding policy or VLAN mapping is not present Resolved an issue that sometimes caused incorrect profile assignment when using Smartport Automations Fixed an issue that caused some clients to fail to authenticate and resolve DHCP in voice VLANs Fixed a bug that sometimes caused ports connected to 100Mbps devices on MS210, MS225 and MS250 switches to fail to pass traffic Ms130 fixed issues Resolved an issue that sometimes caused MS130 switches to fail to pass traffic until the switch was rebooted Ms150 fixed issues Resolved an issue that caused ports to fail to show their accurate connection status when a stacking cable was disconnected or reconnected Fixed a bug that sometimes caused MS150 switches to experience spikes of sdma_tx errors and lose connectivity until they were rebooted Fixed a bug that occasionally caused ports to flap, which caused clients to experience DHCP and other connectivity issues General known issues 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. MS130 and MS150 switches may not properly display IPv6 RA packets in dashboard packet captures Some switches may experience multicast packet loss when storm control is enabled Some MS130 switches may fail to provide PoE after upgrading from factory firmware to MS 18.1.6 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 Ms150 known issues 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. MS150 switches may produce a flood of unicast traffic when their uplink is using a LAG and is connected to a C9300X Resolved an issue that caused some MS150 switches in stack configurations to incorrectly flood unknown multicast traffic while the setting was disabled 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 Other New Feature Highlights • MS-21883: Group Policy ACL on MS130 & MS150 • MS-21889: Maximum MAC support in MAC Allowlists • MS-21885: 802.1x limited access mode with pre-auth GPACL • MS-28340: Local Status Page connectivity diagnostics enhancements • MS-23684: Layer 2 multicast live tool • MS-24285: Traffic Mirroring: RSPAN & VLAN Based SPAN

cmr

cmr · Re: A new stable camera firmware is now available on Thu, 12 Mar 2026

This is the January beta release moving to stable.

cmr · Re: A new stable camera firmware is now available on Thu, 12 Mar 2026

Cameras software versions MV 7.2 changelog New Added support for Video Clips API Added support for Rapid Review 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 security and stability improvements 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

I also note that backup WAN was available on port 4, but is now available on port 3...?

cmr

From 17.15.4 or 18.x there is a built in Meraki service in the standard IOS-XE build. You simply make sure the switch has internet access and start the service. In the dashboard you choose cloud configured or device configured.

cmr

There is no container on the IOS-XE releases, all the commands are natively in the OS and you just start the Meraki service, or you don't, depending on if you want to use them with the dashboard or not.

cmr

@d0rk is there a reason not to try the GA IOS-XE releases, I run 17.18.2 on a 9300L and it has been reliable.

About cmr

cmr

Community Record

Badges