Now I can add the network object.   ... View more

My test was with a manually scheduled upgrade.  I can't simulate Cisco doing the upgrade.   I agree that a Cisco upgrade should be logged somewhere (even if in the event log).  I'm thinking it should be logged when the firmware upgrade is done, rather than just the scheduling of it - but at least - it should definately log it somewhere.   You will need to open a support case if you think this is a bug. ... View more

Nice... Glad you managed to get it resolved @FSaucedo  ... View more

They are channelling their inner Apple ... View more

Hi @Jobsp Thanks for that clarification.   The link provided to you has the ability to narrow down your SFP module and specify which models of switches work with the specific model.  Unfortunately your post didn't specify the full module (just 10Gig and LR type).   ENTER THE TRANSCEIVER PRODUCT ID and all compatible models will be displayed.     If you are looking for a LR type module that works with Meraki MS switches, the MA-SFP-10GB-LR is listed for your consideration, however the MS210 series isn't listed likely because it's not 10Gig compatible.   ... View more

Hi @chrisautomates - might even be worth holding off from the 9300’s and look at the 9350’s.  Newer to the market so more longevity.   https://www.cisco.com/site/us/en/products/collateral/networking/switches/c9350-series-smart-switches/c9350-series-smart-switches-ds.html ... View more

Hi @NishP there are two VPN status. Option 1: Organization >  VPN Status which isn't as detailed as option 2. Option 2: Security & SD-WAN > Monitor > VPN Status which allows you to see IPSec peers which I am assuming you are using with Fortinet in the equation. Give option 2 a try to see if it shows an IPSec Peer tab (as seen in @alemabrahao picture shared). VPN Status Page  ... View more

Had a similar delay with alerts recently. The messages finally came through much later than the actual event, which messed with timing. Using text messaging for quick updates is great, but these lags can throw things off. Ended up adding a small log to track the actual switch times so I could compare with when the SMS arrived—helps to spot if it’s a system delay or network issue. ... View more

It turned out to be a bug in the Cisco OS, we reloaded the Cisco switch and traffic is passed again. Looks to be a layer 2 issue.    Version 17.09.04a ... View more

If you click on a client, on the right-hand side, it shows all the firewall rules and policies that are being applied to the user.     ... View more

Content Filtering is quite effective at blocking access to content *prior* to it being downloaded - but you need an "Advanced Security" licence.   These are the categories I like to use. ps. I chose everything under "Threat Categories".   ... View more

Hi Raphael  This is a known issue that is resolved in firmware version MR 31.1.6 (Stable release candidate). Please upgrade the devices and let me know if the issue still occurs.   I just wished ( real bad ) that MR firmware would include more fixes instead of "General fixes and improvement". This would prevent me from opening a ton of cases.    Will try that firmware and report ... View more

My preferred solution is to run AutoVPN over MPLS. With this configuration, you don't require BGP.  The provider needs to provide the stub routing between all of their stubs, and that is it.   The only catch - something has to provide a single Internet access to the MPLS network for all the MXs to use the VPN registry system.  This can be done via the head office (or the service provider).   @RWelch has already provided the documentation link for this. ... View more

This kind of topology has worked fine for me. ... View more

If migrating the site to Meraki, in order to leverage AutoVPN isn't an option, you could use an MX as a termination point of the Non-Meraki VPN, and route that, statically or dynamically, into the rest of your Meraki topology. It would require you to buy another MX and create a "Gateway" network, which function as the entry point between AutoVPN and Non-Meraki VPN.  ... View more

If you were to click on the client with the long string you should be able to change the name by clicking on the pencil and putting whatever name you wish for this device.   Or you can set a DHCP reservation with the client device's MAC address and put a friendly name. Either way you can adjust the UUID client ID to a more friendly name.  The DHCP reservation would likely offer the best approach if this particular device connects to the network on a routine basis while it might seem like a bit more manual work upfront it will keep your device names cleaner (long term). ... View more

https://documentation.meraki.com/MX/Site-to-site_VPN/Configuring_Site-to-site_VPN_between_MX_Appliances_in_Different_Organizations   ... View more

Not quite the same, but if you have a "Secure SD-WAN Plus" licence, and it is a web app, you can monitor "web app health".     Search for "Web App Health" in this link. https://documentation.meraki.com/MI/MI_WAN_Health/MI_WAN_Health_Overview     There is also a more extensive Thousand Eyes agent integration coming.  I'm not sure of the licence requirements.     ... View more

Thanks for the correction @Ryan_Miles  ... View more

Wouldn't your entries need to be adjusted? D1: Security Appliance: 143.161.65.1/24 to 143.161.65.0/24 (subnet) or 143.161.65.1/32 specific device IP D2 Security Appliance: 143.161.64.1/24 to 143.161.64.0/24 (subnet) or 143.161.64.1/32 specific device IP ... View more

We’ve experienced the same issue after upgrading our switches to 18.1.2. Wireless clients connected were not receiving DHCP addresses. Once we rolled back to 17.2.2, everything returned to normal.   For context, SecurePort is enabled in our environment, and we confirmed the problem was isolated to MS130 switches only. Other switch families (MS225/MS250/MS425) didn’t show the same behavior, or at least weren’t affected in our case, as only four of our sites upgraded and we primarily use the MS130 range.   We’ve logged a case with Meraki Support so they can investigate further, as this seems consistent with the regression others have described here. ... View more

Your post didn't indicate what speed and duplex the WAN interfaces configured for (normally set to AUTO)?   By chance, have you changed either WAN interface from the default (AUTO) to something else?  And if so, did you manually change the other end to match the same speed and duplex you manually configured on the MX device? And if you'd somehow rather not say, then perhaps a tech can help you navigate all of this with a support case. ... View more