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
|