I would like to understand this better, too. I've seen traces like that. I
think the
unexpected returns are from nodes for which netmon had already given up.
But
that timeout of 1 puzzles me. Increasing the retries seemed to have more
effect
than increasing the timeout in the case I saw, but I'm afraid of what that
kind of
setting would do to the snmp polling, since I believe they use the same
values.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
I've noticed something interesting that I can't explain...
On my Netview 5 system, I've got SNMP configured with one profile for the
whole network. I'm using the following values:
Timeout: 2.0
Retry: 3
Status: 5m
And that's about it. According to my Netview class, this should result in
the following behavior:
ping
if no response, wait 2 seconds
ping
if no response, wait 4 seconds
ping
wait up to 8 seconds for response
if no response then device is down.
Well that's what I thought was 'supposed' to happen. But while
troubleshooting intermittent phantom device down reports for some Bay 350
switches, I turned on netmon trace. Netmon trace show that instead of a
timeout of 2 seconds, the time out is actually 1 second.
Here's the excerpts from the netmon.trace log:
08:54:44 :sending ping to 12.19.105.15 seqnum = 33629 ident = 22452 timeout
= 1
08:54:45 :sending ping to 12.19.105.15 seqnum = 33629 ident = 22452 timeout
= 2
08:54:47 :sending ping to 12.19.105.15 seqnum = 33629 ident = 22452 timeout
= 3
08:54:50 : expired ping to 12.19.105.15 (swt13-05.okc.rins.net) seqnum =
33629 ident = 22452
As you can see the timeout value is actually 1 second.
Can anyone tell me why that is? Where else do I modify that value besides
in the SNMP configuration screen?
In a related question, can anyone give me some clues on what could be
causing the behavior below?
08:57:39 :-> received unexpected ping from 12.19.105.15
08:57:40 :-> received unexpected ping from 12.19.105.15
08:57:41 :-> received unexpected ping from 12.19.105.15
08:57:42 :-> received unexpected ping from 12.19.105.15
08:57:43 :-> received unexpected ping from 12.19.105.15
08:57:44 :-> received unexpected ping from 12.19.105.15
08:57:45 :-> received unexpected ping from 12.19.105.15
08:57:46 :-> received unexpected ping from 12.19.105.15
And I'm not just getting them from 1 device, I'm getting these 'unexpected
pings' from alot of different devices.
Thanks.
|
