Thanks for your response. I will test it in MW and monitor it.  Thanks again. ... View more

Yes ,indeed although it is not explicitly mentioned.Thanks anyway.It worked. ... View more

@jimmyt234  is right in his statement. ... View more

Thanks! The option is there if I tick the box next to the client in the client list, but it is no longer there if I click on the client and open the client details page.   Regardless, I'm all set.   Thanks again!     Client Details page:   Client List:     ... View more

These rules can vary shard by shard - so definitely use the tip above to get the firewall rules for the shard that you are on. ... View more

Unfortunately I never got as far as trying it! ... View more

For Cisco equipment such as Catalyst, Access Points, etc. You have the option of collecting information via Cisco Collector using the Smart Net Total Care website. ... View more

Not sure if others already have this but I got a new 'Try new version' popup today on the 'Get help & cases' page (now named 'Support Center').   It has the Recent Cases shown on that page with a link to go to the All Cases page ... View more

Apologies, @DarkStar - sometimes our automatic spam filter is overzealous. Your post has been restored. Also, status.meraki.net now reports the dashboard being down as a known issue under active investigation (I believe this is separate from the issue with the "Get help & cases" page though). ... View more

We have just replaced our MX84 -however I did see speeds of 400 (with the latest supported firmware). We have all the advanced security features.    With our new MX75, we are now getting 900.   Tests are on fast.com and dashboard throughput to Meraki.  ... View more

Did you ever get this resolved? I assume you are getting NAT traversal errors? I am having a heck of a time here. I was on MX 18.210, some of our equipment can't go that high. I had one site downgraded get NAT type B. I can go online with wordwide of regional, but if I try making a room I can, but I cannot join with another. This is with MK8. Very frustrating as we are trying to start e-sports leaques. ... View more

Hi,   Just to re-confirm if i have local AD then i make sure each MX authenticate with AD. all the VLAN default gateway is MX. So for eg. i have a user John, from HR, he logs on to his windows machine using AD credentials, and MX will be able to block youtube.come for John, similarly Andrew from HR gets facebook.com blocked even though both users are coming from HR Vlan but belong to different AD groups in AD?  ... View more

I may have found out something about the 1:1 NAT.  Apparently the 1:1 NAT will not even try to work if the destination is not in the ARP table of the Meraki.  And, in my case the destination device didn't seem to fill the ARP table in my short testing window.  After trying another destination device, it started working about 24 hours where it did not initially upon setup.  Very strange it takes so long to update the ARP table. ... View more

Hm.. You're right, @jimmyt234. Good catch. The setting applies to accessing the local status page on LAN devices that you are not directly connected it. E.g accessing the local status page on an Access Point that you are not currently connected to, but located somewhere else on your LAN. It does not reflect on the Remote Status Page on the Meraki MX. I apologise for the confusion. ... View more

Glad you got it working. 😄 ... View more

@jimmyt234 @cmr @Dalleman Thanks for responding. Conclusion: Failover of Meraki to Non-Meraki IPSec tunnels from Primary to Secondary can be achieved by TAG method mentioned. Better Option: Install a Meraki behind remote DC in customer 2 premises. Thanks a lot for your responses.   ... View more

Thanks Jimmy 🙂 ... View more

https://sites.google.com/meraki.net/merakitechtuesdays/recordings  ... View more

I would go up to .8, not down to .2 ... View more

I could request a support ticket 😂 😉 ... View more

Meh. I got so far as to generating an access token, after registering my app. But the EoX endpoint fails with "Developer Inactive", and this seems to be a known "issue", where one has to go through TAC to get that fixed according to Cisco Community. The apix.cisco.com/hello, seems to work, so something must be okay, though.   But this should be the way to do it. I just can't check it. Assuming the "app" is registered in Cisco API Console curl -L --request POST \ --url "https://id.cisco.com/oauth2/default/v1/token" \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data 'grant_type=client_credentials&client_id=[AwesomeClientId]&client_secret=[AwesomeClientSecret]' which returns the access token to be used in; curl --location 'https://apix.cisco.com/supporttools/eox/rest/5/EOXBySerialNumber/1/[serial]?responseencoding=json' --header 'Authorization: Bearer MyAwesomeAccessToken'   ... View more

I agree.  I feel this violates the "Meraki Simple" premise - the thing that all new GUI features should be measured against.   "Network-Wide" is more intuitive and simple to understand. ... View more

18.208 messed up something with our outbound network connections on older Linux kernels. Couldn't really pinpoint what it was, other than dropping a significant number of packets, making it appear like the VM was unable to communicate with the outside world. We ended up rolling back to 18.107.2 as well, and the problem went away. 18.208 is an absolute trainwreck of a release unfortunately. ... View more