Proxy configuration


Hello all, How are you ?

Well, i'm new to F5 product and here at DevCentral. I'm  using LTM and ASM modules.

Im trying to do some configurations and exploring them to get used with it. I have a service endpoint URL and for now I just want F5 to be a proxy receiving the service's request and fowarding it to web service adress.

I tried to do it but without success, I read F5 white papers and tutorials but i didn't get it well.

Could someone give me a hand on this?

Thanks in advance.


7 Answer(s):

What have you tried exactly? For LTM;

1) Create a Pool with your real server(s) as Pool Members using the relevant Service Port number
2) Create a standard Virtual Server with a HTTP profile assigned and the Pool you created in 1)

That's it really.

Maybe i was not too clear.... I just want F5 for now to receive the requests and foward it to the backend server wich service is exposed.

Reading white papers again, I see that first of all I need to create a VLAN, but where do I make the mapping from F5 to my web server?

Let me see if I'm rigth. The virtual server to F5 is my web service server ? So how will it understant that i want that especific request to be forward to it ?

Here is the senario:
I have a web service endpoint... lets suppose that it is like:
I don't want clients acessing it directly... So i would like to "virtualize" it... the goal is I want the client sending the request to F5 in another IP and Port and F5 fowarding it to the real web service endpoint.

I think it is not very hard to do but as I'm newbie at F5 modules, I'm taking a beating trying to do it. Getting back to vlans.... which are the best pratices now a days? I think that is possible to acomplish my goal with just one vlan but what do you guys advise me?

PS: I'm using smith Big IP Virtual Edition.

Thanks again.

OK, so you have a fresh, licensed install with nothing configured?
Posted By What Lies Beneath on 01/03/2013 08:11 AM
OK, so you have a fresh, licensed install with nothing configured?

Yes, that is it.

Anyway for the network setup, see here:

For the LTM Virtual Server etc., see here:
network configuration (e.g. vlan, selfip, route) is to make bigip able to communicate to other devices.

for load balancing confiugration, you may review implementation guide. Basic Web Site and E-Commerce Configuration is an example of two-armed (two vlans) deployment. Setting up a One-IP Network Topology is for one-armed (one vlan) deployment.

Manual: BIG-IP Local Traffic Manager: Implementations

hope this helps.
this is another good article for newcomer.

Quick Start: Application Delivery Fundamentals by Josh

Your answer: