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

Hi Phil   That worked an absolute charm. Seems almost too good to be true! Now, if I log in to Windows with my MS365 ID, I can connect the AnyConnect VPN without any further authentication required.    I'd up the kudos points by 100 if I could, but it'll only register one!   Thanks very much. I know where to come now if I need a Cisco consultant in New Zealand! ... View more

The Palo is too complex for us.  But yeah, I do need basic features and I'm finding out the MX is missing them. ... View more

Probably not quite what you're after, and a bit of a hack: but if you've got more than 1 MX in the network then you can configure the VPN client differently on each one and get the specific users only to connect to the relevant MX. ... View more

To expand on this, create a layer 3 outbound firewall policy to block these ports that @RaphaelL says above:   ... View more

I was using it as a URL that was set up by default. I don't know at what point it started not working, but I recognized it after the customer asked me, and I didn't change any settings until this point.   there is some NAT rule due to something service related to voice. However, regardless of this, the DNS call response worked normally, so there was no problem in trying the Anyconnect SSLVPN connection through the URL.   I also change local DNS from Private IP to 8.8.8.8 and tried DNS query. But It was still no working DNS reply. ... View more

What..................................................... I really wish all these secret options they can configure for us is made public knowledge somewhere. How are we supposed to know?! ... View more

https://status.meraki.net/incidents/dp7jydl8v5c4   Probably related to this ongoing incident. ... View more

Okay. Thanks for the info. ... View more

Hi Again... Do we have someone that can help with this issue?? Best regard Goran ... View more

I see. didn't take the Azure remote subnet into account.   Thanks to you all... I will def look into the vMX.   ... View more

You are right, but then it would mean that they have, all of the sudden, so much to do, that they can't respond to pings. @AxL1971, think you need to double check your wiring, configs and maybe open a support case if it doesn't make sense, what firmware are you on?   BTW - I'm having trouble with ping responses on MS425 since upgrading to MS15.x. At full hours (like 8:00, 13:00, 19:00) the response times to pings would rise up to 1000ms for no reason, last maybe a minute and then return back to normal. Support is on it, since over a month and they don't see anything weird in the network and are unable to replicate in their lab, despite us seeing this in multiple locations. Never had this weird thing in previous versions. ... View more

I agree with @jimmyt234. MX-105 should be deployed in HA. Primary and secondary internet links should be terminated on the warm MX router so that they can manage their fail over in case one link goes down and the tertiary link should be terminated on the spare MX so if both primary and secondary link goes down traffic can be shifted to spare MX router and tertiary link can be utilised.  ... View more

You can achieve this with group policy rules against the client, best implementation is done via AnyConnect with RADIUS auth:   https://documentation.meraki.com/MX/Client_VPN/AnyConnect_on_the_MX_Appliance#Group_Policies  ... View more

Appreciate the post. This does creep up on people in certain situations. And, I agree it should be configurable by the end user (of just off by default).   If you have a Meraki SE that supports you I would provide them this feedback so they can roll it up to the powers that be. ... View more

As is said above, check your WAN failover behaviour. As a side note, if the network is templated, you can't change the behaviour. It is hard configured to graceful. ... View more

Or ! You could be really creative.     1- Create network tags for your WAN speeds. Eg : Network 1 : TAGS : ['Wan1-100-100',Wan2-50-50']  That would indicate Wan 1 Speed of 100Mbps Up and 100Mbps Down. Same for Wan2. 2- Insight  -> Alerts -> Create an alert for EVERY single WAN Speeds by selecting the appropriate network tag :      If you only have 2-3 ISP with 1-2 speeds , that can be done easily. Otherwise it's hard to manage and maintain.  ... View more

thanks for the confirmation 🙂 ... View more