Date: Thu, 28 Mar 2024 19:32:26 +0100 (CET) Message-ID: <1525202225.111218.1711650746566@srvdoc.doc.ipesoft.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_111217_192272419.1711650746566" ------=_Part_111217_192272419.1711650746566 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
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<= /a>, that directly specified the name of the computer (IP address) with run= ning server. If you enter the parameter along with the name of a RDG, the c= lient process (using the service MULTICAST) detects which = one of running servers is HS and logs on to the HS. All servers must be ava= ilable 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 <= strong>/RD when the RDG servers are not available by means of the = service MULTICAST. The process then browses the table* con= taining the names of all servers connected into the RDG and connects to the= m in order to detect which of them is in the HS state. |
* Table is located in the system registry and has the following form:
[HKEY_LOCAL_MACHINE\SOFTWARE\Ipesoft\D2000V70\Redundancy\RDG_nam= e]
[HKEY_LOCAL_MACHINE\SOFTWARE\Ipesoft\D2000V70\Redundancy\RDG_nam=
e\Kernel_1]
"IpAddr1"=3D"10.12.1.1"
"IpAddr2"=3D"10.12.65.1"
"Name"=3D"DS25A"
[HKEY_LOCAL_MACHINE\SOFTWARE\Ipesoft\D2000V70\Redundancy\RDG_nam=
e\Kernel_2]
"IpAddr1"=3D"10.12.1.2"
"IpAddr2"=3D"10.12.65.2"
"Name"=3D"DS25B"
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 m=
ember 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 us=
ed the multicast address 224.0.2.55, because according to RFC3171, the addr=
ess of 224.0.0.55 is reserved for local broadcasts that are not routed. Imp=
lementation of the multicast address of 224.0.2.55 allows to configure the =
multicast routing, so D2000 system processes may be housed at various netwo=
rk segments.
Multicast requests are sent to the destination UDP port of 3119, the sou= rce port is dynamic. Unicast replies are sent from a dynamic UDP port to th= e UDP port and IP address from which the original multicast request was sen= t.
Related pages: