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

[ruzbehv]

Thanks Guillermo.

Let me know when you hear back from them.

- RV

[Mike Moody]

Hi Guillermo,

I have read that it is mandatory to specify MID Server IP Range for the Orchestration activities to correctly select an available clustered MID server. If you don't want to have to limit the IP range, you could try to create an IP Range record which uses a range of 0.0.0.0/0 which covers the entire IPv4 block, and assign your MID servers to that. Let me know if this works for you. Thanks.

Mike

[madygowtham]

Hi Michael

Hope you are doing well.

Can you please help on this failover clustering where i have the same requirement. And added iprange and made one of the mid servers default and added two mid servers into one cluster with same capabilities.

Thanks in advance.

[Mike Moody]

Hi Madhavarao,

If you are using your clustered MID servers for Orchestration activities, then you should create an IP Address range of type Include Range 0.0.0.0/0 and then go to each MID Server you want the Orchestration activities to run on and associate that IP address range to each MID server via the related list. Also make sure all the same capabilities are selected for each MID Server. That should work.

[madygowtham]

Hi Michael

I have added two clusters with same capabilities   into one ip range as 0.0.0.0/0, still after triggering workflows and checked in ecc queue it is going for default mid server which is not a clustered mid server. Do i need to make any clustered mid server as default server?