Forum Discussion
real_ever_21524
Nimbostratus
Nov 22, 2018Connection limit log
I've set a connection limit for a cluster node, which triggers periodically. It looks like this:
01200017:4: Warning, pool member IP 1.1.1.1 port 80 for pool /PR/eeee.com has reached its connect...
Ustapon
Nimbostratus
Nov 24, 2020I have this issue too.
- jaikumar_f5Nov 24, 2020
Noctilucent
You could go with LB_FAILED event and capture the required info via loggings.
LB_FAILED do gets triggered when connection limit is increased.
Later use the logs and figure out your unique source ip's or if logs are forwarded to some external app's like splunk, filter it there to find the unique sources.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects
