[Nut-upsuser] Tripplite UPS (SU10KRT3/1X) through snmp-ups (nut 2.6.5)
Иши Кылса
ishikylsa at gmail.com
Fri Feb 7 05:17:45 UTC 2014
Hi, Nut-upsusers,
I am having problem configuring NUT to work with Tripplite UPS through SNMP.
There is a Tripplite SmartOnline SU10KRT3/1X and attempts to monitor it
using NUT though SNMP are failing...
OS: Enterprise Linux 6, Nut version: 2.6.5.
ups.conf is configured:
[trippliteups]
driver = snmp-ups
port = 10.200.254.39
desc = "ProductionServer"
snmp_version = v1
community = public
Starting the driver with command
*snmp-ups -a trippliteups -D *
is failing with the following output:
Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5)
0.000000 debug level is '1'
0.000215 SNMP UPS driver : entering upsdrv_initups()
0.020982 trying the new match_sysoid() method
0.026416 match_sysoid: device sysOID value = .1.3.6.1.4.1.935
0.026425 match_sysoid: checking MIB apcc
0.026431 match_sysoid: checking MIB mge
0.026435 match_sysoid: comparing .1.3.6.1.4.1.935 with
.1.3.6.1.4.1.705.1
0.026439 match_sysoid: checking MIB netvision
0.026443 match_sysoid: comparing .1.3.6.1.4.1.935 with
.1.3.6.1.4.1.4555.1.1.1
0.026447 match_sysoid: checking MIB pw
0.026450 match_sysoid: comparing .1.3.6.1.4.1.935 with
.1.3.6.1.4.1.534.1
0.026455 match_sysoid: checking MIB aphel_genesisII
0.026459 match_sysoid: comparing .1.3.6.1.4.1.935 with
.1.3.6.1.4.1.17373
0.026462 match_sysoid: checking MIB aphel_revelation
0.026466 match_sysoid: comparing .1.3.6.1.4.1.935 with
.1.3.6.1.4.1.534.6.6.6
0.026469 match_sysoid: checking MIB eaton_epdu
0.026473 match_sysoid: comparing .1.3.6.1.4.1.935 with
.1.3.6.1.4.1.534.6.6.7
0.026476 match_sysoid: checking MIB pulizzi_switched1
0.026480 match_sysoid: comparing .1.3.6.1.4.1.935 with
.1.3.6.1.4.1.20677.1
0.026483 match_sysoid: checking MIB pulizzi_switched2
0.026487 match_sysoid: comparing .1.3.6.1.4.1.935 with
.1.3.6.1.4.1.20677.2
0.026491 match_sysoid: checking MIB raritan
0.026495 match_sysoid: comparing .1.3.6.1.4.1.935 with
.1.3.6.1.4.1.13742
0.026499 match_sysoid: checking MIB baytech
0.026503 match_sysoid: checking MIB cpqpower
0.026507 match_sysoid: comparing .1.3.6.1.4.1.935 with
.1.3.6.1.4.1.232.165.3
0.026510 match_sysoid: checking MIB bestpower
0.026513 match_sysoid: checking MIB cyberpower
0.026517 match_sysoid: comparing .1.3.6.1.4.1.935 with
.1.3.6.1.4.1.3808
0.026521 match_sysoid: checking MIB ietf
0.026526 match_sysoid: comparing .1.3.6.1.4.1.935 with
.1.3.6.1.2.1.33
0.026529 No matching MIB found for sysOID '.1.3.6.1.4.1.935'!
Please report it to NUT developers, with an 'upsc' output for your device.
Going back to the classic MIB detection method.
0.026534 load_mib2nut: trying classic method with 'apcc' mib
0.029602 load_mib2nut: trying classic method with 'mge' mib
0.032539 load_mib2nut: trying classic method with 'netvision' mib
0.035569 load_mib2nut: trying classic method with 'pw' mib
0.038493 load_mib2nut: trying classic method with 'aphel_genesisII'
mib
0.041481 load_mib2nut: trying classic method with 'aphel_revelation'
mib
0.044521 load_mib2nut: trying classic method with 'eaton_epdu' mib
0.047586 load_mib2nut: trying classic method with
'pulizzi_switched1' mib
0.050465 load_mib2nut: trying classic method with
'pulizzi_switched2' mib
0.053334 load_mib2nut: trying classic method with 'raritan' mib
0.056268 load_mib2nut: trying classic method with 'baytech' mib
0.059312 load_mib2nut: trying classic method with 'cpqpower' mib
0.062278 load_mib2nut: trying classic method with 'bestpower' mib
0.065214 load_mib2nut: trying classic method with 'cyberpower' mib
0.068253 load_mib2nut: trying classic method with 'ietf' mib
0.071168 No supported device detected
Would be grateful if anyone could help me with it.
Ishi Kylsa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140207/001d0cb6/attachment.html>
More information about the Nut-upsuser
mailing list