| 
 | 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 Objects, Object Characteristics and Object Types
 (Page 4 of 4)
 
 SMIv2 Textual Conventions In addition to these types, other 
defined types are also created to again, indicate more specific semantics 
for a particular data type. These are called textual conventions 
and are described in RFC 2579 for SMIv2. For example, a type called 
TimeStamp is defined which is the same as TimeTicks. However, 
seeing an object using the former rather than the latter makes it more 
clear that the variable is representing a particular time stamp value. 
Another is called TimeInterval, which is also just an integer 
underneath its name, but conveys a different interpreted meaning.Example SMIv2 Object Definition If all of the above seemed very confusing 
to you, note that this topic is in fact a significant simplification 
of SMI's object definitions. SNMP is so much fun! If an example will 
help, check out Table 207, 
which shows an object definition from RFC 3418, using SMIv2. 
  Table 207: Example SNMP SMIv2 Object Definition 
| sysLocation 
OBJECT-TYPESYNTAX DisplayString (SIZE (0..255))
 MAX-ACCESS read-write
 STATUS current
 DESCRIPTION "The physical location of this node (e.g., 'telephone closet, 
3rd floor'). If the location is unknown, the value is the zero-length 
string."
 ::= { system 6 }
 | 
 Note that DisplayString 
is a textual convention for a displayed text string. The last part, 
{ system 6 }, will be explained in the next 
topic. 
 
 | 
 | 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.
 |