Confusing SCS/SCI

Administration
1

Hi,

Doing some testing of SCI/SCS and Config Server Failovers in DEV:

SCS: 7.6.001.03 (Solaris)
SCI: 7.6.001.06 (WINTEL)
ConfigServer: 7.6.000.20 (Solaris)
CME/CIM: 7.6.001.01 (WINTEL)

We have the environment running with a single VirtualIP for resiliency, through VERITAS (sic). The “problem” Scenario is:

ConfigServer PRIMARY fails over to BACKUP. SCS/SCI is ok with this.
When ConfigServer PRIMARY returns, it returns in BACKUP Mode, on the PRIMARY Server. SCS/SCI is not ok with this - it refuses to start.

I am aware that there are configuration parameters which can be set individually for SCS and we’ve looked at those but no further ahead.

Has anyone experienced this before? Perhaps that CofigServer PRIMARY returns, but does not actually return as PRIMARY but remains in BACKUP mode..?

Thanks!

ESS

2

What have you got in confserv.cfg for both apps?

3

Thanks Ben - it looks like there is a Hot Fix for SCS 7.6.001.03 (7.6.001.05) which ensures that the SCS retries if unable to connect to the Config Server first time around. Apparently, 7.6.001.03 version only tries once, then gives up…

ESS

2 Likes