Forum Discussion
woliver_163458
Altocumulus
AltocumulusNo traffic going to pool, but works with different name
I'm seeing an odd issue on our LTM where traffic will not flow to one of my pools. It's inside an irule, but the issue isn't with the rule itself. In a bit of desperation, I created a new pool whic...
Just in case anyone else runs into the same issue, the problem wound up being we had pools in different partitions/route domains with the same name, i.e. 'DP_REST_FIREWALL_Servers', which confuses the device if the partition is not explicitly called out. So the fix was just a matter of updating the irule to read
pool /D04TS/DP_REST_FIREWALL_Servers
instead of
pool DP_REST_FIREWALL_Servers
What_Lies_Bene1
Cirrostratus
CirrostratusHmmm, I wonder if that's the issue. Can you remove one of the profiles and try again. You should be able to switch between any available on the system as long as at least one is assigned.
LB_SELECTED occurs before there is any communication with the backend server; it simply feels better to me to do it before the 3WHS but technically, after is OK and will work. I also think using LB_SELECTED means the selection only occurs once for that session. With SERVER_CONNECTED it may occur multiple times.
Out of interest, which Pool is causing the issue?