Re: [Nagios-users] Monitoring Distributed Resource [Resolved]

2012-08-11 Thread Andreas M. Iwanowski
Thank you!

Your assumption about the layout is correct.
I will try to define a parent/child relationship between core_gw_1, core_gw_2 
and each remote gateway connected to it, and then a parent/child relationship 
between the remote_gw and  remote_host.

I've seen the tab for that in centreon, so I'll try to configure this next week.

I appreciate all your great help whith this!

Mit freundlichen Gr??en / With best regards

Andreas Iwanowski - IT Administrator / Software Developer
www.awato.de | 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

Gesch?ftsf?hrer: Ursula Iwanowski | HRB: Neuss 7208 | VAT-no.: DE 122796158


-Original Message-
From: Chris Beattie [mailto:cbeat...@geninfo.com]
Sent: Thursday, August 09, 2012 5:01 PM
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Monitoring Distributed Resource

On 8/8/2012 5:57 PM, Andreas M. Iwanowski wrote:
 So as I understand, if I define a parent-child relationship between
 the VPN services (or core gateways) on the parent side and the remote
 gateway on the other side, the remote gateway will be checked (and we
 notified) as long as one core gateway is online?

This is how I picture your setup:

 core_gw_1
Nagios- -remote_gw-remote_host
 core_gw_2

If you put parents core_gw_1,core_gw_2 in remote_gw's host
definition and parents remote_gw in the remote_host's definition, then
as long as Nagios thinks either core_gw is up, it should continue checking 
remote_gw and remote_host behind it.

 And since the remote hosts all depend on the remote gateway, they
 should inherit that behavior. Correct?

