Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About AlexG
AlexG
Getting noticed
Member since Sep 21, 2017
Oct 28 2024
Community Record
39
Posts
20
Kudos
4
Solutions
Badges
Oct 28 2024
5:41 AM
1 Kudo
It was in fact my JSON formatting.. Appreciate the confirmation that it should be working! I just rebuilt my function and got a successful response.
... View more
Oct 25 2024
8:27 AM
We started using combined networks and I need to rewrite some of the automation for setting up new sites. I'm getting HTTP 400 errors when sending an array of serials for MX, MR, and MS devices while using the L_####### combined network ID. I am finding no discussions around this specifically, so I'm wondering, has anyone else run into this? Will I need to pull the MX network ID per Deep linking to the Meraki Dashboard - Meraki Developer Hub – Homepage - Cisco Meraki Developer Hub & this API endpoint: api.meraki.com/manage/organization/administered_orgs? It's possible my JSON is somehow hosed, but I've look at it multiple times over the past couple of days and I'm just not seeing what the issue would be. Hoping someone here can confirm or deny that what I'm doing should work. Thanks!
... View more
Oct 4 2024
1:36 PM
Update your URL variable to include '?perPage=5000' or whatever number you're looking for. E.g. "https://api.meraki.com/api/v1/organizations/$orgID/networks?perPage=5000"
... View more
Sep 24 2024
7:00 AM
Got quotes back from our VAR and in this case, it doesn't make financial sense to drop down to the MX105 - even if it were recommended by everyone here. MX250 it is. Appreciate the responses here. Also, our Meraki rep did confirm that there are no known upcoming EOS/EOL announcements for either model at this time. Hopefully it stays that way through Q1 next year.
... View more
Sep 20 2024
12:58 PM
Per the sizing guide here: MX Sizing Guide & Principles - Cisco Meraki Documentation, I'd be well within the max allowed 1000 S2S tunnels.
... View more
Sep 20 2024
7:29 AM
Hey everyone, Looking for some advice here. We've got about 350 MX's using an MX600 today as a VPN concentrator (hub). It's basically there to facilitate routing and we don't have any security policies setup as that's handled via Palo Alto's. There's a relatively small amount of traffic traversing this - 50GB/day - with even less expected in the next couple of months as it will essentially turn into SNMP/syslog monitoring traffic only. The MX600 has been complete overkill for us, and I presume we could get away with an MX105. Though possible, I'm not expecting growth to surpass 500 MX's connecting in the next 3 years. We do use active-active AutoVPN with dual uplinks at all sites, but I'm not opposed to turning that back off. From my perspective, the MX250 was released in 2017 and the MX105 in 2021, so it would make sense that the MX105 has a newer architecture and would likely be supported for a longer period of time. Does anyone have any experience with a similar scenario and relatively recently purchased devices? Thanks!
... View more
Labels:
- Labels:
-
Firewall
Jul 15 2024
10:49 AM
Long story short is that we need to replace aging MX65s in the field and I need to understand the repercussions of using an MX65 90w adapter on an MX68. We do not have IT folks at each location, and I'd like to minimize the work needed so any of the employees can assist. Our network racks/cages are small and the power adapters for our MX's frequently get shoved to the back. Because of this, I'd like to be able to ship them an MX and just have them worry about the cables moving to the correct ports and not fishing out an old adapter. I'm sure the answer from Meraki support would be, don't do this, we upgraded the power for a reason. I also know that these are small sites where both ports are not pushing PoE+ and the MX has less than 50Mbps running through it. I also know we have a good 20 or so sites that are already operating this way today. Also, if we could please get screw on power connectors, that would be extremely helpful when having people physically moving around equipment that is all tangled up.
... View more
May 28 2024
6:07 AM
In our specific use-case, flexibility is not what we want. I've got customers who are capable enough to claim new devices to a network and add those to a template, but not savvy enough to know how to configure switch ports. Ideally, I'd preload a combined template in their Org with the 'golden' config in which they'd create new networks from. I can't add that combined golden config template for tens or hundreds of customers right now without this silly manual step of creating a switch profile.
... View more
May 21 2024
12:21 PM
2 Kudos
Maybe @John_on_API can answer as he's been the face of the API release updates as of late. Any word on the addition of the API endpoint for switch profile creation? For those of us with cookie-cutter networks, it's a real bummer that isn't available.
... View more
Nov 17 2022
9:13 AM
1 Kudo
Will these custom webhook templates be extended to Meraki Insight alerts? We're looking to integrate with Jira (Opsgenie, specificallly) and it seems there's no way to handle that currently.
... View more
Jun 16 2022
1:22 PM
We do have some WAN connections NAT'ing through the provider gateways (Comcast modems, Cradlepoints, etc.), however those subnets are not ones in use on the LAN side of our networks so I don't believe that to be the issue.
... View more
Jun 15 2022
7:39 AM
Greetings! I have been getting nowhere with both support and my account rep, so I'm hoping I can get some help from the community. We are currently rolling out MX68's to replace our aging MX60's. We're swapping these at a rate of about 20/week all remote sites. I have started seeing an increase in the number of devices experiencing this 'bug' that causes the MX to reboot. There's seemingly no rhyme or reason to the timing. Sometimes we can go 6 hours, other times it's only 15 minutes. The common event log messages are 'Ethernet port carrier change' for each port we currently have plugged in: I have our devices running the latest 16.16.3 patch, I also have a few of them running 16.16, I have one in my lab that my work computer is connected to running the latest RC 17.8, all still having the same issue. I worked with support who claims that the dev team has identified the issue and provided support with a 'backend fix' to help fix the issue. That device is running 16.16.3 and still is experiencing random reboots with the 'fix' applied. I'm at wits end here because it's causing an issue with our POS environment that's hyper sensitive to routing delays or failures, which happen when the device reboots. Has anyone else been experiencing these issues? Have you heard anything else from support or the dev team?
... View more
Sep 14 2018
1:54 PM
@PhilipDAth has the right idea, in my opinion. We had to bulk create 250ish networks some months back, and I used a fairly simple PowerShell script to hit the API and update the VLANs after the networks were created. I used a script to create the networks and add them to our templates as well but that's not always necessary. Powerful stuff once you get the hang of it!
... View more
Sep 14 2018
1:49 PM
'Connecting' is a pretty common thing we see with our MiFi 620 modems. For us, it generally means the signal strength to the carrier is sub-par, or simply not available. We've tried external antennae, but the RF loss is too great and it simply doesn't work. If it's possible to try a different modem with a different carrier, that may be your best bet.
... View more
Aug 30 2018
8:45 AM
@davidvan I did catch the new launch. It's definitely exciting that we'll have that as an option, but ripping out 900+ devices to replace with MX68C's is not feasible in the near future. We're going to continue looking for alternate options right now for our MX60/65 environment. Utilizing SD-WAN functionality seems like a far better solution than continuing to hold out for fixes to the USB modem logic. I just ran a script against the API again today for our environment, and I'm seeing 64 modems that list their state as 'Ready' with a 192.168.1.2 internal (non-routable) IP, along with 58 modems that list their state as 'Connecting'. That's a 15% failure rate, which is unacceptable.
... View more
Aug 16 2018
8:38 AM
@dustinnewby I have actually come across those modems once before. Do you have any experience with them?
... View more
Aug 7 2018
5:59 AM
@GiacomoS I appreciate the link, but we're moving away from USB modems. They are simply too unreliable. We have numerous cases in the wild where the state of the Cellular modem shows 'Ready', when in fact they've obtained an internal IP address (usually 192.168.1.2) and are not connected to the carrier network at all. There are other cases where the connection will be working one day, and then we find it sitting in the 'Connecting...' state the next. We've been told that engineering will not be incorporating these interfaces into the SD-WAN offering, which is a huge disappointment. We've also been told that there will possibly be an MX model with cellular built in, however this is not helpful when our MX devices tend to be located inside buildings that block cellular signal. We're really looking for a cost-efficient Ethernet 4G LTE modem.
... View more
Aug 6 2018
7:47 AM
Hello! I couldn't find a topic that addressed this exactly, so I'm starting a new one. It's pretty simple: What types of 4G LTE modems/routers are you using? We're wanting to move away from the USB cellular connections, but will never have budget for CradlePoints. This device would simply be there in case the main broadband connection failed. We don't need anything fancy, but I'm also trying to keep security in mind and not really looking to feed the next IoT bot. ConnectedIO has been recommended before, but with the rise of SD-WAN there HAS to be other vendors out there with solutions too. Specifically, I'm looking for vendors that have compatible devices for US - Verizon service. Any advice is appreciated! EDIT: Updated text per Philip's comment.
... View more
Jul 17 2018
9:02 AM
What's the value of the $api variable? My guess would be that you've got a malformed URI. The 308 errors I've gotten in the past have been related to using the wrong URL. The API docs say to use the prefix: https://api.meraki.com/api/v0 before the /organizations/... bit. You could always just 'Write-Host $uri' before you call Invoke-RestMethod to see what it's sending.
... View more
Jul 9 2018
3:45 PM
@PhilipDAth You're not wrong. My preference would be to start at the strongest cipher first and iterate it's way down to the weakest. I found a blog post or two regarding ways to work the snippet I posted above into the local PS profile itself, but when you have automation servers that are changing frequently, or ones that you don't manage, it's a real pain to mess with that.
... View more
Jul 9 2018
2:01 PM
4 Kudos
My scripts all started failing a week ago (ish) as well. There was a sticky post about the Meraki TLS change to the top of this board, but it didn't contain the PS fix. Try adding the below code to the top of your script: [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 Once I added this, it forced the connection to use TLS 1.2 and my API calls succeeded.
... View more
May 7 2018
12:59 PM
Forgot to add the follow-up on this one. Oddly enough, when I switched the link type on the Palo over to broadcast from p2p prior to the MX upgrade, every single route dropped out of the table on the Palo. Once I finished upgrading the MX, the routes were learned again and popped into the active routing table. Could just be a bug within the Palo software, but it was interesting nonetheless.
... View more
Apr 26 2018
5:34 AM
Well, I guess I learned something new. Thanks, @PhilipDAth!
... View more
Apr 25 2018
2:28 PM
Hello! I figured there's a small chance someone else may encounter something similar down the line, so hopefully this is helpful! We've got a multi-site environment with a primary and secondary data center. We have Palo Alto 3050's in place at each site that run OSPF. We also have MX600's that act as our VPN hubs for all of our 900+ spokes. The MX600's were running firmware 12.24. The MX600 at our secondary data center simply acts as a failover and we generally don't run any traffic out of it. While trying to upgrade the firmware on these MX's, I encountered an issue where the routes were not being advertised after the upgrade. Considering I had to perform the upgrade around 1AM, and we have workers coming into these remote spoke sites around 3AM, it got my heart beating. 🙂 After an hour on the phone with Meraki support, I ended up reverting the firmware in defeat. Fast forward a couple of weeks, and I had re-upgraded the secondary site's MX to 13.28. I wanted to do some testing, so I threw an older MX on our test bench and proceeded to block all traffic from it to our primary site via the Palo. Here's the real meat of this post: When the Auto-VPN kicked in and I saw the LSA messages coming from the MX to our Palo (via packet captures), I thought "Hey, this is great!". Upon further inspection, the LSDB on the Palo did contain the two subnets from this test network, however they were not in the active routing table. "What the..." I opened a ticket with Meraki, who once again said it couldn't be an issue with the MX since it's sending the LSA packet. I was skeptical, but in the end it wasn't actually their problem directly. I opened a ticket with our Palo support and found that from firmware 12.24 to 13.28, the code must have changed so that the OSPF Link Type needed to be broadcast versus p2p. Anyone with extensive knowledge into OSPF and Palo Alto's would have known they officially say to use broadcast when the interfaces are connected via Ethernet. We just missed that little detail. 🙂 I'll be upgrading our primary environment soon and will update the Link Type in the Palo along with it. I'll report back once I verify everything is all good.
... View more
Apr 5 2018
9:31 AM
I'm not going to offer up any insider information (because I really don't have it), but there have been rumors about Meraki releasing a security appliance with built-in cellular abilities in the near-ish future. If that is in fact true, I have a feeling that's where the focus/engineering is being placed at this time.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 75807 | Jul 9 2018 2:01 PM | |
| 8293 | Feb 19 2018 12:14 PM | |
| 10753 | Oct 26 2017 8:00 AM | |
| 8879 | Oct 23 2017 7:12 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 4 | 75807 | |
| 4 | 8879 | |
| 2 | 1261 | |
| 2 | 6426 | |
| 2 | 10753 |
© 2024 Cisco Systems, Inc.
