Sorry if this is too basic, but are you using a seedfile? Some things
just don't make any noise, and have to be pinged to be discovered.
Things like hubs, novell servers, routers at the other end of unnumbered
serial connections, etc. On the discovery settings (and on the netmon
daemon setting), make sure you
have turned on all of the options you need, like support for secondary
addressing and unnumbered interfaces. And make sure you have
not check the box that says only discover the local network, or
only discover the seedfile. At a minumum, put all of the routers
you can think of in the seedfile. And consider that ping-spray
option if you think it won't adversely impact your network. And
for the routers you have discovered, are you getting snmp access
to them all? So you see, lots of things can restrict discovery. Can
you be more specific about what is missing?
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager
---------------------- Forwarded by Leslie Clark/Southfield/IBM on 05/16/99
11:46 PM ---------------------------
Paul Fordy <paul.fordy@VIRGIN.NET> on 05/16/99 08:46:30 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: Leslie Clark/Southfield/IBM)
Subject: Re: Netmon Stops Discovering
Are you using NT DNS because this caused us loads of problems especially
if reverse resolution does not always match forward resolution?
I added all my devices to the /etc/hosts file and all worked well. It's
now on my todo list to sort out later - especially as I don't have
control over our DNS server.
Todd E. Lewis wrote:
>
> Netview 5.1.1. NT:
> Has anyone ever had a problem with Netmon discovering a few devices like 24 a
then just stopping for no apparent reason ? The daemon is still running but it
won't discover anymore and the polling time for new nodes just keeps increasing
as the system time hits that setting. I reinstalled Netview with the fresh
option and the problem is still there. Could this be a SQL problem ?
|