Conference tuxedo::dce-products

2174.0. "Does DCE store/use ethernet addresses ??" by RTOMS::DRECHSELM () Mon Mar 03 1997 07:40

	I have two questions about DCE ..

	1: A few days ago, we upgraded a systemdisk from a 3 system
	   VMS cluster from VMS V6.1 to VMS V6.2 (including all 
	   required layered products). The system disk was taken
	   from the customers site, in order to do the upgrade not
	   on the live system. The system where we did the upgrade
	   was 2 system VMS cluster.

	   After that, DCE was not startable anymore. The effect was,
	   that in DCE$SPECIFIC:[VAR.SECURITY.CREDS] thousands of files
	   have been created, an no dce_login was possible anymore.

	   After a clobber and re-configure, everythis was as expected
	   (at least on two systems).

	?: I always thought that a VMS upgrade does NOT require a DCE
	   reconfigure?? Is that true?? My experiance would proof the
	   opposite!

	2: As already said, the "upgrade system" is a 2 node cluster,
	   while the "live system" is a 3 node cluster. We always kept
	   the DCE master server up and booted the 2nd system on time
	   to the 2nd live system or to the 3rd live system. 

	   Now, while configuring the 2nd live system showed no problem,
	   I was not able to add a CDS replica to the 3rd system. It just
	   hang a "create replica".

	?: Could the fact, that now live system 2 and 3 have the "same"
	   hardware interface address, cause problems here? In other
	   words, does DCE somehow store/use the ethernet address of the
	   systems in the configuration??


	Thanks for any help ...

	Manfred Drechsel

>      ?: I always thought that a VMS upgrade does NOT require a DCE
>           reconfigure?? Is that true?? My experiance would proof the
>           opposite!

Normally, this is true.  As long as you upgrade on the same system
that you've been running on (see below), everything will work fine.

>       ?: Could the fact, that now live system 2 and 3 have the "same"
>           hardware interface address, cause problems here? In other
>           words, does DCE somehow store/use the ethernet address of the
>           systems in the configuration??

You've discovered the root of the problem.  DCE does indeed store/use the
Ethernet address of the systems.  This is used as part of the many UUIDs
which are needed by DCE to uniquely identify objects.  I believe that you
would find the same thing happening on any DCE platform where you did this
kind of manipulation during an upgrade, since this problem stems from standard
OSF DCE code.