I have done a lot of these in different kinds of customer environments,
so of course I have an opinion....
The approach I usually take is to do as open a discovery as possible
at first, to be sure I understand everything in the network. I might
tighten
it later on. I prefer to exclude by address range, rather than include. It
keeps me from getting confused. I make a Rules section that does this:
1) Exclude the address ranges assigned to your DHCP servers. This
keeps out most of your desktop PCs. It is worth the work!
2) Exclude any distant but connected networks that you are not
responsible for, as ranges.
3) Exclude by OID to keep out classes of devices - like printers, and
non-snmp devices (OID 0) - if necessary. There is a performance
cost to doing this, but it is not too bad. It is sometimes the only way
if your addressing scheme is not very good. This is generally done
after a full discovery and an analysis of the results (using Smartsets).
Also in the Rules section you may want some of the 'directives' such
as % and $ that are not really about discovery, but are a permanent
part of the seedfile.
Then, to speed up discovery, append a section that includes all of the
routers and major switches that you know about. These are the
explicit addresses that James is talking about. You don't have to
keep this part in the seedfile after discovery, but it speeds things up
a lot. Explicit address entries override exclusions.
If I have excluded the Microsoft OID to keep PCs out, I would also
add an explicit list of server IP addresses to override that exclusion.
This list usually comes from the Server people.
I keep these explicit lists as separate files and only append them
when I need them, for rediscovery. I update them from SmartSet
membership (using the nvUtil command) from time to time.
This is just how I do it. There are many ways to do this, and many
customers doing it differently.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
bducharme@avdl
.com To: IBM NetView Discussion
<nv-l@tkg.com>
Sent by: cc: chuberdeau@avdl.com
owner-nv-l@tkg Subject: Réf. : Re: [NV-L] Seed
file
.com
11/21/01 03:47
PM
Please respond
to IBM NetView
Discussion
So if i understand, with that
!192.*.*.1-20
192.168.4.*
Everything that is in 192.*.*.1-20 will not be permitted to be inserted in
the database,
but everything that is in 192.168.4.* will be permitted to be inserted in
the database.
Right ?
What are your consideration in building a good seed file ?
Benoit Ducharme
Réalisation Technologique - Outils de Gestion
Assurance vie Desjardins Laurentienne
200 rue des Commandeurs
Lévis, Québec
G6V 2R2
www.avdl.com
mailto : bducharme@avdl.com
"James
Shanks" Pour : IBM NetView Discussion
<nv-l@tkg.com>
<jshanks@US.I cc :
BM.COM> Objet : Re: [NV-L] Seed file
Envoyé par :
owner-nv-l@tk
g.com
2001-11-21
15:40
Veuillez
répondre à
IBM NetView
Discussion
If you want to guarantee discovery of your node 192.168.4.56 then that is
what you must add.
Only fully complete individual entries will guarantee discovery.
The others are ranges, which permit discovery (that is they permit
inclusion in the databases provided they are discovered somehow).
So what you have coded,
!192.*.*.1-20
192.168.4.*
Just says that you want to exclude everything in the range of !192.*.
*.1-20 that is not it the range of 192.168.4.*,
but to guarantee 192.168.4.56 is found, you have to add that also. If not,
you might never run across it in the ARP cache of some device you do
discover.
The addition of the complete address of a node overrides any ranges you
code.
!192.*.*.1-20
192.168.4.*
192.168.4.56
James Shanks
Level 3 Support for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
bducharme@avdl.com
Sent by: To:
owner-nv-l@tkg.com nv-l@tkg.com
cc:
11/21/2001 01:51 PM Subject:
Please respond to [NV-L] Seed file
IBM NetView
Discussion
I'm a new Tivoli NetView user.
In the seed file, is the inclusion or the exclusion that wins over the
other ?
I explain myself, if i do that
!192.*.*.1-20
192.168.4.*
Will I be able to get my server that has an ip of 192.168.4.56 ?
Thanks
Benoit Ducharme
Réalisation Technologique - Outils de Gestion
Assurance vie Desjardins Laurentienne
200 rue des Commandeurs
Lévis, Québec
G6V 2R2
www.avdl.com
mailto : bducharme@avdl.com
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|