Well, Joe, I, for one, do not understand this problem you are complaining about.
The fields that netmon uses are always up to date. If he sets them, then he
will modify them on a config poll. The rest of them, the sorts of things set by
nvsniffer, or third-party products, or even added by the user with nvdbimport,
are for use by others, in collections for example. So there is no conflict that
I can see and there is no need for things to get rediscovered in subsequent
versions of NetView. The development team is well aware that you cannot be
expected to re-discover your network with each new release and that is not, nor
has it ever been, a requirement.
As for changes in oid-to-type and oid-to-sym, those files would be updated if
changed in subsequent release and any impacts would be noted in the Release
Notes. You would then only have to delete and re-discover objects if they had
been badly discovered in the first place, which is why the changes would be
made.
Adding third-party products is a different story, and you may well have to
delete and rediscover to get their full benefits, but it should be up to that
product to tell you that, shouldn't it?
So far as I can see, the general problem you allude does not exist, though a
specific case might. Have you got one of those you want to discuss?
James Shanks
Tivoli (NetView for UNIX and NT) L3 Support
"Prokott, Joe" <Joe.Prokott@westgroup.com> on 04/06/2000 06:23:27 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: "'NV Forum'" <nv-l@tkg.com>
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] Keeping NV fields up-to-date
We have a never ending and growing NetView environment and sometimes
struggle keeping all the NV fields for objects up-to-date.
Does anyone know of a good way to verify that all NetView fields are
up-to-date? I know there are some NV fields that only get defined upon
initial discovery and will not change unless rediscovered, even if the
fields files themselves have been updated. Is there a list of these type of
fields that do not change once initially defined? Better yet, is there some
way I can run a script that will either (1) let me know what nodes need to
be re-discovered because there is a conflict with what is defined in the NV
database and what is defined in the fields/oid_to_sym/oid_to_type/etc...
files, or (2) dynamically update these differences to match what is defined.
There are always new fields added to new versions of NetView and I am never
quite sure if these will automatically be added or if I will need to
rediscover the node so the new fields get added. It would be nice if
NetView could tell me what the differences were so we could keep things
up-to-date. It is not practical for us to rediscover our entire network on
some regular basis because we do not know if there are NV object field
changes or not.
I assume many others have this same problem. I would like as close to an
automated solution to this problem as possible.
Joe Prokott
Network Architect
West Group
phone: 651-687-4536
e-mail: joe.prokott@westgroup.com
_________________________________________________________________________
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l
|