I posted last week asking for assitance load balancing WebLogic apps. I received some good responses, but they didn't work. I submitted an F5 support case and was basically told they don't help build new configurations, only fix "broken" ones and I should use professional services. I found some third party WebLogic admin books that suggest load balancers should NOT replace proxies, but be used with them.
So my current isue. I had an existing IIS server using host headers to accept the incoming requests, handle SSL requirements and proxy (forward) HTTP requests to some WebLogic nodes.
I changed DNS and put F5 in front of this (still using a single VIP entry point) to route to the same IIS box then proxy to WebLogic. With this setup I have a few sites (4 out of 11) that seem ok. The rest show infinite loops on the redirects. I've rechecked the IIS config multiple times to make sure the SSL redirects were removed and sites are now HTTP only. The IIS logs seem to show that the traffic actually never gets to the IIS server. I can't seem to figure out how I introduced this redirect. I'm wondering if I need to remove the idea of "host headers" on IIS or F5 or both to get this stable and working.
Hi, Are you asking for the iApp or VS on the F5 or the IIS? I suppose I could figure out how to export the full configuration and share it for review. When I was debugging the new setup yesterday I wasn't actually seeing any evidence that the traffic got past the F5. I think my redirect loop might be occurring there. I'm going to try a wireshark capture this morning on the IIS server to see if I can confirm this.
Thanks for clarifying. I should be clear though, I am using one VS on F5 and a shared IP on IIS to support IP sharing on both devices. My VS looks like this:
The iApp has all the DNS names attached to it and I have an iRule for handling the redirects to URLs that IIS will then proxy to the WebLogic.
I did start my captures on IIS and did find that I missed some of the require SSL settings so at least some of my failed tests are my own stupidity and lack of quality control. I'm still reviewing. However, I'm now questioning this configuration and if it's something that F5 really isn't going to handle well. If I'm forced to request a bunch of new IPs and DNS entries to make this work properly I can abondon this effort and start that approach.
I will note that I've played with this iRule frequently and even completedsome of the testing withot the iRule in the config. That's actually tru of the VS also. I started disabling profiles to see how or if it imapcted the errors but never found these efforts to change much. (Sometimes it got worse)
Right now the pool is actually just a single node and I changed the HTTP port to 81 to help isolate the traffic during dubugging. Yesterday when I thought a lot of the traffic never got to IIS it was based on the IIS logs showing the health traffic but not my testing traffic.
ltm pool IDCFLB.app/IDCFLB_pool { app-service /Common/IDCFLB.app/IDCFLB members { dewsvweb1:81 { address 146.142.201.51 app-service /Common/IDCFLB.app/IDCFLB session monitor-enabled state up } } monitor IDCFLB.app/IDCFLB_http_monitor slow-ramp-time 300 }
Another follow up on my self imposed quality control problem. I only found 1 site where that was the issue. Still have some sites that show the too many redirect errors, but it is inconsistent. A couple sites showed this error then a few seconds later loaded. Right this moment I have more sites loading the home page than not (haven't started deeper regression testing yet), but the incosistencies definitely curb my enthusiasm that I actually fixed anything.
