@CarolineS   I went through community guidelines and now I  Understand. Thanks for sharing..! ... View more

@CarolineS   I went through community guidelines and now I  Understand. Thanks for sharing..! ... View more

@CarolineS   I went through community guidelines and now I  Understand. Thanks for sharing..!   ... View more

The outcome of the STP Election Process can be a little different when utilizing Stacking Technology. Let's follow the process for Switch 2 again below, but with the following in consideration: A switch stack utilizes one logical control plane A Meraki switch stack will utilize a generated chassis MAC address (e.g. 00:18:0A:4F:XX:XX) that is unique to a Meraki Organization A Meraki switch stack will converge and deterministically elect an Active Switch on boot Switch Stack Port IDs will increment starting with the Active switch. 1.A switch port receiving superior BPDUs. Port 1 and 2 receive the same superior BPDU from Switch 1, therefore, further steps are needed to determine the root port. 3.The port with the lowest root path cost. We can see Port 1 and 2 have equal path costs, so we still have a tie. 4. The port with the lowest sender BID. Again, Port 1 and 2 have the same BID (that of Switch 1), and therefore the final step will be used to determine the root port. ... View more

The packet loss issue with your Meraki MX450s, especially after an upgrade and with high traffic, could be due to a few factors, including potential firmware bugs in 19.1.8 RC, resource limitations, or network configuration issues. It's recommended to first verify network performance and then consider downgrading to a stable release, potentially 19.1.7   https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Meraki_Firmware_Release_Process ... View more

Note: To access these Cisco U. Learning Paths (CNIOS & DCAIAA ), please log in or create a free account ... View more

This is Great..! Thanks for sharing..! @PhilipDAth  ... View more

Thanks for sharing..! @RaphaelL  ... View more

Nice..! Thanks for sharing..! ... View more

Survey is done..! Thanks for sharing..!! ... View more

couldn't see..! Thanks for sharing..! ... View more

Done..! Thanks for sharing..! @VanessaMarti  ... View more

1.Log in to your Meraki Dashboard.   2.Go to Network-wide > Clients. Use the search bar to enter the website domain (e.g., facebook.com) — this can help you identify which client accessed it. You can also filter by time to narrow down to when the access occurred.   3.Inspect Client Details Click the Client name or MAC address. Review: SSID they were connected to: Device type, IP address,Hostname, Usage and traffic details, including visited web domains   4. Use Event Logs Go to Network-wide > Event log. Filter by Client MAC or type of event (e.g., "Content filtering block" or "DNS request"). This can help validate web access history.   Thanks ... View more

This is Great..! Thanks for sharing..! @Phi-L  ... View more

Yes, in the new Cisco Meraki dashboard, you can force Meraki MS switches (like MS120, MS210, MS425, etc.) to use a specific firmware version, including older versions, using the firmware downgrade override feature—but only if you have access rights and the correct organization permissions. For more details   I suggest you to check the Meraki documentation..! ... View more

Approx. 6–10 minutes from power-on to being fully operational and connected to the Meraki Dashboard. First-time boot or after firmware upgrade: May take slightly longer due to hardware checks or firmware verification. ... View more

Welcome to the community..! @bperezgo  ... View more

Nice..! Thanks for sharing..! ... View more

Nice..! Thanks for sharing..! ... View more

You can begin with Getting Started with Meraki. Here is the link: https://documentation.meraki.com/Getting_Started_with_Meraki ... View more

Thanks for the updates..! @Mloraditch  ... View more

Nice..! Thanks for sharing..! ... View more

High latency on Meraki wireless networks can stem from various causes, including poor signal strength, interference, bandwidth saturation, misconfiguration, or external network issues. Here's a structured approach to resolve high latency issues for Meraki wireless users:   Step 1: Identify the Scope of the Problem Who is affected? All users or specific ones?   Where is it happening? All APs or specific locations?   When does it happen? All the time or during peak hours?   Step 2: Check Wireless Health in the Meraki Dashboard   Navigate to: Wireless > Wireless Health   Look for:   High latency during DHCP, DNS, or authentication phases.   High client retries, failed connections, or poor throughput.   Step 3: Investigate RF Environment Go to: Wireless > RF Spectrum   Check for:   Channel utilization (over 80% is problematic)   Interference from non-WiFi devices (especially on 2.4 GHz)   Adjust Channels/Power:   Enable or tweak Auto RF: Wireless > Radio Settings   Consider manual channel allocation for high-interference areas.   Step 4: Optimize Wireless Settings Band Steering: Enable it to push clients to 5 GHz (less congested).   Minimum Bitrate: Set it to a higher value (e.g., 12 Mbps) to prevent low-speed client connections from dragging down performance.   Client Balancing: Enable it to distribute load across nearby APs.   Step 5: Check Wired Uplink Health Uplink Latency: Go to Network-wide > Traffic analytics or run a live ping/traceroute from the AP.   Switch Port: Make sure APs are on Gigabit ports with PoE stability.   Backhaul Congestion: Check if WAN connection is saturated.   Step 6: Remove or Isolate Problematic Devices Legacy clients (e.g., 802.11b/g) can drag down performance.   Rogue APs or noisy clients? Check under Wireless > Air Marshal.   Thanks Gopinath ... View more

Nice points Contest..! Looking forward to collecting those kudos and points! ... View more

Congratulations to all  top April Month Contributors..!👏👏💐 ... View more