> > > in snmpd.conf i have:
> > > trapsess -Ci -c public -v 2c snmp
> > > monitor -r 10 -o prNames -o prErrMessage "process table" prErrorFlag != 0
> > Does the trap handler running on the system 'snmp' receive a trap
> > when the agent first starts up (and shuts down) ?
> while there is no comunication on port 162 at all
So you don't even get the "coldStart" trap?
In which case this sounds like a problem with sending traps
(i.e. the "trapsess" line) rather than the disman monitoring
in particular
> on the 161 port i get the following with tcpdump
[snip]
> it seems that thereis no response from the snmpd on snmp to the informs
> ,but why does it send informs from port 161 to and not snptrapd on port 162?
Hmmm....
What happens if you try with:
trapsess -Ci -c public -v 2c snmp:162
i.e. specifying the trap destination port explicitly?
Dave
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
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
