> I am having a trap defined as follows in my MIB:
[snip]
> All the four objects used above are defined in the same MIB as
> not-accessible since they are meant to be sent only along with traps.
In which case they should be defined as "accessible-for-notify"
rather than "not-accessible".
(Most tools probably won't care, but you might as well do it right).
Otherwise I'd agree with Wes' suggestion - omit the sometimes-optional
objects from the OBJECTS list, and document the usage in the DESCRIPTION
clause(s).
> can i achieve this using this single MIB either by defining objectC and
> objectD's status as optional instead of current
Please note that the only valid values for CURRENT in (SMIv2) MIBs are
"current", "deprecated" and "obsolete". "optional" is not an option :-)
It was part of the old SMIv1 format, but SMIv2 has been out for eight
years now, so there is no real excuse for continuing to use SMIv1.
Dave
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
