Using DM cube, some of the devices which were connected are now in timeout and their communication state is "Not Responding" but the IP addresses have not changed and the device settings have not been changed. Could this be a connection problem in the network of the devices, or could it be repairable in dataminer?
Hi Bethany,
The best way to start an investigation when having communication issues is to have a look at the stream viewer.
The stream viewer will show you the real-time data requests and responses between DataMiner and your remote data source.
More details on how to use the stream viewer can be found here.
In the stream viewer, for some devices, there is a response every time the device is polled and they show TIMEOUT. For others for which drivers are still in development it shows NO SUCH OBJECT.
The “No Such Object” error indicates that an SNMP request is made for an OID that is not available on the remote data source.
The “TIMEOUT” error indicates that the connection times out.
This can have two reasons:
1. There is no connectivity between DataMiner and the remote data source on the configured TCP/UDP port.
In this case, you need to verify what is causing these connectivity issues.
Note that connectivity might be available to e.g. the web UI, but not to the SNMP interface
2. There is connectivity between DataMiner and the remote data source on the configured TCP/UDP port, but the data takes too much time to be sent/received. In that case you can increase the command “timeout time” for the connection in the element edit wizard.
To add to Ive's answer
Typically SNMP uses port 161 and HTTP uses 80 or 443 but this depends on the elements configuration and could be different. On the element, right click - > edit.
Hi Bethany,
There could indeed be many reasons why your element goes into timeout. Can you share with us what connector (driver) you are using?
Some connectors have multiple connections (e.g. HTTP(s), serial, SNMP). So it could be that one of these connections or all are causing your timeout. In the settings (edit) of your element, you are able to define which connection can contribute to the timeout state. When right-clicking the element you can also open streamviewer (view => streamviewer) which will show you what data is being send-out or received by DataMiner for that element. I would advise to already have a look there and provide us with a bit more information so that we can narrow down why you are seeing these timeouts.