| 
 | Please Whitelist This Site?I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
 If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads. If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK. Thanks for your understanding! Sincerely, Charles KozierokAuthor and Publisher, The TCP/IP Guide
 | 
 
 
   
  
    | 
  
| NOTE: Using software to mass-download the site degrades the server and is prohibited. If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
 |  |  | 
| 
 
 
 | 
 
 TCP/IP MIB Modules and Object Groups
 (Page 1 of 4)
 The Management 
Information Base (MIB) contains the collection 
of MIB objects that describe the characteristics of a device using the 
Internet 
Standard Management Framework (SNMP Framework). 
When SNMP was first created, there were not that many objects in the 
MIB. Furthermore, they were mostly generic objects that 
applied fairly universally to TCP/IP devices as a whole. In fact, most 
of the MIB objects were variables related to the operation of TCP/IP 
protocols such as IP, TCP and ICMP. For this reason, at first, a single 
document defined the Management Information Base (MIB) for 
SNMP. The first of these documents was RFC 1066, part of the initial 
SNMPv1 specification. It was then revised in RFC 1156. In RFC 1158, 
a second version of the MIB, MIB II, was defined, which was essentially 
the same but made a few changes.The Organization of MIB Objects into Object Groups The number of MIB objects defined 
in these standards was relatively small. However, there were still several 
dozen of them, and it was recognized from the start that more would 
be created in time. To help organize the objects in a logical way, they 
were arranged into object groups. These groups serve the purpose 
of separating the objects and defining how they should be given object 
identifiers in the overall object 
name hierarchy. Each group has associated with it 
three important pieces of information: 
Group Name: A name that is used as a text 
label in the object identification tree we saw in the previous topic. 
These objects are all located within the iso.org.dod.internet.mgmt.mib 
subtree. So for example, the group system would be iso.org.dod.internet.mgmt.mib.system.
 
Group Number: A number corresponding to 
the group name used for making numeric identifiers from the object name 
tree. For example, the group system has the number 1, and so 
the group's object identifier is 1.3.6.1.2.1.1. All objects in that 
group will be under that tree; for example, sysUpTime is 1.3.6.1.2.1.1.3. 
 
Group Code: A text label that may be the 
same as the group name or may be an abbreviation. It is used as a prefix 
in making object descriptors (the text names of objects). For example, 
for the group system the code is sys, and so an object 
in this group is sysUpTime.
 
 
 | 
 | If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |  
|  | 
 | 
 
 
 Home - 
Table Of Contents - Contact Us
 
 The TCP/IP Guide (http://www.TCPIPGuide.com)
 Version 3.0 - Version Date: September 20, 2005
 
 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
 Not responsible for any loss resulting from the use of this site.
 |