We have multiple AP in our network which we need to monitor with our current Network Monitoring system.I have broadband connection through which all my AP are working, what is the way I can configure Management IP on all this AP so that they can be discover in my Monitoring system.
Check here to set static IP addresses:
Regarding SNMP, you can query the dashboard for certain things:
But you can also query devices themselves for certain things.
More info here:
Thanks for the info but I am looking to configure a management IP which I can advertise into my private network through WAN.A Private IP through which I can configure AP and get it monitored in my network.
I am not getting IP edit option on my access point also, snap for ref.
SNMP part I understand but main challenge IP which IP I should configure to get device in our NMS.
So no pencil icon appears next to LAN IP? Is it possible you have read-only access to that network?
Yes, I was having read access, now I got that icon.
But still my concern is how I will get this device in my network.
AP is connected via WAN DHCP let if i configure Private IP to this /device HOW I will route this IP into my private network
The above is my netwirk where I have MX MS and then AP..how I can get AP in monitoring
Where is your monitoring system, what is it, and what kind of access does it need?
My nms is in company local network which has reachability to wan ip...but my concern is how to get ap whicch has local lan ip to get in my nms
So your NMS is in the same site, but the Meraki network you drew is separate from your normal network. And the NMS only has access to the MX's WAN IP? Is that correct?
I see. Well I still don't know what interfaces your monitoring system needs access to, but I assume it's SNMP polling and traps.
As I mentioned before, part of the information is available by polling (querying) the dashboard:
So for that part it doesn't matter where your access points are, you monitoring system will be querying the Meraki cloud.
For polling the other MIBs, your monitoring system needs access to the actual LAN IP addresses of the equipment you want to monitor. This is the case for all vendors. This access could be through routing, VPN tunnels, 1-to-1 NAT, portforwarding, some kind of SNMP proxy, ...
For traps it's the other way around, your devices need access to the LAN IP of the NMS. That access could be provided in a similar way.