You know, of course, that you are running a version that has been
unsupported for
years. Even so, the function you are using should work. The 'unexpected'
usually
means that the ping response came in after Netview gave up, based on your
timeout
and retry settings (Options...SNMP configuration), but I could be wrong
about that. And
it should work whether the names resolve or not, although at different
versions you will
see different behavior in the case where the lookup does not work both
ways. I do not
remember what it did in 4.1.
So what are your status polling settings (defaults are 5 mins, with 2
second timeout
and 3 retries)? And do these nodes resolve properly forward and backward?
And
how do you know that it is not working? What does the IP Status say in
'Tools...
Display Object Info' for the node? Perhaps netmon is updating it, but it is
just not
showing on the map for some reason. Things to think about (while you are
checking
into getting a current version of the product....:)
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Szymon Trocha
<Szymon.Trocha@man. To: nv-l@tkg.com
poznan.pl> cc:
Sent by: Subject: [NV-L] Netmon
pinging
owner-nv-l@tkg.com
01/03/02 08:16 AM
Please respond to
IBM NetView
Discussion
Hi,
I have problem with my netmon. It doesn't see any changes in nodes' status.
I set up netmon tracing with -M 3 mask and looked at netmon.trace. This is
what I can see:
13:29:32 :sending ping to 150.254.212.99 seqnum = 15108 ident = 12588
timeout = 2
13:29:32 :sending ping to 150.254.212.100 seqnum = 15109 ident = 12588
timeout = 2
13:29:32 :sending ping to 150.254.212.57 seqnum = 15110 ident = 12588
timeout = 2
13:29:32 :sending ping to 150.254.212.97 seqnum = 15111 ident = 12588
timeout = 2
13:29:32 :sending ping to 150.254.163.8 seqnum = 15112 ident = 12588
timeout = 2
13:29:32 :sending ping to 150.254.210.165 seqnum = 15113 ident = 12588
timeout = 2
13:29:32 :sending ping to 212.126.29.225 seqnum = 15114 ident = 12588
timeout = 2
13:29:32 :-> received ping from 150.254.212.99 ()
13:29:32 :-> received ping from 150.254.212.100 ()
13:29:32 :-> received ping from 150.254.212.57 ()
13:29:32 :-> received ping from 150.254.212.97 ()
13:29:32 :-> received ping from 150.254.163.8 ()
13:29:32 :-> received ping from 150.254.210.165 ()
13:29:32 :-> received ping from 212.126.29.225 ()
13:29:32 :-> unexpected ICMP message 3 from 150.254.212.97
13:29:32 :ICMP message from: 150.254.212.97
13:29:32 :-> unexpected ICMP message 3 from 150.254.212.57
13:29:32 :ICMP message from: 150.254.212.57
13:29:34 :-> unexpected ICMP message 3 from 150.254.212.97
13:29:34 :ICMP message from: 150.254.212.97
13:29:34 :-> unexpected ICMP message 3 from 150.254.212.57
13:29:34 :ICMP message from: 150.254.212.57
13:29:34 :-> unexpected ICMP message 3 from 150.254.212.99
13:29:34 :ICMP message from: 150.254.212.99
13:29:36 :-> unexpected ICMP message 3 from 150.254.212.99
13:29:36 :ICMP message from: 150.254.212.99
13:29:36 :-> unexpected ICMP message 3 from 150.254.212.57
13:29:36 :ICMP message from: 150.254.212.57
13:29:36 :-> unexpected ICMP message 3 from 150.254.212.97
13:29:36 :ICMP message from: 150.254.212.97
13:29:38 :-> unexpected ICMP message 3 from 150.254.212.99
In spite of I have tens of hosts managed only a few of them (not more then
20) are properly resolved (I mean a host name appears in brackets in
"received ping..." command) in a trace. When I enter #host ip_adress the
above addresses are resolved properly.
What does it mean :-> unexpected ICMP message 3 from ?
In fact netmon detects only a status change in those selected <>20 nodes.
Nothing more! It seems that something is wrong with pinging...
Any advice where to look for a solution?
I have NetView 4.1 AIX 4.2.1
Thanks in advance.
Regards,
________________________________________________________________
Szymon Trocha
Poznan Supercomputing & Ntw. Center ::: NETWORK OPERATION CENTER
Tel. (+48 61) 8582022
http://noc.man.poznan.pl ::: http://www.man.poznan.pl/~konserwa
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|