BGP & Interface monitoring

[Subhendu Ghosh]

Nagios and check_ifstatus are not designed that way.  Nagios treats each 
service as one and only one monitor and will only alarm on changes in 
state.  

It is possible to track (log) the changes in the service within 
the state, but notification is not possible as it is tied to the state.

To log changes wihtin a state - see "Stalking" in the docs.

To be notified for individual interface down issues, use 
check_ifoperstatus on a per-inteface basis instead.

-sg

On Tue, 6 May 2003, BELMONT Christophe wrote:

> Hello,
> 
> I am using Nagios to monitoring many routers of the network. More
> especially, I am using check_bgpstate and check_ifstatus. When a link
> goes down, the Nagios service defined on this host goes down. It is
> acknowledged and does not send alarm any more. If before this link comes
> back up, a second link goes down on the same router, Nagios should raise
> the alarm once again.
> 
> My question is? If the comment after the state returned by the "check"
> script changes (a new interface is listed as down) even though the state
> itself does not change (was CRITICAL and is still CRITICAL), does Nagios
> triggers a new alarm or does it thinks this is still the same previous
> alarm.
> 
> Does somebody already encountered this problem and found out how to
> bypass it?
> 
> Thank you in advance,
> Christophe.
> 

-- 




-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Nagios-users mailing list
Nagios-users at 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