This qualifies as a Frequently Asked Question, but I don't see
mention of it on the Tivoli Customer Support website so I'm copying
netview@tivoli.com
Clarification:
You may put address ranges or wildcards in the seedfile, both
positive and negative. The thing to understand is that ranges
are used as filters. They don't force discovery. When netview
hears from a new address, it will check those ranges to see if
it should be added.
In real life this means that, at least for initial discovery,
you will want to generate a list of 'silent' devices, like hubs
and switches, and force their discovery with an explicit seedfile.
Then remove those entries and replace them with a range. If a new
'silent' device is put on the network, you may need to ping it
from the command line, and netview will hear from the device and the
range will allow it to be added. Note, also, that positive ranges
are exclusive. That means you will need to have ranges that cover
ALL nodes you want to allow. Negative ranges just exclude the
addresses in those ranges. (Negative ranges start with !)
On NT, the ping-spray option can take the place of explicit
lists or pinging from the commandline.
Changes to the seedfile do not cause deletion from the
database, either. Read more about seedfile processing in
a few places: Help for netmon configuration from the Tivoli
context menu, the netmon man page, and references to 'seedfile'
in the online manuals for Unix, and in the sample
\usr\ov\conf\netmon.seed on NT.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager
---------------------- Forwarded by Leslie Clark/Southfield/IBM on 04/30/99
02:20 PM ---------------------------
Philip Guerra <pguerra@dev.tivoli.com> on 04/30/99 01:14:45 PM
Please respond to pguerra@dev.tivoli.com
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: Leslie Clark/Southfield/IBM)
Subject: Re: nv-list
If I am not mistaken you can't have ranges of ip addresses, that you want
to
discover, in the seed file. You can have ranges for address you don't want
to
discover or DHCP ranges but not ranges for machines you want to discover.
Philip Guerra
Senior TME Deployment Engineer
IT-Austin
Tivoli Systems, Inc.
Roger Campagnoni wrote:
> CAUTION: Newbie to the mailing list - question.
>
> I need clarification on the /usr/OV/conf/seed_file.
>
> Currently we have placed all of our Core Routers backbone
> IP Addresses in the seed_file in which NetView's discovery
> process properly detected these routers, and placed the appropriate
> logical links to their corresponding neighbors.
>
> We are attempting to detect devices with specific IP Ranges on
> already discovered networks. However their are not being discovered
> even after several days. I placed in the seed_file (10.70.1-254.245-254
),
> hoping to discover the following devices (10.70.11.245, 10.70.12.245,
> 10.70.21.245).
> But alas none has been discovered.
>
> I did read the trick, to place the IP Address of a device you want to
> quickly
> discover at the bottom of the seed_file and then bounce netview through
> smit. That does seem to work properly.
>
> So for the sake of sanity what am I doing wrong?
> Is the "10.70.1-254.245-254" statement in the seed_file not valid?
> Could I use "10.70.*.*" ?
> Or am I deemed to have to enter devices like "10.70.11.245" ,
> "10.70.12.245" etc, etc. (Which I doubt).
>
> Any help would be appreciated.
>
> Thanks
>
> ---------------------- Forwarded by Roger Campagnoni/IT/CF/CCI on
04/30/99
> 09:10 AM ---------------------------
>
> Gil Irizarry <IRIZARRG@LABS.WYETH.COM> on 04/30/99 05:51:00 AM
>
> To: NV-L@UCSBVM.UCSB.EDU
> cc: (bcc: Roger Campagnoni/IT/CF/CCI)
> Subject: nv-list
>
> I had the same problem. I am told that we do not have an authoritative
> server for network 10 with out internal network. My solution was to
include
> all router ip addresses in my /etc/hosts file.
> Gil Irizarry
>
> >>> Massimo Carnevali <Massimo.Carnevali@COMUNE.BOLOGNA.IT> 04/30 8:45 AM
> >>>
> I too noticed this problem. It seems that for a small perdiod of days
> trying to resolve
> internal addresses (like 10.*.*.*) on the external world gave that
answer.
> Check your DNS inverse ip resolution, may be it is asking outside what it
> should
> keep inside.
> Hope this helps.
> Massimo Carnevali - IBM Global Services -Italy
|