Re: A flurry of notifications at startup
Le Mardi, 27 Mai 2008 12:24:10 +0100, "Dave Shield" <[EMAIL PROTECTED]> a écrit : > Try running "monitor -S " Hi, Thanks for the info. So here's the config now: notificationEvent linkUpTrap linkUp ifIndex ifAdminStatus ifOperStatus notificationEvent linkDownTrap linkDown ifIndex ifAdminStatus ifOperStatus monitor -S -r 5 -e linkUpTrap "Generate linkUp" ifOperStatus != 2 monitor -S -r 5 -e linkDownTrap "Generate linkDown" ifOperStatus == 2 And here are the commands executed: 484 /etc/init.d/snmpd stop 485 /etc/init.d/snmpd start And this how the traps are received: /usr/sbin/snmptrapd -Lf ~/trap_log.txt -F "%02.2h:%02.2j TRAP:%W from %b %P %v\n" As you can see, there is still a bunch of msgs received at the startup: Shutting down: 08:02 TRAP:Cold Start from UDP: [192.168.1.22]:1025 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (5452211) 15:08:42.11 SNMPv2-MIB::snmpTrapOID.0 = OID: NET-SNMP-AGENT-MIB::nsNotifyShutdown SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpNotificationPrefix Starting up: 08:02 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (47) 0:00:00.47 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-MIB::coldStart SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 Bunch of messages: (the test unit was idle since last afternoon - no link up/down and no autehnticationf ailure as far as I know) 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3048) 0:00:30.48 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-MIB::authenticationFailure SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3049) 0:00:30.49 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkDown IF-MIB::ifIndex.5 = INTEGER: 5 IF-MIB::ifAdminStatus.5 = INTEGER: up(1) IF-MIB::ifOperStatus.5 = INTEGER: down(2) SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3049) 0:00:30.49 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkDown IF-MIB::ifIndex.6 = INTEGER: 6 IF-MIB::ifAdminStatus.6 = INTEGER: up(1) IF-MIB::ifOperStatus.6 = INTEGER: down(2) SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3049) 0:00:30.49 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkDown IF-MIB::ifIndex.7 = INTEGER: 7 IF-MIB::ifAdminStatus.7 = INTEGER: down(2) IF-MIB::ifOperStatus.7 = INTEGER: down(2) SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3549) 0:00:35.49 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp IF-MIB::ifIndex.1 = INTEGER: 1 IF-MIB::ifAdminStatus.1 = INTEGER: up(1) IF-MIB::ifOperStatus.1 = INTEGER: up(1) SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3549) 0:00:35.49 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp IF-MIB::ifIndex.3 = INTEGER: 3 IF-MIB::ifAdminStatus.3 = INTEGER: up(1) IF-MIB::ifOperStatus.3 = INTEGER: up(1) SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3549) 0:00:35.49 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp IF-MIB::ifIndex.4 = INTEGER: 4 IF-MIB::ifAdminStatus.4 = INTEGER: up(1) IF-MIB::ifOperStatus.4 = INTEGER: up(1) SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 Curiously the following msgs - part of the same bunch - do not have the ifOperStatus, ifAdminStatus and ifIndex fields: 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (6047) 0:01:00.47 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (6047) 0:01:00.47 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRA
RE: A flurry of notifications at startup
lanas: > The problem is with the quantity of traps received at the start up of > the daemon, all bearing the same time stamp, making them practically > worthless that is, if they actually picture an historical trace of > events. The flurry of notifications at startup appears perfectly normal to me. (Or at least that is how it works on my side as well, so I'm not particularly worried about it.) The SNMP agent reports the flurry of traps to establish a baseline of what it contains in its local MIB copy. Once the flurry is finished then the traps settle down to reflect local changes. I don't know of any way to change that behavior through SNMP agent configuration, but I'm just a user like yourself so my knowledge is limited. The only part of your report that appears odd is the repeated link traps. This leads me to wonder if you still have the "linkUpDownNotifications yes" directive somewhere in your config tree along with the "notificationEvent/monitor" directives. I remember that the former directive resulted in traps that seemed to be missing some information in my setup. Ron The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting all copies. Thank you. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
Re: A flurry of notifications at startup
Hi! I have been watch the ideas about snmptrap and my question is: How do I know if a trap was sent from my agent? What will appear in the screen or log file in the NMS (Network Manager Station)? Thank you and best regards, Murilo Murilo Fujita Engineer of Automation Universidade Federal de Itajuba lanas wrote: Le Mardi, 27 Mai 2008 12:24:10 +0100, "Dave Shield" <[EMAIL PROTECTED]> a écrit : Try running "monitor -S " Hi, Thanks for the info. So here's the config now: notificationEvent linkUpTrap linkUp ifIndex ifAdminStatus ifOperStatus notificationEvent linkDownTrap linkDown ifIndex ifAdminStatus ifOperStatus monitor -S -r 5 -e linkUpTrap "Generate linkUp" ifOperStatus != 2 monitor -S -r 5 -e linkDownTrap "Generate linkDown" ifOperStatus == 2 And here are the commands executed: 484 /etc/init.d/snmpd stop 485 /etc/init.d/snmpd start And this how the traps are received: /usr/sbin/snmptrapd -Lf ~/trap_log.txt -F "%02.2h:%02.2j TRAP:%W from %b %P %v\n" As you can see, there is still a bunch of msgs received at the startup: Shutting down: 08:02 TRAP:Cold Start from UDP: [192.168.1.22]:1025 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (5452211) 15:08:42.11 SNMPv2-MIB::snmpTrapOID.0 = OID: NET-SNMP-AGENT-MIB::nsNotifyShutdown SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpNotificationPrefix Starting up: 08:02 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (47) 0:00:00.47 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-MIB::coldStart SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 Bunch of messages: (the test unit was idle since last afternoon - no link up/down and no autehnticationf ailure as far as I know) 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3048) 0:00:30.48 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-MIB::authenticationFailure SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3049) 0:00:30.49 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkDown IF-MIB::ifIndex.5 = INTEGER: 5 IF-MIB::ifAdminStatus.5 = INTEGER: up(1) IF-MIB::ifOperStatus.5 = INTEGER: down(2) SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3049) 0:00:30.49 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkDown IF-MIB::ifIndex.6 = INTEGER: 6 IF-MIB::ifAdminStatus.6 = INTEGER: up(1) IF-MIB::ifOperStatus.6 = INTEGER: down(2) SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3049) 0:00:30.49 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkDown IF-MIB::ifIndex.7 = INTEGER: 7 IF-MIB::ifAdminStatus.7 = INTEGER: down(2) IF-MIB::ifOperStatus.7 = INTEGER: down(2) SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3549) 0:00:35.49 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp IF-MIB::ifIndex.1 = INTEGER: 1 IF-MIB::ifAdminStatus.1 = INTEGER: up(1) IF-MIB::ifOperStatus.1 = INTEGER: up(1) SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3549) 0:00:35.49 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp IF-MIB::ifIndex.3 = INTEGER: 3 IF-MIB::ifAdminStatus.3 = INTEGER: up(1) IF-MIB::ifOperStatus.3 = INTEGER: up(1) SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3549) 0:00:35.49 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp IF-MIB::ifIndex.4 = INTEGER: 4 IF-MIB::ifAdminStatus.4 = INTEGER: up(1) IF-MIB::ifOperStatus.4 = INTEGER: up(1) SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 Curiously the following msgs - part of the same bunch - do not have the ifOperStatus, ifAdminStatus and ifIndex fields: 08:03 TRAP:Cold Start from UDP: [192.168.1.22]:1027 TRAP2, SNMP v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (6047) 0:01:00.47 SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp SNMPv2-MIB::snmpTrapEnte
Re: A flurry of notifications at startup
2008/5/29 Murilo Fujita <[EMAIL PROTECTED]>: > How do I know if a trap was sent from my agent? It will presumably be received by the configured trap receiver. > What will appear in the screen or log file in the NMS That depends on the trap receiver or NMS that you are using. (and how you have configured it). It's impossible to answer that question without information about what software you are using. Dave - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
Re: A flurry of notifications at startup
Le Jeudi, 29 Mai 2008 09:26:20 -0400, "Ron Rader" <[EMAIL PROTECTED]> a écrit : >> The problem is with the quantity of traps received at the start up >> of the daemon, all bearing the same time stamp, making them >> practically worthless that is, if they actually picture an >> historical trace of events. > The flurry of notifications at startup appears perfectly normal to > me. (Or at least that is how it works on my side as well, so I'm not > particularly worried about it.) The SNMP agent reports the flurry of > traps to establish a baseline of what it contains in its local MIB > copy. Once the flurry is finished then the traps settle down to > reflect local changes. Then the problem, as a new user, might be a conceptual one. And it could be that I need to RTFM. I mean, there could be one of the received trap parameters that simply states: 'please do not mind these traps, I'm only listing them now' which would differentiate these traps from real status changes later on. If that's the case then it's easy to add to the automatic testing of units. If not, then a 'magical' timeout has to be used before starting the tests. > I don't know of any way to change that behavior through SNMP agent > configuration, but I'm just a user like yourself so my knowledge is > limited. Thanks for any comments, it's appreciated. > The only part of your report that appears odd is the repeated link > traps. This leads me to wonder if you still have the > "linkUpDownNotifications yes" directive somewhere in your config tree > along with the "notificationEvent/monitor" directives. I remember > that the former directive resulted in traps that seemed to be missing > some information in my setup. I've made several tests, although I'm quite certain that it was not in the config at the moment. What's strange is that in the same sway there'll be traps with the ifIndex and the two others and then without, only (milli)seconds away. Cheers. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
Re: A flurry of notifications at startup
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. 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? I think after the answer it´ll become easier to understand how the snmptrap works! Thank you! Best regards! Murilo Murilo Fujita Engineer of Automation Universidade Federal de Itajuba Dave Shield wrote: 2008/5/29 Murilo Fujita <[EMAIL PROTECTED]>: How do I know if a trap was sent from my agent? It will presumably be received by the configured trap receiver. What will appear in the screen or log file in the NMS That depends on the trap receiver or NMS that you are using. (and how you have configured it). It's impossible to answer that question without information about what software you are using. Dave - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
Re: A flurry of notifications at startup
If you unplug the cable, the message will not be relayed to NMS unless you're using wireless. Or, I suppose, the Pigeon Protocol. -Dan 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. > 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? > I think after the answer it´ll become easier to understand how the > snmptrap works! > Thank you! > Best regards! > > Murilo > > > Murilo Fujita > Engineer of Automation > Universidade Federal de Itajuba > > > Dave Shield wrote: > > 2008/5/29 Murilo Fujita <[EMAIL PROTECTED]>: > > > How do I know if a trap was sent from my agent? > > > It will presumably be received by the configured trap receiver. > > > > > What will appear in the screen or log file in the NMS > > > That depends on the trap receiver or NMS that you are using. > (and how you have configured it). > > It's impossible to answer that question without information > about what software you are using. > > Dave > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > Net-snmp-users mailing list > Net-snmp-users@lists.sourceforge.net > Please see the following page to unsubscribe or change other options: > https://lists.sourceforge.net/lists/listinfo/net-snmp-users > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
RE: A flurry of notifications at startup
> 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/vse012070mrt/direct/01/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
Re: A flurry of notifications at startup
I imagine everybody that read my e-mail thought "doesn't he know that's impossible relay data when the cable is unplugged?" I know it and I want to know/understand where will appear messages showing linkUp/linkDown. Maybe I made a bad interpretation of man pages, but I ask for help for my doubt, ok? Thanks again. Regards, Murilo 05-30-2008 13:32, dan anderson wrote: If you unplug the cable, the message will not be relayed to NMS unless you're using wireless. Or, I suppose, the Pigeon Protocol. -Dan 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. 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? I think after the answer it´ll become easier to understand how the snmptrap works! Thank you! Best regards! Murilo Murilo Fujita Engineer of Automation Universidade Federal de Itajuba Dave Shield wrote: 2008/5/29 Murilo Fujita <[EMAIL PROTECTED]>: How do I know if a trap was sent from my agent? It will presumably be received by the configured trap receiver. What will appear in the screen or log file in the NMS That depends on the trap receiver or NMS that you are using. (and how you have configured it). It's impossible to answer that question without information about what software you are using. Dave - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
Re: A flurry of notifications at startup
2008/5/30 Murilo Fujita <[EMAIL PROTECTED]>: > I imagine everybody that read my e-mail thought "doesn't he know that's > impossible relay data when the cable is unplugged?" That depends on the network topology of the system where the agent is running. If this box only has a single network interface, then the agent won't be able to communicate with anything if that link goes down. But if you're working with a switch or a router, and one link fails, then it's quite possible that the box can still talk to the NMS, using one of the other interfaces. And if there are several NMS systems configured, then losing the link to one need not affect the route to the others. Bear in mind that there's nothing particularly special about linkUp/Down traps as far as the SNMP agent is concerned. These are just two of the many traps that it might be called upon to generate. It doesn't handle them in any special way. An agent will have a list of trap receivers that it knows about. When it's asked to send a trap, it will try to send it to (some or all of) these systems. If there's no network connection to a given receiver, then those traps won't get sent to that receiver. > I know it and I want to know/understand where will appear messages > showing linkUp/linkDown. If the link to a given NMS is down, then the trap will never be displayed. (by that NMS at least). That's true regardless of whether the trap is a "linkDown" message, or a "someBuggerHasStolenTheSwitch" report :-) There's no magic processing here - if the agent can talk to the NMS, then the trap will be delivered and displayed. If it can't, then it won't. Dave - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
Re: A flurry of notifications at startup
Le Vendredi, 30 Mai 2008 11:54:18 -0700, "Mike Ayers" <[EMAIL PROTECTED]> a écrit : > 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. I stumbled today upon a PDF version of an O'Reilly book about SNMP which provices good reading: http://www.geocities.com/deepesh_indore/ The link originates from: http://www.snmplink.org/snmpresource/snmpv3/#2 So I presume it's OK. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
Re: A flurry of notifications at startup
Le Vendredi, 30 Mai 2008 21:58:27 +0100, "Dave Shield" <[EMAIL PROTECTED]> a écrit : Hello, > An agent will have a list of trap receivers that it knows about. > When it's asked to send a trap, it will try to send it to (some or > all of) these systems. If there's no network connection to a given > receiver, then those traps won't get sent to that receiver. In such a case, will it then buffer them (round-robin ?) and send them when a connection eventually becomes available ? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
Re: A flurry of notifications at startup
No, by default SNMP is over UDP, which is connectionless. Trying to send a UDP packet might throw or return an error if there's no network interface to send it out on, or might do so pre-sending it if you try to resolve a nonexistant name, but if a UDP packet gets out onto the network it's gone and the agent won't know it didn't reach its destination. If one of the former two occurs, it's up to the agent software to do whatever it feels like with that information. -Dan 2008/5/30 lanas <[EMAIL PROTECTED]>: > Le Vendredi, 30 Mai 2008 21:58:27 +0100, > "Dave Shield" <[EMAIL PROTECTED]> a écrit : > > Hello, > >> An agent will have a list of trap receivers that it knows about. >> When it's asked to send a trap, it will try to send it to (some or >> all of) these systems. If there's no network connection to a given >> receiver, then those traps won't get sent to that receiver. > > In such a case, will it then buffer them (round-robin ?) and send them > when a connection eventually becomes available ? > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > Net-snmp-users mailing list > Net-snmp-users@lists.sourceforge.net > Please see the following page to unsubscribe or change other options: > https://lists.sourceforge.net/lists/listinfo/net-snmp-users > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
Re: A flurry of notifications at startup
2008/5/27 lanas <[EMAIL PROTECTED]>: > Still in my net-snmp testing, I observed that some moment after the > startup of snmpd (perhaps 60 seconds or so), and well after the > notification about starting up, a certain number of link up/down traps > are received, all with the same timestamp. I've also managed to track down the cause of this problem. Although the internal linkUp/Down monitoring did indeed have the '-S' flag set, to suppress the startup tests, this wasn't working correctly. It did suppress traps from the initial monitoring pass (as intended), but unfortunately, the *second* monitoring pass would then trigger a linkUp trap for any link that was up, and a linkDown trap for any link that was down. (And the links that were only half way up, were neither up nor down). I've also applied a patch that fixes this problem as well. Again, that will be included in the upcoming 5.4.2 release. Dave - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
