[Nut-upsuser] Tripplite UPS (SU10KRT3/1X) through snmp-ups (nut 2.6.5)

[Charles Lepple]

[Please keep the list CC'd. Thanks!]

On Feb 13, 2014, at 4:55 AM, Иши Кылса wrote:

> Can you try adding "-v 1" to the snmpwalk command? If that works, we can add it to gen-snmp-subdriver.sh.
> 
> Yes, I tried it before, ran command "snmpwalk -v 1 -On -c public 10.200.254.39 .1.3.6.1.4.1.935" 
> 
> Output:
> .1.3.6.1.4.1.935 = NULL
> Error: OID not increasing: .1.3.6.1.4.1.935
>  >= .1.3.6.1.4.1.935
> 
> To solve this error in some forums it is advised to use "-Cc":
> snmpwalk -Cc -v 1 -On -c public 10.200.254.39 .1.3.6.1.4.1.935
> But it outputs infinitely the following:
> .1.3.6.1.4.1.935 = NULL
> .1.3.6.1.4.1.935 = NULL

Does it have the same behavior if you start from .1.3.6.1.4.1.935.1 or .1.3.6.1.4.1.935.1.1? If not, no worries - see below.

> .....
>  
> The important part of "mode 2" is to have the output of snmpwalk. It is possible to query each OID, and manually build the *-mib.c files, but if we can get snmpwalk to work, that would be easier.
> 
> If not, the important OIDs are:
> 
> upsBaseBatteryStatus	1.3.6.1.4.1.935.1.1.1.2.1.1
> upsBaseOutputStatus	1.3.6.1.4.1.935.1.1.1.4.1.1
> 
> Other useful diagnostic OIDs are:
> 
> upsSmartBatteryVoltage	1.3.6.1.4.1.935.1.1.1.2.2.2
> upsSmartBatteryRunTimeRemaining	 1.3.6.1.4.1.935.1.1.1.2.2.4
> upsSmartInputLineVoltage	1.3.6.1.4.1.935.1.1.1.3.2.1
> upsSmartOutputLoad	1.3.6.1.4.1.935.1.1.1.4.2.3
> 
> (Ideally we would include everything the UPS offers, but this should be enough for basic monitoring and shutdown.)
> 
> These parameters are more than enough, even upsBaseBatteryStatus, upsBaseOutputStatus, upsSmartOutputLoad - is all we need. And maybe traps, to know when UPS goes on battery, online etc.
> As I wrote earlier, snmpget commands are working fine "snmpget -v 1 -c public 10.200.254.39  .1.3.6.1.4.1.935.1.1.1.4.1.1" returning correct results:
> 
> XPPC-MIB::upsBaseOutputStatus.0 = INTEGER: onLine(2)
> 
> 

I would like to take this opportunity to make sure that gen-snmp-subdriver is working, so can you please run the following commands:

snmpget -v 1 -c public  -On 10.200.254.39  .1.3.6.1.4.1.935.1.1.1.1.1.1 1.3.6.1.4.1.935.1.1.1.4.1.1 1.3.6.1.4.1.935.1.1.1.2.2.2 1.3.6.1.4.1.935.1.1.1.2.2.4 1.3.6.1.4.1.935.1.1.1.3.2.1 1.3.6.1.4.1.935.1.1.1.4.2.3

snmpget -v 1 -c public  -Os 10.200.254.39  .1.3.6.1.4.1.935.1.1.1.1.1.1 1.3.6.1.4.1.935.1.1.1.4.1.1 1.3.6.1.4.1.935.1.1.1.2.2.2 1.3.6.1.4.1.935.1.1.1.2.2.4 1.3.6.1.4.1.935.1.1.1.3.2.1 1.3.6.1.4.1.935.1.1.1.4.2.3

The output of snmpwalk is very close to the output of snmpget with multiple OIDs, so hopefully this works.

-- 
Charles Lepple
clepple at gmail



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140213/4e8270a9/attachment.html>