This will work as you desire, if you configure the Networks in question under the same configuration Template:   https://documentation.meraki.com/General_Administration/Templates_and_Config_Sync/Managing_Multiple_Networks_with_Configuration_Templates If you don't want to use Templates, you could use an external splash page - something like SplashAccess https://developer.cisco.com/meraki/captive-portal-api/   ... View more

In principle the AP to look at would be the MR46E, but if I remember rightly, the 1260 APs (2 spatial streams) have separate antenna ports for the 2.4 and 5 GHz radios, whereas the MR46E (as a 4 spatial stream + scanning + IoT radios AP) needs dual-band antennas.   The key will be in the specifications of your existing antennas.   What details do you have on those? Bear in mind too that, unless the Meraki AP is paired up with new/appropriate Meraki antennas, with dual-band antenna elements, it won't be supported by Meraki. ... View more

I very much doubt this will be supported on that switch platform in the future - t's both End of Sale and was designed as an edge access switch (think:  aimed at PCs, printers, WiFi APs etc).   LACP teaming only for that switch range, I would suggest:  https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Link_Aggregation_and_Load_Balancing#MS_Series Bear in mind too, in reference to @alemabrahao 's link:   the MS220 doesn't support physical stacking either:   ports in a Link Aggregation Group all need to go to the same switch ... View more

What email address are you using, if you try raising a case that way? ... View more

If you're thinking this is something with your MX, you should look to post to the SECURITY / SD-WAN Forum.   Did you take and examine some packet captures on the WAN / LAN interfaces of the MX, to see whats going on?   If you haven't already, I'd raise a case with Meraki Support too ... View more

I think I'd be tempted to get rid of the unreliable supplier and go for two decent uplinks. ... View more

@Adrian4    Looking back at my initial reply, when I said you need VLAN tagging, I was referring to the physical switch to which the APs are connected (i.e. they need to be configured as trunks).   Sorry for any confusion caused... ... View more

Las ubicaciones para el MR33 y el MR53 suenan bien, en principio; ambos tienen antenas omnidireccionales internas. MR84 no tiene antenas (cero) internamente; solo funcionarán con antenas externas conectadas.   https://documentation.meraki.com/MR/MR_Installation_Guides/MR84_Installation_Guide#Antennas   Parece que alguien ha elegido antenas externas MA-ANT-21 para usar con estas: son antenas de sector de 80° https://meraki.cisco.com/lib/pdf/meraki_datasheet_antenna_5GHz_sector_13dBi.pdf   Estas antenas están optimizadas para operar a 5 GHz y realmente necesitaría dos para cada MR84, apuntando en la misma dirección. Tenga en cuenta que es probable que cualquier solución WiFi nueva tenga algunas ventajas sobre los puntos de acceso que está describiendo, porque los modelos MR que menciona son bastante antiguos ahora. (Todos han sido reemplazados, en la gama de productos Meraki) Todos son AP de alta calidad para su época y aún pueden hacer un buen trabajo ahora. Siempre que tengan licencia, permanecerán respaldados por Meraki hasta el verano de 2026: https://documentation.meraki.com/General_Administration/Other_Topics/Meraki_End-of-Life_(EOL)_Products_and_Dates  ¿Ya están instalados? Si es así, ¿qué tan bien funciona el wifi?   ... View more

OK - any trouble, call up Meraki Support on the phone... ... View more

Not sure what you're suggesting is triggered via the API?   Cloning Networks is a Dashboard operation - it doesn't involve the API. ... View more

Should be...   did you try it? ... View more

It could probably be made to work, if what you're providing is just Internet access (you'd have to have more than one Network for the three MXs) - VPN operations would be more complicated and it wouldn't be very 'Meraki-simple'. Why does the customer need two backup links?   Given the cost of connectivity, two is enough for most customers - particularly if you use MX with built-in cellular (MX67C / MX68CW) ... View more

You have the option of defining the VLAN within either the Group Policy or (if undefined in the GP) on the SSID.   Either way, you will need the switch port to be a trunk, with the necessary VLANs enabled. ... View more

