The migration re-install is documented in the releasenotes, sort of. Read
all of the
parts about migrating and deinstalling carefully, especially the parts
about cleaning
out extra maps and 3rd party products that are not really working. And
about trapd.conf.
(I'm just saying don't use this note as your full set of instructions).
Basically, though:
1) Take a full system backup, of course
2) Turn of netview security of you are using it.
3 Take the Netview backup. This is documented for several releases.
Basically it is
under 'smit nv6000', Maintain, Backup... It creates a filesystem in the
volume group of
your choice called /usr/OV.back.v5r1, for instance, if that's where you
are, or v6r0.
Under that you will find copies of all of the Netview directories and
your changed files.
4) Deinstall Netview using the smit nv6000 option under Maintain.
5) Deinstall the Framework using brute force. Search thoroughly in /etc/
for occurances
of 'oserv'. Don't forget the /etc/Tivoli directory. If you are
sourcing the tivoli environemnt
in your .kshrc, get that out of there. If this is a managed node in a
TMR, deal with that too.
6) Now do your move, hostname change, address change, etc. Verify as for a
new install.
7) Intall the Framework stuff and verify. Install the Netview Framework
patch.
8) Now, in the presence of that backup filesystem, do the Install Product,
but pick the
Update rather than the fresh install. During the course of installing
Netview V6, it will
pickup and incorporate most of your customizations. Exceptions are
noted in the
/tmp/update.log.
When Netview comes up with the old map on the new box, you may have a
little trouble.
Attack that with /usr/OV/service/reset_ci, and mapadmin -f <hostname>. You
will also have
to find and delete the node for the netview server and rediscover it. Watch
the nettl log.
Worst case, you will have to rediscover, but you will probably get away
with it.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Gebhart, Tom (CC-MIS Tech Systems)" <Tom.Gebhart@conagra.com>@tkg.com on
07/25/2000 03:31:50 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'NV-L@tkg.com'" <NV-L@tkg.com>
cc:
Subject: RE: [NV-L] Changing the hostname of a TMR server running Netview
I am very interested in your recent experience described in your
message to the list concerning changing the hostname of a TMR server
running
netview.
We are getting ready right now to do that very thing with our server
as we prepare to move to a new data center across town. We will need to
change both the server hostname and the ip address. The new address will
be
in a new network as well (172.20.x.x to 172.24.x.x). We have a lab rs6000
to practice on and so far we have tried changing the hostname and find
Netview will run just fine. Next we plan to tease it (test it) with the ip
network change.
But looking ahead of this exercise I ask if we are only borrowing
time. If we end up with a system that won't take patches, we don't want to
go there. We will have the time now to reinstall TME and Netview, if we
have to, (we probably won't ever have that time available again).
You state "I of course took a Netview backup and did a migration
install, and that's the course I would advise for anyone needing to change
the hostname of the server running Tivoli." Would you please elaborate on
that process (a migration install) for us as we have never done that
before.
If that would mean we wouldn't have to make Netview rediscover our network
and redo all the cut and paste work it took to layout the maps the way we
have them, then I'd be all for that procedure. Thanks for any help you can
give us.
Tom Gebhart
ConAgra, Inc.
Network Analyst
(402) 978-3837
-----Original Message-----
From: lclark@us.ibm.com [mailto:lclark@us.ibm.com]
Sent: Monday, July 24, 2000 9:26 AM
To: NV-L@tkg.com
Subject: [NV-L] Changing the hostname of a TMR server running Netview
FYI, I have just been through an upgrade from V5 to V6 on a system for
which the hostname was previously changed. The change was done using
the method outlined in the V6 release notes, Appendix B, and was in fact
the system that was the source of those instructions. I can tell you now
that
a system whose hostname was changed in that fashion will work just fine
until you try to put a patch on the Framework. I was unable to apply the
3.6-3.6.2 patch (completed with errors) and I was unable to apply the
Netview Framework patch for 6.0 (failed properly, so at least some of
3.6.2 went on). It failed because of leftover things in the name registry
that
referred to the old hostname. Framework Support kindly sent me an
assortment of additional instructions and advised me to pick through
them looking for clues. I of course took a Netview backup and did a
migration install, and that's the course I would advise for anyone needing
to change the hostname of the server running Tivoli. Life's too short.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|