smartups 6000 RT Battery broken OID

[Anonymous user]

Hi and good Morning,

maybe I'm wrong with my topic, in this case please move the thread.

My problem:

I'm monitoring our smaller UPS devices (APC smartups 3000 to 6000 series) with some self created scripts. All data will be put to RRD databases and provided on web pages for the (my) team. I'm monitoring voltages, load, temperatures, Wattage and last but not least the status of battery and UPS itself.

For Battery I Use OID: 1.3.6.1.4.1.318.1.1.1.2.1.1.0  ( where I use "reply" of 1 as unknown, 2 as Battery OK and 3 as Battery low charged)

For UPS status I use: 1.3.6.1.4.1.318.1.1.1.4.1.1  (with 12 result avalues e.g. 2 as online, 3 on Battery ....)

This was working long time fine, now I recognized by login to my UPS that inside web interface I get a ALarm message:

Replacement Battery Needed

At least one faulty battery exists.

But all my snmp monitoring does not show me ANYTHING about it.

Is there another OID to get this Replacement warnig readout? Any Hints what I'm doing wrong?

So far I always thought a battery status 2 and UPS status 2 would be sufficient as result, but today I learned that a broken Battery is not mentioned here.

Thanks for any hint to 'right' OID or Analysis

regards

Stephan

[BillP · Accepted solution]

Hi Stephan - can you confirm the exact SKU of this UPS? Is it an SURT6000 or SRT6K? 

I have access to both of these model UPSs and they respond to these OIDs. Can you confirm what responses you're receiving from these OIDs or are they timing out completely? The response to .1.3.6.1.2.1.1.1 is helpful too if you want to share that from your UPS.

.1.3.6.1.4.1.318.1.1.1.11.1.1 is another one to maybe check which is upsBasicStateOutputState. You'll get a response of 0's and 1's which represent specific status flags in the system. I pasted the description below from the MIB.

An ASCII string containing the 64 flags representing the current state(s) of the UPS. If the Network Card is unable to determine the state of the UPS, this
 variable is set to 'UNKNOWN'. The flags are numbered 1 to 64, read from left to  right. The flags are defined as follows:
 
 Flag 1: Abnormal Condition Present
 Flag 2: On Battery
 Flag 3: Low Battery
 Flag 4: On Line 
 
 Flag 5: Replace Battery
 Flag 6: Serial Communication Established
 Flag 7: AVR Boost Active
 Flag 8: AVR Trim Active 
 
 Flag 9: Overload
 Flag 10: Runtime Calibration 
 Flag 11: Batteries Discharged
 Flag 12: Manual Bypass
 
 Flag 13: Software Bypass
 Flag 14: In Bypass due to Internal Fault
 Flag 15: In Bypass due to Supply Failure
 Flag 16: In Bypass due to Fan Failure 
 
 Flag 17: Sleeping on a Timer 
 Flag 18: Sleeping until Utility Power Returns
 Flag 19: On
 Flag 20: Rebooting
 
 Flag 21: Battery Communication Lost 
 Flag 22: Graceful Shutdown Initiated
 Flag 23: Smart Boost or Smart Trim Fault
 Flag 24: Bad Output Voltage
 Flag 25: Battery Charger Failure
 Flag 26: High Battery Temperature 
 Flag 27: Warning Battery Temperature 
 Flag 28: Critical Battery Temperature
 Flag 29: Self Test In Progress 
 Flag 30: Low Battery / On Battery
 Flag 31: Graceful Shutdown Issued by Upstream Device
 Flag 32: Graceful Shutdown Issued by Downstream Device
 Flag 33: No Batteries Attached
 Flag 34: Synchronized Command is in Progress
 Flag 35: Synchronized Sleeping Command is in Progress 
 Flag 36: Synchronized Rebooting Command is in Progress 
 Flag 37: Inverter DC Imbalance 
 Flag 38: Transfer Relay Failure
 Flag 39: Shutdown or Unable to Transfer
 Flag 40: Low Battery Shutdown
 Flag 41: Electronic Unit Fan Failure
 Flag 42: Main Relay Failure
 Flag 43: Bypass Relay Failure
 Flag 44: Temporary Bypass
 Flag 45: High Internal Temperature
 Flag 46: Battery Temperature Sensor Fault
 Flag 47: Input Out of Range for Bypass
 Flag 48: DC Bus Overvoltage
 Flag 49: PFC Failure
 Flag 50: Critical Hardware Fault
 Flag 51: Green Mode/ECO Mode
 Flag 52: Hot Standby
 
 Flag 53: Emergency Power Off (EPO) Activated
 Flag 54: Load Alarm Violation
 Flag 55: Bypass Phase Fault
 Flag 56: UPS Internal Communication Failure 
 
 Flag 57: Efficiency Booster Mode
 Flag 58: Off
 Flag 59: Standby
 Flag 60: 
 
 Flag 61: 
 Flag 62: 
 Flag 63: 
 Flag 64: 

