Historic sensor data issues after DCE 7.4.3 update

[DCIM_Support]

Since the DCE7.4.3 update we have seen some anomalies with some sensors on PX500 UPS's

Main Input Apparent Power Phase 1 2 and 3

These sensors seem to have some crossover between VA and KVA values

Main Input Current

These seem to have replaced data between the date of the 7.4.2 update and the 7.4.3 update with a flat line.

It looks like the data migration in 7.4.3 has not worked too well - at least for PX500 UPS's (so far)

So...

Can I really trust the historic data anymore?

Does this have a knock on effect to DCO?

Is this likely to be correct in another DCE update in future?  Although I don't see how the data can be correct once it has been 'corrupted'

Can i remove / purge data just for a particular sensor or device without deleting and rediscovering the device?  I don't want to delete the device as I will have to re configure a number of icons on maps and threshold alarms.  A lot of work.

Is anyone in Schneider investigating any further sensors or devices that may have the same issue?  Frankly I don't have the time to test your software for you 😉 ...

Thanks in advance

(CID:120129204)

[DCIM_Support]

Hi Garry,

Since you noted the migration of data, I'm assuming you are aware of the issue with sensors going off-line in the upgrades prior to 7.4.3. Not all sensors were able to be fixed om 7.4.3 and there is a note about that here:

Unplugged sensors in DCE 7.4.3

Thanks,

Steve

(CID:120129286)

[DCIM_Support]

I had read that page and it states "You can delete the unplugged sensors, but historical sensor data will be lost. Otherwise, you can leave the sensor in the unplugged state to maintain historical data."

My point is that the historical data in both the unplugged sensors and the 'corrected' sensors is not maintained, it is actually wrong.  It could very easily be argued that incorrect data is worse than missing data.

I want to find out if I can delete the data in the 'corrected' sensors (the ones that are not showing unplugged), because I don't want erroneous data in the history graphs.

Also this page does not answer the question - Does this historical data have a knock on effect to DCO?

Regards

(CID:120129826)

[DCIM_Support]

Hi Garry,

There is no way to delete the data for an individual sensor that is currently listed but not unplugged. You could disable/reconfigure SNMP so that it does not communicate with DCE and when the sensor goes unplugged, you can then delete it. It will of course return once comm is re-established. You could also delete the device and re-add it. If you're running DCO though this causes issues where you'd have to re-associate the device there. In either case, I suggest holding off on this.

As for the graph, I have to look into it. When I get anything more, I'll get back to you.

Steve

(CID:120129850)

[DCIM_Support]

Hi Garry,

So I had tested this as well and went through all the upgrades. I too am seeing the sensors available to graph and showing unplugged and showing values in the report when it should not be. I've put in a bug report on this and used both this post and my own server that was able to replicate the issue into the bug.

Steve

(CID:120130286)

[DCIM_Support]

Hi Garry Priestland and Steven Marchetti,

I will add in the form of a comment that, having two Symmetra PX 500 UPSs, after DCE-7.4.2 migration to DCE-7.4.3, I observe a similar situation.

But my question is somewhat different: why if the sensor is unplugged state (starting from the end of April this year for me), does the sensor report for subsequent periods (for example, May) show the presence of readings from the unplugged sensor? I.e., the readings of this unplugged sensor stopped at the end of April this year for me, and the report shows that they also exist in May with the same value equal to the last measured value in April? All of this is clearly seen in the screenshots Garry Priestland.

Very thanks for the support.

(CID:120129352)

[DCIM_Support]

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