Summary. upgrade from TCR 1.4a to 1.5/4.0B to 4.0D

From: Alan Garde <alan.garde_at_transport.uk.eds.com>
Date: Fri, 11 Sep 1998 13:43:13 +0100

Most people seem to experience no problems going from TCR 1.4a to 1.5/4.0B to 4.0D, there are a few useful comments below.

The main points people make are:

1) Read the manual thoroughly and don't try to take any shortcuts
2) Check your firmware revisions carefully
3) Make sure DU patch kit 2 and the latest TCR patch are applied.


After that everything should be fine.

thanks,

Alan

---
>From Chris Ruhnke
Actually, all in all, the upgrade went fairly smoothly.  We have about 20
HSZ40/HSZ50 host-based RAIDsets with numerous LSM volumes and AdvFS filesets
so the preliminary work -- running AdvFS verify on all AdvFS filesets --
took most of Saturday.  We missed one page of the firmware upgrade release
notes and did not know to 1) save a copy of console environment variable
settings and 2) run "build -e" on each CPU after the upgrade (Cf. p 1-8 in
the 8200/8400 release notes).  Your update may be different -- RTFM!
Installing the 4.0D update, layered products, DU Patch Kit #2, TruCluster
1.5 and TCR Patch Kit 11AUG went smoothly.  The systems booted up.  TCR
configured, services came online and everybody seems happy.  Again RTFM
for the TCR update.  And read it BEFORE you try the UNIX update.  There
are instructions for updating UNIX without deinstalling TCR if you want
to come up on V4.0D/1.4 first and then do the TCR 1.5 or you need to 
deinstall TCR before you upgrade UNIX.  One gotcha that bit me this time
was that TCR expects the lmf license manager to be running when you 
run the setld -d.  TCR before 1.4 did not require this.  I thought I
knew what I was doing -- I just skimmed the Fine Manual.  Good ole UNIX
Chomp!  Chomp!  It'll bite you at any opportunity...  Oh well, just restored
/, /usr, /var and started over... 
We've had some small complaints about things that "used to work on V4.0A"
and don't work now...  But there's been a workaround or else a recompile
rebuild fixed things...
>From Ravidan S.
Hi,
        We recently upgraded from 4.0b/TCR 1.4 (not 1.4A) to 4.0d/TCR150
in an ASE environment. Overall the upgrade was pretty smooth.
Points to note:
(1) The TCR 1.5 release notes gives a big list for the Hardware
revisions. Please check that out. We had a couple of RZ28Bs at lower
revisions which had to be upgraded.
(2) TCR 1.5 needs KZPSA at firmware rev 11 .But firmware rev 11 of KZPSA
requires a patch for 4.0D. Hence if using KZPSA then upgrade the frmware
for other hardware then upgrade to 4.0D ,apply the DU patch ,then
upgrade KZPSA , then install TCR1.5 .
(3) Install the DU Patch kit 2 & TCR patch also. We had a few
segmentation fault problems with the TCR1.5 before installing the TCR
patches.
>From Richard Price:
 One thing to be aware of if you haven't heard about it already.
 Following the 4.0D upgrade a cron entry will be added to perform nightly
 advfs defragments - called defragcron. It might be an idea to comment this
 out, as it tends to do things like corrupt filesystems and crash systems. At   
 present there are a couple of ways round it:-
 o Don't use defragcron.
 o Wait for DUNIX V5, where advfs is supposedly re-engineered to fix it.
 o Increase the size of the domain log file.                                  
Original Message
> 
>  Hi,
> 
>  Does anyone have any experiences/gotcha's for doing the upgrade from 4.0B 
>  to 4.0D in a TruCluster environment?  We are considering upgrading to 4.0D 
>  for Y2K compliancy in a AlphaServer 4000 Available Server TruCluster 1.4A    
>  environment.  We will be upgrading each node in turn and reintroducing them >
to   the cluster.
> 
>  Has anyone had any problems with TCR1.5/DU 4.0D?
>  Has anyone has any problems during the upgrade?
> 
>  Has anyone got any comments?
> 
> 
>  cheers,
> 
>  Alan
> 
> 
                                                                        ""

Received on Fri Sep 11 1998 - 12:46:15 NZST