User guide

464
pmp-0229 (Mar 2013)
Management Information Base (MIB) Managing the Network From a
Management Station (NMS)
• under iso (1) above:
o standard (0)
o registration-authority (1)
o member-body (2)
o identified-organization (3)
• under identified-organization (3) above:
o dod (6)
o other branches
• under dod (6) above:
o internet (1)
o other branches
• under internet (1) above:
o mgmt (2)
o private (4)
o other branches
• under mgmt (2) above: mib-2 (1) and other branches. (See MIB-II below.)
• under private (4) above: enterprise (1) and other branches. (See Canopy Enterprise MIB
below.)
Beneath this level are non-standard branches that the enterprise may define.
Thus, the path to an object that is managed under MIB-II begins with the decimal string
1.3.6.1.2.1 and ends with the object identifier and instance(s), and the path to an object that is
managed under the Canopy Enterprise MIB begins with 1.3.6.1.4.1, and ends with the object
identifier and instance(s).
Object Instances
An object in the MIB can have either only a single instance or multiple instances, as follows:
• a scalar object has only a single instance. A reference to this instance is designated by .0,
following the object identifier.
• a tabular object has multiple instances that are related to each other. Tables in the MIB
associate these instances. References to these instances typically are designated by .1, .2,
and so forth, following the object identifier.
Management Information Base Systems and Interface
(MIB-II)
The standard MIB-II (Management Information Base systems and interface) objects are
programmed into the modules. To read this MIB, see Management Information Base for Network
Management of TCP/IP-based Internets: MIB II, RFC 1213 at
http://www.faqs.org/rfcs/rfc1213.html
.