Cluster configuration not working

[guiguille]

Hello guys,

I'm trying to configure a high availability schema in our SN instance for orchestration. So I started looking into capabilities. The thing is that for themselves they don't seem to do anything. Then I read that capabilities work inside IP ranges, and that's something I don't want to use.

So I found clusters, that according to what I read, the configuration shouldn't be too difficult. So, this is the process I followed:

• I created two mid servers
• I added to both of them all the existing capabilities (we don't have any custom created ones)
• I set one of them as the default one
• I create two clusters, one failover and another one load balance with these two servers (I tried first with only failover that is what I want, but it failed so I created the other one)

According to what I read, this should be enough to have a cluster between these two servers, in case one is unavailable. So, my test was to stop the service of the default mid server, and run the workflow. When I do that, I get the error "The configured default MID Server (<DefaultServer>) is not available". When starting the default server's service, the workflow runs without problems (I'm just trying to get the ipconfig from the localhost in my test workflow).

I'm running a "Run Powershell" activity, so adding the Powershell capability should trigger this, right? I'm not sure if I'm missing something.

Thanks in advance, any feedback is appreciated.

Regards

[bernyalvarado]

Hi Guillermo,

Do you have one of your mid servers in the property: mid.server.rba_default ?

Thanks,

Berny

[guiguille]

Hi Berny,

Thanks for the response. Yes, when I was talking about the default mid server, I was referring to the value that appears in that property.

[ruzbehv]

Hi Guillermo,

Were you able to figure the required configuration?   I have the same requirement.

Regards,

RV

[guiguille]

Hi Ruzbeh,

Sorry for the delay. We received a notification from SN that the issue was solved, but when I tried, I got the same result. Waiting an answer from them.