[Nut-upsdev] Updating snmp-mib.c with new Cyberpower v2.0 MIB

Jim Klimov jimklimov at cos.ru
Tue Oct 31 06:13:53 UTC 2017

On October 31, 2017 2:32:36 AM GMT+01:00, Ben Kamen <ben at benkamen.net> wrote:
>Hey all,
> I'm feeling spunky... and want to update nut to handle the new v2.0
>MIB from CyberPower.
>I've looked at the cyberpower v0.1 .c/.h and being new to working on
>nut to this level -- anything anyone has to offer on adding code
>besides the obvious?
>like: should the 0.1 and 2.0 coexist somehow? (maybe different files)
>(also, is there a list of all the parms I can match up from the MIB? --
>i.e. the APC MIB.c is pretty comprehensive, I suppose I could use that
>as a model. I haven't looked at all the SNMP .C files yet though. Will
>do that later tonight and get busy.)
> -Ben
>Nut-upsdev mailing list
>Nut-upsdev at lists.alioth.debian.org


If the new data is in a separate OID tree, it can quite be a new MIB. Otherwise you can use the UNIQUE flag and set the preferred (e.g. newer, more precise) source for a value first in the list of same-named mappings in existing file - if there's a hit on an actual device, it will be used and not iterated onwards. The flag is not yet supported for all cases though (e.g. daisy-chained devices), so some other combinations would set the preferred value mapping last in list.

I'm on the road now so can't point exactly, but there's a text file in docs/ (?)  which lists and describes the mappings which drivers should share (for any media and vendor-protocol -- e.g. networked snmp in this case).

Hope this helps,

Typos courtesy of K-9 Mail on my Android

More information about the Nut-upsdev mailing list