Meraki

Ryan_Miles · ‎May 31 2022

LACP is supported on any of the switch ports. And, no the MS1xx series doesn't have mgig. To get mgig you need to be in the 3xx series.

Ryan_Miles · ‎May 26 2022

The minimum supported version for MG41 is 2.0. Meaning MG41 cannot/will not run 1.x. So, this is not a bug. It's working as expected.

Ryan_Miles · ‎May 25 2022

Per the doc "It is recommended that Root Guard be applied to ports connecting to neighboring, downstream switches that should not be the Root Bridge, to prevent a superior BPDU from being received on the port and causing the election of an unexpected Root Bridge."

Ryan_Miles · ‎May 25 2022

I'd put BDPU guard on the access ports and root guard on the switch to switch links and leave it at that. https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Configuring_Spanning_Tree_on_Meraki_Switches_(MS)#Configuring_STP_Guard_on_a_Switch_Port

Ryan_Miles · ‎May 25 2022

The MG cell gateway is typically meant as a device that connects to an edge router/firewall providing internet access. So yes, you'd typically have other things involved in a network like a firewalls & switches. For your use case just having a MG & MV should work keeping in mind the MG is a simple NAT router and not a full blown stateful firewall. You'd need to power the MG and MV with something external like PoE injectors. Or you could consider using a MX with integrated cellular like the MX67C, MX68CW, or Z3C.

Ryan_Miles · ‎May 25 2022

Do you mean a MV connected directly to a LAN port of a MG or just MV(s) on a LAN with the MG being the upstream WAN connection? Performance over cellular is going to depend on your connection quality/speed.

Ryan_Miles · ‎May 25 2022

Currently, this isn't supported. It would be a feature enhancement request.

Ryan_Miles · ‎May 20 2022

Are you referring to the MR L3 firewall rule section? If so, PUT/networks/{networkId}/wireless/ssids/{number}/firewall/l3FirewallRules controller disconnection behavior is under PUT/networks/{networkId}/wireless/ssids/{number}/splash/settings Btw a method to find API endpoints is do a search for keywords at this link https://api.meraki.com/api/v1/openapiSpec

Ryan_Miles · ‎May 20 2022

Tags for what? Networks, devices, clients? You should be able to edit (add/delete) any tags on whatever page you're on.

Ryan_Miles · ‎May 18 2022

When API is enabled and a key is created per account each admin has a unique API key. That key has the same permissions as the user.

Ryan_Miles · ‎May 17 2022

It's covered here https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/MX_Templates_Best_Practices#Templates_with_MXs_of_Different_Port_Counts

Ryan_Miles · ‎May 11 2022

A simple L2 roam should be the fastest and most reliable. Your issue is likely around the SSID RF config. Can you post your RF profile config for these APs? Also, have you opened a Support case?

Ryan_Miles · ‎May 5 2022

Nope that won't work

Ryan_Miles · ‎May 2 2022

The second image is when you use standalone Meraki APs. That's different than the wireless settings & capabilities in the MX-W.

Ryan_Miles · ‎Apr 29 2022

In your example a client first connecting on floor 1 would get an IP from VLAN 10. When the client roams to 2 or 3 they would associate to an AP on those floors while maintaining their VLAN 10 IP. This is accomplished by a dynamically created AP to AP tunnel. This is with using Client IP Assignment type of "Layer 3 Roaming". This is assuming the switchports connected to the floor 2 & 3 APs DON'T have the 1st floor VLAN on the trunk port. If the trunk ports contain VLAN 10 the client would still remain on VLAN 10, but without the need for an AP to AP tunnel to be created and they would simply join the new AP. This is a nuance of our distributed layer 3 roaming folks often overlook in that a VLAN check occurs and based on presence of the client VLAN on the upstream switchport the roam could be a simple L2 roam or a tunneled L3 roam. It's outlined in great detail here There's also a large building example in the doc based on a deployment I did some years back. I also created a simplified version of this example.

Ryan_Miles · ‎Apr 26 2022

I can see they're rebooting. You need to engage Support.

Ryan_Miles · ‎Apr 25 2022

MS120-8FP is not a layer 3 switch. So, in this design you'll need to put all the L3 interfaces on your MX and use your switch has basic L2 transport. So, make port 1 on the switch a trunk. Create the L3 interfaces/subnets on the MX. I assume the /30 to the main site is just a LAN type link essentially? What traffic will take that route? You'll need static(s) on the MX to send traffic destined for the main site to the next hop 10.1.1.1 (guessing that's the IP of the far end).

Ryan_Miles · ‎Apr 25 2022

Support or your Meraki sales team

Ryan_Miles · ‎Apr 25 2022

I checked it again. It's running the highest supported firmware version a Z1 support (14.56). I don't actually see it rebooting with any scary messages related to firmware, panics, etc. Running the ping tool against 8.8.8.8 I see a fair amount of loss here and there along with some fairly high latency spikes. If you bypass the Z and connect directly to the modem is it stable? Mostly looks like an upstream issue from the Z from what I can tell. Is the modem ethernet port 1 gig capable? The Z is showing the WAN port being at 100 Mbps at the moment.

Ryan_Miles · ‎Apr 25 2022

Can you try a factory reset on the Z1? Poke the reset button with a paperclip or whatever. Hold in for ~10 seconds then release.

Ryan_Miles · ‎Apr 24 2022

DM me your org link

Ryan_Miles · ‎Apr 21 2022

Yes, Support can enable that.

Ryan_Miles · ‎Apr 21 2022

Requires MX SD-WAN license https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/SD-WAN_Internet_Policies_(SD-Internet)

Ryan_Miles · ‎Apr 20 2022

Little tough to follow without a diagram. But, in general if the MX WAN interface shows as down then it means it cannot reach dashboard. Does that interface have a proper route & NAT to reach internet/dashboard?

Ryan_Miles · ‎Apr 18 2022

Liquid detection would be the MT12. Stick the MT10 in liquid and you're bound to have a bad day. As for the MT12 its primary targeted use case is to be dry and when liquid contacts the leak detection cable send an alert. Not sure we've tested the reverse in which the cable spends its time wet all/most of the time. What would you be monitoring here?

About Ryan_Miles

Ryan_Miles

Ryan Miles

Community Record

Badges