Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
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
84823members
354277posts

Error collecting data in DCO

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.

DCIM_Support
Picard
Picard
0 Likes
7
347

Error collecting data in DCO

This question was originally posted on DCIM Support by Javier Zurera on 2018-12-18


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)

7 Replies 7
DCIM_Support
Picard
Picard
0 Likes
5
348

Re: Error collecting data in DCO

This answer was originally posted on DCIM Support by Jef Faridi on 2018-12-18


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)

DCIM_Support
Picard
Picard
0 Likes
0
348

Re: Error collecting data in DCO

This comment was originally posted on DCIM Support by Javier Zurera on 2018-12-18


Thanks Jef, we are going to try increasing some timeouts.

Regards

(CID:137726380)

DCIM_Support
Picard
Picard
0 Likes
0
348

Re: Error collecting data in DCO

This comment was originally posted on DCIM Support by Javier Zurera on 2018-12-18


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)

DCIM_Support
Picard
Picard
0 Likes
0
348

Re: Error collecting data in DCO

This comment was originally posted on DCIM Support by Jef Faridi on 2018-12-19


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)

DCIM_Support
Picard
Picard
0 Likes
0
348

Re: Error collecting data in DCO

This comment was originally posted on DCIM Support by Javier Zurera on 2018-12-19


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)

DCIM_Support
Picard
Picard
0 Likes
0
348

Re: Error collecting data in DCO

This comment was originally posted on DCIM Support by Jef Faridi on 2018-12-21


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)

DCIM_Support
Picard
Picard
0 Likes
0
348

🔒 Closed

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.