On 06/03/07, Ricardo Marin Vinuesa <[EMAIL PROTECTED]> wrote:
> I have now added again the engineID for both of the users:
> And the log of the bash# snmptrapd -f -Lo -D (when I stop the snmpd and
> then I start it again):
[snip]
> Looking at the log, I can see exactly the same. If the 'run alarm 2' has
> nothing to do with the traps, it can be extracted that no trap is
> received by the snmptrapd. Any clue?
Firewalls?
Is this box runing iptables, or something similar?
Maybe that's blocking the trap being received?
The other thing to check is whether the agent is
sending the trap in the first place. Try starting
the agent using
snmpd -f -Le -d
(or similar). The '-d' will have it display a dump of
any packets sent or received.
Do you see a trap sent out when the agent starts up?
Dave
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
