Meraki

RaphaelL · ‎Oct 29 2025

This was teased a long time ago , but never released. This might be coming with the "new" "Security" tab from the dashboard.

RaphaelL · ‎Oct 28 2025

Real diff between MS 18.1.3 and MS 18.1.3.1 Fixed : Ms150 fixed issues Resolved an issue that caused some wireless clients to lose connectivity when roaming between access points connected to different members of the same switch stack Added : Ms150 known issues Some SFP and QSFP modules may experience intermittent flapping on MS150 switches running MS18 firmware MS150 switches in stack configurations may lose connectivity while reporting redundant uplinks as blocked. As a workaround, connectivity can be reestablished by disconnecting the impacted redundant uplink. MS150 switches in stack configurations may incorrectly flood unknown multicast traffic despite the flood unknown multicast setting being disabled 48 port MS150 switches connected to an MX gateway may experience a reduction in uplink throughput if the uplink is on ports 45, 46, 47, or 48. As a workaround, connecting to the MX using ports outside of the 45-48 range will pass traffic at expected speeds. Tbh I wouldn't use MS 18 at this point.

RaphaelL · ‎Oct 28 2025

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 a bug that sometimes caused switches in stack configurations to fail to remove older entries from the MAC forwarding table Ms150 fixed issues Resolved an issue that caused some wireless clients to lose connectivity when roaming between access points connected to different members of the same switch stack Fixed a bug that sometimes caused MS150s to experience transmission errors and lose connectivity until they were rebooted Ms425 fixed issues Resolved an issue that caused clients authenticating via 802.1X with an access policy using hybrid authentication to not correctly log their RADIUS sessions Fixed an issue that caused some switches in stack configurations to experience high CPU utilization in multicast scenarios that sometimes resulted in network instability General known issues MS130 and MS150 switches may not properly display IPv6 RA packets in dashboard packet captures MS130 and MS150 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. 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. Some switches may encounter an error, "incompatible configuration for attributes: allowed_vlans" when attempting to aggregate ports regardless of allowed VLANs configured in Dashboard Ms120 known issues Switches may fail to provide PoE power to legacy access points (always present) Cable tests may report incorrect cable lengths Ms150 known issues Some SFP and QSFP modules may experience intermittent flapping on MS150 switches running MS18 firmware MS150 switches in stack configurations may lose connectivity while reporting redundant uplinks as blocked. As a workaround, connectivity can be reestablished by disconnecting the impacted redundant uplink. MS150 switches in stack configurations may incorrectly flood unknown multicast traffic despite the flood unknown multicast setting being disabled 48 port MS150 switches connected to an MX gateway may experience a reduction in uplink throughput if the uplink is on ports 45, 46, 47, or 48. As a workaround, connecting to the MX using ports outside of the 45-48 range will pass traffic at expected speeds. Ms225 known issues MS225 switches may infrequently stop forwarding client traffic until the switch is rebooted 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

RaphaelL · ‎Oct 28 2025

Troubleshooting MTU Issues Change: Added "If a peer has a reduced MTU, the AutoVPN MTU will automatically propagate across the AutoVPN environment and adjust to match the lowest detected value among all peers. Some examples of possible reasons for a reduced MTU include: Primary cellular uplink, PPPoE connection, ISP-assigned DHCP MTU." This is partially true. I can't test without the NFO that disables Hub-To-Hub meshing. Other parts of that documentation are also partially true from my tests done in the past year. 69 bytes overhead I haven't seen that and I don't understand how it is possible. In reality it is 68 bytes.

RaphaelL · ‎Oct 27 2025

Yes the document is missing the crucial part about firmware versions. If the version is older than 16.16 it WON'T upgrade to the most recent. You have to follow some upgrade steps that are not disclosed anywhere.

RaphaelL · ‎Oct 27 2025

I feel like we influenced the creation of this document : https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Bringing_MX_and_Zs_Online_That_Have_Been_in_Storage_for_a_Long_Time Which lacks a lot of information about the firmware versions.

RaphaelL · ‎Oct 27 2025

Same behavior from the Alert Hub. I have a case opened for like 6 months. An intern could solve that issue in 15 minutes.

RaphaelL · ‎Oct 27 2025

This feature is now in Early Access :https://documentation.meraki.com/General_Administration/Organizations_and_Networks/Energy_Management_Dashboard Why is this the only feature of the dashboard that uses the browser language instead of my dashboard settings ? This is a bit annoying

RaphaelL · ‎Oct 22 2025

Do you have AI-RRM enabled ? Also MR 32.1.4 is beta. I would run MR 31.1.8 instead.

RaphaelL · ‎Oct 21 2025

I hate that but the changelog are quite different : 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. LSP speed test deprecated New feature The Per SSID toggle for 802.11be (Wi-Fi 7) feature allows WiFi 7 access points to operate some SSIDs in 802.11ax mode while others operate in 802.11be mode. This is also called "ax/be mixed mode", "per-SSID 11be." Bug fixes General stability, performance, and experience improvements APs intermittently stop sending beacons & responding to clients on 5GHz (Wi-Fi 6e) APs not responding to probe/auth requests from clients on 2.4 & 5GHz (Wi-Fi 6, 6e) Multi/Broadcast packets (RA/DHCP) not forwarded by APs (Wi-Fi 7) Mesh not forming 6GHz 160MHz (Wi-Fi 6e)

