<br><div class="gmail_quote">2012/10/15 Ing. Ján <span dir="ltr"><<a href="mailto:jan.ondrej@upjs.sk" target="_blank">jan.ondrej@upjs.sk</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br></blockquote><div> <br>Hi<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
thanks for reply. We tested shutdown, but UPS's initial battery capacity is<br>
0%, after power loss, battery started to "charge", capacity is increasing.<br>
When NUT shuts down my server? When UPS is over 95% of it's capacity? :-)<br></blockquote><div><br>I'm not sure to completely understand the use case and issue!<br>could you please elaborate?<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have also an NetVision-5.01-5.0x-unix.mib file, which doesn't help too.<br></blockquote><div> <br>was it provided with the unit?<br>could you please send the MIB file, provided with your device, in compressed form.<br>
<br>a quick search on the net led me to the Delta MIB:<br><a href="http://www.snmplink.org/cgi-bin/nd/m/Ent/D/Delta%20Electronics%20Group/%5BE.%5D%20Delta%20Electronics,%20Inc.%20-%202254/*25Old3/UPSv4.mib">http://www.snmplink.org/cgi-bin/nd/m/Ent/D/Delta%20Electronics%20Group/%5BE.%5D%20Delta%20Electronics,%20Inc.%20-%202254/*25Old3/UPSv4.mib</a><br>
<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When trying to force netvision driver to snmp-ups command, it fails with:<br></blockquote><div><br>this is a different 'netvision', for Socomec units.<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[root@kvm1 ~]# snmp-ups -a local -x mibs=netvision -DDDDD<br>
<div class="im">Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4)<br>
</div> 0.000000 debug level is '5'<br>
0.000380 SNMP UPS driver : entering upsdrv_initups()<br>
0.000396 SNMP UPS driver : entering nut_snmp_init(snmp-ups)<br>
0.051354 SNMP UPS driver : entering load_mib2nut(netvision)<br>
0.051374 load_mib2nut: trying classic method with 'netvision' mib<br>
0.051383 Entering nut_snmp_get_str()<br>
0.051390 nut_snmp_get(.1.3.6.1.4.1.4555.1.1.1.1.1.1.0)<br>
0.059889 [local] unhandled ASN 0x5 received from .1.3.6.1.4.1.4555.1.1.1.1.1.1.0<br>
0.059933 Unknown mibs value: netvision<br>
<br>
I also tested an older version of SNMP interface for this UPS, but looks<br>
like there are communication problems between UPS and older SNMP interface.<br>
With this new one I can see actual values over web interface, but not using<br>
snmp-ups driver.<br></blockquote><div><br>there is no need to do so.<br>while your UPS also provide data using a proprietary MIB, it also support (partially) the IETF MIB, as seen in your first mail.<br>your unit seems well detected and supported, minus a few things.<br>
<br>your battery.charge is indeed "0 %", but the OID serving it is there, so we have no way to determine that it's buggy.<br>on the UPS shutdown, everything is explained here:<br><a href="http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#UPS_shutdown">http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#UPS_shutdown</a><br>
<br>the conclusion is that, as told by Gregor, your unit should not have any issue with the shutdown.<br>but it's true that the support of your unit with the IETF MIB is not fully optimal.<br>a better support could come from the proprietary MIB, but I've personally no time to devote to this currently.<br>
that said, the task is not that hard, even for a non-programmer.<br>if you to have a run, let me know.<br>otherwise, drop the following output (in compressed form) on the list, for potential future processing:<br>$ snmpwalk -v1 -c XXX 192.168.14.10 .1.3.6.1.4.1.2254.2.4<br>
$ snmpwalk -Os -v1 -c XXX 192.168.14.10 .1.3.6.1.4.1.2254.2.4<br><br>the latter will requires the MIB file to actually display the OID string name.<br><br>cheers,<br>Arnaud<br>-- <br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org" target="_blank">http://www.networkupstools.org</a><br>
Debian Developer - <a href="http://www.debian.org" target="_blank">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.fr" target="_blank">http://arnaud.quette.fr</a><br><br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
SAL<br>
<br>
On Mon, Oct 15, 2012 at 07:27:30AM +0000, Friedrich, Gregor wrote:<br>
> Hello<br>
><br>
> I have the same problem. There are 2 MIBs shipped with the ups (attached). I copied these in /usr/share/netsnmp/mibs folder , but no results.<br>
> The general UPS-status (OL...) is supported... automatic shutdown is working in my test system.<br>
><br>
> Regards Gregor<br>
<div class="HOEnZb"><div class="h5">><br>
> ><br>
> > Hello,<br>
> ><br>
> > I have an NETYS RT 1/1 UPS, which is not fully supported. Starting snmp<br>
> > driver displays:<br>
> ><br>
> > [root@kvm1 ~]# snmp-ups -a local<br>
> > Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4)<br>
> > Duplicate driver instance detected! Terminating other driver!<br>
> > No matching MIB found for sysOID '.1.3.6.1.4.1.2254.2.4'!<br>
> > Please report it to NUT developers, with an 'upsc' output for your device.<br>
> > Going back to the classic MIB detection method.<br>
> > Detected NETYS RT 1/1 UPS on host 192.168.14.10 (mib: ietf 1.4)<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.2.3.0<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.2.6.0<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.3.3.1.4.1<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.3.3.1.5.1<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.4.4.1.4.1<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.5.3.1.3.1<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.5.3.1.4.1<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.5.3.1.5.1<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.6.3.8<br>
> > [local] unhandled ASN 0x6 received from 1.3.6.1.2.1.33.1.7.1.0<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.9.6.0<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.9.7.0<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.9.9.0<br>
> > [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.9.10.0<br>
> ><br>
> > Here is output of upsc command:<br>
> ><br>
> > [root@kvm1 ~]# /etc/init.d/ups start<br>
> > Spustenie ovládača radiča UPS: [ OK ]<br>
> > Spustenie upsd: [ OK ]<br>
> > Spustenie sledovania UPS (server): [ OK ]<br>
> > [root@kvm1 ~]# upsc local<br>
> > battery.charge: 0.00<br>
> > battery.temperature: 33.00<br>
> > battery.voltage: 55.00<br>
> > device.mfr: Delta<br>
> > device.model: NETYS RT 1/1 UPS<br>
> > device.type: ups<br>
> > <a href="http://driver.name" target="_blank">driver.name</a>: snmp-ups<br>
> > driver.parameter.pollinterval: 2<br>
> > driver.parameter.port: 192.168.14.10<br>
> > driver.version: 2.6.4<br>
> > driver.version.internal: 0.66 (mib: ietf 1.4)<br>
> > input.bypass.frequency: 49.90<br>
> > input.bypass.phases: 1.00<br>
> > input.frequency: 49.90<br>
> > input.frequency.nominal: 5.00<br>
> > input.phases: 1.00<br>
> > input.voltage: 2320.00<br>
> > input.voltage.nominal: 230.00<br>
> > output.current: 2.30<br>
> > output.frequency: 49.90<br>
> > output.frequency.nominal: 5.00<br>
> > output.phases: 1.00<br>
> > output.power.nominal: 2200.00<br>
> > output.voltage: 2290.00<br>
> > output.voltage.nominal: 230.00<br>
> > ups.beeper.status: enabled<br>
> > ups.firmware: 1.1<br>
> > ups.firmware.aux: 2.0h<br>
> > ups.load: 300.00<br>
> > ups.mfr: Delta<br>
> > ups.model: NETYS RT 1/1 UPS<br>
> > ups.status: OL<br>
> > ups.test.result: done and passed<br>
> > ups.timer.reboot: 0<br>
> > ups.timer.shutdown: 0<br>
> > ups.timer.start: 0<br>
><br>
><br>
<br>
<br>
<br>
<br>
</div></div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@lists.alioth.debian.org">Nut-upsuser@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser</a></div></div></blockquote></div><br><br clear="all"><br>
<br>