A few things here. My 2 pennorth here is that the Operating System move
will have more gotchas than the NetView move. Whether you are going
from NV 6.x or 7.x you will HAVE to go to NV 7.1.4 FP2 - before that,
RHEL 3 was not supported (I didn't try RHEL 3.0 but I did try SUSE 9
prior to fp2 and it's just grief). Also be aware that with NV 7.1.4 FP2
there was a new base CD for RHEL 3 / SLES 9 - you will need to get that
CD / CD image (it's available on Passport Advantage for customers and
Partnerworld for Software if you are an authorised business partner).
Make sure you read the Linux pre-reqs from the old NV 7.1 Release Notes
- these are still as valid as ever and are not repeated in the FixPack 2
Release Notes. In particular, make sure you use the pdksh that is
shipped in the RPMS subdirectory of the NetView CD. I also found that
comments in the FP2 Release Notes about Linux on z/OS also applied to
SuSE 9 on Intel.
Once you have the code, the mechanics of the "upgrade" are well
documented here on the forum and in the manuals - basically use
serversetup to backup all your NetView stuff and do an update install of
the new stuff. Michael - with NV 6, Tivoli Framework was a pre-req.
With 7.x it's optional so the fact that you had some old TMR history
around shouldn't be a problem. The only real reason for installing NV
on top of Framework is if you want to export your NetView trapd and/or
snmpd databases out to an SQL database. (If you are going to integrate
NV with Tivoli Data Warehouse this does NOT pre-req Framework).
If you are moving to new hardware, backup your NetView as above. Tar up
the /usr/OVxxx backup directory. Ship the tar ball to the new box. Do
all the pre-req stuff. Untar the backup. Do an UPDATE install - even
though this new tin has never seen NetView, the update flag says to go
and look for a backup and to apply all that database / customisation
once NetView is installed. Once the install is done, you may need to
run /usr/OV/service/reset_ci and you should be away. If you are going
to a new box, I would try and put it on the same network as the old one
as NetView does tend to have a sense of "where it is" in the network.
It certainly doesn't have to be the exact same address though - that way
you can run the old and new systems in parallel until you are happy.
Feel free to go and get my document about "Tivoli on Linux" from the
NetView TUG site if you wish -
http://www.nv-l.org/twiki/bin/view/Netview/TivoliLinux . Better still -
extend the document or write a similar one for RHEL 3.0 so that the next
folk going around the loop have more experiences to draw on!
Cheers,
jane
Michael Elleby III wrote:
I'm interested in this also, as I am working on a move of a server from
6.0.2 to 7.1.4.. The key to my issue is, the current NetView box is not in
my TMR. It exists in a TMR that went away, thus the added complexity to my
problem.
Are you upgrading the Linux on your server, or are you migrating to a new
box?
Thanx.
Mike-
----- Original Message -----
From: "Mahesh Tailor" <mahesh.tailor@network.carilion.com>
To: "NetView User List" <nv-l@lists.us.ibm.com>
Sent: Friday, March 11, 2005 11:02 AM
Subject: [nv-l] NetView Move
Hello,
Old system:
- Netview 7.1.3 fp3
- RedHat Linux 2.1 AS
New system:
- Netview 7.1.4 fp2
- RedHat Linux 3.0 AS
I am moving my Netview application for one machine to another. As you
can see, I will be going from 7.1.3 on the old machine to 7.1.4 on the
new machine.
I would like to take the map from the old system and use it on the new
system. Can I do this? If so, how?
TIA
Mahesh
--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2005 Jane Curry <jane.curry@skills-1st.co.uk>. All rights
reserved.
|