Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some OPC UA server like Softing DataFEED OPC Suite cannot be scanned #125

Closed
ryan-ms opened this issue Oct 2, 2019 · 5 comments
Closed
Assignees
Labels
need more information Needs more information

Comments

@ryan-ms
Copy link

ryan-ms commented Oct 2, 2019

Describe the bug
I've tried using the OPC Twin module to discover different OPC UA server in the same network including some software transfer from other protocols to OPC UA. Below is the test outcome

OPC UA Server Test Status
Softing DataFEED OPC Suite running on windows Failed to discover
OPC Foundation Sample Server runing on windows Failed to discover
Prosys Simulation Server runing on windows Success to discover
Siemens S7-1500 Success to discover

To Reproduce
Steps to reproduce the behavior:

  1. Running OPC Twin module within IoT Edge in Linux gateway (Ubuntu OS).
  2. Use OPC Twin Web App to start scan process.
  3. The issue happens: The OPC UA server from DataFEED OPC Suite cannot be found.

Expected behavior
All the OPC UA server can be auto discovered.

Screenshots

The DataFEED OPC Suite configuration
tempsnip

No result of DataFEED OPC UA server ( IP: 192.168.4.123) found in opc twin logs
2222

Additional context
If you need more information, please let me know, thank you.

@marcschier
Copy link
Collaborator

"Fast" scan only scans a limited set of ports, namely 4840/4841 and some in the high range. 4980 is not part of the range. Either set port to 4840, or use "Scan" mode (can only be set through the CLI, not CF), i.e. "apps discover -d Scan" to do a full scan of all IANA unassigned ports on a machine.

What was the endpoint address of the OPC sample server? As that one's range should be part of the "Fast" port range list.

@marcschier marcschier self-assigned this Oct 4, 2019
@marcschier marcschier added the need more information Needs more information label Oct 4, 2019
@ryan-ms
Copy link
Author

ryan-ms commented Oct 8, 2019

Hi @marcschier ,

Thank you, after I changed the OPC Server port to 4841. It can work now. I think the issue can be closed, thank you.

But there is another question. After change port, I found that I need to enable ICMP-4 protocol in firewall setting, or the OPC server still cannot be scanned. Could you explain a little bit about this?

@ryan-ms
Copy link
Author

ryan-ms commented Feb 14, 2020

Hi @marcschier ,

"Fast" scan only scans a limited set of ports, namely 4840/4841 and some in the high range. 4980 is not part of the range. Either set port to 4840, or use "Scan" mode (can only be set through the CLI, not CF), i.e. "apps discover -d Scan" to do a full scan of all IANA unassigned ports on a machine.

What was the endpoint address of the OPC sample server? As that one's range should be part of the "Fast" port range list.

So you mentioned that 4840/4841 and some in the high range can support Fast Scan. Could you please provide the supported port list for OPC Twin fast scan?

Thank you.

@monikavar monikavar self-assigned this Feb 24, 2020
@monikavar
Copy link
Contributor

Hi @ryan-ms , the supported port list for fast scan could be found here:

public static IEnumerable<PortRange> WellKnown {

Closing the issue as it is solved, please re-open in case of any other questions/issues.

@ryan-ms
Copy link
Author

ryan-ms commented Feb 25, 2020

Hi @monikavar ,
Thanks for your information. It really help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need more information Needs more information
Projects
None yet
Development

No branches or pull requests

3 participants