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

J_46981's avatar
J_46981
Icon for Nimbostratus rankNimbostratus
Jul 26, 2007

BigIP fronting IIS 6.0 w ASP.NET

More of an inquiry to confirm some suspicions I have, but am having difficulty proving to the IIS management team.     I have 2 IIS/ASP.NET appservers behind BigIP in a round-robin config. I am...
config
design
Deb_Allen_18's avatar
Deb_Allen_18
Historic F5 Account
Jul 26, 2007
Not sure how helpful I can be since I am not an ASP expert, but in general, to LTM, ASP webserver just looks like any other webserver, so standard webserver load balancing optimizations would in order:

 

 

SNAT is not required, so if you want to limit by unique IP, you can set the webserver default route to the LTM floating self-IP and disable SNAT to preserve the true client IP.

 

 

OneConnect will pool connections on the backend, using keepalive connections for multiple requests. With the default mask, connections will be shared among all clients, substantially reducing the number of server-side connections.

 

 

Depending on your LTM version and traffic profile, you may want to tune the tcp profile for LAN traffic as detailed here: Click here

 

 

HTH

 

/deb

 

 

(If you find additional settings that are useful, please post back and I will start a new page specific to ASP server load balancing.)