Can you also provide the event.txt log to look at? You can export it right from the web page under Logs->Event->Log.

[Anonymous user]

Hi Angela,

thanks, that was teh missing link. I know that battery is broken and need replacement, I was only a bit irritated on the fact that battery is reported OK from one OID and marked as "Replace battery" from another OID.

So

OID 1.3.6.1.4.1.318.1.1.1.2.2.4 reponse 1 is Battery OK, 2 for Replace battery

OID 1.3.6.1.4.1.318.1.1.1.2.1.1.0 response 1 is Battery unknow, 2 is Battery OK, 3 is Battery low

Where I now assume one is teh check if Battery is OK or not, whereas teh other OID represents the voltage (or capacity) based info of Battery cherged or not

Thanks a lot.

regards

Stephan

[BillP]

Hi Stephan,

You're welcome. But, if you can clarify what UPS model this is and what responses you got from which OIDs when the web reported needing a battery, I can log a bug if a particular SNMP OID is reporting an incorrect status.

From your response, I am not clear what those OIDs actually responded versus what you expected them to show. By what you've described, I'd expect 1.3.6.1.4.1.318.1.1.1.2.2.4 to respond 2 to you if you have a bad battery and if it said 1, then it sounds like a bug to me..?

[Anonymous user]

Hi Angela,

the OID 1.3.6.1.4.1.318.1.1.1.2.2.4 reports 2 which means battery is bad,

BUT:

OID 1.3.6.1.4.1.318.1.1.1.2.1.1.0  reports also 2. and what I read on the web for this OID (correct me please if I have wrong info) means Battery OK. a 1 tells Unknown state and and a 3 means Battery low charged.

So I was confused that the second OID can show Battery OK when the first OID tells Battery need replacement.

But also your given OID  .1.3.6.1.4.1.318.1.1.1.11.1.1 with the explanation show that Battery need replacement. And for a 4 year old Battery I trust the info that it needs replacement.

My intention in this thread was initially to get right OID's checked in my shell scripts to have correct interpretation of given results.

I will depend more on the 64 digits, as I get all important info from there, and its easy to verify the few important bit there.

The model is a Smart-UPS RT 6000 XL

regards

Stephan

PS:

The OID: 1.3.6.1.2.1.1.1  gives:

SNMPv2-MIB::sysDescr.0 = STRING: APC Web/SNMP Management Card (MB:v4.0.1 PF:v5.1.7 PN:apc_hw05_aos_517.bin AF1:v5.1.7 AN1:apc_hw05_sumx_517.bin MN:AP9631 HR:05 SN: 5A1215T03078 MD:04/12/2012) (Embedded PowerNet SNMP Agent SW v2.2 compatible)

[BillP]

OK, thanks for the clarification! I will see if I can ask about 1.3.6.1.4.1.318.1.1.1.2.1.1.0 to understand a little bit more when it should be used. It seems to more focus on the charge as I think you mentioned earlier, rather than battery needs replacing or not. I'll report back anything I find.

I am glad that other OID is helpful for you.

Lastly, not sure if you know or are interested but you are several firmware revisions behind. We are on 6.4.0 now for this UPS and you have 5.1.7. It is a "major" upgrade as the UI will change but there are many more bug fixes and feature enhancements included in the system. Not sure if you've seen the new firmware on other devices but if you are interested further in upgrading, let me know.

[BillP]

Hi Stephan,

I found out that for Smart UPS, only batteryNormal and batteryLow are supported for 1.3.6.1.4.1.318.1.1.1.2.1.1.0 . batteryInFaultCondition is only supported for a particular 3 phase UPS model. I will log a request to update the description to be more clear on what this OID is for. It is supposed to be for when the UPS is depleted rather than needs replacement as we've already discovered.

[Anonymous user]

Hi Angela,

