Re: TSM 5.2.x/AIX 5.1 upgrade issue/question

        Hmm, I know that we have updated the Atape software in the past
and have not needed a reboot to use it, but in our current procedure, we
are getting a reboot after the update...

        This is 1000-foot view of the process we are using:
        - Use our NIM server to do an "alt-disk-migration" of the OS to
AIX5.2.
        - Reboot onto the AIX 5.2. (not bring up the TSM server at this
point)
        - Fix all the little things that need tweaking after the OS
upgrade (ssh, NIS+, BMC agent, sendmail, dump device, etc).
        - Change links to boot in 64-bit mode.
        - Update Atape and atldd drivers (with the "rmdev" and "cfgmgr"
of them).
        - Reboot again (Primarily to get into 64-bit mode, but is also
helpful in making sure all daemons and such work on reboot).
        - Rip out all Tivoli software.
        - Install 64-bit versions of server 5.2.0.0 then patch to
5.2.1.0 & 5.2.1.3.
        - Install 64-bit client version 5.2.0.0.
        - Start it all up.

        This method has worked for us so far (knock on wood).

Ben

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David E Ehresman
Sent: Friday, December 12, 2003 9:02 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM 5.2.x/AIX 5.1 upgrade issue/question


You did reboot and reconfigure the drives to AIX, right?

>>> zforray AT VCU DOT EDU 12/12/2003 9:17:18 AM >>>
This seems to be a hot topic, so let me add another log to the fire.

We recently upgraded our test TSM AIX server to AIX 5.1.  Then we
upgraded the TSM server to 5.2.0.0.

Unfortunately, I missed the part about having to upgrade ATAPE to 8.2.x
(it was still at 7) *BEFORE* upgrading TSM.

Therefore, the 3590 drive isn't being recognized by TSM (AIX says it is
peach-keen).

Upgraded ATAPE to 8.3.x, but still no joy in Mudville !!!  Even tried
removing and reinstalling the ADSM/TSM drivers.

How do you resolve this ?

Will upgrading TSM to 5.2.1.3 (yes, we discovered you must upgrade to
5.2.1.x before you can install 5.2.1.3 !!) correct this oversight ?