Freshness checks conflict

[Lantech]

Hello!

We are having a issue with freshness checks. Let me explain our nagios XI environment first.

We have 4 customers with windows machines we monitor with NSClient++ and Nagevlog. We monitor our customers only passive for security and performance reasons. To verifide a server is up and running we have freshness checks enabled. NSClient++ sends out a passice check result at least every 60 seconds. The freshness checks will force a host to enter a critical state if the information is older than 300 seconds and a notification will be send to the service desk. This al works fawless.

However when we configured our internal servers with the same configuration as our customers, the host keeps flapping. Before the freshness check threshold is exceeded, the host jumps into the critical state that is specified for the freshness checks. (probably when a active check ore an SNMP check is received.)

The only difference between our customers and our internal network, is that we use active checks (SNMP) and passive checks (NSClient++ nagevlog) in our network. When i disable the active checks of a host, the freshness checks work and a host is responding normal (no flapping state)

It seems to me that there is a some kind of conflict/misconfiguration but i cant find it! I hope you guys can help me out with this issue.

Version: Nagios XI 2011R2.3 (update is scheduled this week)

Roel van Dijk
Lantech

[scottwilkerson]

Freshness checks are designed to be used just with passive checks. Active checks should not need freshness checks because Nagios is already scheduling their check interval.