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

[Ben Kamen]

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