EcoStruxure IT forum
A support forum for Data Center Operation, Data Center Expert, and EcoStruxure IT product users to share knowledge on installation, configuration, and general product use.
Posted: 2020-07-04 04:42 PM
This question was originally posted on DCIM Support by John Smith on 2018-04-20
So according to my DCE Modbus TCP device list, DCE only scans the Modbus devices once a day.
Any thoughts on this? How to troubleshoot?
Regards,
J
(CID:130097691)
Posted: 2020-07-04 04:43 PM
This answer was originally posted on DCIM Support by spezialist on 2018-05-02
Dear John Smith,
An interesting problem... What is your version of DCE software?
Have you tried restarting the DCE server?
Can you do DCE capture logs according to topic ?
Can you then analyze the text file /var/log/messages and identify any errors or problems with your TCP/IP Modbus device (by its IP address and Slave ID)?
With respect and wait for your answer.
(CID:130681868)
Posted: 2020-07-04 04:43 PM
This comment was originally posted on DCIM Support by Ditte Drewer Mathiasen on 2018-04-25
Hi John Smith, thanks for posting. Let's hope you find your answer here.
Kind regards Ditte
(CID:130099183)
Posted: 2020-07-04 04:43 PM
This comment was originally posted on DCIM Support by spezialist on 2018-04-28
Dear John Smith,
Please describe in detail your question: do you want to poll the TCP/IP Modbus devices only once a day, or does your DCE-server have problems with the polling interval of the TCP/IP Modbus devices?
With respect.
(CID:130680473)
Posted: 2020-07-04 04:43 PM
This comment was originally posted on DCIM Support by John Smith on 2018-04-30
My DCE only scans the devices once a day and I would like them to scan on the interval chosen (every 5 minutes).
When I look at the "Last Scan Time" it usually only shows once in the morning and that is it. Looking at the trend graphs, it shows the data point only once a day...
DCE is NOT scanning the device every 5 minutes as it should.
(CID:130680960)
Posted: 2020-07-04 04:43 PM
This answer was originally posted on DCIM Support by spezialist on 2018-05-02
Dear John Smith,
An interesting problem... What is your version of DCE software?
Have you tried restarting the DCE server?
Can you do DCE capture logs according to topic ?
Can you then analyze the text file /var/log/messages and identify any errors or problems with your TCP/IP Modbus device (by its IP address and Slave ID)?
With respect and wait for your answer.
(CID:130681868)
Posted: 2020-07-04 04:43 PM
This comment was originally posted on DCIM Support by John Smith on 2018-05-11
Apparently there is a Known Modbus Scanner issue which was fixed in DCE 7.5. It doesn't go into detail but maybe with the device offline or a register issue, it froze up.
Improvements to Modbus polling Modbus polling is no longer affected by prolonged network disruptions.
(CID:131958890)
Posted: 2020-07-04 04:43 PM
This comment was originally posted on DCIM Support by spezialist on 2018-05-11
Dear John Smith,
I'll correct you: in fact, these fixes were made in DCE-7.4.3 😀. For example, see my answer in topic .
With respect.
(CID:131958908)
Posted: 2020-07-04 04:43 PM
This comment was originally posted on DCIM Support by John Smith on 2018-05-11
Thanks again! I am running 7.4.1 so, yes I need to upgrade. Thanks again for the quick reply as well!
(CID:131958914)
Posted: 2020-07-04 04:43 PM
This comment was originally posted on DCIM Support by spezialist on 2018-05-11
Ok, thanks for the good feedback 😀.
(CID:131958919)
Posted: 2020-07-04 04:44 PM
This comment was originally posted on DCIM Support by John Smith on 2018-05-02
It is loaded with Errors in /var/log/messages
The errors are:
Modbus_session_open: open session failed - Too many open files
nbModbusScannerCreateScan: Error creating Modbus session on <IP>
failscan:Marking scan of <IP> with SCAN_FAILED resultcode.
Error creating scan for <IP>:MODBUS-TCP, No protocol scanner found
nbVarLibAccessContextCreateInNS: cannot open /dev/nbVariablesFree
all the <IP> are the same so I am going to go delete that device and see what that does.
(CID:130681811)
Posted: 2020-07-04 04:44 PM
This comment was originally posted on DCIM Support by spezialist on 2018-05-02
Dear John Smith,
I would, after all, reboot the DCE-server first and watch for some time for the problem TCP/IP Modbus device.
With respect.
(CID:130681815)
Posted: 2020-07-04 04:44 PM
This comment was originally posted on DCIM Support by John Smith on 2018-05-02
That seems to have fixed my issue! The whole server is working better and the device scans have been re-scanning every few minutes now!
Thanks for the help! I will keep watching it and see.
I have another issue where the device discovery is slow and shows "initializing" for a long time but I will post that in another question.
Regards,
J
(CID:130681855)
Posted: 2020-07-04 04:44 PM
This comment was originally posted on DCIM Support by spezialist on 2018-05-02
Ok, thanks so much for the good feedback 😀.
(CID:130681866)
Posted: 2020-07-04 04:44 PM
This answer was originally posted on DCIM Support by John Smith on 2018-05-08
So it worked but there are other issues. Does someone here know what these errors mean?
nbModbusScan: Modbus_session_open: open session failed - Too many open files
nbModbusScan: nbVarLibAccessContextCreateInNS: cannot open /dev/nbVariablesFree
(CID:131336303)
Posted: 2020-07-04 04:44 PM
This comment was originally posted on DCIM Support by spezialist on 2018-05-10
Dear John Smith,
I will not prove, but the reason for the above problems can be, for example, problems with JVM, similar to those described in topic . What is your version of DCE software?
With respect.
(CID:131337115)
Posted: 2020-07-04 04:44 PM
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.