Advertisement
ccitt (0)
...
standard (0)
registration-
authority (1)
directory (1)
mgmt (2)
mib-2 (1)
...
...
...
DECnet (1)
XNS (2)
...
...
As shown in Figure 3, top-level MIB object IDs belong to different standards organizations while
low-level object IDs are allocated by associated organizations. Vendors define private branches that
include managed objects for products. Non standard MIBs are typically in the experimental branch.
A managed object has these unique identities:
The object name—For example, iso.identified-organization.dod.internet.private.enterprise.cisco.
temporary variables.AppleTalk.atInput
or
The equivalent object descriptor—For example, 1.3.6.1.4.1.9.3.3.1.
iso (1)
iso-ccitt (2)
member-
body (2)
internet (1)
experimental (3)
private (4)
...
...
...
enterprise (1)
...
...
cisco (9)
...
temporary
variables (3)
Apple Talk (3)
...
...
atInput (1)
atLocal (2)
atBcastin (3)
atForward (4)
...
...
identified-
organization (3)
dod (6)
...
security (5)
...
...
...
Novell (3)
VINES (4)
...
...
...
...
...
snmpV2 (6)
...
Chassis (5)
...
...
Advertisement
