Configuration and connection of a client to a redundant group
A client process, when connecting the RDG, must find the HS and connect to it. For this purpose, there are two parameters.
| Parameter | Meaning |
|---|---|
| /RDredundant_group_name | The parameter replaces the parameter /S, which directly specifies the name of the computer (IP address) with a running server. If you enter the parameter along with the name of an RDG, the client process (using the UDP MULTICAST packets) detects which one of the running servers is HS and logs on to the HS. All servers must be available using the UDP MULTICAST packets. 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 using the UDP MULTICAST packets. The process then browses the table* containing the names of all servers connected to the redundant group and connects to them to detect which of them is in the HS state. The connection is made by the TCP service to the destination port 3119. |
* Table is located in the system registry and has the following form (<D2000branch> can be D2000V70 or another branch depending on the installation, e.g. DD2000D2000_V22.0.74_SERVERD2000_EXE - see Multiple Installations on One Computer):
[HKEY_LOCAL_MACHINE\SOFTWARE\Ipesoft\<D2000branch>\Redundancy\RDG_name]
[HKEY_LOCAL_MACHINE\SOFTWARE\Ipesoft\<D2000branch>\Redundancy\RDG_name\Kernel_1]
"IpAddr1"="10.12.1.1"
"IpAddr2"="10.12.65.1"
"Name"="DS25A"
[HKEY_LOCAL_MACHINE\SOFTWARE\Ipesoft\<D2000branch>\Redundancy\RDG_name\Kernel_2]
"IpAddr1"="10.12.1.2"
"IpAddr2"="10.12.65.2"
"Name"="DS25B"
The IpAddr1 and IpAddr2 parameters define the IP addresses of the computer, where an RDG server is running.
The Name parameter is the name of the corresponding RDG member, which is identical to the parameter KernelName.
The behavior of a client process connected to a server, that is an RDG member is different in some cases. It depends on the client process type and the connection type.
Note
The multicast address of 224.0.0.55 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 224.0.2.55, because according to RFC3171, the address of 224.0.0.55 is reserved for local broadcasts that are not routed. Implementation of the multicast address of 224.0.2.55 allows to configuration of the multicast routing, so D2000 system processes may be housed at various network segments.
Multicast requests are sent to the destination UDP port of 3119, the source port is dynamic. Unicast replies are sent from a dynamic UDP port to the UDP port and IP address from which the original multicast request was sent.
Related pages:
Pridať komentár