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
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.
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
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
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,
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
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,
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
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
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
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
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
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
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
14 matches
Mail list logo
