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.
SNMP Protocol Information Notification Using Trap(v2) and InformRequest Messages
(Page 2 of 2)
Use of the SNMPv2 InformRequest Message
SNMPv2 also incorporates a second
notification message type: InformRequest-PDU. This type of message
is not the same as a trap, but it is related to traps for two reasons.
First, both message types are used to communicate information without
the recipient initiating the process, and second, the two messages are
sometimes used in conjunction.
The purpose of the InformRequest-PDU
is actually to facilitate the communication of information between network
management stations. The SNMP Manager on one NMS can choose to inform
another of some piece of information by sending an InformRequest-PDU
to that other SNMP Manager. The receiving manager then replies back
with a Response-PDU to the one that sent the InformRequest-PDU,
confirming receipt of the inform message.
A common way that this message is
used is to spread the news when a trap occurs. Suppose a
device experiences a power failure, which results in a Trapv2-PDU
being sent to NMS #1. The network administrator may want to set up NMS
#1 so that receipt of particular traps causes the information in the
trap to be forwarded to another. The InformRequest-PDU
would be used to carry that information from NMS #1 to say, NMS #2.
Key Concept: SNMP managed devices can inform a network management station of an important occurrence by sending it a Trap-PDU or Trapv2-PDU message. Network administrators determine the circumstances under which one of these messages should be transmitted. SNMPv2 adds to this capability the InformRequest-PDU message, which can be used to propagate information about an event between management stations.
|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!|
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.