Re: MIB

[Dave S. <D.T...@li...>]

2009/3/12 Tanisha Kashyap <tan...@ar...>:
> Also I have some doubt about the IMPORTS clause i.e. what should be imported?

Short answer:  everything you refer to in the MIB file.

Longer answer:
  There are two general sets of definition that you would typically IMPORT.
The first are "standard" definitions used in the basic structure of the MIB

The core of this will be:
     OBJECT-GROUP FROM SNMPv2-CONF

     OBJECT-TYPE, MODULE-IDENTITY FROM SNMPv2-SMI

plus any standard (but non-core) syntax types that you will be using
(Integer32, Unsigned32, etc) - also from SNMPv2-SMI

If you're using any of the structured Textual Conventions
(DisplayString, RowStatus, etc), then you should also import
these from SNMPv2-TC and/or SNMP-FRAMEWORK-MIB.

And if you are defining traps, then you should import
NOTIFICATION-TYPE from SNMPv2-SMI and
NOTIFICATION-GROUP from SNMPv2-CONF


The second set of definitions to IMPORT are those that specify how
your MIB fits into the overall MIB tree.   This will typically be the object
used in the definition of the MODULE-IDENTITY clause, plus any other
"cross references" to other MIBs (such as private syntax types,
external index objects, etc)

The best approach is probably to write your MIB, then put it through
something like "smilint".   Fix any problems that this reports, and
keep doing this until smilint reports it clean.


Dave