Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Vic on January 01, 1970, 12:00:00 AM

Title: Oracle Cluster and LCA
Post by: Vic on January 01, 1970, 12:00:00 AM
Dear Genesys Pros,

I have a major problem that I cannot resolve and I need your help:

How can I install Genesys on Cluster without resorting to using individual IPs of each machine in a cluster to connect to? If we do that, it defeats the whole purpose of a cluster...

We are using Oracle Cluster for Configuration and Management layers.
So, it means we have two servers:

Server A and Server B with IP addresses A1 and B1.

Since we are using a cluster, we also have a virtual host with the name A (yes, identical to primary server) and virtual ip A1 (yes, identical to primary server ip)

The cluster is working, our TServer running on host D can access either configserver on host A or B through virtual hostname A.

The problem is LCA.

LCA is installed on both machine A and machine B. When we activate machine B, LCA shows that SCS and other products on that machine are stopped even though they are up.

The reason for it is the fact that LCA is using command hostname (we are using AIX) to identify the host where it is running and then it determines what applications it needs to monitor by trying to find applications in CME with the same host.

Since we are using cluster, we cannot register application with anything other than virtual hostname and IP, thus when cluster switches over, LCA B is up and running and obviously all SCS and configserver, etc are also running, but since their Server Host is set to A, LCA B does not see them. Even though they are running on the same machine.

I am sure I am not the only one who has tried to use Oracle Cluster with Genesys. How can it be done?
Title: Oracle Cluster and LCA
Post by: ecki on January 01, 1970, 12:00:00 AM
Are you using cluster to start LCA?
Title: Oracle Cluster and LCA
Post by: Steve on January 01, 1970, 12:00:00 AM
When I do it on Sun Cluster, I create local resource groups on each node for LCA. This puts them under cluster control put doesn't allow them to failover to the other node. The other applications DBServer, Config Server whatever, are installed on the virtual host and it is only the virtual IP address that is know to Genesys in CME.

I normally set the directory in the startup otions in CME to "Controlled by Cluster" to stop anyone using SCI to stop the apps which would cause a cluster error.

SCI can see the correct status of the applications via the LCA on whichever node is mastering the virtual host.

Steve