Nut upsdev - Nov 2017 - Updating snmp-mib.c with new Cyberpower v2.0 MIB

On 11/02/2017 01:52 AM, Jim Klimov wrote:
>
> I believe the main reason for a new set of .c/.h files here would be if the
new MIB is defined in a separate subtree. The top-level mapping binds the vendor
entry OIDs (often "hidden" so one has to know where to poke). It may
also be higher in the list of snmp-ups.h, in case the device also serves the
older MIB but you'd prefer the newer (e.g. common standard IETF one is
always last).
>
> If both the older and newer data are in the same vendor tree, e.g. new leaf
points are added, you'd extend the existing table.
I'll have to compare...? working on the basics at the moment.

Once I get the new one filled in -- I'll check it to the old 0.1 version
mib.c

Thanks,

?-Ben

Chugging along...

Question for the gang --

CyberPower lists other items in their MIB for controlling PD units and some
other things.

Does NUT support all that and should I make an effort to get all that in or
should we skip for now and get UPS primary ingredients inserted and tested?

just wondering,

?-Ben

-- 
Ben Kamen - O.D.T., S.P.
----------------------------------------------------------------------
Email: ben AT benkamen DOT net                 http://www.benkamen.net
Cell:  224.619.9006                http://www.linkedin.com/in/benkamen
-                                                                    -
NOTICE: All legal disclaimers sent to benkamen.net
or any of its affiliated domains are rendered null and void on 
receipt of communications and will be handled/considered as such.

Hey all,

sorry for my absence  -- it's been a crazy busy time since my last email.

I did I think most of the work for the Cyberpower v2.0 SNMP driver... I'm
looking to get back into finishing this up...

Do any of the devs want to take a look so far to see what else I'm missing?

  -Ben