[Nut-upsuser] Tripplite SU2200XL

[Kirk Bocek]

To answer my own question, looks like no, nothing is missing. Adding '-Cc' to
snmpwalk allows non-sequential OIDs:

UPS-MIB::upsIdentManufacturer.0 = STRING: "Tripp Lite"
UPS-MIB::upsIdentModel.0 = STRING: "SU2200XL"
UPS-MIB::upsIdentUPSSoftwareVersion.0 = STRING: "2.0"
UPS-MIB::upsIdentAgentSoftwareVersion.0 = STRING: "12.03.0024"
UPS-MIB::upsIdentName.0 = STRING: "tripplite1"
UPS-MIB::upsIdentAttachedDevices.0 = ""
UPS-MIB::upsBatteryStatus.0 = INTEGER: batteryNormal(2)
UPS-MIB::upsSecondsOnBattery.0 = INTEGER: 0
UPS-MIB::upsEstimatedChargeRemaining.0 = INTEGER: 100
UPS-MIB::upsBatteryVoltage.0 = INTEGER: 81
UPS-MIB::upsBatteryTemperature.0 = INTEGER: 26
UPS-MIB::upsInputLineBads.0 = Wrong Type (should be Counter32): INTEGER: 0
UPS-MIB::upsInputNumLines.0 = INTEGER: 1
UPS-MIB::upsInputLineIndex.1 = INTEGER: 0
UPS-MIB::upsInputFrequency.1 = INTEGER: 59
UPS-MIB::upsInputVoltage.1 = INTEGER: 117
UPS-MIB::upsOutputSource.0 = INTEGER: normal(3)
UPS-MIB::upsOutputFrequency.0 = INTEGER: 59
UPS-MIB::upsOutputNumLines.0 = INTEGER: 1
UPS-MIB::upsOutputLineIndex.1 = INTEGER: 0
UPS-MIB::upsOutputVoltage.1 = INTEGER: 119
UPS-MIB::upsOutputPercentLoad.1 = INTEGER: 34
UPS-MIB::upsBypassNumLines.0 = INTEGER: 0
UPS-MIB::upsBypassFrequency.0 = INTEGER: 0


Kirk Bocek wrote:
> I figured out how to add TrippLite's MIB files to net-snmp. Now snmpwalk translates
> the OIDs:
> 
> UPS-MIB::upsIdentManufacturer.0 = STRING: "Tripp Lite"
> UPS-MIB::upsIdentModel.0 = STRING: "SU2200XL"
> UPS-MIB::upsIdentUPSSoftwareVersion.0 = STRING: "2.0"
> UPS-MIB::upsIdentAgentSoftwareVersion.0 = STRING: "12.03.0024"
> UPS-MIB::upsIdentName.0 = STRING: "tripplite1"
> UPS-MIB::upsIdentAttachedDevices.0 = ""
> UPS-MIB::upsBatteryStatus.0 = INTEGER: batteryNormal(2)
> UPS-MIB::upsSecondsOnBattery.0 = INTEGER: 0
> UPS-MIB::upsEstimatedChargeRemaining.0 = INTEGER: 100
> UPS-MIB::upsBatteryVoltage.0 = INTEGER: 81
> UPS-MIB::upsBatteryTemperature.0 = INTEGER: 27
> UPS-MIB::upsInputLineBads.0 = Wrong Type (should be Counter32): INTEGER: 0
> UPS-MIB::upsInputNumLines.0 = INTEGER: 1
> UPS-MIB::upsInputLineIndex.1 = INTEGER: 0
> UPS-MIB::upsInputFrequency.1 = INTEGER: 60
> UPS-MIB::upsInputVoltage.1 = INTEGER: 116
> UPS-MIB::upsOutputSource.0 = INTEGER: normal(3)
> UPS-MIB::upsOutputFrequency.0 = INTEGER: 60
> UPS-MIB::upsOutputNumLines.0 = INTEGER: 1
> UPS-MIB::upsOutputLineIndex.1 = INTEGER: 0
> UPS-MIB::upsOutputVoltage.1 = INTEGER: 119
> UPS-MIB::upsOutputPercentLoad.1 = INTEGER: 33
> UPS-MIB::upsBypassNumLines.0 = INTEGER: 0
> UPS-MIB::upsBypassFrequency.0 = INTEGER: 0
> Error: OID not increasing: UPS-MIB::upsBypassNumLines.0
>  >= UPS-MIB::upsBypassFrequency.0
> 
> I wonder if the error on the last line is causing snmpwalk to miss some entries.
> 
> 
> Gregory Gulik wrote:
>> I don't recall needing to do anything special.
>> If it matters I'm running the NUT that comes with RHEL4 which is 2.0.0
>>
>> Kirk Bocek wrote:
>>> Gregory,
>>> I installed an SNMP web card in my Tripplite ups and here's what I get:
>>>
>>> $upsc tripplite1-snmp at localhost
>>> battery.charge: 100.0
>>> battery.voltage: 008.1
>>> driver.name: snmp-ups
>>> driver.parameter.mibs: ietf
>>> driver.parameter.pollfreq: 15
>>> driver.parameter.port: tripplite1.pvt
>>> driver.parameter.snmp_version: v1
>>> driver.version: 2.0.3
>>> driver.version.internal: 0.41
>>> input.frequency: 005.9
>>> input.voltage: 118.0
>>> ups.firmware.aux: 12.03.0024
>>> ups.load: 034.0
>>> ups.mfr: Tripp Lite
>>> ups.model: SU2200XL
>>> ups.status: OL
>>>
>>> The battery.voltage and input.frequency values appear to be off by a factor of 10.
>>> Did you do anything special to your install?
>>>
>>> Thanks,
>>> Kirk Bocek
>>>
>>> Gregory Gulik wrote:
>>>   
>>>> I have a very similar UPS with the SNMP module and it works fine.  Here
>>>> are all the fields I get with upsc:
>>>>
>>>> battery.charge: 100.0
>>>> battery.voltage: 040.8
>>>> driver.name: snmp-ups
>>>> driver.parameter.port: tripplite1
>>>> driver.version: 2.0.0
>>>> driver.version.internal: 0.40
>>>> input.frequency: 059.9
>>>> input.voltage: 115.0
>>>> ups.firmware.aux: Tripp Lite 3.0.37 (GAPI 2.0)
>>>> ups.load: 020.0
>>>> ups.mfr: Tripp Lite
>>>> ups.model: SMART1500RMXL2Ua
>>>> ups.status: OL
>>>>
>>>>
>>>> Kirk Bocek wrote:
>>>>     
>>>>> Well, bummer. I was hoping to get this to work. Thanks for your help
>>>>> though.
>>>>>
>>>>> I guess I'm going to have to spring for an SNMP module for this UPS.
>>>>> Do you know if
>>>>> Tripplite has done anything wonky in their implementation that would
>>>>> cause a problem
>>>>> with nut's SNMP interface?
>>>>>   
>>>>>       
>> -- 
>> Greg Gulik                                 http://www.gulik.org/greg/
>> greg @ gulik.org
>>
>>
> 
> 
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser