Has anyone managed to setup up load balancing using an F5 with two Integration servers?
I have been trying to get this working without any luck. We configured the F5 so all traffic goes through the same FQDN and IP (originally when you pinged the FQDN it was replying with either of the IP numbers from the two Integration servers) however getting inconstant results.
I can go on a users machine and point it towards the FQDN and it correctly brings up the datasource and I can access the files okay but then I can then try another file and it hangs then gives me a logon prompt. When I check the logs on the Integration server that they have been connected to it will say there has been a ODBC error although its clearly okay as it connected fine the first time. This is the error I receive.
Is there any other documentation anywhere explaining how to setup Load Balancing with the F5 or Windows Clustering even? The only thing I have found is a section in the PW implementation manual.
Thanks in advance,
Yes, we have it running with 4 integration servers.
in the dmskrnl.cfg:
1. ServerName and ServerIPAddress must be set to the name/ip used on the F5
2. the fileaccesstoken must be identical on each integration server
and this was a new one we ran into when we upgraded to the latest server version last month:
3. the odbc database passwords are now uniquely encrypted on each server. This means you can't just copy the dmskrnl.cfg from box to box. On each server in your [db##] section for each data source set the database password encryption level to 0 and the password itself to the plaintext password.
projectwise will encrypt the password and rewrite the dmskrnl.cfg with the update. Verify the fileaccesstoken didn't change when you did this.
Because you're having database login issues I suspect you hit that last one too.
(and it really annoys me, I understand the extra security it gives but now dmskrnl.cfg on load balanced servers are different, which sucks).
Thank you that seems to have resolved the ODBC errors.
Now I just need to resolve the F5 changing the users IP number to one of the F5 meaning that caching is impossible. It means im unable to pick a users subnet and point them towards their local cache server because of it masking their IP.
Are you using cache servers with your F5 setup?
Thanks again for your help its much appreciated.
We haven't seen this problem (when i look at the log on our integration servers i see the actual ip addreses of users, not the F5). I didn't configure our F5 we just asked our network group to point a dns name at our 4 servers and it pretty much worked....
that said we may also be avoiding the issue because of how we setup our clients for configuration.
We have a single connection server (not an integration server) setup internally. It has all gateway statements and [dbXXX] blocks on it for all our offices/datasources. We put this server into everyone's ProjectWise Network Configuration Panel. This server is not load balanced for us (yet, we'll probably do that sometime this year).
The [dbXXX] blocks point them at the load balanced integration server dns name. The gateway statements on the connection server point each subnet to their local cache server using ALLOW/DENY statements. we do NOT route traffic through the connection server itself (which is why we don't have to load balance it. user's connect to it for a few seconds on launch, then don't connect again)