When you say depend, do you mean a host dependency as in you've got a define 
hostdependency {... somewhere?  That's more advanced than what I'm talking 
about, and those dependencies are NOT inherited.  You'd have to define one for 
every host.

Defining parent/child relationships is a simple way to describe to Nagios the 
network's layout, specifically for determining if a host can be reached.  If 
remote_host_1's parent is remote_gw and you copy
remote_host_1 when you add remote_host_2, then remote_host_2 will also have 
remote_gw as a parent.

 I don't think the check_cluster would work since the host services are
 checked via nrpe running custom php monitoring scripts on the
 machines, but I'll check it out tomorrow at the office anyways.

Check_cluster is a meta-check.  It doesn't perform the component service or 
host checks itself.  Instead, it examines the results of the checks that Nagios 
is already performing.  Now that I think about it some more, it's probably 
overkill for this case.


--
-Chris

Nothing in this message is intended to make or accept an offer or to form a 
contract, except that an attachment that is an image of a contract bearing the 
signature of an officer of our company may be or become a contract. This 
message (including any attachments) is intended only for the use of the 
individual or entity to whom it is addressed. It may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law or may constitute as attorney work product. If 
you are not the intended recipient, we hereby notify you that any use, 
dissemination, distribution, or copying of this message is strictly prohibited. 
If you have received this message in error, please notify us immediately by 
telephone and delete this message immediately.

Thank you.


--
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

--
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

Re: [Nagios-users] Monitoring Distributed Resource

2012-08-09 Thread Chris Beattie
On 8/8/2012 5:57 PM, Andreas M. Iwanowski wrote:
 So as I understand, if I define a parent-child relationship between
 the VPN services (or core gateways) on the parent side and the remote
 gateway on the other side, the remote gateway will be checked (and we
 notified) as long as one core gateway is online?

This is how I picture your setup:

 core_gw_1
Nagios- -remote_gw-remote_host
 core_gw_2

If you put parents core_gw_1,core_gw_2 in remote_gw's host 
definition and parents remote_gw in the remote_host's definition, then 
as long as Nagios thinks either core_gw is up, it should continue 
checking remote_gw and remote_host behind it.

 And since the remote hosts all depend on the remote gateway, they should
 inherit that behavior. Correct?

When you say depend, do you mean a host dependency as in you've got a 
define hostdependency {... somewhere?  That's more advanced than what 
I'm talking about, and those dependencies are NOT inherited.  You'd have 
to define one for every host.

Defining parent/child relationships is a simple way to describe to 
Nagios the network's layout, specifically for determining if a host can 
be reached.  If remote_host_1's parent is remote_gw and you copy 
remote_host_1 when you add remote_host_2, then remote_host_2 will also 
have remote_gw as a parent.

 I don't think the check_cluster would work since the host services are
 checked via nrpe running custom php monitoring scripts on the machines,
 but I'll check it out tomorrow at the office anyways.

Check_cluster is a meta-check.  It doesn't perform the component service 
or host checks itself.  Instead, it examines the results of the checks 
that Nagios is already performing.  Now that I think about it some more, 
it's probably overkill for this case.


-- 
-Chris

Nothing in this message is intended to make or accept an offer or to form a 
contract, except that an attachment that is an image of a contract bearing the 
signature of an officer of our company may be or become a contract. This 
message (including any attachments) is intended only for the use of the 
individual or entity to whom it is addressed. It may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law or may constitute as attorney work product. If 
you are not the intended recipient, we hereby notify you that any use, 
dissemination, distribution, or copying of this message is strictly prohibited. 
If you have received this message in error, please notify us immediately by 
telephone and delete this message immediately.

Thank you.


--
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


Re: [Nagios-users] Monitoring Distributed Resource

2012-08-08 Thread Chris Beattie
On 8/7/2012 8:33 AM, Andreas M. Iwanowski wrote:
 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.

Would setting parent/child relationships, and maybe using the 
check_cluster plugin help you?

I have two network core switches.  Every physical host on the network 
has both of those two core switches defined as a parent in Nagios. 
Nagios will continue to check everything as long as at least one of 
those two switches is up.

I did something similar with check_cluster.  To monitor a VMware ESX 
cluster comprising three ESX hosts, I defined a Nagios host for each ESX 
host.  There is another Nagios host to represent the cluster whose host 
check is a check_cluster command.  Every guest has the cluster defined 
as its parent.  If one ESX host goes down, the cluster goes into a 
warning state.  If two or more ESX hosts go down, the cluster enters a 
critical state.

The guests may all have migrated onto the still-running ESX host and 
might still be up, but the monitoring of individual guests can take a 
back seat at that point.

-- 
-Chris

Nothing in this message is intended to make or accept an offer or to form a 
contract, except that an attachment that is an image of a contract bearing the 
signature of an officer of our company may be or become a contract. This 
message (including any attachments) is intended only for the use of the 
individual or entity to whom it is addressed. It may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law or may constitute as attorney work product. If 
you are not the intended recipient, we hereby notify you that any use, 
dissemination, distribution, or copying of this message is strictly prohibited. 
If you have received this message in error, please notify us immediately by 
telephone and delete this message immediately.

Thank you.


--
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


Re: [Nagios-users] Monitoring Distributed Resource

2012-08-08 Thread Andreas M. Iwanowski
Thank you Chris!

This sounds great

So as I understand, if I define a parent-child relationship between the VPN 
services (or core gateways) on the parent side and the remote gateway on the 
other side, the remote gateway will be checked (and we notified) as long as one 
core gateway is online?
And since the remote hosts all depend on the remote gateway, they should 
inherit that behavior. Correct?

I don't think the check_cluster would work since the host services are checked 
via nrpe running custom php monitoring scripts on the machines, but I'll check 
it out tomorrow at the office anyways.

-Andy

Mit freundlichen Gr??en / With best regards

Andreas Iwanowski - IT Administrator / Software Developer
www.awato.de | 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

Gesch?ftsf?hrer: Ursula Iwanowski | HRB: Neuss 7208 | VAT-no.: DE 122796158


-Original Message-
From: Chris Beattie [mailto:cbeat...@geninfo.com]
Sent: Wednesday, August 08, 2012 3:12 PM
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Monitoring Distributed Resource

On 8/7/2012 8:33 AM, Andreas M. Iwanowski wrote:
 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.

Would setting parent/child relationships, and maybe using the check_cluster 
plugin help you?

I have two network core switches.  Every physical host on the network has both 
of those two core switches defined as a parent in Nagios.
Nagios will continue to check everything as long as at least one of those two 
switches is up.

I did something similar with check_cluster.  To monitor a VMware ESX cluster 
comprising three ESX hosts, I defined a Nagios host for each ESX host.  There 
is another Nagios host to represent the cluster whose host check is a 
check_cluster command.  Every guest has the cluster defined as its parent.  If 
one ESX host goes down, the cluster goes into a warning state.  If two or more 
ESX hosts go down, the cluster enters a critical state.

The guests may all have migrated onto the still-running ESX host and might 
still be up, but the monitoring of individual guests can take a back seat at 
that point.

--
-Chris

Nothing in this message is intended to make or accept an offer or to form a 
contract, except that an attachment that is an image of a contract bearing the 
signature of an officer of our company may be or become a contract. This 
message (including any attachments) is intended only for the use of the 
individual or entity to whom it is addressed. It may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law or may constitute as attorney work product. If 
you are not the intended recipient, we hereby notify you that any use, 
dissemination, distribution, or copying of this message is strictly prohibited. 
If you have received this message in error, please notify us immediately by 
telephone and delete this message immediately.

Thank you.


--
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

--
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


[Nagios-users] Monitoring Distributed Resource

2012-08-07 Thread Andreas M. Iwanowski
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.dehttp://www.awato.de | 
namez...@afim.infomailto: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