Has anyone found that the MA-ANT-C1-B or any other external antenna will work with an MX67C? ... View more

@John-H I'm afraid not. It didn't help that I only had access to the Meraki side, and then after a short while the requirement was nullified so everything stopped. Sorry...   @RichardChen1 My apologies for not responding to you way back then. I don't recall why. ... View more

We've used it in a lab to test the usefulness. The issues we've noticed are: Support is slow to respond and doesn't always give great answers speed test from speedtest.net will show great speed, iperf3 over vpn does not doesn't come with a built in way to connect the mx, need to order an adapter Other than that, it is a lot cheaper than some options in the middle of nowhere, and better speed than a lot of them ... View more

This is an old subject, but in case anyone is still interested,   Meraki implemented a new feature for VoIP insight, which is Best Effort Monitoring:   There are some VoIP servers that do not allow or drop the ICMP pings used for monitoring VoIP statistics such as MOS, loss, latency, and jitter. However, as VoIP services are critical, we have integrated Best Effort Monitoring to MI VoIP Health to give a “nearest” best estimation on VoIP performance for a given link. You can enable it by clicking on the Best effort monitoring checkbox when adding a new VoIP server: ... View more

Hi Dan,   was the client machine only connected @ 100Mbps? ... View more

Hi Richard, Did you get this working?  I'm trying to do this with Jamf as the MDM to connect to the Meraki Wireless using Microsoft SCEP ... View more

Fantastic. Thanks so much for the prompt reply ... View more

It might work if you create a group policy and attach it to that client.    That’s when the layer 7 will kick in.  Since group policies are stateless. ... View more

@RichardChen1 wrote: Since the concentrator has a lan ip address. What kind of port forwarding required for client vpn to work? Just udp500/4500 to lan ip? Yes, UDP/500 and UDP/4500 is enough as with NAT-T, after the initial exchanges on UDP/500 all is encapsulated in UDP/4500. ... View more

We just tested it on a lab that we created for this purpose (2 MX's and 2 routers to simulate the MPLS) but the plan is to move to production this week.   What is important to have clear is : 1.- The MPLS has to be on the LAN of the MX. 2.- To have an SDWAN  tunnel up (not ordinary VPN's) using a WAN port.  3.- To understand the purpose of each route of your table, the priority of each route and to be clear what happens when one of your routes overlap another one (the redundant one). If you are not clear about the purpose of each of your routes and how they behave in every scenario, then it could not work as it should. ... View more

That depends on the WAN circuits you are using. Really the only requirement is for each WAN port that you are using on the hub to be able to access the Meraki registry (essentially the internet) - so if you have direct internet connections then you will be fine, or if you're using an MPLS network that provides NATed internet access then you will be fine, for both these or a combination of them you should be able to run the MX in routed mode.   Generally one arm concentrator is only a necessity if you want to do dynamic routing, have multiple DCs providing access to the same subnets, or if you need to provide the internet access from an MPLS network - although that's not a prescriptive list. ... View more

I have not integrated Webhooks with Solarwinds but it's possible.  Like I said, you will need an intermediary to ingest the webhook and take the appropriate action in SolarWinds.  That intermediary can get the webhook then decide what to do with it in Solarwinds.  Then it can make an API call to Solarwinds to update it.  There is no direct integration via Solarwinds. ... View more

Hi Richard,   Yes, Cisco has documentation explaining how to integrate AD and Meraki, I followed this steps, my certificate has all requirements presents in this documentation. ... View more

Wow, that was a cool tool! ... View more

I've sold them but never installed one myself.   They are IP67 rated.     ... View more

Which migration step did you take eventually?   I have migrated DMVPN to Meraki before with HUB vpn concentrator + static route between the Hub DMVPN router. ... View more

I don't remember clearly now.  I don't think you need to change anything for AutoVPN to work. ... View more

@RichardChen1 wrote: Check this out: https://www.willette.works/mx-warm-spare/ Yeh... There's falsities in that and I would not recommend you follow that guide. There are some good things in there, but the whole heartbeat thing is not truly possible and very misleading.  ... View more

Our Mac guru has found a workaround by adding a script that runs everytime the VPN is connected. ​ https://akrabat.com/routing-specific-traffic-to-the-vpn-on-os-x/ ... View more

This isn't 'solved'. Is this supported yet? I can find requests for these features all the way back to 2017 on these forums. ... View more

@WillN  I had that same thought because of the short amount of time it was online.  I use templates to push out my configurations and my template uses version MX14.45 which is stable release.  I did not look to see what version is shipped so I'll have to wait for my replacement (RMA was initiated yesterday).  I am wondering if I should upgrade my code on the template to 14.50 but found these not so satisfying entries in the code notes.    Although 14.50 did say it fixed this:   Resolved an issue that could result in MX67(W) and MX68(W,CW) appliances entering a reboot loop if 802.1X port authentication was configured while wireless was also enabled.   The caveats still show this: "We have recently become aware of an issue introduced in this firmware version that may result in communication issues between devices connected to ports 3-7 and devices connected to ports 8-12 on MX68(W,CW) appliances. We are working to provide an updated firmware version that resolves this issue as quickly as possible. Until that version is available, we will not be scheduling any further upgrades to MX 14.50 and we advise customers take additional caution before upgrading further MX68(W,CW) appliances to this version."   MX67C, MX68CW, and Z3C units must be connected to the Meraki Dashboard initially to retrieve an update to allow for proper use of the integrated cellular connectivity. This is most likely to be an issue when bringing the units online for the very first time.     Edit:  Meraki shipped replacement with 14.40 so I downgraded my template to 14.40 and then tried again to add the MX.  Could have been just a coincidence and I did not have the luxury of trying to brick another one so I just downgraded before plugging it in.  But all worked out now but I do have my suspicions on the 14.45 code, which is no longer available.   Thanks all for the input! ... View more

I tested the same setup on a few Android and iPhone.   I was able to replicate the same issue on all iPhones but not Androids.   @PhilipDAth @MerakiDave I believe you are correct on this. Thank you. ... View more

Thanks @MerakiDave  Issue resolved.   My lab ISE was running on vmware that bridge to wireless connection.   I was able to resolve it by changing from wireless to wired connection.     ... View more

On your vpn concentrator make sure the public ip and ports are allowed on PA. Dashboard -> Help -> Firewall info   On the spoke MX, go to dashboard -> Monitor -> VPN Status see if you have any error message. ... View more

Yes, configuration will be automatically synced as soon as your device is able to contact Meraki cloud. ... View more