is BigIP connect Webserver with client?

Hi Rajesh,

 

 

When you say session do you mean a TCP connection or a browser session? If you enable a OneConnect profile, LTM can select a new pool member for the same clientside TCP connection. Without a OneConnect profile LTM will not select a new pool member for a clientside TCP connection. For a browser session, you could enable persistence on the virtual server to ensure the client is sent to the same pool member over multiple HTTP requests/TCP connections. You can check the LTM configuration guide for your version for more details on persistence.

 

 

Aaron

Actually we are having website developed in asp.net,as I mentioned that our website is hosted on three server which is manged by Big-IP.Now we want to keep our webpage viewstate in session so our page performance get increased.what we are trying to understand that if we keep our viewstate in session than whether the client request will come will be handled by only one webserver or big ip will route it on another webserver, if same client in same browser put the request next time and webserver get changed than we won't be able to access the view state.

 

Please help me out

 

Thank for your kind help.

 

 

The simplest and most effective persistence option is to use cookie insert persistence. When you enable this option on the virtual server, LTM will insert an HTTP cookie in the response and use that cookie on subsequent client requests to track which server the client was sent to on previous HTTP requests. You can create a custom OneConnect profile with a 255.255.255.255 source mask to ensure LTM processes multiple HTTP requests on the same clientside TCP connection.

 

 

Aaron

have you tried using persistence. You can either go with Cookie persistence or source ip persistence. Given your description I think going with source ip persistence is better.

 

After the VS set-up is done, you should see the source_ip persistence profile in the drop down on the Rsource tab.

I am using two method LoadPageStateFromPersistenceMedium() and SavePageStateToPersistenceMedium() to store viewstate into session.my problem is not that how to maintain/store viewstate.I have very simple query that whether if any request comes first time from any client to any my webserver than is there any possibility that Big_IP will pass the second time any request from same client within same session to my another webserver?

If I and dochack understand your requirements correctly, enabling session persistence on the LTM VS will work. I'd suggest using a 255.255.255.255 source mask OneConnect profile and a Cookie Insert Persistence profile on the VIP to do this. Else, source address persistence should work also.

 

 

Aaron