Yes.  The health checks from load balancer are typically easy to configure
to look at an http response code.  The bad thing with this approach is that
you are making the availability of the arserver dependent upon the proper
functioning of an application stack (web server, servlet container, etc.)
that has nothing to do with Remedy.  This may also require that the midtier
be on each of the arservers, which may or may not be the case.

Alternatively you may look at writing an iRule to replay a conversation to
the arserver.  If you wrote an api that preforms something simple, like
ARGetServerUser, you could replay that conversation, and that would be more
than sufficient to properly check the health of the server.  This was on my
to-do list for a long time, but I never found the time to follow through.
 The iRule docs are available here:
http://devcentral.f5.com/HotTopics/iRules/tabid/1082202/Default.aspx

Other things I explored, but shied away from:
1. Writing a program to put on the F5 (C language), that checks the health,
then calling that from health check.  this was possible but not reccomended
because of the library dependencies (placing the libs on the f5 could prove
to be problematic in the future).

The program I intended to use is available here:
https://communities.bmc.com/communities/docs/DOC-9059

The discussion on the F5 Dev Central is available here (more good
information):
http://devcentral.f5.com/Community/GroupDetails/tabid/1082223/asg/52/aft/19000/showtab/groupforums/Default.aspx

Axton Grams

On Mon, Oct 31, 2011 at 8:58 AM, Sanford, Claire <
[email protected]> wrote:

> **
>
> When I run this I get a reply that says  “200_OK”  is this what I am
> supposed to see?****
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> [email protected]] *On Behalf Of *patchsk
> *Sent:* Monday, October 31, 2011 12:18 AM
> *To:* [email protected]
> *Subject:* load balancer ars health check****
>
> ** **
>
> ** Just curious to see what are the different health check mechanisms
> being used for ARS in a load balanced env in different companies.****
>
> We are using F5 and we have load balancing for Midtiers and also for ARS.*
> ***
>
> For midtiers our health check was to monitor
> http://webserver:port/arsys/home url. And no issues with this.****
>
> For ARS we are using tcp monitor on the ARS tcp port.****
>
> However recently we are seeing on ars side that the ars tcp port is
> responding fine but the arserver itself is hung, so the load balancer is
> detecting as if the ARS is up and running but users end up getting timeouts
> during login.****
>
> So how are you avoiding this situation in your organization?****
>
> ** **
>  _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to