Conference decwet::hsm-4-unix

236.0. "How to upgrade DU when RW536 is involved?" by SWETSC::HAGLUND () Fri Apr 11 1997 08:22

			Hello!

	  Swedish Landsurvey has a RW536 running on a DEC3000 - M400
	with DU V3.0 (Rev. 347). They have tried to upgrade this
	machine a while ago to v3.2C, but didn't succeed because they 
	couldn't get the /dev/mc21 device to connect to the drive.
	
	They used their backup to go back to v3.0. Now I got this
	blitz telling me that v3.0 will be unsupported 1-jul-1997 so
	we have to upgrade this machine to v3.2G. I have read note
	212 in this conferance and I hope there is no problem to
	upgrade to v3.2G. Are there any known patches that should
	be installed (except for thoose found in DUV32GAS00001-19970328.tar)?

	I have no experience in using/managing the optical device
	RW536 so I want to make sure we are on the right track
	with theese upgrade steps.

	Do we need to remove CLCMC220, CLCOP220 and NJAPOLYHSM121
	before the upgrade? If we have to do that, will the customers
	HSM configuration remain when installing the newer versions
	of CLC (CLCMC311 and CLCOP311)?

	 This is what I hope will work:

	1. Remove CLCMC220, CLCOP220 and NJAPOLYHSM121 (+ other layered prod.
	   that are described in Release Notes.
        2. Installupdate to v3.2.
	3. Upgrade firmware to SRM V6.9.
        4. Installupdate to v3.2C
	5. Upgrade install to v3.2G.
	6. Reinstall NJAPOLYHSM121 and install CLCMC311 + CLCOP311.

	Now the $1000000 question :-)

	Will the Optical thing work? Or do I have to do a major rebuild
	of everything?

	 I have heard a rumour that says there is a "end of life" of the
	HSM/RW536 products. Is this true or false?

	Regards,

	Tomas Haglund
	UNIX support SWEDEN

Hello, Tomas!

> They have tried to upgrade this
> machine a while ago to v3.2C, but didn't succeed because they 
> couldn't get the /dev/mc21 device to connect to the drive.

There is only one order of installation that works, which is almost exactly
what you described.  The only difference is that CLC must be installed before
HSM.  So the order is:

  Deinstall CLCMC220, CLCOP220, NJAPOLYHSM121, other layered products (order
    doesn't matter).
  Upgrade the os.
  Install other layered products.
  Install CLCMC311 and CLCOP311.
  Install NJAPOLYHSM121.

The deinstallation of HSM will leave the HSM configuration in place, but it
would be good to make a copy of the /usr/efs and /usr/efs/jmd_data directories,
in case something happens during the os upgrade.  (They don't need to copy the
binaries like /usr/efs/bin.)

-- Pat Tressel

Tomas --

I forgot one thing:  After the upgrade, and after installing CLC and HSM and
rebuilding the kernel and rebooting, it may also be necessary to delete
/dev/mc* and /dev/op* and recreate them using /dev/MAKEDEV.MC and
/dev/MAKEDEV.OP.  For instance (using mc21 and op20 as examples),

  rm /dev/mc21
  /dev/MAKEDEV.MC mc21
  rm /dev/*op20*
  /dev/MAKEDEV.OP op20
  ...

(In a previous case, the major number assigned to the mc or op devices changed,
but the old files were still there, and so had the wrong major numbers.)

-- Pat

    Thanks, Pat!
    
    I really appreciate your reply!
    
    Best Regards,
    
    Tomas