EcoStruxure IT forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-05 03:32 PM . Last Modified: 2024-04-03 11:24 PM
Hi team,
in DCO 8.2.7 we hare recently receiving this error mesage when it tries to get information from DCE.
We saw previous posts where it suggested to improve DCE capacity. We checked DCE 7.5 virtual machine and we saw that it was at 100% CPU. We duplicated the CPU and RAM and now it is at 50%, but we are still receiving the same error message. Not so often as before, but it still appears:
This is the configuration of the external system:
This is the CPU load of DCE virtual machine:
And this is the RAM:
(CID:137726329)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-05 03:32 PM . Last Modified: 2024-04-03 11:24 PM
Hi Javier,
According to error notification, you might have read timed out issue. You might want to try to increase the timeout settings for "Stop waiting for data after" (try for example 1200 s or even 3600 s).
You might also want to try/test increasing the device update intervals,
update device information every 300 s
Full alarm synchronization every 3600 s
Kind regards
(CID:137726361)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-05 03:32 PM . Last Modified: 2024-04-03 11:24 PM
Thanks Jef, we are going to try increasing some timeouts.
Regards
(CID:137726380)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-05 03:33 PM . Last Modified: 2024-04-03 11:24 PM
Hi Jef, we have changed the values as you suggested but we have still the same error.
Joshua Ellis is helping us with some DDFs, and he would like to know what it is the problem.
Regards
(CID:137726533)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-05 03:33 PM . Last Modified: 2024-04-03 11:24 PM
Hi Javier,
Since when do you see this issue?
Do you know what sort of changes might have done to affect this?
Would it be possible to ask for a copy of the backup file + server logs, then I will see what I can find, thanks
I will send you an invite to my =S= box shortly, so the data safely can be shared with me.
Kind regards
(CID:137726855)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-05 03:33 PM . Last Modified: 2024-04-03 11:24 PM
Hi Jef,
we see this error since last week. The customer has included new devices in DCE, it is a big deployment with 983 monitored devices and in DCO 840 racks installed.
I will ask the customer for the logs and the backup.
Regards
(CID:137726879)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-05 03:33 PM . Last Modified: 2024-04-03 11:24 PM
Hi Javier,
Many thanks for providing the data.
According to log entries getting device groups (from DCE) failing. It seems that the "value type" for at least one sensor gets returned as null, while it should have been one of the following values:
BOOLEAN,
DATE,
DATE_TIME,
DOUBLE,
ENUM,
FLOAT,
INTEGER,
STRING,
TIME,
UNKNOWN;
Unfortunately from DCO side/logs it is not possible to say which sensor or indeed if it is the only one in the data set.
Kind regards
(CID:137727586)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-05 03:33 PM . Last Modified: 2023-10-22 02:03 AM
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.