First, did you setup your server group?
Second, server group name is whatever you want. Well, respecting dns regulations of course, something like: "sgname".
On the ARS server, it doesn't need to point (be resolved) to the LB in front of the ARS, actually it's better to make it point to the ARS server itself.
So if you have ARS1 and ARS2, "sgname" DNS on ARS1 should point to ARS1, and "sgname" DNS on ARS1 should point to ARS2.
On the mid-tier "sgname" should point to the LB in front of the ARS servers.
Now, if you don't have any LB in front of the ARS and you have two mid-tiers, that means there is no real balancing. So in Mid-tier configuration you should use "sgname" as an ARS server name, but dedicate one Mid-tier on one ARS (direct link).
So for example MT01 should forward to ARS01 and MT02 to ARS02.
In order to do that:
-> on MT01, that means that "sgname" should point (be resolved) to ARS01,
-> on MT02, that means that "sgname" should point (be resolved) to ARS02,
When you'll have a LB in front of the ARS, you'll just have to resolve "sgname" to the LB's IP (on the MT servers).
Well you'll have the failover at "operation" level. For example if you put FTS indexing on ARS1 at rank1 and FTS at rank2 on ARS2 and ARS1 is down (maintenance / reboot), ARS2 will "failover" the FTS.
Though as MT1->ARS1 and MT2->ARS2, if ARS1 is down, that means that all query that go to MT1 will fail since ARS1 is down.
Hummm, can you try opening all ports? disabling the portmapper is quite easy, it means, in ar.cfg (and set a TCP port):
And of course deactivate "ARS portmapper" (or something along this name).
Of course if you had configured the midtiers, change the configuration of ARS servers in mid-tier config page, the TCP port would be "3500" now.
Hi Good Day!! I tried configuring the primary server as per the server group white paper. What happened is that the plugin server stopped responding and users where not getting autheticated with their AD account. ARERR (8760) Cannot establish a network connection to the AR System Plug-in Serve is the error message and ARSYS.ARDBC.......... RPC program not registered.
I din't replace them with the server group name. Still the error is coming. I haven't done any changes to the pluginsvr_config file. All I did was
- 1. OnPrimary Server, AdministrationConsole > General > System Information, then select the Configurationtab. Then, select the Server Group Member check box and click Apply.
- 2. Backupthe ar.conf original file
- 3. Server-Group-Member:setting is set to T(Server-Group-Member: T )
- 4. Multiple-ARSystem-Servers:T
- 5. Server-Name– xxexample
- 6. Server-Connect-Name– Host name of the Primary Server.
- 7. Domain-Name– Lowest sub domain name
- 8. IP-Name– The possible ways the client could connect to this server
- 9. Restartthe server and test the functionality
- 10. Updatehost file on all the servers to resolve the host name.
The values given for parameters in my previous post were just examples. But the values I had given was in line with what you have said, but no luck.
I am seeing certain posts that the pluginsvr_config and all the entries for Server Plugin Alias should point to the server group name and not the ar server. But this is not given in the white paper for server group configuration.