Dear Nagios Gurus, We've been using nagios for the past two years (actually centreon/nagios), and are very happy with it.
However, I couldn't find a way to monitor a distributed resource. Let me explain what I mean. For example, I may have redundant VPN gateways, so if one goes offline it is not catastrophic. I may also have monitored devices behind the VPN, so I set up host dependencies. I would like to have host dependency in an "either or" configuration. I.e. if the primary gateway goes down and the standby takes over, I would still like to be notified about host troubles behind the VPN. Only if both were to be down nagios should stop sending messages. Does that make sense? I'm sure there is a way to implement this in Nagios, but I haven't found out how quite yet... Has anyone implemented something in this way? Mit freundlichen Gr??en / With best regards Andreas Iwanowski - IT Administrator / Software Developer www.awato.de<http://www.awato.de> | namez...@afim.info<mailto:namez...@afim.info> T: +49 (0)2133 2969 28 | F: +49 (0)2133 2969 69 awato Software GmbH | Salm Reifferscheidt Allee 37 | D-41540 Dormagen avisor-Support | T: +49 (0)621 6094 043 | F: +49 (0)621 6071 447 [awato Software GmbH] [cid:qrCode-63e3864e-f744-4ad2-aae3-38aaf37b4110a750d4] Gesch?ftsf?hrer: Ursula Iwanowski | HRB: Neuss 7208 | VAT-no.: DE 122796158
<<inline: qrCode-63e3864e-f744-4ad2-aae3-38aaf37b4110a750d4>>
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
