Meraki

RaphaelL · ‎Jul 13 2022

Should be an easy fix ! Syslog shows : dport=51514 but the rule states 51414...

Sandra_Linares · ‎Jul 12 2022

Hello, The message no longer appears in my organization's dashboard. I guess it was a bug in the Meraki platform. Thank you very much everyone for your answers. All the best

GIdenJoe · ‎Jul 5 2022

Oh, I didn't know you could get that enabled on a single link. The answer I got once on the phone was that it was not doing that for single links.

sungod · ‎Jul 3 2022

Perfect! Thanks

Ryan_Miles · ‎Jun 26 2022

Details on containment here

PhilipDAth · ‎Jun 25 2022

Ask support to enable the "Enhanced Failover" option. Then configure the MX for "immediate" failback and your SIP issue will be resolved. https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Connection_Monitoring_for_WAN_Failover#Enhanced_WAN_Failover_and_Failback > Why would you want the flow to remain on the secondary WAN (in a non-load-balanced network), after switching back to primary So that it does not break anything using TCP. For example, we use MS Teams for our phone system (which is TCP based). By not doing an immediate failback, anyone on a phone or video call can continue to complete that call without any interruption.

PoprCoDa6819 · ‎Jun 23 2022

Ok, I'll try that then. Thank you for that information Ryan, and have a great weekend!

bkrautner · ‎Jun 20 2022

Hi, You can find here: Just toggle the two slider buttons off and refresh page.

rsage_voda · ‎Jun 17 2022

Upgraded my MG21 from 1.9 to 1.11 dashboard says everything is OK but the status LED continues flashing white 15 minutes after the upgrade. I would have expected it to go solid purple. Is that your experience

Ryan_Miles · ‎Jun 8 2022

The last part of the doc is actually incorrect. You don't need to unbind anything to add a MG into a bound network. Steps to get it done are this. I also created a video walking through it. 1. Ensure your template supports the MG device type which is outlined in this section of the doc. More recently created combined templates should already have MG, MV, MT device groups in them. 2. Create new MG network 3. Bind that MG network to your template (requires step 1 to be completed) 4. Optional, combine the previous MX, MS, MR network with the new MG network into one bound combined network

Trininox · ‎Jun 8 2022

One caveat I discovered, this feature is only available when the MX67C is not bound to a template, otherwise, the option never appears to use the cellular actively. That's somewhat disappointing as it eliminates the ease of managing changes to a good number of sites in my environment having to manage them independently.

PhilipDAth · ‎Jun 7 2022

If you have an AP that has gone EOS (end of support) and the unit dies - you DO NOT get a replacement device. The support has ended.

Larry_Woods · ‎Jun 7 2022

@KRobert... I have actually been trying to test this scenario for the last 18 months or so and it has been pretty consistant. I have had a MT12 with the cable ran into my shower so that I can show when it detects water but if you notice it does take some time to NO LONGER detect water by the examples below... Theoretically for you, this could work but it will not be immediate as I have seen upwards of 4-5 hours after turning the shower off before the sensor no longer detects. But as @Ryan_Miles is accurate as the MT12 is primarily for the use case to detect water... not the absence of it. I have also tried this in the back of my toilet tank (THE BACK PART) to see if it could be useful to show that after a flush it could show some data around no water being in the back tank but sure enough it just never has enough time to dry and thus always shows as water detected. But the big thing here is that you will never be immediately notified if that tank is empty as it would take time for the sensor to dry.

ww · ‎Jun 2 2022

Those numbers are from 14.x firmware. I was suprised to. But I guess it can differ each firmware

Takis_Samanis · ‎Jun 1 2022

Thanks guys 😀

Tore · ‎May 27 2022

Not unnecessary if you have pinned firmware for devices @John_on_API Then it would be very valuable to get the per device firmware. Also this is something that should be possible: To have different firmwares for devices in the same network.

Tore · ‎May 27 2022

It is also worth to notice that the firmware version displayed in Dashboard doesn't have to be the actual firmware running on the device. It is just what is configured for the Network. If the firmware version displayed on the device page is different from what is displayed in the Firmware Upgrade page, we have to assume it is a UI Bug.

cmr · ‎May 26 2022

@RobertGardner I second your request, that does seem somewhat of a mistake!

Ryan_Miles · ‎May 25 2022

Per the doc "It is recommended that Root Guard be applied to ports connecting to neighboring, downstream switches that should not be the Root Bridge, to prevent a superior BPDU from being received on the port and causing the election of an unexpected Root Bridge."

RobertGardner · ‎May 25 2022

Thanks Ryan. I'll reach out to my Meraki reseller to get a quote on the MX68CW, which seems to be the only model with integrated LTE and PoE ports (to power the MV).

Allen-O · ‎May 25 2022

Comparing the L3 fw rules from an existing SSID to the one I'm trying to create with the API, it looks like you were right about that one as well :). Now I'm just trying to figure out how I get around the API requiring the destination to be in CIDR format instead of "Local LAN" which is what I get from the other SSID when I do a GET with the API.

mak2018 · ‎May 18 2022

Great thanks all!

rgforge · ‎May 17 2022

Thank you!!!

DavidH-NBH · ‎May 12 2022

Thanks for the suggestion, but we now have opened a formal support case. I don't want to waste any more of your time on the issue, but I appreciate the comments and suggestions.

KR7766 · ‎May 11 2022

Thanks rymiles. I appreciate your reply.

About Ryan_Miles

Ryan_Miles

Ryan Miles

Community Record

Badges