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 CyberDingo
CyberDingo
Here to help
Member since Mar 28, 2023
3 weeks ago
Community Record
18
Posts
6
Kudos
0
Solutions
Badges
Dec 8 2023
8:03 AM
Thank you for your thoughtful response and confirming my suppositions. I am very frustrated right now as there does not seem to be any realistic path forward, and Meraki support has not been helpful. I am not sure what to do next.
... View more
Dec 8 2023
7:50 AM
Thank you for the response. I appreciate your recommendations. Unfortunately this will not work as I am moving from a per-device license to a co-term license set-up and can't set one up in per-device Organization before moving it to a co-term Organization. In addition, our locations are so far spread out that we cannot reach all the locations to migrate them over in one day.
... View more
Dec 8 2023
6:23 AM
This is going to be a very specific question, but Meraki support has been giving me the run around without solid solutions, so I am going to ask here to see if anyone has any recommendations. My company is cutting ties from a MSP managing our MXs (SD-WANs) at all our locations (networks). We purchased all new devices and licenses to replace our current set-up. The goal is to replace all our current devices and licenses owned by the MSP with these new devices and licenses owned by my company. In addition, our MSP set our organization up as a per-device licensing model. We would like to switch to what the majority of users have, co-termination license model. From speaking with Meraki support, it is not possible to switch a an Organization, within an account, from a per-device license model to a co-termination license model, even if purchasing all new licenses for every device. The solution posited from support is to create an identical Organization, configured the same as the current Organization, and migrate all the devices over. After having done this and labbing the transition, I have found that Meraki requires VPN set-ups between Organizations to be created as "Non-Meraki VPN peers" even if they are both Meraki MX devices. They are not able to use the AutoVPN feature between Organizations. The problem I run into with this is that we are hoping to slowly migrate our Organization over one network at a time, as our I.T. team is centrally located and cannot be at all locations within my company at once. This creates the main problem; the "Non-Meraki VPN peer" does not account for MXs that use dynamic public IPs, and therefore have changing IPs. We have a few locations that are not static IPs, and I do not want to lose connectivity when they switch IPs. Our sites have to be able to VPN with each other. I admit that this could come down to me not fully understating the IKEv2 ability to connect via hostname. I've read the KBAs but it still is not clear to me how to use Local ID and Remote ID. In addition, this can get very complicated trying to handle the two Organizations with same subnets not conflicting with each other. Right now I feel stuck. I am not sure how to move forward with this migration. If anyone has any recommendations, I would greatly appreciate it.
... View more
Sep 6 2023
5:47 AM
As always, thank you for posting.
... View more
Aug 18 2023
6:40 AM
2 Kudos
This is now a stable release.
... View more
Aug 16 2023
5:11 AM
18.107.4 is a patch. If memory serves me right, usually you have to update and then patch when moving to a new version number.
... View more
Aug 16 2023
5:10 AM
1 Kudo
MX 18.107.4 is now able to be upgraded from 18.107.2 in the dashboard.
... View more
Aug 15 2023
5:40 AM
Not yet. But to be honest, we changed it yesterday, so it has not been a full work day yet to see any hiccups.
... View more
Aug 15 2023
5:39 AM
Thank you. I was able to fix the problem by changing the Client tracking to "IP Address."
... View more
Aug 15 2023
5:38 AM
I was able to fix the problem by upgrading to v18 and change Client tracking to "IP Address." The problem was the new Content filtering changed in v17 was not working well with my internal L3 routing.
... View more
Aug 15 2023
5:34 AM
1 Kudo
@Oderbang We were able to get it working by updating and switching Client tracking to "IP address." Thank you for your work on this and sharing the fix with the community.
... View more
Aug 1 2023
8:01 AM
1 Kudo
Please fix the issue with the Content Filter loading web pages slowly if there is a L3 device within the LAN. This has been a problem since v17 and is preventing many of us from updating our Meraki SD-WANs.
... View more
Jul 25 2023
6:14 AM
1 Kudo
Hey @JonP, glad you found a way to get it working for your team. Looking at the documentation for it, it does look like "Unique Client Identifier" fits our situation: The problem I have is that on all my other sites that are functioning that have been upgraded to v18; they do not have "Unique Client Identifier" as an option. They are of similar model as the problem site (MX100):
... View more
Jul 25 2023
5:57 AM
Commenting so I can follow this post. We are experiencing the same problem. Thank you for researching it with Meraki. We have one site that that has a L3 Switch (which is Meraki brand) within the LAN that processes routing that is having this problem with the Meraki. All our other sites are not set-up like this and are not experiencing this issue of slow web sites loading when a user goes to a new web site (a URL that is not yet cached). As of version 18.107.2 we are still experiencing this problem and we had to roll back to v16.16.9
... View more
Jul 25 2023
5:49 AM
Thank you for the recommendation. I tried disabling Web Cache and it still shows the same problem. After scouring this community page, I think the problem shows itself when the Meraki passes to a L3 device within the LAN. In my case it is a L3 Switch, but I have seen others say they have the same problem with a L3 VPN Concentrator. As of version 18.107.2 the problem persists. I hope Meraki can address this issue.
... View more
Jul 21 2023
1:20 PM
Are you still experiencing this problem because I am. 😞
... View more
Jul 21 2023
1:01 PM
I don't know about others, but I am still experiencing this issue with v18.106.1 and v18.107 😞
... View more
Mar 28 2023
1:21 PM
When I update the firmware of my Meraki MX100 SD-WAN Security Appliance from it's current version of MX 16.16.9 to 17.10.2 it seems to work fine, except for this strange issue. Any web search for a new website takes an unusually long time to reach. After the first time, however, any subsequent loading of the web site (or any site within the web site's domain) runs at normal loading speeds. I assume this is due to DNS caching. I have tried updating to 17.10.4 and have experienced the same issues. When calling Meraki tech support, they recommended me rolling back to 16.16.9 (which is what it is currently at). Has anyone else experienced this issue, and/or has found a solution to this?
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 647 | |
| 1 | 935 | |
| 1 | 5143 | |
| 1 | 2942 | |
| 1 | 5534 |
© 2024 Cisco Systems, Inc.
