r/meraki

Hello,

I have a Meraki MX95 that is alerting blocks in the event log for adult sites, but the IP address is showing the wireless AP they are connected to and not the client in question.

How can I find the client device that is accessing these sites?

Hello,

My company bought several APs and we received an order claim code in the format of \#1A2B3C4D5E6F. When I try to claim these devices, I can only enter a code in the format of XXXX-XXXX-XXXX. I tried modifying the order claim code to fit that format, but no dice. All the documentation I could find (even on Cisco/Meraki's KB) refers to the old portal. The new portal seems to be missing the option to claim an order. Claiming licenses works just fine. Anyone know what I am doing wrong?

Does this SW version have really bad issues with the AP 9171, or am I just crazy?

Problems like randomly disconnecting clients and not letting them reconnect? (Only fix is rebooting the AP.)

Problems like clients connecting but not passing any data? (Fix is toggling Wi-Fi on the iPhone.)

I’ve been using this AP since February… sometimes it works, sometimes it just doesn’t. I tried different settings, and in the end I even went back to basic WPA2-PSK. Still not working properly.

Just replaced this shitbox with a 2802 again.

Wondering what everyone is replacing their home Meraki gear with now that CMNA renewals were killed off?

Good Afternoon everyone.

I use a pair of 9300X as our aggregation switch to all of our campus buildings.

The recommended firmware now is IOS XE 17.15

Currently on CS 17.2.1

Any gotchas on the firmware change? We mange and configure the 9300x’s with Meraki.

Just checking in before we make the switch.

Hello, I have a Meraki MS120-8LP switch and I want to assign it a static IP address through its web interface. I performed a factory reset, but I can't connect to 1.1.1.100 as the manual indicates. My PC has the IP address 1.1.1.99/24 and the DNS server 1.1.1.100, but I can't access it. What could be the problem?

To anyone who has deployed a vMX to Azure in the past couple of years: did they ever work out the issues with vMX deployment in Azure where you might have to deploy repeatedly to get it hosted on hardware that didn't cause a TON of latency? I forget the specifics of the hardware that was causing the problem but definitely recall deploying a couple of vMX's repeatedly (10+ times each) before we got one that was usable. Azure has likely replaced whatever server platform was causing the problem - I think it was older hardware then, but it was still in the majority based on the number of times we had to redeploy.

Is there a way on the MX security appliances to only allow incoming connections from say the US, but allow outbound connections to all but a handful of locations?

Want to only allow US connections for client VPN. And yes, do have MFA on VPN (using SAML through Entra).

When I was looking at layer 7 rules, it says to/from on that rule, so I'm guessing it is going to block both ways including established outbound connections.

Appreciate any nudges in the right direction.

So I consolidated two houses into one, and one WAP is moving to the network of the other home. I deleted it from the Meraki Go account for the old home, and am now scanning the QR code on it to add it to the new home, but it says "Already Claimed." How do I work around this?

Wondering if anyone has ever seen anything like this or has any ideas what could cause this.

We have an office that has a total of 6 Meraki MS350-48 switches. They are in two stacks in two separate locations. Two switches in one stack upstairs connected to an APC UPS with an MX and some servers. The other 4 switches are in a stack in a warehouse connected to a PDU in a rack. Two CAT6 runs connect the two stacks.

Late last week we suddenly had the site go down and started troubleshooting. It turned out one of the switches in the first stack was down and simply would not even boot up - power supplies cables etc all good but switch won't even power on. We move the uplink to the other switch but it won't link up - like no link light even. The MX is on and all good - reachable, hasn't gone down etc... We notice some of the link lights on the switch seem weird - like the right half of the switch has some link lights on on ports with no cables and some ports won't link up at all. But roughly port 1-24 seem to have normal link lights so we move the uplink to port 24 and voila it links up and gets uplink. We also move the downlink that goes to the other stack to one of these ports and it also lights up. So of these two switches one is dead and one has half the ports completely failed. We even troubleshoot with Meraki on the phone and this is the result. No firmware updates or power outages seem to have occurred.

So this isn't even the end of the story - now the other stack. Similar story - the entire stack is offline - switch-1 has dead ports including the stacking ports. Switch 2 and 3 are the same. Switch 4 is offline and won't even power on. We end up replacing all 4 switches in the second stack as well to get everything back online.

Out of six switches, two are completely dead and four others have ports dead we can't get to work - even after reset. They were in two separate locations and some of them were on a UPS. We've had the occasional switch fail before but how can 6 switches all fail at the same time? Nothing else at the site seems to have had any issues.

Good Afternoon,

A Cisco rep emailed me in regards to four APs on our network, MR18s, being EoL. The rest of our APs are MR44s which are not EoL. We currently have an active agreement with Cisco.

What's stopping me from buying four new (or used but unclaimed) MR44s from eBay, removing the MR18s, and putting the MR44s in? I can get four MR44s for the price of one new Meraki AP. The MR44 serves us well in our environment and we don't have a need for anything with more capabilities at this time.

Thoughts?

I've got a client that moved to Meraki a while back.

They just purchased a bunch of C9300L coming with the cloud managed firmware. Some of these will be stacked using the C9300L stacking kit. What's interesting is the order for the stacking kits and cables actually state "MERAKI".

I've been following the documentation since Jan. for changes to Meraki cloud management for these switches and TBH, the documentation is confusing.

My questions:

1. Can I pre-provision & pre-configure the switches that will be stacked?

2. I believe standalone switches can be pre-provision & pre-configure. Am I right?

The plan is the pre-provision all the switches, pre-configure them, then once onsite assemble everything, perform any firmware updates / stacking requirements and then connect and *HOPE* the pre-configuration works.

Thanks in advanced!

Hey,

I'd like to use an MX for my homelab / home setup. I got an unclaimed MX64 at a very good price. Now I am searching for a reseller in Europe (specifically Germany if that matter).

Could you recommend any?
I contacted two different companies, but unfortunately they only sell to businesses.

I am aware of the EOL next year.