Thanks for your suggestion. I did not prefer do this. But tried to check whether am i achieving the persistence or not.
Can we achieve this with any other work around? Thanks -Sujith On Tue, Jun 15, 2010 at 6:42 PM, Scott T. Cameron <[email protected]>wrote: > port http sticky and cookie insertion are mutually exclusive. Basically, > sticky will override the cookies. > > The implication is that any group of users who use the same IP address > (proxy or ISP NAT) will all be stuck to the same server, rather than an > accurate loadbalance based on real users. > > There may be other implications, but that one is usually the important one. > If you have only 10 users, and those 10 users all come from 1 IP address, > they will only ever hit 1 real server. > > Scott > > > On Tue, Jun 15, 2010 at 9:08 AM, Sujith <[email protected]> wrote: > >> Hello, >> >> As Scott suggested, i have configured the virtual server with port http >> cookie-name ServerID with port http sticky option to get it working. >> >> At present, I am not facing any connection timeout or error from the >> application perspective. >> >> Is there any other implications on adding the sticky options? >> >> Need your valuable suggestions!!! >> >> Thanks >> -Sujith >> >> >> On Mon, Jun 14, 2010 at 7:31 PM, Sujith <[email protected]> wrote: >> >>> Hi Scott, >>> >>> I just tested with the below recommendations and still I am getting the >>> error on entering the login credentials. >>> >>> Thanks >>> -Sujith >>> >>> >>> On Mon, Jun 14, 2010 at 7:08 PM, Scott T. Cameron >>> <[email protected]>wrote: >>> >>>> You need 'port http cookie-name ServerID' on the vserver. >>>> >>>> You'll probably also want to change no-http-downgrade to port http >>>> keepalive. >>>> >>>> Scott >>>> >>>> >>>> On Mon, Jun 14, 2010 at 9:36 AM, Sujith <[email protected]> wrote: >>>> >>>>> Thank you very much for all your suggestions. >>>>> >>>>> I have attached the running configuration along with this email. The >>>>> configured rule no. 30 and rule no . 31 is configured for server >>>>> persistence. >>>>> >>>>> Please let me know if there is anything wrong with the configuration. >>>>> >>>>> Thanks >>>>> -Sujith >>>>> >>>>> >>>>> On Mon, Jun 14, 2010 at 6:35 PM, Scott T. Cameron <[email protected] >>>>> > wrote: >>>>> >>>>>> There's not really any good technical reason for not inserting a >>>>>> cookie. >>>>>> >>>>>> However, you can enable IP-based sticky via 'port # sticky' on the >>>>>> virtual server. This can lead to very imbalanced traffic if any users >>>>>> behind large NATs/proxies connect to your website. >>>>>> >>>>>> Those are your only two options as far as persistence is concerned. >>>>>> >>>>>> Scott >>>>>> >>>>>> On Mon, Jun 14, 2010 at 8:17 AM, Sujith <[email protected]> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> Thanks for your valuable time and suggestions. >>>>>>> >>>>>>> I have a website hosted on 3 servers and the servers are load >>>>>>> balanced using ServerIron 4G-SSL using a round-robin predictor. >>>>>>> >>>>>>> I need to configure certain URL to be persistent on single server for >>>>>>> the complete session initiated by the Client to the server. >>>>>>> >>>>>>> The web application are written in asp.net and the client is very >>>>>>> much sure of not inserting cookies into the client browser. >>>>>>> >>>>>>> The problem i am hitting at it is, whenever i hit the URL from the >>>>>>> client browser, i get the http page from the server where i have to >>>>>>> give the >>>>>>> username and password. Once the credentials are entered, i get a error >>>>>>> page >>>>>>> and i believe it is redirected to another server on round robin and the >>>>>>> persistence is lost. >>>>>>> >>>>>>> I run through the Foundry guide and brocade community portal for >>>>>>> cookie switching. At present, i tried to do a cookie switching given >>>>>>> exactly >>>>>>> in the brocade portal for cookie switching. This solution works >>>>>>> sometime and >>>>>>> suddenly it does not work. >>>>>>> >>>>>>> I have not tried or tested on other solutions. >>>>>>> >>>>>>> Also please let me know, if we can track or troubleshoot from the >>>>>>> ServerIron perspective. I did not >>>>>>> >>>>>>> If the above explanation is not clear, please let me know. >>>>>>> >>>>>>> Thanks >>>>>>> -Sujith >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> foundry-nsp mailing list >>>>>>> [email protected] >>>>>>> http://puck.nether.net/mailman/listinfo/foundry-nsp >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> foundry-nsp mailing list >>>>>> [email protected] >>>>>> http://puck.nether.net/mailman/listinfo/foundry-nsp >>>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> foundry-nsp mailing list >>>> [email protected] >>>> http://puck.nether.net/mailman/listinfo/foundry-nsp >>>> >>> >>> >> > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp >
_______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
