Forum Discussion
Mar 04, 2014
Check here for a list of deployment guides: https://f5.com/solutions/deployment-guides
Choose the guide that fits your components the best ie, Microsoft Internet Information Services + v11, and follow it as well as you can.
Your scenario seems to be a pretty much straight forward solution covered by the docs in that list.
Short version of what you need to do it:
- Create nodes (the server IP's that hosts your application). Local Traffic -> nodes
- Create a pool and assign those nodes as members. Local Traffic -> Pools
- If the application will run over ssl, you need to import an SSL certificate + key or create a self signed one (self signed is NOT recommended for security reasons). System -> File Management -> SSL Certificate list
- Create an SSL profile and assign the certificate + key in the drop down menus. Local Traffic -> Profiles -> SSL -> Client.
- Create a virtual server and chose the public IP you want to use for the people accessing the application. -> Local Traffic -> Virtual servers
- In the Virtual traffic creation form, choose HTTP profile "HTTP", choose the SSL Client profile you just created, choose the pool you created earlier as default pool
- If your application servers does not use the load balancer as default gateway you need to specify "automap" in the "Source translation" option when creating the virtual server. Please note that this would hide the client IP's in the web server logs unless you enable X-Forwarded-For and make sure that web servers can log that header value.
Note that this short guide would assume that you have everything correctly setup in terms of networking on the load balancer (self IP's, VLANs, routes, etc).
But I would still check out the deployment guide. :)
Good luck!
/Patrik