Well, the location.conf file is the way
to do, but you will have to be at at least
Version 6.0 to do it, and while you're at
it, you may as well go all the way to
6.0.2. If you have a support contract
the upgrade is free for the asking from
your account rep.
You say no major design changes (such as
an upgrade to 6.0.2) will be welcomed, but
in the same breath you say you're going to
keep it running for 2 years. If that's the
case (keeping it running for 2 years), it
is well worth the effort to:
1. Upgrade to 6.0.2
2. Create a new seedfile and location.conf
3. Wipe out your database and let NetView
re-discover the entire network.
You will really like the appearance of your map
with the locations on it, and a little bit of
manual moving around of things will make it
beautiful (this is the voice of experience speaking).
You'll probably get a standing ovation as did I.
Les Dickert
Verisign Consulting
>From: "Allison, Jason (JALLISON)" <JALLISON@arinc.com>
>Reply-To: IBM NetView Discussion <nv-l@tkg.com>
>To: "'nv-l@tkg.com'" <nv-l@tkg.com>
>Subject: [NV-L] TME10 - Cluttered Map
>Date: Wed, 13 Jun 2001 17:07:13 -0400
>
>List:
>
>My new task is "reducing the number icons in the Netview Map." I believe
>we
>are running Netview 5.1.3, I am new to this project (and company). My
>background is in using Netviews robust API to integrate SNMP Management
>into
>real-time systems, i.e. most of this front-end desktop work is new to me.
>
>Background -
>Our displays have ~400 subnets (quite cluttered) which include many end
>stations per subnet. As a note, this is a VERY stable base-lined cash cow
>product that is being phased out over the next 2 years, no major design
>changes will be greeted nicely. I have been searching the archived lists
>and have come across two possible solutions. I wanted to discuss these
>with
>the list to see what I am missing as well as determine "best practice"
>approaches.
>
>Solutions:
>1. (Easiest, most operator work) - Manually creating multiple containers
>in
>some sort of hierarchical approach to "tree" all of the end systems. Then,
>cutting and pasting objects in and out of the old to new containers. At
>work we have proven this is a workable solution. Coming from a software
>background, I don't believe this is the best solution. It does not scale,
>and once this paradigm is set, re-design or re-work is exponentially
>costly.
>Also, this solution has more potential for operator error.
>
>2. Create a location.conf file of the desirable map layout. I am not sure
>if this is even possible. From what I have read, one needs to have their
>map all set up, then create a location.conf file from their database, which
>can be used for restoring the map, etc. With that said, it seems to me
>that
>it could be generated, am I wrong? What is the best approach for this?
>
>3. ?? What are your thoughts? Have any of you worked though this problem
>yourselves?
>
>Thanks for the help,
>Jason
>_________________________________________________________________________
>NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________
|