Иши Кылса
2014-Feb-14 03:49 UTC
[Nut-upsuser] Tripplite UPS (SU10KRT3/1X) through snmp-ups (nut 2.6.5)
> 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. > > Yes, says "Timeout: No Response from 10.200.254.39", Ok.> ..... > > >> 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: >> >> upsBaseBatteryStatus1.3.6.1.4.1.935.1.1.1.2.1.1 >> upsBaseOutputStatus1.3.6.1.4.1.935.1.1.1.4.1.1 >> >> Other useful diagnostic OIDs are: >> >> upsSmartBatteryVoltage1.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 >> upsSmartInputLineVoltage1.3.6.1.4.1.935.1.1.1.3.2.1 >> upsSmartOutputLoad1.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. > >Yes, this works fine: 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.2.1.1 .1.3.6.1.4.1.935.1.1.1.2.2.1 .1.3.6.1.4.1.935.1.1.1.2.2.3 .1.3.6.1.4.1.935.1.1.1.1.1.1.0 = STRING: "Intelligent" .1.3.6.1.4.1.935.1.1.1.2.1.1.0 = INTEGER: batteryNormal(2) .1.3.6.1.4.1.935.1.1.1.2.2.1.0 = INTEGER: 100 .1.3.6.1.4.1.935.1.1.1.2.2.3.0 = INTEGER: 270 snmpget -v 1 -c public -On 10.200.254.39 .1.3.6.1.4.1.935.1.1.1.3.2.1 .1.3.6.1.4.1.935.1.1.1.4.1.1 .1.3.6.1.4.1.935.1.1.1.4.2.1 .1.3.6.1.4.1.935.1.1.1.4.2.2 .1.3.6.1.4.1.935.1.1.1.4.2.3 .1.3.6.1.4.1.935.1.1.1.3.2.1.0 = INTEGER: 2006 .1.3.6.1.4.1.935.1.1.1.4.1.1.0 = INTEGER: onLine(2) .1.3.6.1.4.1.935.1.1.1.4.2.1.0 = INTEGER: 2309 .1.3.6.1.4.1.935.1.1.1.4.2.2.0 = INTEGER: 500 .1.3.6.1.4.1.935.1.1.1.4.2.3.0 = INTEGER: 7 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.2.1.1 .1.3.6.1.4.1.935.1.1.1.2.2.1 .1.3.6.1.4.1.935.1.1.1.2.2.3 upsBaseIdentModel.0 = STRING: "Intelligent" upsBaseBatteryStatus.0 = INTEGER: batteryNormal(2) upsSmartBatteryCapacity.0 = INTEGER: 100 upsSmartBatteryTemperature.0 = INTEGER: 260 snmpget -v 1 -c public -Os 10.200.254.39 .1.3.6.1.4.1.935.1.1.1.3.2.1 .1.3.6.1.4.1.935.1.1.1.4.1.1 .1.3.6.1.4.1.935.1.1.1.4.2.1 .1.3.6.1.4.1.935.1.1.1.4.2.2 .1.3.6.1.4.1.935.1.1.1.4.2.3 upsSmartInputLineVoltage.0 = INTEGER: 1998 upsBaseOutputStatus.0 = INTEGER: onLine(2) upsSmartOutputVoltage.0 = INTEGER: 2309 upsSmartOutputFrequency.0 = INTEGER: 500 upsSmartOutputLoad.0 = INTEGER: 7 Slightly changed the list, took from running snmptranslate for all parameters: snmptranslate -IR -On upsBaseIdentModel upsBaseBatteryStatus upsSmartBatteryCapacity upsSmartBatteryTemperature upsSmartInputLineVoltage upsBaseOutputStatus upsSmartOutputVoltage upsSmartOutputFrequency upsSmartOutputLoad upsSmartControlUpsOff upsSmartControlSimulatePowerFail upsSmartControlFlashAndBeep .1.3.6.1.4.1.935.1.1.1.1.1.1 .1.3.6.1.4.1.935.1.1.1.2.1.1 .1.3.6.1.4.1.935.1.1.1.2.2.1 .1.3.6.1.4.1.935.1.1.1.2.2.3 .1.3.6.1.4.1.935.1.1.1.3.2.1 .1.3.6.1.4.1.935.1.1.1.4.1.1 .1.3.6.1.4.1.935.1.1.1.4.2.1 .1.3.6.1.4.1.935.1.1.1.4.2.2 .1.3.6.1.4.1.935.1.1.1.4.2.3 .1.3.6.1.4.1.935.1.1.1.6.2.1 .1.3.6.1.4.1.935.1.1.1.6.2.4 .1.3.6.1.4.1.935.1.1.1.6.2.5 (Last 3 OIDs didn't return values with snmpget, all others returned correct values as listed above.) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140214/eb0d9bb4/attachment.html>
Charles Lepple
2014-Feb-14 14:26 UTC
[Nut-upsuser] Tripplite UPS (SU10KRT3/1X) through snmp-ups (nut 2.6.5)
On Feb 13, 2014, at 10:49 PM, ??? ????? wrote:> Slightly changed the list, took from running snmptranslate for all parameters: > snmptranslate -IR -On upsBaseIdentModel upsBaseBatteryStatus upsSmartBatteryCapacity upsSmartBatteryTemperature upsSmartInputLineVoltage upsBaseOutputStatus upsSmartOutputVoltage upsSmartOutputFrequency upsSmartOutputLoad upsSmartControlUpsOff upsSmartControlSimulatePowerFail upsSmartControlFlashAndBeepAll but the last three are mapped here: https://github.com/networkupstools/nut/tree/snmp_subdriver @ ab7b0452e (might need to re-clone this; I rebased this on master.) I haven't read up on the difference between NUT variables and commands in snmp-ups. Please try building snmp-ups, and let me know how the output of upsc looks.> .1.3.6.1.4.1.935.1.1.1.6.2.1 > .1.3.6.1.4.1.935.1.1.1.6.2.4 > .1.3.6.1.4.1.935.1.1.1.6.2.5 (Last 3 OIDs didn't return values with snmpget, all others returned correct values as listed above.)The upsSmartControl* OIDs are probably write-only (although the MIB indicates you should be able to read them back). -- Charles Lepple clepple at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140214/031e9cbf/attachment.html>
Charles Lepple
2014-Feb-14 14:59 UTC
[Nut-upsuser] Tripplite UPS (SU10KRT3/1X) through snmp-ups (nut 2.6.5)
On Feb 14, 2014, at 9:26 AM, Charles Lepple wrote:> On Feb 13, 2014, at 10:49 PM, ??? ????? wrote: > >> Slightly changed the list, took from running snmptranslate for all parameters: >> snmptranslate -IR -On upsBaseIdentModel upsBaseBatteryStatus upsSmartBatteryCapacity upsSmartBatteryTemperature upsSmartInputLineVoltage upsBaseOutputStatus upsSmartOutputVoltage upsSmartOutputFrequency upsSmartOutputLoad upsSmartControlUpsOff upsSmartControlSimulatePowerFail upsSmartControlFlashAndBeep > > All but the last three are mapped here: https://github.com/networkupstools/nut/tree/snmp_subdriver @ ab7b0452e (might need to re-clone this; I rebased this on master.)I forgot to mention, if you don't want to deal with autoconf, etc., when building from Git, you can grab a snapshot from Buildbot: nut-2.7.1.5.tar.gz This builder generates the snapshots: http://buildbot.networkupstools.org/public/nut/waterfall?show=Debian-x64-gcc> > I haven't read up on the difference between NUT variables and commands in snmp-ups. > > Please try building snmp-ups, and let me know how the output of upsc looks. > >> .1.3.6.1.4.1.935.1.1.1.6.2.1 >> .1.3.6.1.4.1.935.1.1.1.6.2.4 >> .1.3.6.1.4.1.935.1.1.1.6.2.5 (Last 3 OIDs didn't return values with snmpget, all others returned correct values as listed above.) > > The upsSmartControl* OIDs are probably write-only (although the MIB indicates you should be able to read them back). > > -- > Charles Lepple > clepple at gmail > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140214/28c9a286/attachment.html>
Reasonably Related Threads
- Tripplite UPS (SU10KRT3/1X) through snmp-ups (nut 2.6.5)
- Tripplite UPS (SU10KRT3/1X) through snmp-ups (nut 2.6.5)
- Tripplite UPS (SU10KRT3/1X) through snmp-ups (nut 2.6.5)
- Tripplite UPS (SU10KRT3/1X) through snmp-ups (nut 2.6.5)
- Tripplite UPS (SU10KRT3/1X) through snmp-ups (nut 2.6.5)