Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello everyone,I am struggling to understand how to interpret the "Claimed At" attribute that is returned in the "getOrganizationInventory" endpoint.I guess this is supposed to indicate the date at which the device was claimed, but I don't get which ...
Hello everyone,I have already opened a case to the support but I want to know if anybody else is facing the same issue.Since last Friday approximately our provisioning scripts (provisioning of networks and SSIDs) keep failing. More precisely they fai...
Hello everybody,I tried to search if this had already been discussed somewhere but I can't find anything.In our environment we use a Cisco ISE used to authenticate our WiFi clients. As you may know, before the authentification takes place, the device...
Have you tried disabling the Bonjour Forwarding feature ? I don't know if this could explain your issue (don't think so) but If all devices are in the same VLAN it shouldn't be required anyway.
Turns out that this is supposed to be a "one-time error" from Meraki. Their golden rule is that new API releases should not break the structure of existing API requests, which they have failed to achieve in this case.The solution was "simply" to remo...
That is exactly what my Meraki SE suggested to me: using the Webex Teams to follow closely what they release on the API sode.Still, I'm a bit pissed off that they don't provide "retro-compatibility" when they modify their APIs, it should be a basic r...
Since the API endpoint doesn't seem to exist, have you tried adapting your script to:Disable the email alert that is triggered by the port status changeDisable the portEnable the portEnable the email alert againOf course you'll need to get the networ...
