DCE Battery Age and Battery Replacement Status Snapshot Report not showing for Symmetra PX250/500kVA

[DCIM_Support]

This question was originally posted on DCIM Support by Steven Marchetti on 2019-01-16

---

Not really a question...Since the system closed spezialist 's  post here:

http://sxwhelpcenter.ecostruxureit.com/questions/134027211/comments/134686224

I wanted to update him/you on that issue. 

If you have the most recent UPS DDF (it's actually listed as smart-UPS) which is 96 at the moment, you should be able to see the last battery replacement date in view sensors as well as having a listing other than "unknown" in the battery age report. The only bad thing is there is only a single age so if you have multiple batteries with multiple ages, it won't show in the report.

You can get the most recent by simply updating DCE to version 7.6. I'm unsure if you can get it under device support but you can look. I'll see if I can get a copy if you need it. 

MISSING IMAGE: image2019-1-16 13:20:25.png

Also note that even though the PX is listed now with a battery date of 1.0 years (as long as one is set up on the unit) the replacement status is showing as unknown. I have raised this issue and this was why I was delaying my response. I wanted to wait till everything was working but since we're now auto-closing posts that are older, I wanted to get something out to you now.

The latter issue appears to be a device firmware issue but we're looking to get it addressed.

Steve

 

(CID:138380995)

[DCIM_Support]

This answer was originally posted on DCIM Support by spezialist on 2019-01-17

---

Dear Steven Marchetti,

Thanks for the answer, but unfortunately it does not work even with the latest version of the DDF-file apcsmartups.xls  v.98 ☹️.

Let me explain the reason for the developers: the Battery age sensor is not displayed for the above mentioned UPS series, as the condition from the above specified DDF-file is not met:

xml109apcsmartups.xml v.98true <!-- SmartUPS specific functionality --> <device deviceid="smartups"> <oidMustMatch ruleid="smartupssysid" oid=".1.3.6.1.2.1.1.2.0"> <valueList> <value>.1.3.6.1.4.1.311.1.1.*</value> <!--PCBE Windows--> <value>.1.3.6.1.4.1.318.1.3.2</value> <!-- Arakni --> <value>.1.3.6.1.4.1.318.1.3.2.*</value> <!-- Other SmartUPS --> <value>.1.3.6.1.4.1.318.1.3.3</value> <!-- MatrixUPS --> <value>.1.3.6.1.4.1.318.1.3.3.*</value> <!-- Other MatrixUPS --> <value>.1.3.6.1.4.1.318.1.3.5</value> <!-- Symmetra --> <value>.1.3.6.1.4.1.318.1.3.5.*</value> <!-- Other Symmetra --> <value>.1.3.6.1.4.1.318.1.3.6.*</value> <!-- SmartUPS DP --> <value>.1.3.6.1.4.1.318.1.3.6</value> <!-- SmartUPS DP --> <value>.1.3.6.1.4.1.318.1.3.7.*</value> <!-- SmartUPS DP300E --> <value>.1.3.6.1.4.1.318.1.3.7</value> <!-- SmartUPS DP300E --> <value>.1.3.6.1.4.1.318.1.3.13.*</value> <!-- Other Symmetra 3P --> <value>.1.3.6.1.4.1.318.1.3.13</value> <!-- Symmetra 3P --> <value>.1.3.6.1.4.1.318.1.3.16.*</value> <!-- Other AIS5000 --> <value>.1.3.6.1.4.1.318.1.3.16</value> <!-- AIS5000 --> <value>.1.3.6.1.4.1.318.1.3.17</value> <!-- SmartUPS VT --> <value>.1.3.6.1.4.1.318.1.3.17.*</value> <!-- Other SmartUPS VT --> <value>.1.3.6.1.4.1.318.1.3.23.1</value> <!-- PX48K --> <value>.1.3.6.1.4.1.318.1.3.23.2</value> <!-- PX160K --> <value>.1.3.6.1.4.1.318.1.3.23.5</value> <!-- PX100K --> <value>.1.3.6.1.4.1.318.1.3.27</value> <!-- Microlink --> <value>.1.3.6.1.4.1.318.1.3.27.*</value> <!-- Other Microlink --> <value>.1.3.6.1.4.1.318.1.3.28</value> <!-- Galaxy --> <value>.1.3.6.1.4.1.318.1.3.28.*</value> <!-- Other Galaxy --> <value>.1.3.6.1.4.1.318.1.3.30</value> <!-- EPS UPS --> <value>.1.3.6.1.4.1.318.1.3.30.*</value> <!-- EPS UPS subtypes --> <value>.1.3.6.1.4.1.318.1.3.8.4.1.3.2.*</value> <!-- RMD1 --> <value>.1.3.6.1.4.1.318.1.3.8.4.1.3.5.*</value> <!-- RMSY --> </valueList> </oidMustMatch>

The condition is not fulfilled, as for Symmetra PX250/500kVA UPS series:

$ snmpget -On -v2c -cpublic 192.168.0.102 .1.3.6.1.2.1.1.2.0
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.318.1.3.23.4

I hope this is clear.

Therefore, six months ago I modified my DDF-file odin_diag_battery_frame_temperature.xls (see my tip ) so that the Battery age sensor is displayed for this UPS series:

xmlodin_diag_battery_frame_temperature.xml v.3 <device deviceid="odinbattery"> <!-- Odin implements only some battery OIDS --> <oidMustMatch ruleid="smartupssysid" oid=".1.3.6.1.2.1.1.2.0"> <valueList> <value>.1.3.6.1.4.1.318.1.3.23.3</value> <!-- Odin 250K --> <value>.1.3.6.1.4.1.318.1.3.23.4</value> <!-- Odin 500K --> </valueList> </oidMustMatch>   <!-- Battery age --> <numSensor ruleid="battage"> <type>timeindays/batteryage</type> <sensorId>BATT_AGE</sensorId> <value> <round increment="1"> <div> <op> _{<op> <curUTCTime/> </op> <op> <parseDate> <getOid>.1.3.6.1.4.1.318.1.1.1.2.1.3.0</getOid> </parseDate> </op>} </op> <op>86400</op> </div> </round> </value> <minValue>0</minValue> <valueInc>1</valueInc> <label>Battery Age</label> <sensorSet>UPS Battery Status</sensorSet> </numSensor>

I hope the DDF team will find time to validate the above changes.

With respect.

(CID:138381355)

[DCIM_Support]

This comment was originally posted on DCIM Support by Steven Marchetti on 2019-01-17

---

spezialist, I didn't realize I had the ability to re-open the post so I was going to delete this one and put my comments there but had issues...I guess we'll leave them both for now.

Hopefully the DDF team can look at this for you but if you're editing the DDF, I'm not sure I can support you here. If you edited another DDF it's possible that the 2 are now in conflict. Are you certain you didn't edit the smart-ups DDF and increase the version number? I can't troubleshoot your changed DDFs. Either way, I'll defer to the team here if they can look at it.

As for the issue, you can see in my screenshot above, I am able to get the report to see the battery age. My system is a PX250 as shown in that screenshot. My counterpart in engineering is seeing this data in Smartups version 96 and I have a test version 99. I used a UI to poll the OID and get products.system.symmetraPX.symmetraPx250kVA which is the textual representation of .1.3.6.1.4.1.318.1.3.23.3....also not shown in your version of the DDF.

I checked the DDF I have and I do see the following:

<value>.1.3.6.1.4.1.318.1.3.23.1</value>

<!-- PX48K -->

<value>.1.3.6.1.4.1.318.1.3.23.2</value>

<!-- PX160K -->

<value>.1.3.6.1.4.1.318.1.3.23.3</value>

<!-- PX250K -->

<value>.1.3.6.1.4.1.318.1.3.23.4</value>

<!-- PX500K -->

Perhaps my colleague has version 96 but an edited version. Can you tell me where exactly you go the version 98 DDF?

Steve

(CID:138381493)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2019-01-17

---

Dear Steven Marchetti,

From your comments:

...Are you certain you didn't edit the smart-ups DDF and increase the version number?

Of course I did not. I made all the changes and additions in my DDF-file odin_diag_battery_frame_temperature.xls, which does not conflict with the standard DDF-file apcsmartups.xls (v.96 from DCE-7.6.0 or v.98 from the Device Support resource).

...Perhaps my colleague has version 96 but an edited version. Can you tell me where exactly you go the version 98 DDF?

Probably, this is the case ☹️. Since the official version of v.96, which is included in DCE-7.6.0, does not have this changes. Just like v.98, which I downloaded from the above mentioned resource:

With respect.

(CID:138381506)

[DCIM_Support]

This comment was originally posted on DCIM Support by Steven Marchetti on 2019-01-17

---

Not released yet but here's v99. Can you try it?

apcsmartups.xml

(CID:138381617)

[DCIM_Support]

This comment was originally posted on DCIM Support by Steven Marchetti on 2019-01-17

---

FYI, UPS may show sensors go unplugged until you rescan

(CID:138381643)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2019-01-18

---

Dear Steven Marchetti,

Unfortunately, the html-script fourohfour.action is downloaded via the link you specified:

<!DOCTYPE html> <html> <head> <title> - Help Center: Support for EcoStruxure IT, StruxureWare for Data Centers, and NetBotz</title> <style> .profile .aui-nav a[href="/users/viewmydrafts.action"]{ display:none; } #user-drafts-link{ display:none; } </style> <meta http-equiv="X-UA-Compatible" content="IE=EDGE,chrome=IE7"> <meta charset="UTF-8"> <meta id="confluence-context-path" name="confluence-context-path" content=""> <meta id="confluence-base-url" name="confluence-base-url" content="http://sxwhelpcenter.ecostruxureit.com"> <meta id="atlassian-token" name="atlassian-token" content="0e0ab52140eb55c5f5c78a8eebf6809bef997b1c"> <script type="text/javascript"> var contextPath = ''; </script> <meta name="robots" content="noindex,nofollow"> <meta name="robots" content="noarchive"> <meta name="confluence-request-time" content="1547795872353"> ... ... ...

With respect.

(CID:138381911)

[DCIM_Support]

This comment was originally posted on DCIM Support by Steven Marchetti on 2019-01-18

---

Not sure what happened, I just uploaded the file. Let's try the zip:

apcsmartups_v99.zip

(CID:138806994)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2019-01-18

---

Unfortunately, nothing has changed: I am still downloading the html-file fourohfour.action ☹️. This is bad...

Very thanks for the support.

(CID:138807018)

[DCIM_Support]

This comment was originally posted on DCIM Support by Steven Marchetti on 2019-01-18

---

spezialist, you may want to look at your browser settings. I double checked the file when I first posted it by clicking the link myself and had no issue. The HTML is supposed to bring up an in-window download screen:

In any case, here's a box link:

https://schneider-electric.box.com/s/ovajxgn54dhb6amyifsilzy4hb6naiqw

(CID:138807032)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2019-01-18

---

Dear Steven Marchetti,

That's right, I also see a black download screen. And after clicking on the Download button, a window opens asking you to save the html-file fourohfour.action.

However, I was able to successfully download the DDF-file from =SE= box resource. Later I will write the result.

Very thanks for the support.

(CID:138807048)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2019-01-18

---

I successfully checked: with the apcsmartups.xls version v.99, the Battery Age sensor is displayed normally 😀.

It remains to solve the problems with the Battery Replacement Status sensor. This is probably the problem with the UPS firmware...

Very thanks for the support.

(CID:138807075)

[DCIM_Support]

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