Invalid Calibration: bug in DDF or NMC2 firmware for Symmetra PX500?

[DCIM_Support]

Hi all!

Here decided to ask still here the answer to my five-year question 😀 on the following bug.

Bug essence: successfully executed operation Runtime Calibration on the Symmetra PX500 UPS for some reason is always displayed in DCE-7.x as "Invalid Calibration". It is a bug in the DDF-file for this UPS or nevertheless a bug in NMC2 firmware?

For an example, here a piece of logfile from NMC2, in which is shown successful executed operation Runtime Calibration on the Symmetra PX500 UPS on March 6, 2017:

And the same operation, but already in a graphics of states and values from DCE-7.4.2, where it is well visible, that above the specified operation terminated in failure:

My UPS: Symmetra PX 500, Firmware Revision 4.36.12.

My NMC2 in UPS: AP9635 Hardware Revision 05, Application Module v6.4.6 Dec 15 2016, APC OS (AOS) v6.4.6 Oct 6 2016.

Very thanks for the support.

(CID:113643852)

[DCIM_Support]

Hi Spezialist,

Was this an alert in DCE or was it simply a sensor reporting this value? This is an To find out if this event/state is being reported by the card or is a false reading by DCE, you'd need to run an SNMPwalk of the device, more specifically the enterprise branch of the mib, while the alarm/state is active. If we can't see what DCE is reading, we can't tell if the device is sending the right info. 

Steve

(CID:113643889)

[DCIM_Support]

Steve, specifically at the moment my Symmetra PX500 says to me, that runtime calibration test was executed successfully:

The same is displayed also in NMC2. But the server DCE-7.4.2 claims, that runtime calibration test is executed unsuccessfully:

In my opinion everything is clear. Or still any information is required?

Very thanks for the support.

(CID:113643965)

[DCIM_Support]

Spezialist. 

In order to determine what the issue is, we need data. The NMC could be putting the correct data on the web interface but incorrect data in the SNMP stack. It could be putting the correct data in both places and DCE may be misreading it. We need to know if that data is correct in order to proceed. 

One thing I am focusing on is that you ran a graph on this. Specifically, it appears that at about 2:30, the state you graphed changed and then changed back again at the same time the output of the UPS changed. It looks like DCE saw a change in state and not necessarily an alarm. To verify this, we need to know what the NMC provided to DCE at that moment. 

Is it still in this state in DCE? Is it NOT in alarm? Just check .1.3.6.1.4.1.318.1.1.1.7.2.6.0

Steve

(CID:113644002)

[DCIM_Support]

One thing I am focusing on is that you ran a graph on this. Specifically, it appears that at about 2:30, the state you graphed changed and then changed back again at the same time the output of the UPS changed. It looks like DCE saw a change in state and not necessarily an alarm. To verify this, we need to know what the NMC provided to DCE at that moment.

 Everything is correct, the graphs given above show successful process of runtime calibration on the UPS. And of course DCE at detection of Invalid Calibration shouldn't give any alarm.

Is it still in this state in DCE? Is it NOT in alarm? Just check .1.3.6.1.4.1.318.1.1.1.7.2.6.0

 Yes, it still in this state in DCE and it NOT in alarm, but:

bashAP9635 runtime calibration# snmpget -v2c -cpublic 192.168.0.101 .1.3.6.1.4.1.318.1.1.1.7.2.6.0 SNMPv2-SMI::enterprises.318.1.1.1.7.2.6.0 = INTEGER: 2

what according to the apcsmartups.xml DDF-file means Invalid Calibration:

bashapcsmartups.xml 1 0 2 1 3 2 * 2 OK Invalid Calibration Calibration In Progress

Very thanks for the support.

(CID:113644204)

[DCIM_Support]

Spezialist. 

That's not just from the DDF. This is from the MIB:

The results of the last runtime calibration.
Value ok(1) means a successful runtime calibration.
Value invalidCalibration(2) indicates last calibration did
not take place since the battery capacity was below
100%.
Value calibrationInProgress(3) means a calibration
is occurring now.

If it's returning a 2, the device's SNMP is responding with invalid calibration. DCE is reporting correctly as it sees the SNMP value. The device would appear to be reporting incorrectly. 

I'll see if one of the 3 phase guys here has any more info but if you need support on the UPS, you may need to contact one of the 3 phase guys locally.

Steve

(CID:113644980)

[DCIM_Support]

So the 3 phase guys here say you really shouldn't run a calibration on those big units but that's something to discuss with them. As for the result, they say they're unaware of any issues but some times the calibration just ends without a true result in the NMC.

(CID:113644985)

[DCIM_Support]

Hi Steve,

If it's returning a 2, the device's SNMP is responding with invalid calibration. DCE is reporting correctly as it sees the SNMP value. The device would appear to be reporting incorrectly.

 I also wrote about it 😀.

So the 3 phase guys here say you really shouldn't run a calibration on those big units but that's something to discuss with them. As for the result, they say they're unaware of any issues but some times the calibration just ends without a true result in the NMC.

 A little surprisingly 😀. Annual runtime calibration on such big UPSes according to all instructions at our enterprise carry out exclusively service personnel of Schneider Electric in EMEA (already not the first year). They are also already informed about above the specified bug, but no more. I.e. there is no solution of a bug yet...

Very thanks for the support.

(CID:114231457)

[DCIM_Support]

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