You have confirmed that EFM is running, and you can open a broker connection using port 8080 or 8443 from the EFM server. However, from an external broker, not hosted on the same machine, the connection is refused.
Is this is your first external broker then probably EFM server is not listening for connection requests on outside interfaces. From a remote destination you can try to telnet to either 8080 (http) or 8443 (https) ports: if the connection is refused, this is likely your problem. It might also be a firewall or access-list problem, but then this is a network issue, not an EFM issue.
By default ans starting with EFM 1.6 the EFM broker only listens to the local, loopack interface (127.0.0.1). To confirm this is the case, check the configuration file:
The "host" option tells EFM on which interface it should be listening for incoming connections. 127.0.0.1, called the loopback address, will only permit connection originated by EFM server itself to be successful. Should you want to open this up to the outside world, edit the file and replace 127.0.0.1 (loopback) by 0.0.0.0 (all interfaces):
efm-server:~ $ vi /opt/cisco/kinetic/efm_server/server.json
You need to restart the EFM server for this change to take effect:
Hi there, did one of you ever get the OPC link up and running?Currently my small demo consists of a EFM 1.5 installed locally on Windows and a simulated OPC-UA server running on a separate Windows machine.The documentation on github describes the fol...
I have devices registered in Actility ThingPark Wireless (NS in the cloud) and I have several ways to send my data, but I don't know exactly how to configure that in Actility neither in EFM.
On Actility side i have the following possibilitie...
We have observed something weird in dataflow while using "insert row" node api of parstream dslink as a block in dataflow:
In case we used insert row block to insert data into parstream, it keeps on duplicating table fields in "insert row" block.