Meraki

Brash · ‎Sep 7 2023

As is said above, check your WAN failover behaviour. As a side note, if the network is templated, you can't change the behaviour. It is hard configured to graceful.

Brash · ‎Sep 6 2023

As far as I'm aware this has historically not been the case. It's possible they are doing this now as it looks like Meraki will soon be changing up their licensing where an MX64 and MX67 will use the same license SKU https://documentation.meraki.com/General_Administration/Licensing/Meraki_MX_Subscription_Licensing

Brash · ‎Sep 6 2023

🤦 Yep, "Noting" was definitely what I was going for. Autocorrect has some other ideas. 😄

Brash · ‎Sep 6 2023

Nothing that this doesn't apply to individual switches within a stack. They must all be in the same network and will all upgrade simultaneously.

Brash · ‎Sep 6 2023

Your best bet is to delete the stack, recable and build new stacks. From a config perspective, not sure what you mean about getting the existing config. I can't recall whether deleting the switches from the stack factory resets them or whether you need to do that manually to clear the old config.

Brash · ‎Sep 5 2023

Currently there's no way to migrate licenses between device types. An MX64 license is specific to that device and is not transferable to an MX68. I suggest talking to your Meraki/Cisco sales rep to see if you can get a cheaper deal on the new license.

Brash · ‎Sep 5 2023

Engage a trusted partner for the design work. If you are the partner working on behalf of the customer, reach out to your Meraki rep. They can probably tee up a session with some technical folks to help get the deal over the line.

Brash · ‎Sep 5 2023

I'm not aware of Meraki boxes containing the Mac addresses on them. Here is a photo of an MR33 box for reference.

Brash · ‎Sep 4 2023

My guess would be that the tool doesn't know how to test/interface with Meraki equipment. Meraki gear isn't accessible via SSH

Brash · ‎Sep 4 2023

In that case, I'd start at layer 1 and look at swapping out patch cables/SFP's on that link.

Brash · ‎Sep 4 2023

It's more than likely the STP event is a symptom of the actual problem which is the port going down. What is the port connected to? Do you see anything in the logs on the that connected device?

Brash · ‎Sep 2 2023

You'll need to ask your colleague to remove it from their organisation so that you can claim it into yours.

Brash · ‎Sep 1 2023

No, they can't be used in content filtering. Network Objects/Groups can be applied in the below firewall rules: Individual and Template Networks: Layer 3 Inbound, Layer 3 Outbound, and Failover Cellular Firewall Rules Organization-wide Site to Site VPN Outbound Firewall Rules https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Network_Objects_Configuration_Guide

Brash · ‎Aug 31 2023

There's no hard and fast rule. It's all about airtime rather than client count. There's technologies that theoretically maximize the amount of available airtime for clients (Eg. MIMO) but it may not always see real world benefits as much of it is clients based. Finally, there's the amount of data a given client is trying to transmit and how frequently/infrequently they will be needing airtime to transmit/receive. I've always really liked this video as a good explainer of some of the basic concepts and calculations: https://youtu.be/U31fQGCsmKk?si=rUHOU32H463jEEzj All this boils down to, overspec or understand your requirements very clearly and engage a wireless professional. Personally, for a typical office based working area, my rule of thumb is ~25 devices per AP.

Brash · ‎Aug 30 2023

Is anyone across changes to Meraki licensing? Or is this specifically for the MSP Portal? A bunch of new documents have been created around what looks like changes to the existing licensing model. The main differences I've seen are: Licenses are now added to subscriptions, and networks bound to a subscription. The idea being that you can have multiple subscriptions within a single org, with different networks bound to different subscriptions. Products are licensed using more generic SKU's. Eg. Both an MS225-24-HW and an MS320-24 can be licensed with the same SKU as they're both classed as 'Medium' switches. Going out of compliance only impacts the specific subscription that is out of compliance and the networks bound to it, not every network in the org Links to new docs: Meraki Subscription Licensing Overview Meraki Subscription Licensing - Subcription Claim Meraki Subscription Licensing - Network Binding Meraki MG Subscription Licensing Meraki MX Subscription Licensing Meraki Z Subscription Licensing Meraki MS Subscription Licensing Meraki MR Subscription Licensing Meraki MV Subscription Licensing Meraki MT Subscription Licensing Meraki SM Subscription Licensing

Brash · ‎Aug 29 2023

The port is used to access the local device management page which lets you make some very basic changes. It's purpose is to help you to get the switch connected to the Meraki cloud if you've made a bad config change or need done specific config during initial setup.

Brash · ‎Aug 28 2023

As others have said above, it it's entirely expected. My 2 cents: Whilst I do see there would be logic in only disabling devices which are in overdraft, it then would require some sort of logic to decide which devices are taken offline. Additionally, if it's a switch license that's in overdraft, it going down could take down all of your attached AP's, or your core network etc. While it might save done parts of your network from outage, it becomes messy quite quickly and may not be entirely obvious to the network admin what the problem is. The easiest way (arguable whether objectively the best or not) is to bring everything down which will certainly tell the network admin there is something going on and to check the dashboard immediately.

Brash · ‎Aug 28 2023

Could be a faulty device or need a factory reset. There's a community specifically for Meraki Go here. They might be able to provide further insight. Otherwise you might need to contact Meraki Go support.

Brash · ‎Aug 26 2023

Check the event log for L7 rule matches. Temporarily change the printer L3 rule to any to verify whether additional ports are required to be open

Brash · ‎Aug 25 2023

Bad cabling. For a short, probably poorly terminated at the patch ports but could also just be a bad patch cable. Start replacing cables or cable testing the runs to confirm

Brash · ‎Aug 25 2023

That would be your issue. The Meraki dashboard logs into the device via Netcong (over SSH) to pull data. What does your running config look like? Did you have existing config on the switch before integrating it with the dashboard? What privilege is the Meraki user account configured for on the switch? Do you have ACL's set up for SSH?

Brash · ‎Aug 24 2023

Assuming you have an SD-WAN Plus license, you should be able to setup SD-WAN policies to direct Site-To-Site VPN and Internet traffic to the respective uplinks.

Brash · ‎Aug 24 2023

Sounds like a couple of issues going on there which may have a deeper underlying problem - especially if data isn't pulling into the dashboard. I'd reach out to support on this as they'd be able to get a clearer idea of what is going on.

Brash · ‎Aug 24 2023

From the above output, the clear majority of network traffic from that client is SMB file sharing. If that's an unexpected usage amount, you'll have to get a clearer idea of what they're pulling down from the file server and why. To prevent it, you could look at applying group policies and setting bandwidth limits via a traffic shaping policy.

Brash · ‎Aug 24 2023

How many AP's are you seeing this issue on? And what version are they running? Are they all connected to a Meraki switch and powered via PoE or do you have PoE injectors?

About Brash

Brash

Community Record

Badges