The note underneath the table gives a bit more of an explanation: "Carrier compatibility is generally based on having compatible bands on the modem. In the open market, carriers may only require regulatory domain certifications and open market certifications, like the PTCRB and GCF, to be compatible for their network. Sometimes carriers will require additional testing before a device can be used on their network. The section Tested Carriers is based on Meraki device certifications being approved by those specific carriers. A carrier being listed above means that they have officially certified the Meraki product for their cellular network. There maybe many unlisted carriers could be functionally compatible with Meraki devices. The list of tested certified carriers is based on the carrier validating Meraki per their network parameter requirements. If a carrier you are looking to use is not listed above, it could be that they do not require additional compliance testing for their network." Basically, as long as the carrier supports the bands on the device, and the SIM isn't locked in any way, there's no technical reason it wouldn't work. It's more that the listed carriers have approved and certified that the Meraki devices will work on their network. ... View more

This is not uncommon for Meraki where a product is slowly phased out where there is a better option available - or a similar option already within the Cisco portfolio. A few examples are:  - No longer supporting USB 4G dongles with the release of the MG21 and MG41 products.  - Stopping development on SSL decryption on the MX with the integration of Cisco Umbrella which can do cloud based SSL decryption. In this case, Anyconnect is a far superior product with better stability, features and functionality. Since it has MX integration (and has done for a little while now), the Meraki VPN is more-or-less being left behind in terms of its functionality. If I were you, I'd begin looking at Anyconnect, or another VPN option rather than trying to stick with the Meraki native VPN. ... View more

The cabling job only looks a little ugly because you've got a longer cable than is necessary so your eye just see's the big loops. As @GIdenJoe mentioned, getting some shorter cables might help.   Some other general guidelines:  - Micro/Slimline cables make a world of difference  - Cable management (where it works)  - Velcro cut to various sizes as needed  - Try to keep cable runs going to similar sides of the rack. Eg. Most cables going to switch 1go left while cables going to switch 2 go right. Or left half of the switch runs left, right half of the switch runs right.  - Where possible, use appropriately sized cables. In the real world this isn't always possible but the worst cabling jobs are where you find a 2m ethernet cable for a 20cm connection, and the rest of it is looped up somewhere. ... View more

Glad to hear mate 👍 ... View more

@ww  is spot on. The core switch can't have a management IP that it itself is the default gateway of. ... View more

I've typically found the splash screen to be fairly consistent. A couple things of note. The splash page won't appear until the client sends http traffic. Https traffic will not generate the splash screen as it is encrypted. The splash page won't appear if the client is accessing web pages from cache. ... View more

The 3 AP's that show the green circle with white in the middle are running as repeaters. They are meshed back to TP-A1. Assuming they have physical lan connections (not just power), you may want to look at the following link for troubleshooting. https://documentation.meraki.com/MR/Monitoring_and_Reporting/Gateway_AP_Switches_to_Repeater_Mode ... View more

That would be quite the complex setup.   It would seemingly be far easier to place another mx at site 2 so both have primary wan uplinks. You can then set the point to point link as a secondary WAN uplink. Assuming you have the appropriate routing that would achieve the uplink redundancy you're looking for.   But going strictly off what you're asking, unless your point-to-point link is providing some sort of stretched layer 2 overlay, I don't see how you can make it work. ... View more

I typically don't set new years resolutions but last year I re-certed my CCIE which was a big tick off the list.   Certification wise this year I've got ECMS 500-220 in my sights. Stretch goal is either CCNP of a different track or potentially an Azure exam given I've been doing a bit of that these days. ... View more

Just to add to this, I'd probably steer clear of using MFA for wifi auth. It can be a frustrating experience for users, and from what I've heard it can be a pain when roaming or at wifi signal boundaries. ... View more

You make the change in the Meraki dashboard under Wireless -> Access Control. Select the SSID you want to make the change to and look for "Advanced RADIUS settings"   One other thing to be aware of is that the RADIUS server also has a timeout of how long to wait for the MFA response. Azure MFA with NPS - 20 seconds timeout extension - Microsoft Q&A ... View more

What are the other devices that do work? Different OS or version? Have you disabled MAC randomization in the wifi advanced settings? ... View more

No, all Meraki devices must be connected to the dashboard (with an applicable license) in order to function ... View more

As @Bruce said, it sounds like you're using Meraki NAT mode on the Wifi SSID. So the clients communication are all NAT'd out by the AP. https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/NAT_Mode_with_Meraki_DHCP ... View more

Configuration is stored locally so devices can continue to run. For something like the event log, it will be written locally until cloud connectivity is restored. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Meraki_Event_Log   As for the local storage capacity and timeframe of storing local data, as far as I'm aware it's not publicly documented. ... View more

Verify that the fibers in the pair are the correct way around. Try crossing them on one of the cables and see if the link comes up. ... View more

Best to check with your Meraki rep to confirm 100% but I've only ever seen 2.5gbs on rj45 switchports. Fiber has always been 1/10/40/100gbps. The ms355 documentation seen to support this as well. https://documentation.meraki.com/MS/MS_Overview_and_Specifications/MS355_Overview_and_Specifications   Additionally there's no 2.5gbps SFP's supported. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/SFP_and_Stacking_Accessories ... View more

Worth verifying that the local device status page is enabled in the Meraki Dashboard under Network-Wide -> General. ... View more

Congratulations everyone 🙂 ... View more

VMX's aren't sized by number of users, but by the bandwidth and number of VPN tunnels they support. https://documentation.meraki.com/MX/MX_Installation_Guides/vMX_Comparison_Datasheet ... View more

From the Meraki side it's relatively simple, you just tell it where to send the logs https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/Syslog_Server_Overview_and_Configuration#Configuring_a_Syslog_Server   In terms of setting up a syslog server, there's multiple options out there - paid products and open source. The basic premise is the same for all, they simply ingest logs. The main differentiator is the interface, ease of deployment/use, filtering and alerts etc.   Some popular ones include graylog, ELK, nagios, splunk, kiwi. ... View more