Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Markus
Community Record
17
Posts
10
Kudos
2
Solutions
Badges
Feb 22 2018
5:41 AM
1 Kudo
Yes, thats what I said. It is the same license level across an organization. So in your case you need two organizations. If the tunnel ends on a different MX then the one that does the filtering, your setup should work from my point of view. The edge MX treats all traffic coming from the LAN side as internal. It does not make a difference if this traffic comes from a VPN concentrator or not. It does not work if you do filtering on the MX that terminates the VPN tunnels. I have never built this design so far, so best would be if you have the chance to verify it. But from my point of view it works if you create a dedicated organization for the edge MX.
... View more
Feb 22 2018
3:38 AM
yes, I dont like it as well. But have a look at following link: https://documentation.meraki.com/zGeneral_Administration/Licensing/Cisco_Meraki_Licensing_Guidelines_and_Limitations This statement is from the referenced page: Please note that the MX licensing edition is uniform across the Organization. For example, you can have all 25 appliances using Enterprise Edition or Advanced Security Edition, but you cannot have 20 appliances using one edition and 5 using the other edition. If you wish to use Enterprise Edition for some appliances and Advanced Security Edition for other appliances, you need to create two Organizations, one for your appliances with the Enterprise Edition, and another for the appliances with the Advanced Security Edition.
... View more
Feb 22 2018
3:30 AM
Hi, as far as I understand the license model of Meraki, all MX within an organization have the same level. You cannot upgrade single MX within your organization. Either all of them are with the basic license or all of them are advanded. Regards, Markus
... View more
Feb 15 2018
9:09 AM
2 Kudos
Yes... It actually does not matter whether you have one or two RADIUS Servers configured. Both of them need to be successfull. If you get an error, there is a problem with the RADIUS Server or the credentials. In your case I think it is the NPS. I‘d recommend to have a look into the NPS log. Did you check that already? Did you export and import the NPS Config?
... View more
Feb 9 2018
8:27 AM
1 Kudo
In the NPS GUI you can export the config as XML and import it on the other NPS so they are in sync with the config.
... View more
Feb 9 2018
8:09 AM
How do you bring them online then? (they need an IP to download the config)
... View more
Feb 9 2018
8:08 AM
1 Kudo
You can also export and import the config in the GUI if you want.
... View more
Feb 9 2018
7:59 AM
You can try to use PUT device config https://documenter.getpostman.com/view/897512/meraki-dashboard-prov-api/2To9xm#d4a122ee-0679-dda7-d787-9b70a068d069 I am not sure if lanIp is supported as PUT but it is in GET for sure. So maybe worth a try. Anyway, I would not recommend to use static IP‘s. What is your reason for that?
... View more
Feb 9 2018
7:21 AM
1 Kudo
Hi, you can do it via API. For 900+ AP's that's worth the effort. https://documenter.getpostman.com/view/897512/meraki-dashboard-prov-api/2To9xm
... View more
Feb 9 2018
6:48 AM
1 Kudo
Yes, AD is replicating automatically, but NPS is not. The config needs to be manually synched between the two servers. Maybe you should check this is the case. In my setup the check in dashboard was successfull for all RADIUS servers.
... View more
Feb 9 2018
5:58 AM
1 Kudo
Hi Julian, are you using Microsoft NPS, or what is your RADIUS Server? I have implemented this many times and not seen this issue so far. Normally your RADIUS Servers authenticate against the same AD's. (Could be different servers, but the same AD cluster) Could you explain the setup in more detail? Regards, Markus
... View more
Feb 7 2018
6:38 AM
1 Kudo
this should work with a portforwarding from public port 80 to internal port 80. Or with a 1:1 NAT as you have it configured. The hostname is not changed by the MX as it is part of the HTTP header. What is the problem that you are facing. Just to mention it, for this config you need split DNS. One DNS that resolves internal requests with the internal IP and one public DNS that resolves the public IP. You cannot use the public IP from internal network if you're behind the same MX as the Webserver.
... View more
Feb 7 2018
5:09 AM
1 Kudo
I am not sure if I understand your question correctly. If you are trying to publish an internal website with a different port then 80 over the MX to the internet with port 80, you can do it with portforwarding under firewall rules. So point your external DNS to your MX IP and configure a portforwarding for your MX IP port 80 to your IIS with the specific port. If you do it on the Meraki MX you can use port 80 only once, meaning you can have only one webserver / TCP port combination published with port 80. If you have more then oine you need to use a reverse proxy or the like. The Meraki MX is not a reverse proxy. Am I understanding your problem correctly?
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 5344 | Feb 22 2018 5:41 AM | |
| 4521 | Feb 7 2018 6:38 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 30419 | |
| 1 | 5344 | |
| 1 | 30452 | |
| 1 | 30456 | |
| 1 | 8073 |
© 2025 Cisco Systems, Inc.
