Thank you for your reply. I've put on work a configuration like you mention, but this have a problem, it need a initial state for the equipments to work, taking me to solve another problem first. What I'm doing now is using the Dashboard API to get the status of the devices in one row and storing those responses on a server. This response takes less than a second to get and I'm polling the status every two minutes as I have only 250 Meraki devices on my Meraki network, but with 1,000 or 10,000 devices won't be that fast. This response for 250 devices takes about 45KB and I can get the response, this solution one also have a point of failure, in case a response arrives with a timeout, a 404, 50X or whatever other error is, I won't have the status of the 2 minutes timeframe and I need to store (if everything goes well) 720 responses per day for a weekly analysis later, this means power to process the information to show the report, and storage to have the historic information of the data as every analysis will take 5,040 responses to analyze with 250 devices (for now) and if I do it monthly it will take 22,320 responses in the months of 31 days (the longer ones). The bad part of this is that I must have agreement of the customer that the status information of the Meraki devices will be every 2 minutes. This is what I've found for a solution, but I think Meraki have a better one as I can see the OutageGraph available on the Dashboard. Going back to your suggestion, 1.-How did you get the initial status? 2.-What happens if that UDP (SNMP) message is not fully received properly on the SNMP server or is not retransmited in case of packet failure? I'm trying to explore other options to achieve this and also help the Meraki community. Best regards,
... View more