Accelerating the probe verification in failed status
Hi experts. We are using an ACE 4710 and we decided to put some probes on our server farm for health monitoring. Those probes are set to monitor the health on each 60 seconds in order for us not to full the IIS logs. But if a real problem occurs, I want that robing to accelerate to 5 seconds each time. If it fails after 3 attempts, I would want to close this real server. Any clue on the settings I should use for probing?
Re: Accelerating the probe verification in failed status
Thank's for the answer. The only thing I am not sure of is that there is a field for he passdetect interval which I believe is the time a new probe will be sent to a passed probe after a server as been in a failed state. In regards to this option, the pass detect count would be the number of time a probe request would be sent to that same failed server before it is brought back in the server farm.
But I dont see any faildetect option which could have accelerated the probe on a fail server in order to take a decision whether or not to take that server out of rotation in the server farm. I believe we have to wait until the next probe which could have been scheduled to happen at a later time. Am I correct on this one? Am I missing something?
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...