About ls08

ls08 · ‎02-02-2023

This is only true for devices on the network. I'm only getting a handful of MGs with the API call below. We have 250 that are unclaimed. I can probably come up with a python script to create a dummy network and add the devices to get the information. response = dashboard . organizations . getOrganizationDevices ( ORGID , total_pages = ' all ' , models = ' MG41 ' )

ls08 · ‎01-31-2023

sungod has it nailed in python the code below will do what OP is looking import meraki API_KEY = " API-KEY-HERE " dashboard = meraki . DashboardAPI ( API_KEY , suppress_logging = True ) response = dashboard . networks . getNetwork ( network_id ) #This looks for existing tags and stores it into local variable updated_tags = response [ ' tags ' ] #Below adds two tags. updated_tags . append ( ' WIFI ' ) updated_tags . append ( ' NEW YORK ' ) #Finally update the network with the tag. Keeps the existing tags and adds the two I mentioned. response = dashboard . networks . updateNetwork ( network_id , tags = updated_tags ) print ( response )

ls08 · ‎01-07-2023

Using a MX85 17.10.2 and ran into this issue. If I unbind a network from a template that is using and using VLANs in some firewall rules as policy objects ( the object has a D in a circle). The firewall rules will glitch out if I I edit and save the rules with VLAN objects. It looks like the VLAN rules are ignored and the firewall rules break. I can still add more rules with VLAN objects and save the changes, nowhere do I get an error for having VLAN objects in a network that is not on a template. My meraki switches lost network to meraki dashboard because of this weird firewall rules. The vlan that the switches use didn’t have any block rules to the web. Eventually I figured out it was the VLAN objects and I removed all the rules, saved the changes, refreshed and then created the rules using network objects and not VLANs. From the manual on objects: Compatibility Network Objects can be applied alongside our existing VLAN Objects used in Template Networks Firewall Rules. VLAN Objects VLAN Objects are solely used to represent Template created VLANs. They can only be created and modified within Template Network Firewall Rules. For additional information regarding VLAN Objects, please refer to:

ls08 · ‎12-15-2022

How are you all running your speed test ? i perf to public servers ?

ls08 · ‎10-20-2022

I think I’m experiencing this issue and I can reproduce it with only a MG41. I read a post on the MG section and tried to connect a MG41 to a MS120-48LP. My MG41 would get power, and on the port status the lightning symbol appears. Eventually the lightning disappeared and the MG41 was off. I flipped the connection with a Cisco 8811 IP phone. The phone powers on and I see the boot logo. The MG41 is now on the port the phone and powers on, but then turns off after a few seconds. The port turns off and also the 8811. I also have a MR access point on the switch and that loses power. Now no other port works with POE and the power tab on the switch on then dashboard does not show the POE consumption. Just a blank screen. Rebooting the switch fixes it and I try to reproduce the issue again. I plug in MG41 to port 48, 8811 on port 45 and MR back on port 37. I do the phone and MR first and they boot and connect. I now do the MG41 and the device powers on. On the port status I see it drawing 1.3 w to .9w or 0. This cycles for a few seconds then eventually 0 and the device stays off. I flip the 8811 and MG41. Phone is powering on and MG. Eventually everything POE turns off phone MR and MG. Reboot fixes the issue. This MG41 works on a MX85 it did prior to connecting to the switch. I’ve read other posts of users connecting to the switch on their network to get the MG41 POE power. So this is supposed to work, but it looks like the switch is having issues. MS 14.33.1

ls08 · ‎07-14-2022

Also experiencing this issue with our APs 28.6.1 did not fix the issue for us.

ls08 · ‎02-28-2022

Currently testing them out with a MX85. I activated the SIM cards for Verizon and had the MG41 was not connecting to the network. So I popped in a AT&T SIM and still no go. I set the APN manually and that worked. I inserted Verizon as the 2nd SIM and for whatever reason the MG41 was using it as a primary and was not able to connect to Meraki Dashboard. I connected directly to the MG with my laptop and went to 192.168.0.1 to the configuration page and change the active SIM and then it worked. While also on the config page I set Verizon's APN. On Meraki Dashboard I noticed it was blank, which makes sense, so I configured the APN on the dashboard. Playing around with the MG some more I set the 2nd SIM as primary then rebooted the MG. MG came back online and then I forgot about it. Later on the MG lost connection. I rebooted the device and still not connecting. I do have a bad signal with Verizon and I did disable AUTO SIM FAILOVER. So I removed the Verizon SIM card from the MG and then it came back on with AT&T on SIM 1. I'm wondering if the AUTO SIM FAILOVER feature would've helped me with this issue.

ls08 · ‎02-11-2022

Just making sure, there is no way to configure Air Marshal through API? I looked through - https://developer.cisco.com/meraki/api-v1/#!introduction and there's only scan results from the air marshal. We are only using MR70s from what I gather this is a dual-radio AP and I'll have to set it as a Air Marshal mode to scan our remote locations then disable it so it can act as an AP again. I'm hoping there's an API that can help me do this process since I need scans as part of PCI.

ls08

Community Record

Badges

Re: Meraki API for LTE information

Re: How to add a tag without losing the information that was there before?

MX policy object issues after removing from template

Re: MX-85 slowdown recently. Firmware?

Re: PoE - Physically Separating PoE Devices

Re: AP loses connection to Cloud frequently - how to troubleshoot

Re: MG cellular gateways

Enable/Configure Air Marshal through API V1

Re: PoE - Physically Separating PoE Devices