¿En qué tipo de entorno se están implementando? Si se trata de una oficina típica, los MR33 quedarán bien en el techo, pero tenga cuidado de que no sea demasiado alto. Para el MR74 y el MR84, ¿no menciona qué antenas están instaladas Si están usando el MA-ANT-20 básico, estos no quedarán tan bien fijados al techo. Sin embargo, normalmente no usaría AP al aire libre como estos, en una oficina. El patrón de cobertura del MR33 se incluye en la hoja de datos, ya que tiene antenas integradas: https://meraki.cisco.com/lib/pdf/meraki_datasheet_MR33.pdf El patrón de cobertura para MR74 y MR84 depende de las antenas, por lo que los patrones se encuentran en la hoja de datos para esos, por ejemplo https://meraki.cisco.com/product-collateral/dual-band-omni-antennas-4-7-dbi-datasheet/?file ... View more

You need to use VLAN tagging.   Assuming you're talking about iPSK without RADIUS, the key your client uses should match to one of the iPSKs you define.  The client will be placed in the configured (default) VLAN under 'VLAN tagging' - by tagging the relevant frames from that client.   With no tagging, how are the clients using different keys kept logically separate? You would only add another VLAN ID if you wanted such clients to be placed in a different VLAN, when associating through a different AP  (one you've applied the relevant AP tag to).   Most customers will simply want to use one (the Default) VLAN, to keep things simpler. ... View more

Lo más probable es que un firewall ascendente esté bloqueando parte del tráfico de un MX a algo en el tablero de Meraki o hacia el otro MX. Las reglas necesarias se encuentran en Ayuda (o ?) > Información del cortafuegos Realice capturas de paquetes en los enlaces ascendentes de WAN en los MX en ambos extremos para verificar qué se envía y recibe. ... View more

There's no really easy way to use two links upstream of an MX on it's backup WAN port, currently.   You'd need a further upstream router, really.  This functionality will come to MX models with >2 WAN ports in the future, via firmware update. ... View more

Have you checked you're running the latest firmware on the switches?  Reboot can still take a while for large stacks and dependent on configuration, but the times have reduced pretty significantly with later software.  With MS390 in particular I'd recommend release 15 firmware (currently 15.21.1) ... View more

All Meraki switches ship with at least one power supply, AFAIK.   Occasionally more than one switch range utilises the same PSU.   What switches are you receiving? ... View more

MR76 and MR86 are specifically designed for outdoor use (think:  weather-resistant).   Consider using these indoors if you have environmental challenges in that location, similar to weather issues:   e.g. if the APs are likely to get wet or particularly hot/cold.   Make sure you match up the right antennas to your AP choice;  the indoor APs / antennas have RP-TNC connectors, the outdoor APs / antennas have N-type.    In terms of choosing between the models, that's likely down to usage - use an experienced Cisco partner to help with the choice - but try to gather as much info about who will be using the WiFi when, for what and using what kinds of devices - they should be using that to help scope the solution.   In particular around concurrency - how many connected clients at the same time? Slightly concerned about your mention of not putting APs in the greenhouses - don't assume that the WiFi signal will penetrate the glass.   One of the things your Cisco partner should be able to provide is a proper site survey, which should assess and test all this stuff. ... View more

This can't be done at the Meraki end currently.   Your syslog server would need to be application aware (translate the IP / port source /destinations etc for you) ... View more

You will need to find a Cisco Meraki partner (reseller), to purchase Cisco Meraki licences (and/or devices).   https://locatr.cloudapps.cisco.com/WWChannels/LOCATR/openBasicSearch.do Most companies already have a preferred supplier, if you speak to your purchasing department.   We include 5 free MT licences in every Meraki Organization, to encourage customers to try the MT sensors - and I suspect these are what you're seeing.   You do need to ensure you have sufficient licence count and time to cover your needs though.   In particular check your License expiration date -  and check the 'Current device count' for each product does not exceed the 'License limit' alongside it.   https://documentation.meraki.com/General_Administration/Licensing/Meraki_Licensing_FAQs ... View more

Or you could use Systems Manager (with Sentry) to fully control your devices, including providing an appropriate WiFi profile.   With this option Meraki provides the X.509 certs and cloud RADIUS. https://documentation.meraki.com/SM/Deployment_Guides/Systems_Manager_Sentry_Overview   If you can't or don't want to fully manage the devices (maybe they are staff-owned?) then consider Trusted Access https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Trusted_Access_for_Secure_Wireless_Connectivity   Ether of these options will require you to purchase Systems Manager licences for the devices requiring connectivity.   You may still need to use username and password as an initial means of setup - after all, you still want to check what's connecting to your network to start with, right? ... View more