NeophyteNeophyteHonored to have the legendary Patrick_Rouse comment on this post. :) And of course, I have tried multiple support tickets on these issues. More issues just keep popping up the more I work with the API integration. I don't believe I've made any modifications to the LM Meraki API modules in our portal, so that shouldn't be causing issues. Interesting you mention meraki.snmp or SNMP at all, for that matter, as I thought the API calls were supposed to essentially replace the need for SNMP. Still, we have SNMP properties on our devices as well so I don't think this is causing any issues.
For the modules to work, you "need" the following properties on each device (set directly or inherited)
To this, I would say this is by far the most tedious thing as the Netscan almost never pulls in all the right properties by default. Furthermore, I believe my individual issue of thousands of Warning Alerts (it jumped up to 4500+ overnight) was also due to the inheritance you mention and it not working as expected. I'm still working with support on these issues as I have no idea why inheritance doesn't seem to be translating down to the devices in this regard. Also weird that only some devices were alerting, and not all. If it were truly an issue with one of those properties you mentioned above, I would expect all devices in that Org or Network would be alerting--especially because I set the meraki.api.key at the parent level and meraki.api.network at each site folder underneath that. But I'm working on that with support right now.
Just mostly meant to say that this stuff is so tedious and almost feels like more work than it's worth sometimes. But I'm not giving up on it yet. I agree with Allister that a Wizard of sorts would be nice. I mentioned in one of my support tickets for Netscan that it would be nice to see what kind of changes to expect before "approving" them as I've had the Netscan remove devices in my portal with no warning whatsoever. That Wizard or confirmation screen would be nice.
