For ARS: - Create an F5 farm for udp/111, tcp/111, and the port ars listens on - Enable session persistence based on src ip (needed due to floating licenses) - Configure a server group in ARS
For MidTier: - Create and F5 farm for tcp/80 and tcp/443 - Enable session persistence based on src ip (needed because midtier does not synchronize/use central store for session information) When you configure the midtier as to what arservers to point to, there are a couple of options: - point it to the ars farm: this causes issues because all midtier sessions go to the same arserver - point each midtier server to the individual server When working with the F5, you need the arservers to be on a network that gives a route to the db that does not traverse the F5. This is typically accomlished using a back end network that the arservers and db servers are connected to. Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. On Fri, Dec 4, 2009 at 2:35 AM, Martin Liu <[email protected]> wrote: > ** Hi List, > > I have two physical windows machines running ARS. > > Another two machines behind F5 are installed Mid-tier, they will connect to > ARS. > > The customer have HA requirement for ARS. I could have two options: 1)MS > Windows Cluster; 2)Remedy server group. > > But I don't know how to configure for HA architecture. Any advice? > > -- > Regards, > > 刘征 Martin Liu > ---------------------------------- > Blog: http://martinliu.cn > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers > Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
