Re: Cheetah2 connection manager and failover arbitrator

Posted in 2008

Andrew Ford — Mon, 9 Jun 2008 14:08:54 -0500 — source: Usenet: comp.databases.informix

----- Original Message ----- From: Nilesh Ozarkar To: Andrew Ford Cc: informix-list@iiug.org ; informix-list-bounces@iiug.org Sent: Monday, June 09, 2008 11:13 AM Subject: Re: Cheetah2 connection manager and failover arbitrator > I think so - depends on how you configure SLA. To avoid > redirection to dedicated port, use explicit server names in > SLA configuration instead of server type and avoid using the > dbserveralias which is configured with s=6. I tested and using explicit server names in the oncmsm.cfg file does not prevent a connection redirect to the other dbserver aliases for that engine. With my CM SLAs defined as SLA cheetah_pri=cheetah04 SLA cheetah_sec=cheetah03 I am still redirected to the cheetah04 and cheetah03 dbserver aliases (cheetah04_hdr and cheetah03_hdr) Even if this would work I would I would have to change the oncmsm.cfg file and restart CM each time a failover occurred to reflect the new primary and new secondary. Let me know if I misunderstood what you meant by using explicit server names for this config. Thanks, Andrew