Thanks for the info everyone, I tested it last night and it worked great, we now have load balancing and the keepalive running. Here's the config for one of the services
Cheers Pat service portal2 ip address 172.16.10.12 string portal2 protocol tcp keepalive port 81 keepalive type http keepalive uri "/index.html" active sam sneed wrote: > There are 2 methods of keepalives, get and head. > > get: > CSS gets the web page, computes a hash based on the page and stores it for > reference. The next time the CSS gets the webpage it looks for 200 OK and > stauts and compares the new hash with the hash stored for reference. If they > are different the CSS marks the service as down. So you can conclude this > method only works well for static content on pages. > > Head: > CSS only issues an HTTP head on the service and looks for 200 OK status , if > it gets it service is marked up other wise its down. Less overhead than get > method and good for Dynamic content as well. > > hope that helped a bit. > > ""Patrick Donlon"" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > Hi Dave > > > > I've not had chance to test the keepalive yet but I see you mention using > > head or get > > can depend on the page type. Can you explain further or do you have any > > links? > > > > Cheers > > > > Pat > > > > David Harrison wrote: > > > > > This is correct. The domain name is not necessary. Since the CSS knows > > > the ip address of the box it's watching it doesn't have to rely on a > > > domain name to find the location of the server. > > > > > > However it is important that the css know the path to reach the > > > reference page. > > > > > > I've used the following: > > > service blah_blah > > > ip address 10.1.1.1 > > > keepalive frequency 8 > > > keepalive type http > > > keepalive uri "/.reference/arrowpoint-keepalive.html" > > > active > > > > > > I usually use the default "head" method vs the "get". Depends on whether > > > the file you are watching is static or dynamic. > > > > > > Dave > > > > > > -----Original Message----- > > > From: John Neiberger [mailto:[EMAIL PROTECTED]] > > > Sent: Friday, May 03, 2002 12:19 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: Content Switching and Keepalives [7:43141] > > > > > > I'm not positive about this but I don't believe you're supposed to > > > include the domain name in the URI. We simply use 'keepalive uri > > > "/index.htm"' and that works well. Give that a shot and see if it works > > > for you. > > > > > > John > > > > > > >>> "Patrick Donlon" 5/3/02 9:54:47 AM >>> > > > Hi > > > > > > I tested it and for some reason it didn't work, I configured the > > > following > > > on the > > > service: > > > > > > keepalive port 81, > > > keepalive method get, > > > keepalive type http > > > keepalive frequency 25, > > > keepalive retry 25 > > > keepalive uri "www.blahblah.com/index.html" > > > > > > I then activated the service (and re-activated it a few times just in > > > case) > > > Any thing > > > obviously wrong and what should I check in the log > > > > > > cheers > > > > > > Pat > > > > > > Patrick Donlon wrote: > > > > > > > Hi All > > > > > > > > I have two web servers which are being load balanced behind a CSS, > > > this > > > > is working fine. Currently we're using the default ICMP keepalive, > > > this > > > > is OK if the failure is at this level but when the web services > > > process > > > > is stopped by the DBA the CSS thinks it's up and running. I've seen > > > the > > > > different options, tcp, http gets, etc, and would like to know > > > anyone > > > > else's experience in what is the best balance over performance and > > > > detecting the lost of service > > > > > > > > Cheers > > > > > > > > Pat > > > > > > > > [EMAIL PROTECTED] Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=43475&t=43141 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
