Vertical PDU Total power unplugged

DCIM_Support · ‎2020-07-04

This question was originally posted on DCIM Support by Shaik Mahboob Ali on 2018-01-28

Hi ,

We have Vertical PDU AP8886 showing sensor values in DCE report but i cannot see Total Power Output & showing as unplugged. I can see now as new sensor value as " Total Real Power". Before i use to get Total Power Output and now as unplugged.

Can any one have idea on why this is happening.

DCIM_Support · ‎2020-07-04

This answer was originally posted on DCIM Support by spezialist on 2018-01-29

Dear Shaik Mahboob Ali,

If this is the reasons then sensor data field should be an identical mapping and it should not have loss of data , what if i need to fetch the data before updates and after updates in my report then my result reports are not accurate from DCE.
In any case proper data mapping should be done to avoid reporting issue with existing sensor data to new sensor data.

I understand this perfectly, but often this requirement, when developing updates to DDF-files or firmware devices, is very difficult to perform or impossible to do at all.

But we need a solution to fetch reports along with old data and new data ?

Many DCE customers, including myself, often asked themselves a similar question. The solution to this problem was perfectly described in topic .

I.e., in your case, in order to avoid such problems in the future, it is necessary to create a Virtual Sensor Total Power (W). This virtual sensor should consist of two device sensors Total Power Output (W) and Total Real Power (W). The problem is only, that the data history of this virtual sensor will start only from the moment it was created. And accordingly, the data history in the past for this virtual sensor will be unavailable.

I hope this is what you need.

With respect.

See Answer In Context

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by spezialist on 2018-01-28

Dear Shaik Mahboob Ali,

In this case there may be two independent reasons why it happened.

Reason 1: the most likely is the update of the version of the DCE software, which resulted in the update of the corresponding native DDF-files.
Reason 2: sometimes this happens also after the device firmware update.

I think it will help you understand why this happened.

If there are more questions, please ask.

With respect.

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by Shaik Mahboob Ali on 2018-01-29

Hi ,

If this is the reasons then sensor data field should be an identical mapping and it should not have loss of data , what if i need to fetch the data before updates and after updates in my report then my result reports are not accurate from DCE.

In any case proper data mapping should be done to avoid reporting issue with existing sensor data to new sensor data.

But we need a solution to fetch reports along with old data and new data ?

DCIM_Support · ‎2020-07-04

This answer was originally posted on DCIM Support by spezialist on 2018-01-29

Dear Shaik Mahboob Ali,

If this is the reasons then sensor data field should be an identical mapping and it should not have loss of data , what if i need to fetch the data before updates and after updates in my report then my result reports are not accurate from DCE.
In any case proper data mapping should be done to avoid reporting issue with existing sensor data to new sensor data.

I understand this perfectly, but often this requirement, when developing updates to DDF-files or firmware devices, is very difficult to perform or impossible to do at all.

But we need a solution to fetch reports along with old data and new data ?

Many DCE customers, including myself, often asked themselves a similar question. The solution to this problem was perfectly described in topic .

I.e., in your case, in order to avoid such problems in the future, it is necessary to create a Virtual Sensor Total Power (W). This virtual sensor should consist of two device sensors Total Power Output (W) and Total Real Power (W). The problem is only, that the data history of this virtual sensor will start only from the moment it was created. And accordingly, the data history in the past for this virtual sensor will be unavailable.

I hope this is what you need.

With respect.

DCIM_Support · ‎2020-07-04

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