Workings of the Connectivity Verifiers (Full Version)

All Forums >> [ISA 2006 Firewall] >> Logging and Reporting


rmharp -> Workings of the Connectivity Verifiers (20.Jan.2010 11:37:19 AM)

I have read the articles about the inner workings of the ISA connectivity verifiers but one thing has never been totally addressed. 

I have a connectivity verifier that does an HTTP Get request out to a web farm that is critical for operation.  The timeout is set to 5000 ms (the default) 

At what point does it trigger a "No Connectivity" Alert?  Because I get "Slow Connectivity" Alerts and it states that the measured response was 9452 ms or 12343 ms.  So I would assume this breaks the 5000 ms threshold and it should throw a "No Connectivity" alert but it does not.  At what point does a "Slow Connectivity" turn into a "No Connectivity"?  Is there a drop dead point in there somewhere?


PatrickM -> RE: Workings of the Connectivity Verifiers (6.Oct.2011 4:39:58 AM)

Im trying to understand this myself :)
When I interperate this tutorial :
..i draw the following conclutions:
If threshold set to 5000msec (default) the Slow Connectivity will trigger from 5sec up to 30sec. Above 30 it will trigger No Connectivity.
Can someone confirm that I understand this right?

What if I set threshhold to a number above 30000msec? like 50000msec...
Does it wait two cycles (2x30sec) before flags as No Connectivity?

Then.... A really strange thing we've notised:
Depending what threshold I set, I get different responcetimes... Not that it should be affected of threshold...

Aprox. Examples:
Threshold set to 50000msec gives responce of 60000-65000msec response(website restart)

Threshold set to 25000msec gives responce of 36000-44000msec response(website restart)

Threshold set to 5000msec gives responce of 15000-20000msec response(website restart)

Threshold set to 2000msec gives responce of 4000-6000msec response(website restart)


Page: [1]