sorry for late reply, surely I'm interested in Firmware /Software upgrade for teh UPS devices in my control. I just checked the support page but did not "on the fly" could identify the right files to download. Maybe more time is need for that.

I just earned the monitoring job, so I'm collecting data from multiple UPS devices in REALLY different states. All are in factory level of their Software / firmware. I need to get first up to speed with my local device before I can start upgrading all remote ones. Bad thing: there are models from 2200 smart ups up to 6000 versions. all are different.

I think, once I have more UPS device on latest and greatest Firmware, monitoring becomes also easier.

regards

Stephan

[BillP]

Hi Stephan,

I can help you with what firmware to choose. If you have an AP9630, AP9631 or AP9635 with some type of Smart-UPS - doesn't matter if it is a 2200 or 6000, as long as it is a "Smart-UPS", they all use the same firmware which is @ http://www.apc.com/us/en/tools/download/ and you'll want to Filter by Software/Firmware and select Firmware Upgrades - UPS Network Management Cards. Then, look for part number SFSUMX640. Help upgrading is here -> http://www.apc.com/us/en/faqs/FA156106

If you have other models of either Network Management Card and UPS, then we'll have to check further on what it will use. But, most options you probably need are on the UPS Network Management Cards Firmware Upgrades page you see the SFSUMX640 on.

I suggest maybe you upgrade one first and take a look at the new interface in the management web UI if you're not familiar with it. Or, if you want to log into a live, public device we have on testdrive.apc.com website, let me know (sometimes they are inaccessible) but we have public NMCs for customers to check out there. You could see the new UI first since you're on the blue/white UI which we've changed.

And yes, I agree, I hope the monitoring will get easier when you've upgraded and also when everything is on the same version.

Please let me know if you have any questions.

[Anonymous user]

Hi Angela,

thanks for the links.  Would the suggested part number also work on AP9617 for example. In teh download area I see a smart-ups section fort teh Ap9616/17/18 seperated.

I think we have some really old devices... 😉 (It's a different one then the initial one described.

I have at one location:

"Smart-UPS 3000 RM"
SNMPv2-MIB::sysDescr.0 = STRING: APC Web/SNMP Management Card (MB:v3.6.8 PF:v2.6.4 PN:apc_hw02_aos_264.bin AF1:v2.6.1 AN1:apc_hw02_sumx_261.bin MN:AP9617 HR:A10 SN: ZA0633007820 MD:08/08/2006) (Embedded PowerNet SNMP Agent SW v2.2 compatible)

and a second device:

"Smart-UPS RT 6000 RM XL"
SNMPv2-MIB::sysDescr.0 = STRING: APC Web/SNMP Management Card (MB:v4.0.1 PF:v5.1.7 PN:apc_hw05_aos_517.bin AF1:v5.1.7 AN1:apc_hw05_sumx_517.bin MN:AP9631 HR:05 SN: 5A1346T00542 MD:11/11/2013) (Embedded PowerNet SNMP Agent SW v2.2 compatible)

As for my understanding: I need the SFSUMX640 for the second device, and the SFSUMX372 for the first one, right? Or will the SFSUMX640 fit for the first one too, even if different NMC Ap9617 is in?

regards

Stephan

[BillP]

Hi Stephan - what you said first is accurate: 

As for my understanding: I need the SFSUMX640 for the second device, and the SFSUMX372 for the first one, right?

AP9630/31/35 (NMC2) and AP9617/18/19 (NMC1) cards are different animals so they do require separate, incompatible firmware. Go with the above statement and download the different firmware SKUs and put the SFSUMX372 firmware on your 3000RM and the SFSUMX640 firmware only on any AP9630/31/35 cards you find.

The above firmwares are also for Smart-UPS only. If you come across any Symmetra UPSs, they'll also need different firmwares for either NMC1 or NMC2 respectively.

Let me know if you have any further questions 

[Anonymous user]

Hi Angela,

sorry for bothering you again.

Will FW updates on NMC cause power loss on attached devices? Or will it only have a reboot of NMC ?

Will e.g. IP settings be kept?

regards

Stephan

[BillP]

Hi Stephan,

The NMC itself will only do a warm/soft restart. No effect on the UPS and also no effect on the settings of the NMC. The only thing I'd say is if you're using a DHCP assigned address on the NMC, it will do have to do a DHCP request again to the server - and probably get the same IP address or slim chance it won't I suppose.