LTM pool showing as Red(down) and unable to connect before deadline
I have a couple pool members that are not responding to 443 monitors all of the sudden, It has worked fine forever but not it is in a down state while the port 80 monitors continue to stay green. is this most likely a health monitor issue? I wouldn't think so since it operated properly beforehand. the troubling part to me is that is down on 2 separate nodes both for 443. The only thing I can think is that it could be on the customers side but I am really not sure why it would be 443 only. any insight would be very helpful
Best way to set a pool member as Disable from Irule
Hi all, I have a requirement that needs pool members to be disabled when a certain number of concurrent sessions has been reached to stop new sessions going to the member ( memory locking errors in the app occur above certain user counts and they would rather hard deny users then bring everything down). I have written an irule that does all this tracking and management but what i cant figure out is a simple good way to disable nodes. This irule will be applied to many pools and 100 odd nodes so it cant be hard coded. Right now in my dev environment i am lopping over pool members and if any are over threshold using LB:DOWN on that pool member. After looping i then forcing a LB::select, this works because i am relying on a health monitor up delay to keep all the members i just marked as down, down. Thus this logic gets repeated for every new session, and i have nodes constantly going up and down. i would much rather mark them as disable and bring them back to active if the session count drop below threshold then what i am doing now but i cant figure out at good way. i cant see how you would do it with icall as all the example i see have hardcoded triggers. So what will work best? i assume some kind of sideband connection? also running 11.6 HF5 All advice and ideas welcome! cheers
How to configure members in pool... Wildcard or specific ports?
I'd like to know the best practice for putting members in a pool. I have a two virtual servers setup for an application, one for tcp 80 and one for port 50000. Both of these virtual servers use the same pool. Is it better to have the members as 192.168.1.10:80 and 192.168.1.10:50000 or just use 192.168.1.10:0? I will have multiple servers in the pool for load balancing.
