Best practices for a NMS solution
Posted on 2009-04-01
I've been using SolarWinds ipMonitor 8.5 for a while now to remotely monitor some servers via SNMP however the system isn't very efficient and doesn't give me what I'm looking for in some cases. I am going rolling out a new instance of ipMonitor 9.x shortly and am currently tinkering with SolarWinds Orion NPM 9. See below for additional details, and eventually my question =)
I have ~35 clients that I manage. An average client has between 3 and 5 servers. We currently have one-way VPN connections to all clients so we can remote in for work. We could setup rules for two-way communication if required.
All clients are running HP & Dell systems. All systems have their Vendor Management utilities installed. Windows servers across the board. About 20% of our servers are running VMware ESX stand-alone servers.
I'm looking for monitoring that will alert me when any physical hardware has issues (ie. dead physical disk or predictive failure, etc.) in addition to windows/software alerting (ie. partitions running low on space, services not running, etc.).
Not to point out the obvious, but the key is to acheive a reliable system in the most network efficient manner possible. I assume this would involve setting up some SNMP traps instead of polling every server every 5 minutes but I'm not sure how exactly. I'm completely open to any and all ideas. Any references and or documentation are much appreciated as well. Ultimately if someone could draft a model for me that says for every client you should do X, Y, Z and then A, B, C from my end to get this up and running, it would be great. Thanks in advance.