Nimbostratus
MVPRead this carefully:
Check time until up, manual resume, ramp up time, etc. Also, be sure to check the timeout and monitor check settings.
Finally, you are making a very very BAD assumption. Ping is not a good monitor. If a web server reboots, and even the BIG-IP has a web server, the device will respond to Ping way before it responds to HTTP. Why? Device is rebooting and the HTTP service has not yet started!!! So even if you have manually marked the server as up immediately via Ping, it doesn't mean the backend server is ready to accept HTTP connection and indeed the client may be experiencing an outage at that point.
Nothing in life is quick, have patience 🙂
NimbostratusMany thanks for the reply.
I think I wasn't very clear on the issue.
So I'll give as an example
I have an application that is with the MONITOR (TCP) when there is an oscillation in the network, this monitor drops and does not come back when the application returns (I have to manually) make any change in the Monitor to force it to respond with status ok
MVPYou need to provide some more information my friend!
- Can you post a screenshot and/or configuration snippet of the monitor?
- Can you search /var/log/ltm and grep out the log entries for this particular monitor?
NimbostratusThe issue is that when the network presents instability and the monitor points as offline status, however the network works again and the Monitor status does not change automatically. like this was a bug or something.
because I have to go manually (change any parameter) inside the monitor for it to reprocess