upsAdvStateAbnormalConditions returns empty string

[Anonymous user]

If we query the AP9630 or AP9617 management module on Smart-UPS RT 3000 XL with SNMP for upsAdvStateAbnormalConditions, we get an empty string.

We have upgraded to firmware 5.1.5.

Issues are with the SURTD3000XLI with the AP9617 and AP9630.

Model: Smart-UPS RT 3000 XL
Serial Number: NS0918002036
Firmware Revision: 4.1 (ID5)
Manufacture Date: 04/30/2009

snmpget -On -v1 -c public UPS .1.3.6.1.2.1.1.1.0
snmpget -On -v1 -c public UPS .1.3.6.1.4.1.318.1.1.1.11.2.1.0

.1.3.6.1.2.1.1.1.0 = STRING: APC Web/SNMP Management Card (MB:v4.0.1 PF:v5.1.5 PN:apc_hw05_aos_515.bin AF1:v5.1.5 AN1:apc_hw05_sumx_515.bin MN:AP9630 HR:05 SN: BA0915014135 MD:04/11/2009) (Embedded PowerNet SNMP Agent SW v2.2 compatible)
.1.3.6.1.4.1.318.1.1.1.11.2.1.0 = ""

Expected is
.1.3.6.1.4.1.318.1.1.1.11.2.1.0 = STRING: "00000000000000000000000000000000"

Is anybody else experiencing the same problem?

Thanks in advance.

Mark

[BillP]

this string should only have data when there is an abnormal condition present. to me, this looks normal if your UPS is running just fine.

here is the description of the OID which i found by using a MIB browser (keep in mind not every UPS supports every condition listed below:

An ASCII string containing the 32 flags representing the current active UPS faults. If the Network Card is unable to determine the values of the flags, this
variable is set to 'UNKNOWN'. If this variable is not supported by the connected UPS, this variable is set to 'NOT SUPPORTED'.

The flags are numbered from 1 to 32, and read from left to right. The flags are defined as follows:

Flag 1: Power Module Failure
Flag 2: Main Intelligence Module Failure
Flag 3: Redundant Intelligence Module Failure
Flag 4: Battery Failure

Flag 5: Load(kVA) Alarm Threshold Violation
Flag 6: Redundancy Lost
Flag 7: Redundancy Below Alarm Threshold
Flag 8: Bypass not in Range; Either Frequency or Voltage

Flag 9: Bypass Contactor Stuck in Bypass Condition
Flag 10: Bypass Contactor Stuck in On-Line Condition
Flag 11: In Bypass due to an Internal Fault
Flag 12: In Bypass due to an Overload

Flag 13: In Maintenance Bypass
Flag 14: Input Circuit Braker Tripped Open
Flag 15: System Level Fan Failure
Flag 16: Redundant Intelligent Module in Control

Flag 17: IIC Inter-Module Communication Failure
Flag 18: No Working Power Modules
Flag 19: Load Shutdown From Bypass; Input Frequency
Flag 20: Runtime Below Alarm Threshold

Flag 21: Extended Run Frame Fault
Flag 22: Output Voltage out of Range
Flag 23: UPS Not Synchronized
Flag 24: No Batteries Installed

Flag 25: Battery Voltage High
Flag 26: UPS Specific Fault Detected
Flag 27: Site Wiring Fault
Flag 28: Backfeed Protection Relay Opened

Flag 29:
Flag 30:
Flag 31:
Flag 32:

[Anonymous user]

Thanks for your reply.

In the forum, part of your message is truncated. However, the full text is in the email notification.

From the MIB file:

An ASCII string containing the 32 flags representing the current active UPS faults.
If the Network Card is unable to determine the values of the flags, this
variable is set to 'UNKNOWN'. If this variable is not supported by the
connected UPS, this variable is set to 'NOT SUPPORTED'.

My interpretation is that there are three possibilities:

.1.3.6.1.4.1.318.1.1.1.11.2.1.0 = STRING: "00000000000000000000000000000000"
(a zero may be one if a condition is met)
.1.3.6.1.4.1.318.1.1.1.11.2.1.0 = STRING: "UNKNOWN"
.1.3.6.1.4.1.318.1.1.1.11.2.1.0 = STRING: "NOT SUPPORTED"

An empty string is not a valid option, it is not specified in the MIB file.

We also have a 3000 RM XL UPS, that does return
.1.3.6.1.4.1.318.1.1.1.11.2.1.0 = STRING: "00000000000000000000000000000000"
as expected.

Is there a way to force a flag to be 1 on a SURTD3000XLI, so we can check if the string is correctly returned if one of the flags is set to 'one'?

Regards, Mark

[BillP · Accepted solution]

hi mark,

i mis-read your initial post and saw the reply of all zeros and thought thats what you got back which was a line below when you said got "" - sorry about that!

actually, i found that we have an issue logged against this for the SURTD3000XLI model. it will be fixed in sumx 6.x which i think will be available later this year but essentially it is an NMC firmware bug with that particular UPS. it won't get addressed on AP9617 based management cards because those are discontinued now.

hope that helps!