Re: [nv-l] Netview upgrades

[James Shanks <jshanks@us.ibm.com>]

There is no direct migration from NetView
5.1 to 7.1, and that is one of the very big pitfalls you face in a highly-customized
environment when you do not stay current.  The migration effort increases
exponentially.  

For example, if you have a highly customized
trapd.conf, with many new traps, you can merge it with the updated trapd.conf
 shipped in 7.13 or 7.1.4  using  nvaddtrapd (/usr/OV/bin/nvaddtrap
<old.trapd.conf> )  but you will not get the  changes you
made to existing NetView traps and others which are also included.  So
you will likely have to do a lot of manual editing.  Br sure to keep
backup copies of your old and new until you are satisfied with the result.

It sounds to me as though your best
bet for a map migration is to make use of location.conf.  I don't
believe that is a part of NetView 5.1 and even if it is, it would not have
the same functionality that it has today.  What you need is a utility
to take your existing database and map and create a location.conf file
from it.  That would preserve most, if not all, of your map customization.
 NetView itself does not offer such a utility but others do.  It
will soon be available on the NetView user's group website, http://www.nv-l.org/

So my advice  is to become an active
member of the NetView User's Group.   They could help you with the
migration using their experience and advise you on learning how to utilize
the new features of NetView 7.1.   To join, visit http://www.tivoli-ug.org/groups.php?groupid=151

As for Forwarding to TEC, that's entirely
optional, so if you don't need to do it anymore, you need not.  It
is controlled by the file /usr/OV/conf/tecint.conf.
Just rename that file and restart nvserverd
and TEC forwarding ceases.    But you'll have to explain what
you mean about using a different ruleset to handle your events.  Rulesets
are active only in a particular context.   Some are used for event
windows, one is specified in the tecint.conf to handle TEC forwarding,
and others may be specified in  /usr/OV/conf/ESE.automation to perform
various background tasks.  But there is no general ruleset which handles
all your events. 

HTH

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

"Gavin Newman" <NEWMANGJ@banksa.com.au>
Sent by: owner-nv-l@lists.us.ibm.com

03/24/2004 07:57 PM

Please respond to
nv-l

To	<nv-l@lists.us.ibm.com>
cc
Subject	[nv-l] Netview upgrades

I'm currently running Netview 5.1 on AIX 4.3.3. We
need to move to AIX
5.x and will need to upgrade to Netview 7.1.x. 
We will be installing the new version on a new platform so it need not
be an upgrade over the top of 5.x (which I understand needs an
intermediate 6.x step). 

Given that we would have a fresh 7.x install how can we transfer our
existing rules, configurations, maps etc to the new installation so as
not to have to redraw our very complicated maps etc.

Secondly - we used to forward events to Tivoli using a complicated rule
set. Over time the rules changed such that 99% of our events now trigger
scripts which do various things and we are now dropping the forward to
Tivoli altogether.
We currently define the rule to be used by Netview by starting Tivoli
and setting the "Forwarding to Tivoli" config option. If we no
longer
have Tivoli involved in our Netview installtion how do we tell Netview
which ruleset we want to handle our incoming events?

Cheers - Gavin Newman



**********************************************************************
*****   IMPORTANT INFORMATION    *****
This document should be read only by those persons to whom it is 
addressed and its content is not intended for use by any other 
persons.  If you have received this message in error, please notify
us immediately.  Please also destroy and delete the message from 
your computer.  Any unauthorised form of reproduction of this message
is strictly prohibited.

St George Bank Limited AFSL 240997 or its subsidiaries ASSIRT Pty Ltd 
AFSL 240979, Advance Asset Management Limited AFSL 240902, PACT 
Accountants Investment Group Pty Limited AFSL 240693, St George Life 
Limited AFSL 240900, ASGARD Capital Management Limited AFSL 240695 
and Securitor Financial Group Limited AFSL 240687 is not liable for 
the proper and complete transmission of the information contained in 
this communication, nor for any delay in its receipt.
**********************************************************************