Nut upsdev - Feb 2011 - Getting started generating new MIB-to-NUT mapping for unsupported interface

I'm following advice from Arjen de Korte and Charles Lepple (see
http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-January/005829.html).

I added a full update on the specifics of my situation:
http://lists.alioth.debian.org/pipermail/nut-upsdev/2011-February/005255.html

Would appreciate guidance on getting started generating a MIB-to-NUT
mapping (tools, etc):

OS: CentOS 5.5

NUT version 2.6.0

Thanks for any advice or guidance,

-- 
Philip J. Tait, Software Engineer (FMOS,HSC)
http://subarutelescope.org

Citeren Philip Tait <philip op naoj.org>:
> Would appreciate guidance on getting started generating a MIB-to-NUT
> mapping (tools, etc):
>
> OS: CentOS 5.5
>
> NUT version 2.6.0
Assuming that you're able to successfully build NUT from sources,  
you're all set. Unlike USB HID PDC subdrivers, we have no automated  
tools available to generate a OID to NUT mapping. So basically what  
you need to do is create this mapping yourself. The 'ietf-mib.[ch]'  
files in the drivers/ directory of the sources should provide you with  
a starting point. With a bit of luck, you might be able to get your  
device supported by just modifying the entry point.

Best regards, Arjen
-- 
Please keep list traffic on the list (off-list replies will be rejected)

2011/2/11 Philip Tait <philip at naoj.org>
> I'm following advice from Arjen de Korte and Charles Lepple (see
>
>
http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-January/005829.html
> ).
>
> I added a full update on the specifics of my situation:
>
>
http://lists.alioth.debian.org/pipermail/nut-upsdev/2011-February/005255.html
>
> Would appreciate guidance on getting started generating a MIB-to-NUT
> mapping (tools, etc):
>
> OS: CentOS 5.5
>
> NUT version 2.6.0
>
> Thanks for any advice or guidance,
>
Arjen already pointed out drivers/ietf-mib.{c,h}
Other *-mib.ch files from the same directory may help too.

Now, you will also need a numeric walk, since we don't use textual names,
which require to have the .MIB file on the computer (which is a dependency
with no added value).

So, walk again using:
$ snmpwalk -On -c public -v 1 ups3 .1.3.6.1.4.1.476.1.1


2 things are then required:
- knowing OIDs information, ie the meaning and unit, which can be checked
using a MIB GUI
- knowing the NUT data on which this OID maps. Note that some OIDs may not
map on NUT data.
All the existing NUT variables are there:
http://www.networkupstools.org/docs/developer-guide.chunked/apa.html

As an example, here is the mapping for the first OIDs:

LIEBERT-UPS-MIB::lcUpsIdentManufacturer.0 = STRING: "Liebert"       
=>
{device,ups}.mfr
LIEBERT-UPS-MIB::lcUpsIdentModel.0 = STRING: "AP341/342"           
=>
{device,ups}.model
LIEBERT-UPS-MIB::lcUpsIdentSoftwareVersion.0 = STRING: "2.5.3A"       
=>
{device,ups}.mfr
LIEBERT-UPS-MIB::lcUpsIdentSpecific.0 = OID: LIEBERT-UPS-MIB::luSeries300
LIEBERT-UPS-MIB::lcUpsBatTimeRemaining.0 = INTEGER: 65535            =>
battery.runtime
LIEBERT-UPS-MIB::lcUpsBatVoltage.0 = INTEGER: 406                    =>
battery.voltage

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20110215/2ca1b674/attachment.htm>