On Thu, 2005-10-20 at 16:58 +0530, Nithin wrote:
> We have written MIB by using SMIv1.
Why?
SMIv1 has been obsolete for over six years!
> We want to write MIB for SNMPv3
> for that which version of SMI we have to use and what the changes to be
> made in MIB file
None.
The version of SMI used to define a MIB is completely independent
from the version of SNMP used to retrieve the values from it.
If your MIB is written in SMIv2, then you can use SNMPv1(*),
SNMPv2c or SNMPv3 to query it.
(*) apart from Counter64 objects
If you are still living in the dark ages, and your MIB is written
in SMIv1, then you can use SNMPv1, SNMPv2c or SNMPv3 to query it.
The version of SMI chosen does not affect the version of SNMP.
It's like saying
"I want to drive on a road that's only just been built.
How new a car do I need to buy, in order to use it?"
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? :-)
Dave
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
