A little off topic, but has anybody tried similar with Foundry. Got it to work yet? Got it to fail properly when the service is unavailable or does it pass the ICMP health check, then fail the layer 7 check and flap forever. Can't believe how flaky Foundry is turning out to be recently.
I've got a bee in my bonnet... Layer 3 filtering on Foundry NetIrons contained in all the documentation. Tried to implement it, didn't work, reported to Foundry. Informed that NetIrons do not now support it. Sure enough, the documentation was almost immediately updated. They've just binned it - one of many. Bit late when you've sold it. Tried adding/removing ports from VLAN's with the web management. Doh! We're looking at stripping out ServerIrons and putting in CSS, partly due to the extra flexibility available with the Cisco health checking, but mainly because the support works! You can knock Cisco all you like, but we keep coming back to them. Anybody got any views on this? Gaz ""David Harrison"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > 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=43272&t=43141 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
