Re: network monitoring of firewalled/NAT'd systems
Intellipool can run in distributed mode, where you have one monitoring server inside each firewall that reports back home to the mothership. http://www.intellipool.se/ Not *quite* what you asked for, but may serve. --DTVZ On Tue, May 18, 2010 at 5:48 PM, Michael ODonnell michael.odonn...@comcast.net wrote: I wrote: We want to monitor (from a central server at HQ) the health and performance status of multiple machines [mostly Windows -( ] at each of multiple customer sites despite them being NAT'd/firewalled. ...and then mentioned a bunch of features we're dreaming about. A more specific question: does anybody even know of a package that can do passive monitoring? IOW, in our scenario some sort of agent on each workstation would be responsible for initiating a connection to HQ and pushing its own monitoring data back to our central server since we'd not be able to initiate connections in the other direction as they'd be blocked at the customer's firewall. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: network monitoring of firewalled/NAT'd systems
On Tue, May 18, 2010 at 05:48:15PM -0400, Michael ODonnell wrote: I wrote: We want to monitor (from a central server at HQ) the health and performance status of multiple machines [mostly Windows -( ] at each of multiple customer sites despite them being NAT'd/firewalled. ...and then mentioned a bunch of features we're dreaming about. A more specific question: does anybody even know of a package that can do passive monitoring? Nagios can do this. We monitor a dozen or so remote sites at work where they are small networks NAT'ed behind a single IP. Nagios runs out of cron on the workstations/servers at those locations and reports back to our main Nagios server. -b -- half a man's life is devoted to what he calls improvements, yet the original had some quality which is lost in the process. e.b. white ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: network monitoring of firewalled/NAT'd systems
Michael ODonnell michael.odonn...@comcast.net writes: I wrote: We want to monitor (from a central server at HQ) the health and performance status of multiple machines [mostly Windows -( ] at each of multiple customer sites despite them being NAT'd/firewalled. ...and then mentioned a bunch of features we're dreaming about. A more specific question: does anybody even know of a package that can do passive monitoring? IOW, in our scenario some sort of agent on each workstation would be responsible for initiating a connection to HQ and pushing its own monitoring data back to our central server since we'd not be able to initiate connections in the other direction as they'd be blocked at the customer's firewall. Anything that uses SNMP traps? -- Don't be afraid to ask (λf.((λx.xx) (λr.f(rr. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
network monitoring of firewalled/NAT'd systems
We want to monitor (from a central server at HQ) the health and performance status of multiple machines [mostly Windows -( ] at each of multiple customer sites despite them being NAT'd/firewalled. We assume all the remote systems will be able to initiate outbound connections through whatever protective layers are between them and the Internet, so we'll want to rig those remote systems with agents such that they each periodically phone home to report status to HQ's central server [ probably Linux ;- ] as we'll generally not be able initiate such contact in the other direction. So we're evaluating network monitoring packages and, at least for now, I've arbitrarily limited our choices to those mentioned in this table: http://en.wikipedia.org/wiki/Comparison_of_network_monitoring_systems ...since this much larger list: http://www.slac.stanford.edu/xorg/nmtf/nmtf-tools.html ...makes my brain hurt. I'd be interested in hearing recommendations (pro or con) about those or other network monitoring packages with an emphasis on our situation, ie. gathering info from multiple remote systems that aren't directly IP addressable from HQ. Research so far indicates Zabbix, Pandora and OpenNMS are good candidates so I'd be particularly interested in comments about them. Most such packages have most of their features in common with many of the others, but FWIW some of our criteria are: - Configuring/extending the behaviors of agents and server is assisted via abstractions like groups and templates, where possible/appropriate. - When scripting is necessary, commonly used languages are supported (eg. Perl/Python/etc preferred over Rexx/Tcl/etc). - Pretty charts/graphs/reports to impress management. Bonus: trending/prediction. - Windows agent cooperates with WMI and such; Windows log files can be scraped relayed. - Other entities at HQ (eg. trouble calls to Customer Service) can feed into server's notion of a system's status. - Events of interest trigger arbitrarily scriptable responses. - WWW based access to central server. Bonus: access control on a per-user basis. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
