Community Record
30
Posts
12
Kudos
2
Solutions
Badges
Apr 21 2023
10:11 AM
I just asked for an update on my case. The latest note in it from January 2022 from Meraki Support was they are still waiting to hear from the developers. What's sad is when I first raised awareness about this issue in the forum, a Meraki engineer on the forum said it is not an API bug, but how they are reading the data. He said he added a note to my case, but I never saw it. Perhaps, it was in an internally visible only field. I've checked it using the interactive documentation and get the same result. Maybe now with multiple people raising the issue, we can get some actual traction on it. If the can't provide reliable data to with that API endpoint, they should disable that endpoint until they fix it.
... View more
Apr 20 2023
3:39 PM
I've had a open since 4/26/2020 about that end point returning inconsistent results. I run a weekly report and every week there are usually about 100 of our 600 networks that return 500 for all the values. I haven't spot checked it recently, but previously, a network where that happens one week would show the correct values the following week. But every week it is always around100 networks that show the incorrect values. No progress so far on this issue.
... View more
Feb 2 2023
11:57 PM
Do you have the device model number in the spreadsheet? If so, determine the device type by the first two characters of the model field, MX, MS, MR, etc.
... View more
Apr 5 2022
6:01 PM
@ByronZ, @John_on_API My observation when receiving "Not running configured version" coincides with a device that has been offline a while and is now in a "dormant" status. Use the https://developer.cisco.com/meraki/api-v1/#!get-organization-devices-statuses API call to see device statuses for the organization. We've been doing some hardware upgrades and in some cases I've found the old equipment hasn't been removed from the network yet or the network is test network and only gets brought online at various times. As a result, these devices show in dormant status and the firmware shows as "Not running configured version". See if that is the case for you.
... View more
Jun 30 2021
1:10 PM
4 Kudos
From Meraki's documentation found here ... https://documentation.meraki.com/MX/Monitoring_and_Reporting/Device_Utilization MX Device Utilization Calculation The device utilization data reported to the Meraki dashboard is based on a load average measured over a period of one minute. The load value is returned in numeric values ranging from 1 through 100. A lower value indicates a lower load, and a higher value indicates a more intense workload. Currently, the device utilization value is calculated based upon the CPU utilization of the MX as well as its traffic load. Due to load averaging, it’s possible for transient load spikes to occur without being visible in the utilization metric. For example, a device load that is consistently shown as less than 85% may still be experiencing transient load spikes. These transient load spikes may cause packets received in excess of the device’s forwarding capacity to be dropped.
... View more
Apr 21 2021
8:05 AM
1 Kudo
@Willem_vd_Pas - If you are referring to changing this on Layer 3 switches, it was added in API V1. https://developer.cisco.com/meraki/api-v1/#!update-device-switch-routing-interface-dhcp Description: Update a layer 3 interface DHCP configuration for a switch Larry
... View more
Apr 22 2020
1:03 AM
Why wouldn't the code below work? I just threw it together to answer your question. It is how I would do it in Python 3.82 using Meraki API 0.100.1. This would update the DHCP relay servers on all vlans - adjust accordingly to fit your need. I have used the update vlan API call to update vlans on MX appliances. You may want to add some error checking logic. Replace ['se.rv.er.01, se.rv.er.02'] with your new server IP's. I would test it on one network/vlan first to be sure you get the desired result and confirm the new setting works, ie. no typos on the server IP's. # no api_key specified below it uses environment variable "MERAKI_DASHBOARD_API_KEY" Merakiclient = meraki.DashboardAPI(api_key='', base_url = 'https://api.meraki.com/api/v0', wait_on_rate_limit = True, maximum_retries = 2, log_file_prefix = __file__[:-3], log_path='') orgs = Merakiclient.organizations.getOrganizations() orgid=orgs['id'] # use above API getorgs() call or code the orgid here newRelayServers = ['se.rv.er.01, se.rv.er.02'] networks = Merakiclient.networks.getOrganizationNetworks(orgid) for network in networks: print('Processing network: ',network['name']) vlans = Merakiclient.vlans.getNetworkVlans(network['id']) for vlan in vlans: print('Processing Vlan: {} - {}'.format(vlan['id'], vlan['name'])) if vlan['dhcpHandling'] == 'Relay DHCP to another server': result = Merakiclient.vlans.updateNetworkVlan(network['id'], str(vlan['id']), dhcpRelayServerIps = newRelayServers) updatedVlan = Merakiclient.vlans.getNetworkVlan(network['id'], vlan['id']) print('Vlan {} DHCP Relay Servers after update: {}'.format(updatedVlan['id'], updatedVlan['dhcpRelayServerIps'])) Larry
... View more
Kudos from
My Accepted Solutions
Subject | Views | Posted |
---|---|---|
2704 | Jun 30 2021 1:10 PM |
My Top Kudoed Posts
Subject | Kudos | Views |
---|---|---|
4 | 2704 | |
1 | 7594 |