 |
|
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
|
|
|
Custom Search
|
|
SNMP Protocol Overview, History and General Concepts
(Page 2 of 2)
SNMPv2 and the Division of SNMP into Protocol Operations and Transport Mappings
When SNMPv2 was created, the single document describing the SNMP Protocol was split into two standards, to make the protocol more modular and better reflective of the layers used in internetworks. This division has been maintained in SNMPv3 as well. The two types of documents specify the following:
- Protocol Operations: The first document
of the pair describes the actual mechanics by which MIB objects are
moved between SNMP devices using particular SNMP message types. In SNMPv3
it is RFC 3416, Version 2 of the Protocol Operations for the Simple
Network Management Protocol (SNMP). When people talk about just
“the SNMP standard”, this is the document they usually mean.
- Transport Mappings: The second document details how the SNMP protocol operations described in the first standard above can be transported over a variety of different protocol suites. By using the correct mapping, SNMP operations can be carried out using lower-layer technologies other than IP. This standard is represented in SNMPv3 by RFC 3417, Transport Mappings for the Simple Network Management Protocol (SNMP).
I discuss transport mappings in a little more detail in the topic on SNMP messaging, but since IP/UDP is by far the most common transport mechanism, there isn't a great deal to say about that aspect of the SNMP Protocol. The focus of most of our look at SNMP will concentrate on SNMP protocol operations: what messages are used, how they are structured and how they are exchanged. In examining these messages we will see the two main ways that information exchanges occur in SNMP (by polling and by interrupt) and also discover how the SNMP Protocol works with MIB objects.
|
Key Concept: The actual mechanism used to communicate management information between network management stations and managed devices is called the Simple Network Management Protocol, which may be called the SNMP Protocol to differentiate it from the SNMP Framework. It consists of a number of protocol operations that describe the actual message exchanges that take place between devices, and a set of transport mappings that define how these messages are carried over various types of internetworks. The Internet Protocol is the most common transport mapping used for SNMP.
|
| |||||||||||||||||||
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.