Meraki

PhilipDAth

Typically, you wouldn't see transmit power levels over 100mW (if it was cranking). Your hands generate more heat than this.

CarolineS

@nbv thanks! Do you think the existing "API" label should be changed to "Scripts", or does it make sense to have both "API" and "Scripts"?

PhilipDAth

Painfull! Maybe it is a bandwidth squeeze. Try configuring the WAN uplink bandwidth (on your MX) to match what it actually is. Then then create a QoS rule to make the RADIUS traffic high priority. More general information: https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/SD-WAN_and_Traffic_Shaping

PhilipDAth

PDL is being terminated as a program ...

TyShawn

I thought the same thing... and I hope the support agent was misspoken with that comment.

BlakeRichardson

@Erick_Rojas have a look at this post and see if any of it is useful, it's not directly related to Grafana but there might be something useful in the information. https://wirelesslywired.com/2022/06/06/meraki-mt-mqtt-node-red-amp-home-assistant-auto-discovery/

Dudley5526

Colin, I would like more information. We have been using Meraki MDM for 2 years, but we have lots of questions.

Jams

I thought the anonymous identity field might be the cause (and who knows? Maybe still is...) From my experience - A couple years ago, it didn't seem to matter what went in there. Some time later, it was only authenticating when people copied their username to the anonymous id field. As of recent, I've tried: blank/empty left the default "anonymous" mirrored the username (i.e., anon id = username) full AD user (domain\username) UPN (username@domain.suffix) No success. Timing-wise from when the problem started, and some testing on other devices still on Android 14 (which connect fine), it 'seems' to be related to A15. Whether it has something to do with something changing in how it handles the Anon Id field - since that has affected things before - or something else altogether... Still stumped.

ggarolla

I am having the same issue (SSID using WPA2-PSK and clients all of a sudden showing EAPOL Timeouts, which does not make any sense), but I do not understand how enabling 802.11r could solve it, since we are using PSK. I will try it though

BlakeRichardson

I have opened a support ticket as the device page isn't even showing current information.

Brash

Congratulations all, and especially to the fresh faces joining the club 🙂

PhilipDAth

Is this AutoVPN, client VPN, AnyConnect, or a non-Meraki site-to-site VPN?

dmbooth

OS is Windows 11 and these are brand new laptops. Have tested by building a clean install Windows 11 VM and also see the same behaviour. The SM agent is v4.2.2, but as mentioned these are App installs via MDM that are failing including the install of the SM Agent itself. Thanks

cmr

What kind of configuration and ports in use do they have?

prabhulkars

According to the documentation below, as long as the AP is receiving power but no internet, it should be able to broadcast the default SSID which can be used for administration purpose. https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page#Cannot_connect_to_the_local_status_page_when_connected_to_an_SSID

Gedanken_leben

Thank you to every one that took time to reply, very much appreciated. I learnt something that I would not have understood otherwise. Marking @PhilipDAth as the solution purely because anyone else reading this thread in the future will benefit from the links.

BlakeRichardson

@JBOFL Meraki much like other vendors does not publicly release their roadmap

BlakeRichardson

@garonson This will 100% work, one network I manage has MS, MV, MR and MT all sitting behind a Fortigate. As Darren mentioned just make sure that the required outgoing WAN rule allows the required ports. These can be found by logging into the dashboard and under the help menu and selecting firewall info.

BlakeRichardson

For others that might want to help the text on the second screenshot says " You must set an ipad unlock code within 59 minutes"

Ferguson79

See screen shot below, its stating the both products below will replace the above products, meaning the MS120 (now EOS replaced by MS130) and the MS225 would be a viable recommended replacement. The MS225 does have an * next to it, which is noted at the bottom of the document saying (* Please refer to the next line for current functionality equivalent) this is because the MS225 would be a good recommendation, but is also Static Layer 3, while the MS120 is layer 2, similar to the MS220. Current there is not EOS announcement for the MS225 series switches.

CHC_Cheo

So when are we going to get device uptime for MXs? How has it been 4.5 years and we still don't have this wildly basic functionality?

Meraki_Gwen

Thank you, I have reached out to our internal teams. I will let you know when I have an update on your network.

BlakeRichardson

I guess at the end of the day who legally owns the equipment i.e. who purchased it and has proof of purchase.

Macguy

I've seen this "low power mode" for a long time now. We have Aruba switches and I've tried various things on the switch end to try and resolve. The only fix I've had success with is physically unplugging cable from switch and plugging back in. Sounds dumb but it works every time (same port). Reboot AP doesn't fix, nor does disable/enable PoE. Really weird, on the switch end it has the correct power class and power utilization. For whatever reason, the dashboard claims low power mode. Glad its acknowledged by Meraki as a bug.

BlakeRichardson

I also found the MT20 door sensor a much better option and then simply assign a camera to that sensor.

About BlakeRichardson

BlakeRichardson

Community Record

Badges