Full access is just steps away!
Join Exchange for FREE and get unlimited access to our global community of experts.
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Solved
Go to Solution
Accepted Solutions
This answer was originally posted on DCIM Support by Steven Marchetti on 2018-09-17
Hi Javier,
I can't say there's a specific maximum latency in DCE. Every install is pretty much unique due to the different devices, number of sensors, amount of devices, network LAN/WAN traffic, etc.
What I would suggest is if you are more concerned with alerts than data AND if you are using APC devices, you can decrease the poll time as noted in k-base FA271584. You'll get less data but DCE should still alert for the device issues. This does not account for 3rd party devices or modbus devices. The reason I mention this is because if you increase timeouts and retries, eventually you could cause DCE to be polling more and more often and taking some processing away in other areas may help if that becomes an issue.
The main thing you'll likely want to look at is timeouts and retries. These can be found for each device under the device menu, SNMP device communication settings, device scan settings.:
You can select one or more devices and increase the timeouts and retries here:
All of that is also noted in k-base FA226273. Maximum timeout is 60 seconds and maximum retries is 10. If you do use the maximums however, you're talking about a potential delay of 10 minutes to get data and if your normal scan time is less than that, you'll potentially run into issues such as I began this post with.
Modbus has timeouts and retries as well and any settings like this are something you'll have to test in your environment to see what works best for you.
Thanks,
Steve
This answer was originally posted on DCIM Support by Steven Marchetti on 2018-09-17
Hi Javier,
I can't say there's a specific maximum latency in DCE. Every install is pretty much unique due to the different devices, number of sensors, amount of devices, network LAN/WAN traffic, etc.
What I would suggest is if you are more concerned with alerts than data AND if you are using APC devices, you can decrease the poll time as noted in k-base FA271584. You'll get less data but DCE should still alert for the device issues. This does not account for 3rd party devices or modbus devices. The reason I mention this is because if you increase timeouts and retries, eventually you could cause DCE to be polling more and more often and taking some processing away in other areas may help if that becomes an issue.
The main thing you'll likely want to look at is timeouts and retries. These can be found for each device under the device menu, SNMP device communication settings, device scan settings.:
You can select one or more devices and increase the timeouts and retries here:
All of that is also noted in k-base FA226273. Maximum timeout is 60 seconds and maximum retries is 10. If you do use the maximums however, you're talking about a potential delay of 10 minutes to get data and if your normal scan time is less than that, you'll potentially run into issues such as I began this post with.
Modbus has timeouts and retries as well and any settings like this are something you'll have to test in your environment to see what works best for you.
Thanks,
Steve
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Connect with Peers & Experts
Discuss challenges in energy and automation with 30,000+ experts and peers.
Get Support in Our Knowledge Base
Find answers in 10,000+ support articles to help solve your product and business challenges.
Ask Questions. Give Solutions
Find peer based solutions to your questions. Provide answers for fellow community members!