I had some cases like this and the problem was that an IP address of one of
the interface of the object I try to discovered (not necessarly the one in
the
seed file) was previously used on an interface of another object previously
discovered
by Netview (even if this interface is actually shutdown now).
No error messages in netmon.trace or whatever. The solution: remove the IP
address
on the shutdown interface of the other router, delete this interface in
netview and
stop/start netmon.
(this happens in version 7.1.3 fixpack2 )
On 02.03.2004 19:08:22 "Christopher J Petrina" wrote:
>I have seen this now for awhile. I have ip addresses in the seed file
that
>are not being discovered. Theya re valid and pingable IP addresses. I
reviewed
>the netmon.trace log and it shows both a sending and a receiving of a ping
from
>10.213.1.6 but nothing else. When I do an ovtopodump | grep 10.213.1.6
returns
>no value either. I ahve seen this in many of the IP addresses. All of
which
>have basically the same entries in netmon.trace they are sent a ping they
>return the answer and then nothing more comes of these devices. These are
by
>the way L3 switches/Router ip addresses. I never thought anything of it
since
>finding devices via a seedfile is a very core level of Netview and never
have I
>heard of Netview not finding a device in the seedfile when it was alive.
So
>Ithought it could be the way in whcih I was discovering them. But this
just
>does not seem to make sense to me. Any h! elp? it is a fairly big
seedfile
>as we are not doing auto discovery. We only want to discover what is in
the
>seedfile.
>
>Chris Petrina
|