RE: A flurry of notifications at startup
"Mike Ayers" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <83E753BE7B6A324ABB336245BAF1DAAC08A1A8E1@mailserver.metatv-ds.metatv.com> |
> From: [email protected] > [mailto:[email protected]] On > Behalf Of dan anderson > If you unplug the cable, the message will not be relayed to NMS unless > you're using wireless. Or, I suppose, the Pigeon Protocol. SNMP was designed for exactly this. Well, not necessarily pigeons, although they'd work, but the use of secondary channels to carry state information, such as loss of the link which delivers most of the other state change information. So you are correct, but throw in ATM, dialup modem, USB cable, etc. et al., and the idea of getting that information becomes more practical than you may have realized. > 2008/5/30 Murilo Fujita <[email protected]>: > > Hi! > > Sorry my last e-mail. Let me try again: > > I want to know if the trap was sent by the agent to the NMS. Source-of-trap is something that has always caused fits. It was not built into SNMP, and explaining why can be difficult. For now, let's just say that there is no universal way to identify a source. > > My NMS is Ubuntu Linux and my agent is windows > > (net-snmp-5.4.1-3.win32.exe). > > I would like an idea about snmptrap. For example, if I > unplug the UTP > > cable from agent, how the message is relay to NMS? Generally, the agent keeps a protocol, notification type (trap or inform), and address information for each target, then attempts to send the notification directly to the target. UDP based notifications may not arrive. Informs must be acknowledged, or they will be considered unacknowledged (what this means depends on agent configuration, etc., and is an advanced topic). > > I think after the answer it´ll become easier to > understand how the > > snmptrap works! One of the things that really throws people off is how complex notification processing really is. I suggest you spend some serious quality time with the SNMP Applications RFC (http://www.ietf.org/rfc/rfc3413.txt); study of the Framework document (http://www.ietf.org/rfc/rfc3411.txt) should be helpful here. HTH, Mike ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users