MIB Smithy comes with with over 200 IETF and IANA standard MIB modules pre-installed to help get you started and familiarize yourself with the application. IETF modules are installed in the mibs/IETF/
directory, and are also available in RFC document form from www.ietf.org. IANA modules are installed in the mibs/IANA/
directory, and are also available from www.iana.org.
Listed below are some of the more important modules that you're likely to need to get started in your MIB development work. Some of these are also installed in the mibs/
directory. Any MIB files located in this directory are automatically loaded on startup, so you can customize your default MIB library as desired. For instance, you may want to add a MIB file to this directory that defines the common records (such as your enterprise OID assignment) used throughout your products.
Defines the main branches of the OBJECT IDENTIFIER tree used by SNMP, the primary MACRO definitions (MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE and OBJECT-IDENTITY), as well as the core SNMP data types (Integer32, IpAddress, Counter32, Gauge32, Unsigned32, TimeTicks, Opaque, Counter64). All SMIv2 modules are required to import from this module, if for no other reason than the requirement that all SMIv2 modules contain exactly one MODULE-IDENTITY definition.
Defines a common set of TEXTUAL-CONVENTIONs (derived data types) used by most SMIv2 MIBs, as well as the TEXTUAL-CONVENTION MACRO its self. All SMIv2 MIBs defining TEXTUAL-CONVENTIONs or using one of these common types (DisplayString, PhysAddress, MacAddress, TruthValue, TestAndIncr, AutonomousType, InstancePointer, VariablePointer, RowPointer, RowStatus, TimeStamp, TimeInterval, DateAndTime, StorageType, TDomain and TAddress) are required to import from this module. Note that while SMIv2 allows derived data types to be defined using the ASN.1 Type Assignment form (TypeReference ::= Type), it is discouraged.
Defines the IANAifType TEXTUAL-CONVENTION, which contains the registered interface types used by the ifType object of MIB-II. Most SNMP agents implement at least the Interfaces Table of MIB-II, and therefore also the ifType object. New interface types are defined periodically, and the version installed with MIB Smithy may lag behind from time to time. The latest version of this MIB can always be downloaded from the IANA (Internet Assigned Numbers Authority web site.
The MIB module for managing IP and ICMP implementations, but excluding their management of IP routes. This module is part of MIB-II, and obsoletes the version defined by RFC 1213.
The MIB module for managing TCP implementations. This module is part of MIB-II, and obsoletes the version defined by RFC 1213.
The MIB module for managing UDP implementations. This module is part of MIB-II, and obsoletes the version defined by RFC 1213.
This MIB module defines objects to help support coexistence between SNMPv1, SNMPv2c, and SNMPv3.
The MIB module to describe generic objects for network interface sub-layers. This MIB is an updated version of MIB-II's ifTable that obsoletes the version defined by RFC 1213 and incorporates the extensions defined in RFC 1229.
The SNMP Management Architecture MIB. Obsoletes RFC 2571.
The MIB for Message Processing and Dispatching. Obsoletes RFC 2572.
These MIB modules define MIB objects that provide mechanisms to remotely configure the parameters used by an SNMP entity for the generation of SNMP messages. Obsoletes RFC 2573.
The management information definitions for the User-based Security Model used by SNMPv3. Obsoletes RFC 2574.
The management information definitions for the View-based Access Control Model for SNMP.
The MIB module for SNMP entities. Contains definitions for the system group, among other things, which are required for every SNMP implementation.