Hi @PhilipDAth,   That is correct.  ... View more

Hi @nadalfan1984,   As far as I know dynamic public IP can be used if both firewall are Meraki, since they are using the SDWAN technology feature called Auto VPN.   If ever the one of the firewall is a non-Meraki, I typically require that the non-Meraki has the static IP and supports DMVPN (Dynamic Multipoint VPN). Meraki MX can either have dynamic or static IP. Suggested also that the main branch should have a static IP and the branch can by dynamic.     Cheers!   Terry ... View more

Hi @RameshSesetti,   Heatmap can be enabled if you have at least 3 Access Points as it uses the triangulation    Go to Wireless > Monitor > Location heatmap   In addition, Meraki has a marketplace for 3rd party tools that are confirmed can be integrated using APIs though take note those are not free as you need to have subscription with those 3rd party. https://apps.meraki.io/     Cheers!   Terry ... View more

Hi @big-net,   Content Filtering usually used when blocking categories or sites. If you use this to block all, it will both block internet and internal access. One possible solution is to create a firewall rules on your MX to allow only specific IP (like proxy, internal networks) and the last rule is block any source to any destination using any ports. In this way, users cannot access internet directly.     Cheers!   Terry     ... View more

Hi @EJN,   Same I am also looking into that. For now the closest one I could think of is the View all network then select the Devices tab. You will see the list of devices, the number of clients connected to each devices, status of connectivity. etc. You can also filter the devices using the Search bar.   In addtion, if you need other details, click the plus + icon at the upper right corner to choose other details you need.    Hope this helps 🙂     Cheers!   Terry ... View more

Hi @RafaelDanelon,   The Historical device data on the Access Point summary page is about the real-time connectivity status with options to preview up to last month only. I am not sure if Meraki will be adding a custom range feature for this but definitely I am also interested on that.   As far as I know, there is no way to download the historical device data for now. But what you can do is to register or enroll your Meraki device on an NMS or monitoring tool wherein it can give you the data that you are looking for. If you have also knowledge with API it would also be a great way to capture the data you need.   Maybe some of our friends here in the community has other ways 🙂     Thanks   Terry ... View more

1. Go to Security & SD WAN > Configure > Site-to-Site VPN 2. At the top portion of the page you can see the Type 3. Select Off ... View more

Wow. Such an amazing community. Congratulations to all of us! 😊🎂🍾 ... View more

I'll try to configure the MX using the MX uplinks instead of the virtual uplink IPs. Unfortunately the sites were configured that way and I cannot change it as those are datacenters. It was designed as flat network so that when during business continuity drills, all IPs addresses and networks on Site1 is replicated at Site2. Appreciate you help bro. Thanks! ... View more

Thanks bro for this. I've already read these articles as well.   Ok. So on our setup, the WAN uplinks are not in HA. Meaning, ISP1 is only for MX1 and ISP2 is only for MX2. Hence I cannot use the warm spare configuration that uses the uplinks.   Yes there will be VRRP on LAN side for the heartbeat. However in our setup, the LAN interfaces of the MX are configured with IP address (done by creating a VLAN x with y.y.y.y/24 address and associate that VLAN on a LAN port of the MX).   Let's say I have: MX1  - VLAN10: 10.10.10.2/24  - Port 1 - access mode vlan 10 MX2  - VLAN10: 10.10.10.3/24  - Port 1 - access mode vlan 10   These MX's port 1 are connected on the switches. Behind the switches are L3 devices (e.g. router). I need to configure the routers to have a static route points to the VRRP IP of the MX so that when MX1 fails, the router at Site 1 will use MX2 and ISP2. if the MetroE goes down, both MX will go active.   ... View more

Corp VLANs A, B, and C are also at Site 2. When the MetroE/VPLS went down, both MX will become active. But when the MetroE/VPLS went up, Site 2 MX will become passive again.   ... View more

More likely that one, but the switches are connected to a layer-2 Metro Ethernet link. It is a flat network wherein all VLans at Site 1 are propagated as well on Site 2. Networks on Site1 are also in Site2. It is a mirrored setup actually. Warm spare will have VRRP at the LAN side, and the switches static route will point towards to the VRRP IP. ... View more

Anyways I have talked with Meraki TAC and says that it is not possible to have VRRP on the LAN side. Thanks guys for the help though. Appreciate it. ... View more

I have that kind of HA on my other side thanks. But I need is a different one. What I need is on the LAN side not in the WAN/uplink side. If possible to have VRRP on LAN side so that may static routes from my Catalust switches will just point to the MX LAN VIP. ... View more

Hahaha!!! That's the best way I guess 😛 ... View more

I don't know if this is what you are looking for. Hope it helps: https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/Seamless_Roaming_with_MR_Access_Points ... View more

The URL shows the recommended clients per MX models. Though # of connections, I think it supports already the # of users. I suggest if you have these numbers of clients, go for the next model (e.g. if you have 50 clients, go for the next model which is MX84 so that you still have some space for growth). ... View more

Hi pstewart, Well, they have this one: https://meraki.cisco.com/lib/pdf/meraki_datasheet_ms.pdf Though it only provides basic comparisons (e.g. throughput. number of interfaces). But at the last page it has the links of all MS switches datasheets. You just need to read them one by one 🙂 ... View more

Meraki has also a sizing guide for you to be able to properly choose what MX model you need on your network: https://meraki.cisco.com/lib/pdf/meraki_whitepaper_mx_sizing_guide.pdf ... View more

pstewart, DAI is only supported by Layer 3 MS switches: MS210, MS225, MS250, MS350, MS400 series https://documentation.meraki.com/MS/Other_Topics/Dynamic_ARP_Inspection ... View more

Hi Lubandw1, Since MX uses port 80 for its local page, try changing the DVR port. ... View more

Hi Porch, You may try to exchange the APs. Try to exchange the affected AP from the other APs. Then connect on that affected AP, and test also the AP that was exchanged from the previous location of the affected AP. Let see if you are still having problems with the affected AP, or there is an issue on its location. ... View more

Hi Porch, How about when connected to other AP? If the signal and ping is good at other APs, you may check Layer 1 which is the cable of the AP. Possible that the cable of the AP from the switch exceeds 100 meters which there is loss along the cable. ... View more

Hi Porch,   Few questions: 1. Have you checked the Heatmap for any interference? 2. How is the SNR of the signal? 3. How about some laptops are they also experiencing the same issue? 4. Can you try to go below on the AP and try to ping again? ... View more