SNMP Subagent Programmer's Guide

Writing and Compiling MIBs
SNMP Subagent Programmer’s Guide—119728 3-5
Encoding MIBs
object-name-sequence
consists of a list of subtrees, a space, and a number identifying the object. The
subtrees are listed from highest to lowest in the SNMP name hierarchy, ending with
the subtree in which the object resides. Format an object-name-sequence as follows:
{ iso(1) org(3) dod(6) internet(1) 4 }
Examples
The MIB definition for the Hello World sample program contains these object name
definitions; the subtree in which the Hello World MIB, hello, resides is one of several
registered to PEER Networks, Inc.:
private OBJECT IDENTIFIER ::= { iso(1) org(3) dod(6) internet(1) 4 }
enterprises OBJECT IDENTIFIER ::= { private 1 }
peer OBJECT IDENTIFIER ::= { enterprises 442)
peer-products OBJECT IDENTIFIER ::= { peer 1 }
peer-demos OBJECT IDENTIFIER ::= { peer 2 }
hello OBJECT IDENTIFIER ::= { peer-demos 1 }
MIB objects defined by Tandem all reside in the tandem subtree, which has been
assigned the number 169. For example, object name definitions for the Tandem EMS
Trap MIB look like this:
iso OBJECT IDENTIFIER ::= { 1 }
org OBJECT IDENTIFIER ::= { iso 3 }
dod OBJECT IDENTIFIER ::= { org 6 }
internet OBJECT IDENTIFIER ::= { dod 1 }
private OBJECT IDENTIFIER ::= { internet 4 }
enterprises OBJECT IDENTIFIER ::= { private 1 }
tandem OBJECT IDENTIFIER ::= { enterprises 169 }
nonstopsystems OBJECT IDENTIFIER ::= { tandem 3 }
ems OBJECT IDENTIFIER ::= { nonstopsystems 12 }
MIB Information Resources
When you define a MIB, it should reside in a hierarchy beneath your own subtree in the
“enterprises” subtree. To acquire a subtree of your own, contact the IANA at:
Internet Assigned Numbers Authority
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
United States of America
e-mail: [e-mail]
Once you have an enterprise subtree of your own, you can organize nodes beneath it
however you wish.