RaphaelL · ‎Oct 20 2025

@Oren Sorry to tag you , but this seems like something you would be able to answer 😊

RaphaelL · ‎Oct 17 2025

side note , but this is such a horrible bandaid imo... ( not refering to your code , but the official sdk ) if direction == "next" and "next" in links: # Prevent getNetworkEvents from infinite loop as time goes forward if metadata["operation"] == "getNetworkEvents": starting_after = urllib.parse.unquote( str(links["next"]["url"]).split("startingAfter=")[1] ) delta = datetime.now(timezone.utc) - datetime.fromisoformat( starting_after ) # Break out of loop if startingAfter returned from next link is within 5 minutes of current time if delta.total_seconds() < 300: break # Or if the next page is past the specified window's end time elif event_log_end_time and starting_after > event_log_end_time: break metadata["page"] += 1 nextlink = links["next"]["url"] elif direction == "prev" and "prev" in links: # Prevent getNetworkEvents from infinite loop as time goes backward (to epoch 0) if metadata["operation"] == "getNetworkEvents": ending_before = urllib.parse.unquote( str(links["prev"]["url"]).split("endingBefore=")[1] ) # Break out of loop if endingBefore returned from prev link is before 2014 if ending_before < "2014-01-01": break metadata["page"] += 1 nextlink = links["prev"]["url"] else: break

RaphaelL · ‎Oct 17 2025

Does the network contains a MX ?

RaphaelL · ‎Oct 17 2025

Hi , I just tried it and it still returns : https://api.meraki.com/api/v1/networks/L_XXXXXXXXXXXXX/events/eventTypes { "category": "Filtering", "type": "cf_block", "description": "Content filtering blocked URL" } https://api.meraki.com/api/v1/networks/L_XXXXXXXXX/events?productType=appliance&includedEventTypes[]=cf_block {"message":"No matching events found between Sep 17 11:15 and Oct 17 11:15.","pageStartAt":"2025-09-17T15:15:06.417862Z","pageEndAt":"2025-10-17T15:15:06.417862Z","events":[]}

RaphaelL · ‎Oct 16 2025

As mentionned by Ryan in this thread : Yeah banners seem to not be enabled yet

RaphaelL · ‎Oct 16 2025

Both ww and Mloraditch are right. Side note , you "can" put the same VLAN ID for both access and voice vlan but it is not recommended and you will end up with issues. Don't do that. I have seen some phones that do not use the voice vlan at all and stops working when a voice vlan is configured. I don't remember the SKUs to be honest, I will have to look at my notes.

RaphaelL · ‎Oct 16 2025

Is he probably refering to the new feature in the Inventory. I don't have vMX to confirm if the EOS/EOL dates are present for these SKUs

RaphaelL · ‎Oct 16 2025

Correct. I do see both EOS EOL dates on my orgs with EA 2.0 licences

RaphaelL · ‎Oct 16 2025

What licence mode are you using ?

RaphaelL · ‎Oct 16 2025

From Support earlier this week : Thank you for your time on the call today. I would like to inform you that an internal case has been opened with our backend team. Their investigation has confirmed that not all firmware versions are impacted by this issue. Please find the details below: Impacted Releases (cloud-managed switches): All available Cloud Native IOS XE 17.15 releases: 17.15.1, 17.15.2, 17.15.3, 17.15.3.1, 17.15.4 Not Impacted: CS17 or earlier CS releases MS releases Cloud Native IOS XE 17.18.1 Based on the above, your switch network is currently running MS firmware 17.1.4, and therefore is not impacted by this issue.

RaphaelL · ‎Oct 13 2025

Real diff between MS 18.1.3 and MS 18.1.2 : 4 fixes : General fixed issues Fixed a bug that sometimes caused switches in stack configurations to fail to remove older entries from the MAC forwarding table Ms150 fixed issues Fixed a bug that sometimes caused MS150s to experience transmission errors and lose connectivity until they were rebooted Ms425 fixed issues Resolved an issue that caused clients authenticating via 802.1X with an access policy using hybrid authentication to not correctly log their RADIUS sessions Fixed an issue that caused some switches in stack configurations to experience high CPU utilization in multicast scenarios that sometimes resulted in network instability 2 new issues : MS130 and MS150 switches may not properly display IPv6 RA packets in dashboard packet captures Ms150 known issues Wireless clients may lose connectivity when roaming between access points connected to different members of the same switch stack 1 removed ( with no listed fix ) : LACP links may take an extended time to come back up when the Active Member of a stack reboots

RaphaelL · ‎Oct 13 2025

MX26 didn't expect that. I would love to know why the jump from 20 -> 26

RaphaelL · ‎Oct 10 2025

This ^ I have around 400 users. Most of them are 100% clueless about networking. They only want to see the status of the switch ports , view the usage and so on. I don't want them to do packet captures, port cycles. Hell no.

RaphaelL · ‎Oct 10 2025

Confirmed by support this is not a bug. The doc as mentionned will be modified. I have been advised by our development team the feature of packet capture is available in switch port page for Read-only user as by desgin in a new dashboard UI version. Our KB Packet Capture Overview will be updated accordingly.

RaphaelL · ‎Oct 10 2025

I haven't tested all the ways to do it but this is one of them : Might also be accessible with the new UI from Intelligent packet capture

About RaphaelL

RaphaelL

Raphael Letourneau

Community Record

Badges