For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Taj_150182's avatar
Taj_150182
Icon for Nimbostratus rankNimbostratus
Aug 13, 2015

virtual server web server request

I have a request as below. We have •webservers are apache in on VLAN 100 •application servers are jboss in VLAN 101 •Virtual server of LTM is on VLAN 100 •I have other VLANs 102, 103 etc configured with SIP/FIP in LTM •All the VLANs 100, 101, 102 etc are created in core switch. •F5 ltm, web servers, app servers are connected to core switch •default gateway of web servers are FIP in LTM •default gateway of application servers is core switch.

 

The traffic flow is user PC --> VS --> Web server --> app server

 

The requirement is 1.Users need to connect to virtual server which in turn load balance to web servers (This is straight forward) 2.The web server and app server need to view the user PC IP address.

 

a.I can use x-forwarded-for or irule to configure it or b.disable snat 3.on a separate transaction, app server need to communicate to web server a.For this I can create a NAT for web servers on vlan 102 in F5 ltm and provide it to app server to communicate. This is the traffic will be flowing via F5 (App server --> F5 --> webserver) or b.I can configure static routing in core switch, such that for web server IP address (source) next hop is F5 ltm FIP (gateway) and create forwarding IP virtual server for vlan 100 and vlan 101

 

Can you tell me which option is better to use, 3(a) or 3(b)

 

1 Reply

  • Isn't there a communication now between the Web & App Server? It would also be appropriate to see the routing on the core switch and F5.

     

    I would rather prefer 3(a) but it would again depend if you have route back to App servers on the F5.