The .mib file contains a set of definitions for each managed object. It defines the data type of the object, as well as the current validity of the object. The .mib file also provides a brief description of the purpose of each MIB object. The role of the .mib file can be compared to the role of a .def file in a DLL.
TOASTER-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212
DisplayString
FROM RFC-1213;
epilogue OBJECT IDENTIFIER ::= {enterprises 12}
toaster OBJECT IDENTIFIER ::= {epilogue 2}
toasterManufacturer OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The name of the toaster's manufacturer. For instance,
Microsoft Toaster."
::= {toaster 1}
toasterModelNumber OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The name of the toaster's model. For instance,
Radiant Automatic."
::= {toaster 2}
toasterControl OBJECT-TYPE
SYNTAX INTEGER {up (1), down (2)}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable controls the current state of the toaster. To
begin toasting, set it to down (2). To abort toasting
(perhaps in the event of an emergency), set it to up (2)."
::= {toaster 3}
toasterDoneness OBJECT-TYPE
SYNTAX INTEGER (1..10)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable controls how well-done is the ensuing toast. It
should be on a scale of 1 to 10. Toast made at 10 generally
is considered unfit for human consumption;
toast made at 1 is warmed lightly."
::= {toaster 4}
toasterToastType OBJECT-TYPE
SYNTAX INTEGER {
white-bread (1),
wheat-bread (2),
wonder-bread (3),
frozen-waffle (4),
frozen-bagel (5),
hash-brown (6),
other (7)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable informs the toaster of the type of material that
is being toasted. The toaster uses this information, combined
with toasterToastDoneness, to compute for how long the material
must be toasted to achieve the required doneness."
::= {toaster 5}
END
