Glad it worked for you. ... View more

This reminds me of this bug fix: Makes me wonder if the same thing need to be applied in a future firmware release for the MS130 series... 🤔 ... View more

If you have VSAN then I'd either stop the VMs for an upgrade or break the stack into two pairs so that only one connection to each server goes down at a time.  I used a stack of four, but has FC connected SANs at each site, so no issues there.  Simply disable DRS before the switch upgrade and reenable afterwards. ... View more

Hi @rhbirkelund, @KarstenI, and @PhilipDAth, Thank you all for your valuable insights! I really appreciate the time you took to share your recommendations on how to best connect and secure the MS130-8. I wanted to share our planned approach based on your feedback. Planned Changes for Securing the MS130-8 1️⃣ The MS130-8 remains a managed WAN switch (no changes in hardware). 2️⃣ Local Status Page will be disabled by default for security. 3️⃣ Emergency access to the Local Status Page will be restricted to a single port on a dedicated Management VLAN 4️⃣ Firewall rules will be put in place to restrict management access, blocking unauthorized traffic from other VLANs. 5️⃣ Meraki Dashboard connectivity is currently routed via the internal network, but we will first check if we have spare public IP addresses available before deciding whether to assign one.   Thanks again for your valuable input—I truly appreciate the expertise and best practices shared by the community! ... View more

I strongly agree with your comment.  Most problems come from client issues if RF is OK. ... View more

Moderator note: Moving this thread to the MX board; seems like the likely best place for it. @MicJameson2 please let us know if you are indeed using Secure Connect, and I'll move it back if so. ... View more

Going sideways, if you use SAML authentication, you can't be locked out. https://documentation.meraki.com/General_Administration/Managing_Dashboard_Access/Configuring_SAML_Single_Sign-on_for_Dashboard   ... View more

Hi,  Sorry for delayed reply. Most I know of in our customer base is maybe 10.  Since Meraki is vague at best re the root problem and solution, can't say if 25 will be fine - guessing so.  The more active translations you have (port contention) the more likely you are to have issues.  May have to restart switches over and over until the ports they use locally can align with the ports the MX has available to NAT. ... View more

Offline is including the end devices, with the switch lights turning amber. The problem seems to occur when either fibre cables used as uplinks to the core switch gets pulled out and back in. Oddly enough, if we unplug and then plug back in either fibre, the stack comes back online.   I'll need to check the root priority and understand the process before making any changes. Our network setup exclusively uses Meraki switches, so no non-Meraki devices are involved.   I've sent a TAC request but unfortunately, it's been over 24 hours with no response so far. Additionally, the connection to the dashboard is lost, and the switches show as offline.   Regarding the firmware, when we set up the switches in August, we often had to restart them multiple times to bring the stack online. They never seemed to come online straight away after a reboot without needing a hard reboot once or twice. Sometimes, we let one switch (the root of the stack) come online first, and once it's up, we plug in the others. Because of this, we're hesitant to take any risks in the evening ... View more

I would be interested to know how your RMA swap goes, @Stephen_P . Meraki support had suggested that for us at one point, but we resisted because our issues were present regardless of which member of our HA pair was acting as the primary unit.   We haven't run into the MX device reboot issue, though the issues that have been plaguing us for almost the past year seem just as bad sometimes. We have been seeing random drops of our WAN connections at seemingly random times during the day (all WAN traffic stops for 1-3 minutes). We've also been fighting a problem where the MX stops passing certain traffic, and we have to modify a firewall rule (any firewall rule) to get it to start passing traffic again. At least for that issue, I can proactively "poke the firewall" each morning, and that seems to keep that issue at bay for the most part. I haven't found a way to prevent the WAN drops, which can be nearly as challenging as a device reboot, but "thankfully" only happen a few times a week. ... View more

When you say vanity url, do you mean simply putting e.g dashboard.meraki.com as the logout url? ... View more

Thanks a lot! ... View more

yes looked it up seems to be working only with the switch(wired devices), couldn't make it work with SSID's ... View more

Just to be super clear. The Meraki kit is used in the two depot networks, not in the back end WAN. Each depot has an MX68 and some MR access points. ... View more

I have no experience with Forescout.  Typically with RADIUS servers you can add a subnet (e,g. 10.0.0.0/8) and provide a configuration for every device in that subnet.   You shouldn't need to say what kind of device it is.  The RADIUS request says what kind of authentication the device requires (such as wired or WiFi 802.1x). ... View more

Hi,   Same problem here, but with Cloud VPN on Google Cloud ... View more

Was more thinking if Wifi is still active then device is more likely to continue background tasks including things like photo syncing which do make devices warm.  ... View more

Thanks! Right now I'm just speculating in advance, when the time comes I'll get in touch with support and/or my account manager and see what looks best. ... View more

For my environment, and most likely other environments, Ansible most likely is going to be installed under a virtual environment, I have noticed this if you use pip to install Ansible.   Please use my photos for reference.   In photo two, the output of ansible --version, you see the "ansible python module" that is where python is looking for the library always. But in the output of my photo 5, "pip install meraki" You can see that the location it is placing it is not the same. My solution was to use the cp -R and place it in the virtual environment. Basically the default location the python modules are going to is the similar path structure as the virtual environment. So for example, the commands are going to look similar to:   cp -R /usr/local/lib/<your python version>/site-packages/<package, i.e. urllib3> /home/<your username>/.local/pipx/venvs/<your virtual environment>/lib/<your python version>/site-packages/<package, i.e. urllib3> cp -R /usr/local/lib64/<your python version>/site-packages/<package, i.e. aiohttp> /home/<your username>/.local/pipx/venvs/<your virtual environment>/lib64/<your python version>/site-packages/<package, i.e. aiohttp>       You can run pip install meraki again to get the packages needed, and where they installed it to. Please pay attention to keep the lib and lib64 directories the same so you dont place them into incorrect directories.   To ultimately avoid this in the future like if you were to install it again is to run the source command and enter the virtual environment, and then install it that way. If you install the python library not in the virtual environment first, then any time you wish to install it through the virtual environment it will say its already installed.  I hope this explaination helps you. ... View more

yeah you are right. This was the conclusion of my old 2023 case :     This means that if the MX receives DNS responses for 2 different URLs that share the same IP address, the latest DNS entry will override the previous one; the previous entry will not re-populate the DNS table of the MX. ... View more

will try to ask support, thank you   ... View more

Thanks  ... View more

Since removing an erroneous sign in a string is apparently a >6 months task for Cisco, LibreNMS has been patched to resolve this issue:   https://github.com/librenms/librenms/pull/17065 ... View more