RegisterServer2 in multicast discovery

Unified Architecture topics related to OPC UA Specification, compliant behavior and any technical issues of OPC UA, like Security, Information Model, Companion Specs DI, PLCopen, ADI, ...

Moderator: Support Team

Post Reply
rakshan
Full Member
Full Member
Posts: 9
Joined: 07 Jun 2019, 08:35

RegisterServer2 in multicast discovery

Post by rakshan »

Hello,
I have a LDSME enabled server running on port 4840. I run another server which is also mDNS enabled on port 4841. Now if I run the FindServersonNetwork, I am able to see both the servers. This kindoff makes sense with the name of the service. And since both the servers advertise their services using mDNS records.
However, Theoretically, the server on 4841 should register to the LDS ME on 4840, only then the servers become discoverable right?
In my observation above, there was no registration with the LDSME done. Yet I could observe both the servers. May i please know how is that?

Irrespective of whether the server being registered to the LDSME,findServersOnNetwork would still produce the available servers? So far, I believed the purpose of registering the server is to make itself discoverable. However, since findServersOnNetwork recognises servers through mDNS announcements, it is confusing as to whether register server service is needed or not?

Regards,
Rakshan

Post Reply