Refer to this doc https://documentation.meraki.com/MX/MX_Overviews_and_Specifications/WAN_behavior_on_MX75%2F%2F85%2F%2F95%2F%2F105#MX75   On the MX75 the first 2 ports are both "WAN 1" and you can only use one or the other. It will detect for presence of a SFP on boot. ... View more

I agree with @alemabrahao and keep it simple. Put APs in a mgmt subnet. Drop clients in another subnet(s). A /22 isn't unreasonable for wireless networks. And with our APs you can use L3 firewall rules to stop some of the noise if you want (example, deny netbios and other unnecessary and chatty protocols).    Not sure how many SSIDs you intend to have, but fewer is always the aim. As for the clients joining APs on other floors. There's nothing inherently wrong or bad about that. As @alemabrahao said roaming is a client decision and if a client can obtain a usable signal from another floor AP so be it. ... View more

How are you measuring throughput? From the Tools tab on the switch or from a wired client using some other test method? If you're talking about the Tools tab throughput test that won't show maximum speed of the switch or internet circuit. Not even close.   And, MS390s will generally show a much faster throughput using the dashboard test tool versus traditional models like MS35x, 2xx, 1xx due to underlying architectural & software differences.   To measure wired client throughput you should be using standard tools like iPerf, speedtest.net, etc.   Are you troubleshooting a specific issue here or just seeing unexpected results using the throughput test? ... View more

https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Throughput_test_to_the_Cisco_Meraki_Dashboard#Comparing_to_Similar_Throughput_Tests  ... View more

I just tested using Postman and changing the true/false setting for dhcpNoLeases is working fine for me ... View more

Please open a Support case on this one ... View more

Great updates in this release! ... View more

Appreciate the post. This does creep up on people in certain situations. And, I agree it should be configurable by the end user (of just off by default).   If you have a Meraki SE that supports you I would provide them this feedback so they can roll it up to the powers that be. ... View more

Open a Support case so our Engineers can look at it.   It could be the AP firmware at the new location. Make sure you run the latest version 29.6.1, 29.7 RC, or 30.4 beta. Or, it could be upstream firewall rules preventing TCP port 7734. Impossible to say without being able to access the dashboard and do some troubleshooting. ... View more

Nope ... View more

I made a short slide deck on this topic awhile ago. Posting here for reference.   Also, the BIG DISCLAIMER - this "hack/trick" isn't suggested, recommended, nor supported. So use it if you like, but just be aware at some point behavior could change or Support might recommend you not do this.   Now for the slides   https://docs.google.com/presentation/d/1FDD0qU6stBYm1dzWejoW_0vocgyB7UjUKUPi9EB_--M/edit?usp=sharing ... View more

That API doc is for Cisco IOS products not Meraki. And Meraki Subscription licensing isn't available yet.   For Meraki API documentation please see this link https://developer.cisco.com/meraki/api-latest/  ... View more

As mentioned by others no breakout cables are supported. The only converter supported is the CVR-QSFP-SFP10G version 2. This is mentioned here https://tmgmatrix.cisco.com/?npid=2301     Anything outside of the above is not tested or supported so you may luck out and it works, but likely it will not. ... View more

Firmware upgrades to template bound networks will/should adhere to the network's local timezone. Is that not the behavior you're seeing? If this is not truly following the locally configured network timezones I'd recommend you open a Support case. ... View more

One more example just to show how random clients can be and why it's tough to be super accurate in dashboard unless you have some very controlled way to configure hostnames.   I compared the dashboard detected hostnames from three Macs, two iPhones, two Apple Watches, and a Honeywell thermostat. All Macs, phones, watches run the exact same OS builds as the other same device types.   For my phone, Sandra's watch, and the thermostat I have not configured a name in dashboard hence that column is empty. You can see phones for whatever reason send two different mDNS name formats, the watches send nothing, one Mac has netbios name and the other two don't.   All devices are wireless. All devices are on the same SSID.   User specified name mDNS name Netbios name DHCP name Ryan's iMac Ryans-iMac-3465.local RYANS-IMAC-3465 Ryans-iMac-3465 rymiles MBP 14 M1 RYMILES-M-J294.local null RYMILES-M-J294 Sandra's MBA M1 Sandras-MBA-M1-8.local null SandrasMBAM18   ryPhone.local null null Sandra's iPhone 6c562065-9259-44e8-9d4b-4656fa13b68a.local null null Ryan's Apple Watch null null null   null null null   Lyric-C1FF37.local null Tstat-C1FF37 ... View more

I don't think it's model specific. More config/enabled features dependent.  ... View more

You can also do a quick test using capture in dashboard. In this example I captured on my MX LAN interface (it's my DHCP server) used the filter udp port 67 and verbosity medium. Then on my Macbook I did a DHCP renew to force the transaction.   ... View more