<p>Hi Arnaud,</p>
<p>Sure I am willing to take this up. Will need guidance on how to get started as I am new to doing stuff like SNMP walks.<br>
Just lead the way :) .<br>
</p>
<div class="gmail_quote">On Mar 23, 2011 5:29 PM, "Arnaud Quette" <<a href="mailto:aquette.dev@gmail.com">aquette.dev@gmail.com</a>> wrote:<br type="attribution">> Hi John,<br>> <br>> 2011/3/16 John Huong <<a href="mailto:jahuong@gmail.com">jahuong@gmail.com</a>><br>
> <br>>> Hi,<br>>><br>>> Just started using NUT with a Liebert PSI-XR 3000 with an Intellislot web<br>>> card.<br>>><br>>> It seems I can't get it to run properly.<br>>><br>
>> I am using NUT 2.6.0 built from source on Ubuntu 8.0.4 .<br>>><br>>> My build parameters are :<br>>><br>>> ./configure --enable-strip<br>>> --with-linux-hiddev=/usr/include/linux/hiddev.h<br>
>> --with-udev-dir=/lib/udev \<br>>> --prefix=/usr \<br>>> --exec-prefix=/ \<br>>> --sysconfdir=/etc/nut \<br>>> --mandir=/usr/share/man \<br>>> --libdir=/lib \<br>
>> --includedir=/usr/include \<br>>> --without-ssl \<br>>> --with-dev \<br>>> --enable-static \<br>>> --with-statepath=/var/run/nut \<br>
>> --with-altpidpath=/var/run/nut \<br>>> --with-drvpath=/lib/nut \<br>>> --with-htmlpath=/usr/share/nut/www \<br>>> --with-pidpath=/var/run/nut \<br>>> --datadir=/usr/share/nut \<br>
>> --with-pkgconfig-dir=/usr/lib/pkgconfig \<br>>> --with-user=nut --with-group=nut<br>>><br>>><br>>> I get this when I run upsdrvctl start<br>>><br>>> Detected LiebertPSI on host 192.168.0.11 (mib: ietf 1.3)<br>
>> [liebertpsiweb] unhandled ASN 0x6 recieved from 1.3.6.1.2.1.33.1.7.1.0<br>>><br>>> Then when I run /etc/init.d/nut I get<br>>><br>>> * Starting Network UPS Tools [<br>
>> OK ]<br>>><br>>> Broadcast Message from <a href="mailto:nut@mail.sop.com.my">nut@mail.sop.com.my</a><br>>> (somewhere) at 1:02 ...<br>>><br>>> Communications with UPS liebertpsiweb@localhost lost<br>
>><br>>> Running upsc liebertpsiweb@localhost gets me :<br>>><br>>> battery.charge: 100.00<br>>> battery.current: 0.00<br>>> battery.runtime: 0.00<br>>> battery.runtime.low: 120.00<br>
>> battery.temperature: 30.00<br>>> battery.voltage: 55.00<br>>> beeper.status: enabled<br>>> device.mfr: Emerson Network Power<br>>> device.model: LiebertPSI<br>>> device.type: ups<br>
>> <a href="http://driver.name">driver.name</a>: snmp-ups<br>>> driver.parameter.mibs: auto<br>>> driver.parameter.pollinterval: 2<br>>> driver.parameter.port: 192.168.0.11<br>>> driver.version: 2.6.0<br>
>> driver.version.internal: 0.50 (mib: ietf 1.3)<br>>> input.bypass.phases: 0.00<br>>> input.current: 0.00<br>>> input.frequency: 50.00<br>>> input.frequency.nominal: 50.00<br>>> input.phases: 1.00<br>
>> input.realpower: 0.00<br>>> input.transfer.high: 0.00<br>>> input.transfer.low: 0.00<br>>> input.voltage: 247.00<br>>> input.voltage.nominal: 2300.00<br>>> output.current: 0.00<br>>> output.frequency: 50.00<br>
>> output.frequency.nominal: 50.00<br>>> output.phases: 1.00<br>>> output.power.nominal: 0.00<br>>> output.realpower: 0.00<br>>> output.realpower.nominal: 0.00<br>>> output.voltage: 249.00<br>
>> output.voltage.nominal: 2300.00<br>>> ups.firmware: EX000842<br>>> ups.firmware.aux: 2.39.CP504.ABE.00<br>>> ups.load: 17.00<br>>> ups.mfr: Emerson Network Power<br>>> ups.model: LiebertPSI<br>
>> ups.start.auto: no<br>>> ups.status:<br>>> ups.test.result: done and passed<br>>> ups.timer.reboot: -1<br>>> ups.timer.shutdown: -1<br>>> ups.timer.start: -1<br>>><br>>> What can I do or is this particular model not supported?<br>
>><br>> <br>> the support for this unit, and more generally Liebert SNMP support, doesn't<br>> yet exist.<br>> <br>> the best for you is to check the MIB(s) supported, since Liebert may provide<br>
> its own, with a basic RFC 1628 (aka IETF MIB) supplement.<br>> <br>> if you're willing to work on this, we will help you.<br>> The idea is to create a lookup table between SNMP data and values to the NUT<br>
> ones, as done for example here (look for "snmp_info_t"):<br>> <a href="http://svn.debian.org/wsvn/nut/trunk/drivers/eaton-mib.c">http://svn.debian.org/wsvn/nut/trunk/drivers/eaton-mib.c</a><br>> <br>> So, send us back an SNMP walk of the device, and start checking for creating<br>
> this mapping.<br>> Note that you may want to work with Philip Tait<br>> <a href="http://lists.alioth.debian.org/pipermail/nut-upsdev/2011-February/005255.html">http://lists.alioth.debian.org/pipermail/nut-upsdev/2011-February/005255.html</a><br>
> <a href="http://lists.alioth.debian.org/pipermail/nut-upsdev/2011-February/005263.html">http://lists.alioth.debian.org/pipermail/nut-upsdev/2011-February/005263.html</a><br>> <br>> Have a special look at the 2nd thread!<br>
> <br>> cheers,<br>> Arnaud<br>> -- <br>> Linux / Unix Expert R&D - Eaton - <a href="http://powerquality.eaton.com">http://powerquality.eaton.com</a><br>> Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>
> Debian Developer - <a href="http://www.debian.org">http://www.debian.org</a><br>> Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br></div>