Ok, I tried the rule you have above. The user can log into the web portal fine, there is a link on the portal that sends the user to the port 8008 virtual server. Sometimes it works, and sometimes it just hangs. The virtual servers are listed below, and the 2 physical servers are 10.10.11.252 and 10.10.11.253.
here is the output from the log we put in the HTTP_RESPONSE event:
Aug 26 15:53:29 local/tmm1 info tmm1[13658]: Rule persist_prod : cookie value set to 10.10.11.252
I'm still getting the TCL error in the line: foreach member [active_members -list [LB::server pool]] {
Should/could we include both pools in the LB::server function somehow?
What about an irule that grabs the IP::remote_addr from the http_response when the user hits the vs_HTTPS vs, and apply the rule to the 8008 vs, having them hit the same server thats returned by the IP::remote_addr? Is there a way we could do that?
virtual vs_HTTPS {
snat automap
pool p_Luminus
destination 10.10.11.230:443
ip protocol tcp
rules persist_prod
httpclass web-acc-class
profiles {
http {}
luminus-temp-clientssl {
clientside }
tcp-lan-optimized {}
} }
virtual vs_Resource_Prod {
snat automap
pool p_Resource_8008
destination 10.10.11.230:8008
ip protocol tcp
rules persist_prod
profiles {
http {}
tcp {}
} }