The instructions that have been posted here before indicate that you
really ought to do a re-install, though no customization need be lost.
Basically you are supposed to follow the instructions in the Release
Notes for a migration. Do the backup, which saves everything you have
done to a special filesystem, then remove netview and remove tivoli
framework, then do the Create Managed Node from the TMR server,
then put the patch on the server and the managed node, then do the
Create NetviewServer from the TMR Server onto the Managed Node.
The install process will notice the backup filesystem and re-merge
all of that stuff.
There was a rumor a while ago of a 'fake' install that allows you to leave
Netview alone and just remove the framework, create the managed node,
and then, via a script, update all the stuff in the framework that is required
to link Netview and the Framework. You might call Support and see if there
is a curren version of that script, though I doubt that it would be supported.
Personally, I would opt for the re-install with migration as the safest way.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Hi all,
we have several production netview 5.1.1 machines each of them residing in a
separate Tivoli Management Region (TMR), i.e. each machine is also running as a
separate TMR Server. Now, we need to have these netview machines within our new
TMR on a new machine, so what has to be done to get all this netview machines as
ManagedNodes into our new TMR ?
The reason for this is, we want to use Distributed Monitoring and want to
install specific Monitors on all netview machines, so you need to have them all
as ManagedNodes in your new TMR where Distributed Monitoring is installed. So,
what to do? Is there a chance just to remove the framework on all netviews,
cause this is only needed for installation purposes and after this create just
new ManagedNodes for the netviews on the new TMR ?
I´m not to sure whether it would be a valid way to create ManageNodes for the
netviews on the new TMR regardless the point that actually all netviews still
reside in their own TMR?
We don´t want to do any tests on our production machines without any kind of
backround information, so any help from you would be appreciated,
Only as a remark: we don´t want to run a interconnected TMR approach, especially
that the netview TMRs are connected with the new TMR, cause we thinks that this
would decrease performance, wouldn´t it ?
Thanks in advane...
Mit freundlichen Grüßen/Kind regards
Thorsten Mildeberger
AT&T Global Network Services Deutschland GmbH
Mailing Address: Hechtsheimer Str.2, 55131-12, Dept. 8730, Mainz/Germany
|