Configuration and connection of client to redundant group
A client process, when connecting the RDG, must find the HS and connect to it. For this purpose, there are two parameters.
|/RDredundant_group_name||The parameter replaces the parameter /S, that directly specified the name of the computer (IP address) with running server. If you enter the parameter along with the name of a RDG, the client process (using the service MULTICAST) detects which one of running servers is HS and logs on to the HS. All servers must be available by means of the service MULTICAST. The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Ipesoft\D2000V70\IPMask must be specified.|
|/RFredundant_group_name||The parameter is used instead of the parameter /RD when the RDG servers are not available by means of the service MULTICAST. The process then browses the table* containing the names of all servers connected into the RDG and connects to them in order to detect which of them is in the HS state.|
* Table is located in the system registry and has the following form:
The parameters IpAddr1, IpAddr2 define the IP addresses of the computer,
where a RDG server is running.
The parameter Name is the name of corresponding RDG member, which is identical with the parameter KernelName.
The behaviour of a client process connected to a server, that is a RDG member is different in some
cases. It depends on the client process type and the connection type.
The multicast address of 220.127.116.11 has been used for multicasts since the D2000 v7.0. Since the D2000 V7.01.004 release A060113017, there is also used the multicast address 18.104.22.168, because according to RFC3171 the address of 22.214.171.124 is reserved for local broadcasts that are not routed. Implementation of the multicast address of 126.96.36.199 allows to configure the multicast routing, so D2000 system processes may be housed at various network segments. Multicasts are sent to the UDP port of 3119.