Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- About RickA
About RickA
RickA
Here to help
Member since Sep 24, 2021
Mar 20 2024
Community Record
16
Posts
2
Kudos
1
Solution
Badges
Mar 20 2024
2:03 PM
Thank you for the ideas, I don’t believe a 30 minute down window is ideal but your second idea provides a much better approach (nice out of the box thinking). In the end I’ve found we don’t have the “Device Boot” Feature yet…imagine 3 months from rollout and the phased in approach hasn’t arrived in our Dashboard yet. Hopefully soon and thank you an all the respondents — I appreciate each of you immensely!
... View more
Mar 20 2024
12:55 PM
Yes, in large deployments where many shop floor devices (iPhones, tablets, kiosks, handheld barcode scanners, equipment monitoring, etc.) are moving around from AP to AP they build up the cache table which begins making them get a little flaky after a while. I've been in shops all around the U.S. where they don't use as much Wi-Fi moving devices, primarily stationary so this does not pose as much of an issue. However, when you have management team members, supervisors, inventory control specialists, etc. moving all over the shop their devices change APs frequently and sometimes cause more cache table entries and thus the connectivity problems occur. However, we are way off topic for this thread...LOL.
... View more
Mar 20 2024
12:05 PM
Doing some further research, it appears we have a mix of Meraki Access points running two different firmware versions. The latest APs are operating at version 30.6, whereas the older APs are operating at version 26.8.3. The new "Device Boot" feature is only available to APs with a firmware version 30 or higher. It is possible with the mixed environment this feature is not available in our Meraki Dashboard. Next option ?
... View more
Mar 20 2024
11:55 AM
Unfortunately, a script running only logs if the script ran and is not able to track the physical power cycle of the AP. I do already have a script which tells me if my batch file was successful, but CMMC compliance requires an audit trail such as a Meraki Dashboard report detailing date/time of an AP recycle. Great thought again, and I love the thinking here.
... View more
Mar 20 2024
11:38 AM
I believe "ww" responded similarly, but we do not have the "Device Boot" choice within our filters. Even if we try to type it in manually, it will not take since there is not choice available. It is possible this new feature has not yet been deployed to our Meraki Dashboard. I sincerely appreciate the replies from everyone and am continuing to research an answer.
... View more
Mar 20 2024
11:30 AM
This is not an accurate statement, I didn't want to make this a novel so I didn't elaborate how the restarts occur. We have a regularly scheduled batch file which runs every Sunday early in the morning. However, we need to ensure the reboots occurred within the Meraki Dashboard as part of our compliance and auditing requirements.
... View more
Mar 20 2024
11:28 AM
I'm finding no such event type as device boot in any of the choices available but that is a great thought.
... View more
Mar 20 2024
7:49 AM
During the last several years we have found the need to restart our Meraki Access Points weekly. These restarts appear to clear the cached entries and allow a more optimal connectivity during the work week. We are attempting to review regularly that these planned restarts are occurring. However, we are unable to find any reporting or page which shows the last Access Point restart for each Meraki AP. Is this an available feature? NOTE: The only way we have been able to find the restart is to create a case with Meraki, and allow Meraki Engineers to tell us the last restart for each AP.
... View more
Oct 28 2021
4:00 AM
Pertaining to our two issues (1) AD authentication using SM Agent 3.1.1, this issue appears to be resolved. However, we have not received word from Meraki what the root cause and fix are as of yet. For our second issue (2) unable to create new Meraki Case within the Meraki Dashboard, this issue appears to be resolved. However, we have not received word from Meraki what the root cause and fix are as of yet.
... View more
Oct 25 2021
2:34 PM
@EPSD_Robert - You are correct, the "End User authentication settings" is indeed where you setup how your users authenticate. The "AD gateway type" is where you setup your SM Agent to use Systems Manager installed on a Windows/Mac machine. Although we have the latest version, something we believe from the Meraki side broke and no longer works with this agent. Meraki Developers and Support confirmed this was the case, since they were able to reproduce the issue. Unfortunately, another Engineer was working our case since I personally was doing some fire-fighting with staff. I believe Meraki had tested bypassing AD authentication by going directly to the MX (firewall), but I'm not 100% sure of the location to make that change. Just wondering if others were experiencing this issue and what steps they have taken to resolve. I appreciate your feedback, and will try to add any new notes from our Meraki Development team we may find.
... View more
Oct 25 2021
2:23 PM
1 Kudo
@PhilipDAth- if your Meraki equipment is on a private network, and you allow users to "authenticate" for security sakes and to ensure not just anyone can get into your system you have to have some type of authentication method. We chose AD Authentication, which allows us to point our Meraki Dashboard to a network server. Within this network server you need to setup the Meraki Agent (latest version is 3.1.1). This ensures you restrict access to your network and enforces group policies based on membership in Active Directory groups. In the event you were replying to "Creating a Meraki Case" these are Meraki accounts (AD authentication is the other issue). We have actually had three separate administrators all attempt to create a new Meraki Case and could not do so. We ended up calling into Meraki Support several times, always waiting for at least 30 minutes to have Support team members create the case for us. As outlined in my post, there are two separate issues.
... View more
Oct 25 2021
12:10 PM
Early last week we found that AD authentication was not working with a local network server and the Meraki Agent (ver. 3.1.1). We also attempted to create a case through our Meraki Dashboard and found we are unable to do so. We have placed numerous calls to Meraki, and have been waiting for approximately 4 days now to have the Meraki Developers look into this. Issue 1: we are unable to use AD authentication to the Meraki Agent (ver. 3.1.1) on a local network server. We rebooted the server, we have removed Windows patches installed approximately a week earlier and we can authenticate through the MX directly instead of the Meraki Agent. Issue 2: we are unable to create a new Meraki Case through the Meraki Dashboard. Anyone else experiencing similar issues, and have you been able to find a resolution? We know Meraki is working heartily on this, but this waiting game is much too long as we need to add several new devices and unable to authenticate properly.
... View more
Labels:
- Labels:
-
Other
Sep 27 2021
8:48 AM
@MarcAEC just a small correction, we are not having difficulty reaching the websites outlined. If I recall correctly, it is @putt4show which is unable to reach those websites. As a potential solution, I would suggest temporarily removing Hong Kong and/or Singapore from your Layer 7 "deny" list and saving. Then you can immediately add it back in and save the changes again. Our organization does indeed block both of these country communications, and we can reach those websites today!
... View more
Sep 27 2021
8:34 AM
@putt4show We also block almost every country outside of the United States, and yes we have Hong Kong blocked in our Layer 7 rules. I just wanted to let you know and can confirm, we are able to access both of the websites you listed. I'm certain this seems as though it is a strange coincidence, but Meraki is definitely not blocking those websites and is definitely not seeing those website IPs as China/Hong Kong. POSSIBLE SOLUTION: Just for the measure of testing, try removing Hong Kong from your Layer 7 rules and save. Then add it back in and save.
... View more
Sep 27 2021
8:14 AM
@putt4show Both of your listed websites are working for our organization, and we are full Meraki Cloud deployed. If these websites are not working for you it has to be something other than Meraki. Websites you listed are http://ontargetrange.com/ https://officesolutions.com/log-in/
... View more
Sep 24 2021
1:14 PM
1 Kudo
We have also confirmed, adding Hong Kong back into our Layer 7 "deny" list works fully by still allowing access to www.google.com, www.youtube.com, etc. MERAKI: An email notification or updated Meraki Dashboard banner would have been helpful.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 1716 | Oct 28 2021 4:00 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 1 | 1806 | |
| 1 | 29672 |
© 2024 Cisco Systems, Inc.
