This is a discussion on Re: MIB for SNMPv3 within the SNMP Coders forums, part of the Networking and Network Related category; Dave Shield wrote: -- snippage has occurred -- > There is *NO* good reason to be using SMIv1 to define *ANY* new ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Dave Shield wrote:
-- snippage has occurred -- > There is *NO* good reason to be using SMIv1 to define *ANY* new MIB. > There hasn't been for years. SMIv1 is obsolete, past it, defunct, > dead, buried (I wish!), irrelevant. Life has moved on, it has earned > its retirement, Do Not Use It! > Do I make myself clear? :-) In the best of all possible worlds you would be correct. In the real world which most of us inhabit, we have tools and/or devices which do not support SNMPv2 for one or more of traps and get/set. (e.g. device does, management agent does not.) I have to convert SNMPv2 MIBs into SNMPv1 to keep those dinosaurs happy. Fortunately libsmi makes this easy. -- There's no point in being grown up if you can't be childish sometimes. -- Dr. Who ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/...et-snmp-coders |