Good suggestions above - also:  did you try switching the 2 fibres around, to ensure you've got TX ->  RX    RX -> TX ... View more

This ask for clarity has been passed up to the BU ... View more

I'd go for an MX75 if you can get the money for that.   An MX67 (or 67C) if the required funds aren't available. ... View more

Advanced / Advantage licences don't hold any meaning for the majority of MS switches;   they don't support the Adv features.   MS130 is the only exception;   130X and 130R have Adaptive Policy capabilities.   The traditional SKUs for co-termination / PDL licences for all the older MS models hold a clue;   these are all Ent only. ... View more

It depends what you mean by traffic steering.   Do you mean that you configured WhatsApp to break out to the Internet locally?   This would be part of the reason for running pcaps - does the traffic show within captures on an Internet or a VPN interface?   If it sill shows in VPN - and you're getting matching FW logs in SC - you can be pretty sure that traffic is still being tunnelled, and you'd want to look at your local breakout config.  Don't forget to consider traffic flowing in the opposite direction too, when reviewing the captures. ... View more

An unlicensed MR36 makes a very elegant (if rather large and expensive) door stop...?  😁 But when you license it...   https://tenor.com/bQRKu.gif  ... View more

Bear in mind too - the Meraki AP will need to be able to communicate with the Meraki Dashboard, via the Internet, to operate effectively - even if your user-traffic does not touch the Internet. ... View more

Sorry @PhilipDAth - you probably realised I didn't see your own post regarding WPN / iPSKwoR, before I put mine on...   At least we basically said the same thing!  😁 ... View more

Given your scenario, I'd look at using a common SSID for everyone, but with WPN: https://documentation.meraki.com/MR/Encryption_and_Authentication/Wi-Fi_Personal_Network_(WPN) Probably using iPSK without RADIUS You might want to consider an onboarding app, such as that offered by SplashAccess (covererd in principle in the doc above) to make the setup more readily user-friendly and admin-light.   ... View more

I think you're going to need to provide some more information about what it is that you have  (is the firewall a Meraki MX?) and what you are actually trying to achieve.    I suspect it's unlikely you need to segregate bandwidth for individual APs, though you might be able to do that by running all SSIDs in NAT mode and using traffic shaping on the MX.   Maybe more likely you want to apply a per-client or a per-SSID bandwidth limit? https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Traffic_and_Bandwidth_Shaping ... View more

Yes - switches are needed for Traffic Analytics:   https://documentation.meraki.com/MS/Monitoring_and_Reporting/Switch_Traffic_Analytics ... View more

YOu could also set up Netflow to an appropriate collector for flow data:   https://documentation.meraki.com/MX/Monitoring_and_Reporting/NetFlow_Overview   I'd go with running some packet captures as a starter... ... View more

Did you read the document fully?  Templates for MX caters for different LAN subnets per site (search for ‘unique’) ... View more

As Darren suggested - pick up a phone and call Support;  it's better in almost every way.  If you already have a case open, quote the case reference to them. ... View more

Good point - I'll look to see if we can remove them  (it'll be related to the original planned date for EoS - which still lies in the future;   in reality inventory ran out before that)   PS. I'm not going to bite on the 'expensive' comment. Though, if something isn't for sale, how can it be expensive? 😀 Oh - that probably counts as a bite... 🙄😂 ... View more

While we're being super-penickety on specifics here: C9300LM-M   (where the -M indicates 'Meraki management') does not currently exist.   You currently can't for example, convert a C9300LM bought with traditional on-prem management into Meraki-managed mode.   I.e. the fourth family on the list here is only currently available with traditional on-prem style management ... View more

Remember that a Network in the Dashboard is effectively a container for configuration;   you place a device in a Network and it gets the configuration that is in there.   So if you take a device out of a Network, it loses its configuration and gains whatever config exists in the new Network in which it's placed. There are some scripts out there that use the Dashboard API, to allow config to be pulled from the current Network and pushed to the new one. ... View more

I'm sure they do - unfortunately they are no longer on sale:   https://documentation.meraki.com/General_Administration/Other_Topics/Meraki_End-of-Life_(EOL)_Products_and_Dates ... View more

'Stacking kit' as a term would apply solely to C9300L   (of academic interest here, it would seem) Called a kit cos it includes the stacking modules as well as the cable C9300-M and C9300X-M have built-in stacking ports - you only need to order the compatible cables.   These are, incidentally, different ones from those in the C9300L stacking kit - it's an entirely different stacking architecture. ... View more

Those aren't quite accurate SKUs, as it happens but yeah - within a family (i.e. 9300 here) they are, of course, inter-stackable.  Port count and PoE / non-PoE makes no difference.   The main cautions have already been pointed out by @GIdenJoe    The only thing I'd add is, if you're considering stacking 9300L switches, they don't have built-in stacking ports, you need to add the stacking kit to each unit you want to stack:  C9300L-STAK-KIT2-M This includes a 1/2m stacking cable.   1M & 3M options are available. Remember; no StackPower support on C9300L either ... View more

Because they're not End of Sale!    (so this is good news for your target customer.)   😁 ... View more