An example: http://msdn.microsoft.com/en-us/library/windows/desktop/cc307934(v=vs.85).aspx
More information: http://blogs.msdn.com/b/clustering/archive/2008/06/24/8648702.aspx With Remedy you either need to check the port that Remedy listens on or you need to emulate an RPC conversation to the server and take actions based on that response. The bad thing about just checking the port is that the port can be bound to but the service may not be responsive, for example, during start-up or a hang. Axton Grams On Thu, Oct 27, 2011 at 3:52 AM, Phil <[email protected]> wrote: > Hi, > > I’m trying to set up a Remedy server group to load balance 2 app > servers behind a Windows load balancer 2008. > > Remedy is configured to run on a specific port and the Windows load > balancer is configured with a port rule as follows: > > Cluster operation mode: Unicast > Filtering Mode: Multiple Host > Affinity: None. > > The Life span setting is enabled in Mid Tier. > > I can succesfully connect to Remedy via the wlb but if I stop the > Remedy service on one of the app servers the WLB doesn’t appear to > recognise the service is down and still attempts to connect to the app > server which is down causing the login to fail. > > What do I need to do to ensure the wlb won’t direct traffic a server > when the Remedy service is not running? > > Thanks > > Phil > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.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"
