Node

When talking about digitalization in the industry, security often comes up as one of the main concerns. Usually production environments are decoupled from other areas to prevent unauthorized actions. To realize this, a common practice is to separate networks into different segments like Production, OT, Office, Cloud. The concept of Node to Node communication comes in handy in these scenarios.

Issue: You have installed the Node by following the instructions in the Node Installtion documentation but the Node does not show up as active in Crosser Cloud.

Follow these steps to troubleshoot these type of issues:

There is no automatic scaling but processing can be split over multiple nodes by for example selecting subsets of data using filter conditions or separate by data sources.

One of the great benefits with Crosser is the performance, tests show that we can process >100 000 messages per second on a pretty basic VM. A Raspberry Pi3 can process about 8000 messages per second.

In this article we describe what options you have and how to utilize provided interfaces for integration into your monitoring solution.

There is no automated support for redundant nodes. However, the same flow can be installed on multiple nodes and started from the Cloud service on failure. You can also use container management tools, such as Kubernetes, to build high-availability setups with Crosser Nodes.

The Edge node communicates with the Crosser Control Center is using HTTPS on port 443. The HTTPS port is also used by many modules that connects to web services. All traffic is initiated from the edge node, so this port must be open for outbound traffic. Locally port 9090 is used for inbound HTTP(S) traffic to the HTTP Listener module and port 1883 / 8883 for inbound MQTT traffic (MQTT Sub Broker/Client modules). The local web UI and API is accessed through port 9191. Inbound port mappings are configurable.

Yes, the Crosser Node needs to be configured locally when sitting behind a proxy. See here for more information. By default Crosser Nodes uses websocket communication with Crosser Cloud during remote sessions, so if the proxy does not support websockets the default configuration needs to be changed.

The Crosser edge node runs as a Linux container, which is currently not supported by the enterprise version of Docker on Windows. 

The Node shows up in the list of available Nodes when you click on "Connect to node" inside the Flow Studio, but then you never get connected (the popup stays with a spinner waiting). Learn the two ways to solve this issue.