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 Kozierok Author 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.

The TCP/IP Guide  9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)       9  TCP/IP Network Configuration and Management Protocols (BOOTP, DHCP, SNMP and RMON)            9  TCP/IP Network Management Framework and Protocols (SNMP and RMON)                 9  TCP/IP Structure of Management Information (SMI) and Management Information Bases (MIBs)

TCP/IP Structure of Management Information (SMI) and Management Information Bases (MIBs) Overview 1 2 3 4 TCP/IP MIB Object Descriptors and Identifiers and the Object Name Hierarchy and Name Notation

Syntax

An object’s Syntax defines its data type and the structure that describes it. This attribute of an MIB object is very important because it defines the data type of information that the object contains. There are two basic categories of data types allowed:

• Regular Data Types: These are single pieces of information, of the type we are used to dealing with on a regular basis; examples would be integers or strings. These are called base types in SMIv2. SMIv1 differentiates between primitive types like integers defined in ASN.1, and defined types that are special forms of primitive types that are still single pieces of information but with certain special meaning attached to how they are used. SMIv2 doesn't use those two terms.
  
  
• Tabular Data: A collection of multiple data elements. This may take the form of a list of base types or a table of base types. For example, a table of integers could be constructed to represent a set of values. In SMIv1 these are called constructor types; in SMIv2 they are conceptual tables. They can be accessed using special SNMP mechanisms designed for reading tables. See the topic on SNMP table traversal for more on tables.

This field defines the ways that an SNMP application will normally use the object. In SMIv1, there are four different possible values: read-only, read-write, write-only, and not-accessible.

In SMIv2 there are five values, which are described as a hierarchy of sorts. SMIv2 calls this characteristic Max-Access (maximum access) to make it explicit that higher access levels include the lower levels as well. For example, an object with read-create access can also be used in any of the modes “below it”, such as read-write, but not vice versa. Table 205 shows the five SMIv2 access values, in decreasing order of access. Note that write-only has been removed in SMIv2:

Indicates the currency of the object definition. In SMIv1 there are three values: mandatory, optional and obsolete. In SMIv2, the first two are combined into simply current, meaning a current definition. The value obsolete is retained, and deprecated is added, meaning the definition is obsolete but maintained for compatibility.

A textual description of the object.

TCP/IP Structure of Management Information (SMI) and Management Information Bases (MIBs) Overview 1 2 3 4 TCP/IP MIB Object Descriptors and Identifiers and the Object Name Hierarchy and Name Notation