This question was originally posted on DCIM Support by Mark Tucker on 2017-12-22
We are running DCE 7.4.3 and when new devices are added it can take up to 48 hrs for all the devices sensors to appear.
Here is an example of a device recently added :
This is the same type device as it should appear
This answer was originally posted on DCIM Support by Ed Tarento on 2017-12-22
How many devices are you polling? At what intervals?
How much data are you keeping? What's your trim setting?
Is DCE a VM or a physical server? If VM, what is the disk performance in IOPS?
When was DCE last restarted?
This comment was originally posted on DCIM Support by Steven Marchetti on 2017-12-22
Just to add to Ed's questions/comments,
Also look at the repository settings. Is it getting full? Have you tried purging?
If it is a VM as Ed asked, have you given it an extra hard drive?
Does this happen to any new device or just this one?
This comment was originally posted on DCIM Support by Mark Tucker on 2017-12-26
Polling 2662 devices, polling details below. Device is a physical server and was last restarted approx 3 months ago.
This comment was originally posted on DCIM Support by Ed Tarento on 2017-12-27
Great info Mark
As you have that many devices, I infer it's a DCE Enterprise 2U appliance AP9475. This is a well provisioned server for most instances. Please confirm you've left the default polling at 5 minutes.
The only thing I can recommend is that you push polling out for selected devices. Many DCE users increase the polling interval for devices that don't need such "aggressive" polling. E.g. they change polling of rack PDUs / power rails from default to say 15 minutes or even an hour. Little if anything is lost and since rPDUs are often by far the most populous device type, a great benefit can be achieved for little down side by decreasing the polling CPU and IO load on the server. But of course each site is different and only you can make such an assessment. I believe you can easily change the polling interval for multiple devices in a single command but sadly cant recall how to do that. This is just a guess at whats happening and without being at your DCE system I cant make a more informed recommendation.
Even if you decide that this is not a solution (or work around) for you, trying this and noting the result will help in deciding next steps.
This comment was originally posted on DCIM Support by Steven Marchetti on 2017-12-27
I noticed that the most data is in the “other” category. That’s usually an indication that the information is coming in faster than the server can process it. Ed’s suggestion about slowing the polling frequency is absolutely the best place to start. SNMP devices alone however don’t usually have such an issue with memory.
Do you also use NetBotz with cameras? If so, I’d also look into lowering frame rate and resolution.
For both SNMP and NetBotz, if the devices are alerting too often, resolving said issues will also lower throughput to the server allowing it to better keep up with the incoming data.
This answer was originally posted on DCIM Support by spezialist on 2017-12-27
Dear Mark Tucker,
From your screenshots you can clearly see that this equipment Enlogic Co. And the above problem is related only to the hardware of this vendor. Did I get it right?
If so, first you need to make sure, that your DCE-server does not contain more, than one DDF-file for Enlogic hardware. Can you tell which version of the Enlogic DDF-file is on your DCE-server?
In my work I already encountered the problem described by you and for its successful solution it is necessary to have the latest version of DDF-file Enlogic, and it should be only in one copy on the DCE-server (old versions of DDF-files must be deleted).
I think it will be very interesting for you to read Anonymous User comment in topic on Enlogic equipment. Anonymous User himself faced and solved a similar problem with Enlogic equipment. At the same time, the current version of the DDF-file for Enlogic equipment is v23.
I hope this helps you.
If you have any questions, please ask.
This comment was originally posted on DCIM Support by Mark Tucker on 2017-12-27
Thanks for the response, unfortunatly the issue is effecting more than juts the enlogic devices.
This comment was originally posted on DCIM Support by spezialist on 2017-12-27
Ok, then you better accurately publish with which devices which vendors you are experiencing the above mentioned problems (for example, native APC/Schneider Electric devices or 3-rd party devices)?
And of course, if this is a 3-rd party devices, what versions of the DDF-files do you use in the DCE-server?
This comment was originally posted on DCIM Support by spezialist on 2018-01-15
Dear Mark Tucker,
Have you been able to solve your issue or not?
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!