HOOD, Andy writes:
Another idea that came to my mind, is to add a much more verbose description to errors, since for errors like "index element `%s::%s' of row `%s' should but cannot have a size restriction" I would wonder if people get this error and do NOT ask what it means. :-)
Andy> If you could persuade Cisco, HP, IBM, Intel, etc. to put range Andy> restrictions in MIBs I might stop suppressing that warning.
You can not put a size constraints on OIDs and this is why the warning quoted above sounds so esoteric.
Andy> Are some of the warnings not relevant to SMIv1 MIBs, or SMIv2 Andy> ones converted to SMIv2 by, say, smidump?
It depends. ;-)
Andy> While we're here, what is the correct way to do these (taken Andy> from INTELCORPORATIONBASEBOARD-MIB which is SMIv1):
[...]
I believe (and libsmi implements it that way) that you can not ship 64 bit INTEGER in SNMPv1 or that you can define 64 bit INTEGER data types in SMIv1. (Although people sometimes argue about this.)
Andy> The other way I've seen this done would use INTEGER instead of Andy> DmiComponentIndex as the index, and that causes most of the same Andy> errors.
/js