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