Entegrity DCE and DFS for HP Tru64 UNIX
Installation and Configuration Guide

Software Version 4.3.1

[Previous] [Next] [Contents] [Index]

1.1 Overview of License Registration

The License Product Authorization Key (PAK) is no longer needed. The written license is still in effect.

1.2 Installation Options

Entegrity® DCE for Tru64 UNIX provides the additional option of installing DCE in a Dataless Management System (DMS) environment. You can find instructions for a DMS installation on Section 1.13 on page 41.

1.3 Installation Prerequisites

Follow this sequence for installing DCE and creating a cell with servers and clients:

1. Install the DCE software.

2. Create a cell.

3. Configure a client after you create your cell.

NOTE: You can stop the installation procedure at any time by pressing <Ctrl/C>. Files created up to that point are not deleted. You must delete the created files manually.

1.3.1 Hardware Requirements

To perform the installation, you need the following hardware:

• A Tru64 UNIX version 5.1 machine, minimum 96 MB memory
  
• A CD-ROM drive for reading the distribution media
  

You must know how to load the CD-ROM provided with the software distribution kit on the appropriate drive. See the Compact Disc User's Guide for more information.

1.3.2 Software Requirements

To perform the installation, you need a system with the Tru64 UNIX Version 5.1 operating system installed. To determine the version number of your operating system, enter the following command:

# sizer -v

Before installing DCE, you must install the following subsets provided with the operating system:

• Document Preparation Tools (OSFDCMT) — This subset is a prerequisite for using the DCE reference pages (manpages); it includes text-processing tools and several macro packages.
  
• Software Development Environment (OSFPGMR) — This subset is a prerequisite if you want to build DCE applications with the Application Developer's Kit subset; it contains include files required by DCE applications.
  
• Standard Header Files (OSFINCLUDE) — This subset is a prerequisite if you want to build DCE applications with the Application Developer's Kit subset; it contains header files required by DCE applications.
  

The table below lists the disk storage requirements for the subsets installed with the DCE kit.

Table 1-1: Disk Space Requirements for DCE Subsets

Subset Name	Disk Space (in Megabytes)
DCERTS410	19.0
DCECDS410	1.0
DCESEC410	3.0
DCEADK410	1.4
DCEMAN410	1.0
DCEADKMAN410	1.3
DCEDFS410	3.5
DCEDFSBIN410	2.4
DCEDFSUTL410	1.0
DCEDFSMAN410	1.0
DCEDFSNFSSRV410	1.0
TOTAL (for all subsets)	35.6

An initial DCE server configuration (consisting of dced, cdsd, cdsadv, two cdsclerks, secd, and dtsd) consumes 50 MB of swap space. A DCE client configuration (consisting of dced, cdsadv, one cdsclerk, and dtsd) consumes 25 MB of swap space. Large cell configurations may require additional swap and disk space.

1.3.4 Privileges Required

You must have superuser (root) privileges on the system on which you are installing DCE.

1.4 Performing a DCE Cell Backup

Entegrity Solutions® recommends that you back up your system disk before installing any software. Use the backup procedures established at your site. For details on backing up a system disk, see your Tru64 UNIX documentation. To back up DCE databases from an existing configuration, Entegrity recommends that you back up files in /opt/dcelocal and /krb5 by using the following command:

tar cf $ DCE_BACKUP_DIR/dcebackup.tar \

./krb5 \

./opt/dcelocal/*.db \

./opt/dcelocal/etc \

./opt/dcelocal/var/adm/directory/cds/clerk_mgmt_acl_* \

./opt/dcelocal/var/adm/security \

./opt/dcelocal/var/adm/time/dtsd.acl \

./opt/dcelocal/var/audit \

./opt/dcelocal/var/dced \

./opt/dcelocal/var/dfs \

./opt/dcelocal/var/directory \

./opt/dcelocal/var/svc/routing \

./opt/dcelocal/var/security

NOTE: The above command does not contain the full list of files under the /opt/ dcelocal/ directory. Additionally, any DCE application specific files and directories may need to be archived as well. Such files include, but are not limited to, application specific local keytable files.

1.5 Re-Installing DCE Over an Older Version of DCE

Before reinstalling either the current version or a new version of the Entegrity DCE for Tru64 UNIX software, perform the following steps:

Remove existing DCE software subsets.

To determine whether any existing subsets have been installed, enter the following command:

# setld -i | grep DCE | grep "_ _installed"

(The _ _ indicates to enter two spaces)

If a subset is installed, you see a display similar to the following:

DCECDS410 installed       DCE CDS Server V4.1

If the subset has not been installed, the words not installed appear in the middle column. (prior to v5.0a this came up as blank; but if installed, it said installed.)

Delete any existing DCE subsets as follows:

# setld -d subset-id [subset-id...]

where subset-id is the subset name and version number. For example, to delete the Runtime Services subset, enter this command (where 410 is the subset version number):

# setld -d DCERTS410

Re-execute the setld command to reinstall the DCE kit where kit_location is the directory containing the DCE subsets:

# setld -l <kit_location>

If you do not want to delete your current DCE configuration, answer n when the installation procedure displays the following prompt:

Directory /opt/dcelocal exists.  It may contain the DCE databases.

Do you want to delete the old DCE databases? (y/n/?) [n]:

DCE includes the following installation subsets:

Table 1-2: Subsets

Subset Name	Essential Information
DCE Application Developer's Kit V4.1 (DCEADK410)	This subset includes the RPC IDL compiler, XDS interface to CDS, and other tools required for developing DCE applications.
DCE Application Developer's Kit Manual Pages V4.1 (DCEADKMAN410) (optional)	This subset consists of online application development reference pages (manpages) for programming reference information.
DCE CDS Server V4.1 (DCECDS410)	This subset provides a directory service for naming and locating users, applications, files, and systems within a DCE cell. This subset includes the CDS server and the Global Directory Agent (GDA).
DCE Command Manual Pages V4.1 (DCEMAN410)(optional)	This subset consists of online reference (manpages) pages for managing DCE. It also includes HTML versions of OSF and Entegrity documentation.
DCE DFS Base OS Services V4.1 (DCEDFS410)	The DCEDFS (runtime) subset has to be installed to use the DCE Distributed File Service.
DCE DFS Kernel Binaries V4.1 (DCEDFSBIN410)	The DCEDFSBIN subset must be installed to use DCE/DFS.
DCE DFS Command Manual Pages V4.1 (DFSMAN410) (optional)	This subset consists of online reference (manpages) pages for managing DFS.
DCE DFS NFS-DFS Secure Gateway Server V4.1 (DCEDFSNFSSRV410)	The DCEDFSNFSSRV subset must be installed to use the NFS-DFS Secure Gateway Server.
DCE DFS Utilities and Debugging Tools V4.1 (DCEDFSUTIL410)	This subset is optional. These are primarily diagnostic programs and are not part of normal use. They do not need to be installed to use DCE/DFS, although they can make it easier to diagnose problems or run DCE/DFS tests.
DCE Runtime Services V4.1 (DCERTS410)	This subset consists of base services required for the runtime execution of DCE applications. These services include the RPC runtime and DTS clerk and server. The CDS clerk, the security client, the PC Nameserver Proxy Agent, XDS runtime, (nsid), and various administrative utilities are also included in this subset. You must install this subset on all systems on which you want to run DCE applications.
DCE Security Server V4.1 (DCESEC410)	This subset provides secure communications and controlled access to resources in a distributed environment. It includes the registry/KDC/Privilege server (secd) and security administration tools (sec_admin).

See the Entegrity DCE for Tru64 UNIX Product Guide for more information about the subsets included in this kit.

1.7 Installation Steps For a Non-TruCluster Environment

Be aware before you begin:

• Databases can be saved and reused from prior releases. The installation procedure asks whether you want to delete them or not. To make sure databases are saved, do not use clean or clobber when performing the installation. Also, databases in V1.3 format can be converted to V2.0 format.

• If you want to stop the installation at any point, press <Ctrl/C>; however, you must then delete any subsets that have been created up to that point. To delete the subsets, perform the steps in step 2 below.:

STEPS

1. Log in as superuser (login name root) to the system on which you are installing the DCE software.

2. Remove existing DCE software subsets (kits).

   To determine whether any existing subsets have been installed, enter the following command:

   # setld -i | grep DCE | "grep_ _installed"
   

   (The _ _ indicates to enter two spaces.)

   If a subset is installed, you see a display similar to the following:

   DCECDS410       installed       DCE CDS Server V4.1
   

   If the subset has not been installed, the words "not installed" appear in the middle column. (prior to v5.0a this came up as blank; but if installed, it said installed.)

   To remove the existing DCE subsets, use the following syntax:

   # setld -d subset-id [subset-id...]
   

   where subset-id is the subset name and version number. For example, to delete the Runtime Services subset, enter this command where xxx is the subset version number:

   # setld -d DCERTSxxx 
   

3. After deleting any previous versions of DCE software, you can load the subsets in the DCE software either by changing directories to where the software is placed, then entering the setld command OR you can enter the setld command followed by the location where the software is placed, as in the following examples:

   # cd <kit_location>
   

   # setld -l 
   

   If you mounted the DCE CDROM on the /mnt/ directory, then the kit 
   location is /mnt/kit 
   

   OR
   

   # setld -l  <kit_location> 
   

   # setld -l /mnt/kit
   

4. After several seconds, the installation procedure displays the names of the optional subsets and prompts you to specify the subsets that you want to install.

   The subsets listed below are optional:
   

   There may be more optional subsets than can be presented on a single 
   

   screen. If this is the case, you can choose subsets screen by screen
   

   or all at once on the last screen. All of the choices you make will
   

   be collected for your confirmation before any subsets are installed.
   

        1) DCE Application Developers Kit V4.1
   

        2) DCE Application Developers Manual Pages V4.1
   

        3) DCE Cell Directory Server V4.1
   

        4) DCE Command Reference Manual Pages V4.1
   

        5) DCE DFS Base V4.1
   

        6) DCE DFS Kernel Binaries V4.1
   

        7) DCE DFS Man Pages V4.1
   

        8) DCE DFS NFS-DFS Secure Gateway Server V4.1
   

        9) DCE DFS Utilities/Debug V4.1
   

       10) DCE Runtime Services V4.1
   

       11) DCE Security Server V4.1
   

   Or you may choose one of the following options:
   

       12) ALL of the above
   

       13) CANCEL selections and redisplay menus
   

       14) EXIT without installing any subsets
   

   Enter your choices or press RETURN to redisplay menus.
   

   Choices (for example, 1 2 4-6):12
   

   Load the subsets that you want to install.

   NOTE: For a minimum cell configuration, choose options 3, 10, and 11. If you specify more than one at the prompt, separate each number with a space, not a comma.

5. Next, the installation procedure lets you verify your choice. For example, if you enter 12 in response to the previous prompt, you see the following display:

   You are installing the following optional subsets:
   

           DCE Application Developers Kit V4.1
   

           DCE Application Developers Manual Pages V4.1
   

           DCE Cell Directory Server V4.1
   

           DCE Command Reference Manual Pages V4.1
   

           DCE DFS Base V4.1
   

           DCE DFS Kernel Binaries V4.1
   

           DCE DFS Man Pages V4.1
   

           DCE DFS NFS-DFS Secure Gateway Server V4.1
   

           DCE DFS Utilities/Debug V4.1
   

           DCE Runtime Services V4.1
   

           DCE Security Server V4.1
   

   Is this correct? (y/n):y
   

   If the subsets displayed are those you want to install, enter y. The installation procedure then checks the system space.

   Checking file system space required to install selected subsets:
   

   File system space checked OK.
   

   11 subset(s) will be installed.
   

   The installation procedure displays the subsets being installed.

   Loading 1 of 11 subset(s)....
   

   DCE Runtime Services V4.1
   

      Copying from  (disk)
   

           Working... Fri Mar 12 07:19:26 EST 2000
   

      Verifying
   

   Loading 2 of 11 subset(s)....
   

   DCE Security Server V4.1
   

      Copying from   (disk)
   

      Verifying
   

   Loading 3 of 11 subset(s)....
   

   DCE Cell Directory Server V4.1
   

      Copying from   (disk)
   

      Verifying
   

   Loading 4 of 11 subset(s)....
   

   DCE Application Developers Kit V4.1
   

      Copying from   (disk)
   

           Working.... Fri Mar 12 07:19:26 EST 2000
   

      Verifying
   

   Loading 5 of 11 subset(s)....
   

   DCE Command Reference Manual Pages V4.1
   

      Copying from   (disk)
   

      Verifying
   

   Loading 6 of 11 subset(s)....
   

   DCE Application Developers Manual Pages V4.1
   

      Copying from   (disk)
   

           Working.... Fri Mar 12 07:19:26 EST 2000
   

      Verifying
   

   Loading 7 of 11 subset(s)....
   

   DCE DFS Base V4.1
   

      Copying from   (disk)
   

      Verifying
   

   Loading 8 of 11 subset(s)....
   

   DCE DFS Kernel Binaries V4.1
   

      Copying from   (disk)
   

      Verifying
   

   Loading 9 of 11 subset(s)....
   

   DCE DFS Utilities/Debug V4.1
   

      Copying from   (disk)
   

      Verifying
   

   Loading 10 of 11 subset(s)....
   

   DCE DFS Man Pages V4.1
   

      Copying from   (disk)
   

      Verifying
   

   Loading 11 of 11 subset(s)....
   

   DCE DFS NFS-DFS Secure Gateway Server V4.1
   

      Copying from   (disk)
   

      Verifying
   

   11 of 11 subset(s) installed successfully.
   

   Configuring "DCE Runtime Services V4.1" (DCERTS410)
   

       Copyright (c) Entegrity Solutions, Inc.      2000, 2001
   

       Copyright (c) Digital Equipment Corporation, 1996, 1997, 1998, 1999
   

       All Rights Reserved.  Unpublished rights reserved
   

       under the copyright laws of the United States.
   

       Possession, use, or copying of the software and
   

       media is authorized only pursuant to a valid written
   

       license from Entegrity Solutions, Inc.
   

       RESTRICTED RIGHTS LEGEND   Use, duplication, or
   

       disclosure by the U.S. Government is subject to
   

       restrictions as set forth in Subparagraph (c)(1)(ii)
   

       of DFARS 252.227-7013, or in FAR 52.227-19, as
   

       applicable.
   

At the end of the installation procedure, the screen displays the following message and asks-----if you have existing DCE databases from a previous configuration-----whether you want to delete them:

=============================================================

Beginning configuration of DCE Version 4.1.

You will be asked a few questions before configuration can proceed. 

Online help is available where the prompt contains a "?" choice.

=============================================================

If DCE was installed previously, the following message is displayed:

Directory /opt/dcelocal exists. It may contain the DCE databases.

Do you want to delete the old DCE databases? (y/n/?) [n]:

You might have existing DCE local databases. These databases can contain information from your previous DCE configuration. This information includes your cell name, the cell namespace database, security credentials, and the DCE services you used in the previous configuration. The installation script will make the DCE databases specific for each of the cluster members.

If you type "n" or press <return> (the default), you preserve the old DCE configuration.

If you type "y", you delete the old configuration and the following message displays:

The existing DCE databases will be removed upon the

successful completion of installation of DCERTS410.

IMPORTANT:

For SECURITY reasons, you may want to make sure that the location you will 
type now is native to this host; i.e., is not NFS mounted!

The configuration portion automatically creates local copies of files in the DCE permanent file system and other files and directories required to run the DCE services.

The installation procedure prompts you to choose a directory under which these local files are to be located:

Please enter the location for new DCE local databases,

or press <RETURN> for the default location [/var]:

You can specify the default or enter another directory name; the directory is created if it does not already exist. The entire directory tree initially requires about 100 KB of disk space; it requires more space as you use the DCE services. The installation procedure now completes installation of the subsets.

Whether you entered yes or no, the following lines show:

There will be no more questions asked for the remainder of the configuration.

Creating DCE local directory structure.

If you had answered yes, to delete old databases, two lines follow here:

Removing old DCE local databases as directed. 

	Created new DCE local database directory /opt/dcelocal

Whether you entered yes or no, the following lines show:

===================================================================

Installation of all the requested DCE subsets is completed.

You have installed the DCE software which requires further action

to configure and start it. To do so please invoke "/usr/sbin/dcesetup"

and select option 1 (Configure DCE services) from the main menu.

===================================================================

If errors occur during the installation, the system displays failure messages. Errors can occur during the installation if any of the following conditions exist:

• The prerequisite software version is incorrect.
  
• The system parameter values (such as disk space) for this system are insufficient for successful installation.
  
• A previous DCE version is installed on the system.
  

If the installation fails because of insufficient disk space, the setld procedure displays an error message similar to the following:

There is not enough file system space for subset DCERTS410

DCERTS410 will not be loaded.

If the usr file system is read-only during installation, the procedure displays the following error message:

Warning: The usr filesystem is not writable. Therefore links from it to the 
permanent filesystem will not be made.

When the Tru64 UNIX system displays this message, the installation of the shared DCE library fails. In this case, the DCE services can not be configured or started because they rely on the shared DCE library. You should reinstall with a writable usr file system.

If you encounter errors from the setld utility during the installation, see the Diagnostics section of the setld(8) reference page for an explanation of the error and the appropriate action to take. If an error occurs while you are using DCE, and you believe the error is caused by a problem with the product, contact Entegrity Technical Support (support@entegrity.com).

1.10 Installing DCE in a TruCluster or Sierra Cluster Environment

For cluster installations, the installation scripts first install the common files to shared cluster locations, then to the member template area (member 0), and then onto each of the members in member specific locations.

Be aware before you begin:

• If Installing DFS: first configure DCE with dcesetup, then configure DFS with dfssetup. Dfssetup is described in Entegrity DCE for Tru64 UNIX Distributed File Service (DFS) Configuration Guide.

• DMS is not supported in a clustered environment though it is supported in a non-clustered environment.

• It is preferrable to install on a cluster rather than on a specified member. Unless specified to install on a specific member using the member installation switch provided by the setld command, DCE is installed on all members of a cluster.

  To find a member's status enter:

  # setld -i -m < cluster member name>

  (where i means the kit installation inventory and m means member. The man pages explain setld.)

• Databases can be saved and reused from prior releases. The installation procedure asks whether you want to delete them or not. To make sure databases are saved, do not use clean or clobber when performing the installation. Also, databases in V1.3 format can be converted to V2.0 format.

• If you want to stop the installation at any point, press <Ctrl/C>; however, you must then delete any subsets that have been created up to that point. To delete the subsets, perform the steps in step 2 below.:

STEPS

1. Log in as superuser (login name root) to the system on which you are installing the DCE software

2. Remove existing DCE software subsets(kits).

   To determine whether any existing subsets have been installed, enter the following command:

   # setld -i | grep DCE | "grep_ _installed"
   

   (The _ _ indicates to enter two spaces.)

   If a subset is installed, you see a display similar to the following:

   DCECDS410       installed       DCE CDS Server V4.1
   

   If the subset has not been installed, the words "not installed" appear in the middle column. (prior to v5.0a this came up as blank; but if installed, it said installed.)

   To remove the existing DCE subsets, use the following syntax:

   # setld -d subset-id [subset-id...]
   

   where subset-id is the subset name and version number. For example, to delete the Runtime Services subset, enter this command where xxx is the subset version number:

   # setld -d DCERTSxxx 
   

3. After deleting any previous versions of DCE software, you can load the subsets in the DCE software either by changing directories to where the software is placed, then entering the setld command OR you can enter the setld command followed by the location where the software is placed, as in the following examples:

   # cd <kit_location>
   

   # setld -l 
   

   If you mounted the DCE CDROM on the /mnt/ directory, then the kit 
   location is /mnt/kit.
   

   OR
   

   # setld -l  <kit_location> 
   

   # setld -l /mnt/kit
   

4. After several seconds, the installation procedure displays the names of the optional subsets and prompts you to specify the subsets that you want to install.

   NOTE: The example here is to install without DFS, in order to later show installing DFS. You can install DFS in the original installation.

   The subsets listed below are optional:
   

   There may be more optional subsets than can be presented on a single 
   

   screen. If this is the case, you can choose subsets screen by screen
   

   or all at once on the last screen. All of the choices you make will
   

   be collected for your confirmation before any subsets are installed.
   

        1) DCE Application Developers Kit V4.1
   

        2) DCE Application Developers Manual Pages V4.1
   

        3) DCE Cell Directory Server V4.1
   

        4) DCE Command Reference Manual Pages V4.1
   

        5) DCE DFS Base V4.1
   

        6) DCE DFS Kernel Binaries V4.1
   

        7) DCE DFS Man Pages V4.1
   

        8) DCE DFS NFS-DFS Secure Gateway Server V4.1
   

        9) DCE DFS Utilities/Debug V4.1
   

       10) DCE Runtime Services V4.1
   

       11) DCE Security Server V4.1
   

   Or you may choose one of the following options:
   

       12) ALL of the above
   

       13) CANCEL selections and redisplay menus
   

       14) EXIT without installing any subsets
   

   Estimated free diskspace(MB) in root:285.6 usr:636.3 var:1140.9
   

   Enter your choices or press RETURN to redisplay menus.
   

   Choices (for example, 1 2 4-6):1-4 10 11
   

5. Load all but the DFS subsets.

   NOTE: If you specify more than one at the prompt, separate each number with a space, not a comma.

   NOTE: While, in this example all DCE kits are installed, it is recommended that you only install the Command Reference Manual Pages and the Runtime Services in a cluster environment ( : 4 10 ). The others might work, but are not fully tested, so are not supported. Also, before loading the kits, make sure that you have the proper license.

        1) DCE Application Developers Kit V4.1
   

        2) DCE Application Developers Manual Pages V4.1
   

        3) DCE Cell Directory Server V4.1
   

        4) DCE Command Reference Manual Pages V4.1
   

       10) DCE Runtime Services V4.1
   

       11) DCE Security Server V4.1
   

6. Next, the installation procedure lets you verify your choice. For example, if you enter 1-4 10 11 in response to the previous prompt, you see the following display:

   You are installing the following optional subsets:
   

           DCE Application Developers Kit V4.1
   

           DCE Application Developers Manual Pages V4.1
   

           DCE Cell Directory Server V4.1
   

           DCE Command Reference Manual Pages V4.1
   

           DCE Runtime Services V4.1
   

           DCE Security Server V4.1
   

   Estimated free diskspace(MB) in root:285.6 usr:265.7 var:1140.3
   

   Is this correct? (y/n):y
   

   Checking file system space required to install selected subsets:
   

   File system space checked OK.
   

   6 subsets will be installed.
   

   Loading subset 1 of 6 ...
   

   DCE Runtime Services V4.1
   

      Copying from . (disk)
   

   	Working....Mon Mar 12 14:51:41 EST 2001
   

      Verifying
   

   Loading subset 2 of 6 ...
   

   DCE Security Server V4.1
   

      Copying from . (disk)
   

      Verifying
   

   Loading subset 3 of 6 ...
   

   DCE Cell Directory Server V4.1
   

      Copying from . (disk)
   

      Verifying
   

   Loading subset 4 of 6 ...
   

   DCE Application Developers Kit V4.1
   

      Copying from . (disk)
   

      Verifying
   

   Loading subset 5 of 6 ...
   

   DCE Command Reference Manual Pages V4.1
   

      Copying from . (disk)
   

      Verifying
   

   Loading subset 6 of 6 ...
   

   DCE Application Developers Manual Pages V4.1
   

      Copying from . (disk)
   

   	Working....Mon Mar 12 14:52:54 EST 2001
   

      Verifying
   

   6 of 6 subsets installed successfully.
   

       Copyright (c) Entegrity Solutions, Inc.      2000, 2001
   

       Copyright (c) Digital Equipment Corporation, 1996, 1997, 1998, 1999
   

       All Rights Reserved.  Unpublished rights reserved
   

       under the copyright laws of the United States.
   

       Possession, use, or copying of the software and
   

       media is authorized only pursuant to a valid written
   

       license from Entegrity Solutions, Inc.
   

       RESTRICTED RIGHTS LEGEND   Use, duplication, or
   

       disclosure by the U.S. Government is subject to
   

       restrictions as set forth in Subparagraph (c)(1)(ii)
   

       of DFARS 252.227-7013, or in FAR 52.227-19, as
   

       applicable.
   

During the installation procedure, the screen displays the following message and asks-----if you have existing DCE databases from a previous configuration-----whether you want to delete them:

=============================================================

Beginning configuration of DCE Version 4.1.

You will be asked a few questions before configuration can proceed. 

Online help is available where the prompt contains a "?" choice.

=============================================================

If DCE was installed previously, the following message is displayed:

Directory /opt/dcelocal exists. It may contain the DCE databases.

Do you want to delete the old DCE databases? (y/n/?) [n]:

You might have existing DCE local databases. These databases can contain information from your previous DCE configuration. This information includes your cell name, the cell namespace database, security credentials, and the DCE services you used in the previous configuration. The installation script will make the DCE databases specific for each of the cluster members.

If you type "n" or press <return> (the default), you preserve the old DCE configuration.

If you type "y", you delete the old configuration and the following message displays:

The existing DCE databases will be removed upon the

successful completion of installation of DCERTS410.

IMPORTANT:

For SECURITY reasons, you may want to make sure that the location you will 
type now is native to this host; i.e., is not NFS mounted!

The configuration portion automatically creates local copies of files in the DCE permanent file system and other files and directories required to run the DCE services.

The installation procedure prompts you to choose a directory under which these local files are to be located:

Please enter the location for new DCE local databases,

or press <RETURN> for the default location [/var]:

You can specify the default or enter another directory name; the directory is created if it does not already exist. The entire directory tree initially requires about 100 KB of disk space; it requires more space as you use the DCE services. The installation procedure now completes installation of the subsets.

Whether you entered yes or no, the following lines show:

=============================================================

There will be no more questions asked for the remainder of the configuration.

Creating DCE local directory structure.

=============================================================

If you had answered yes, to delete old databases, two lines follow here:

Removing old DCE local databases as directed. 

	Created new DCE local database directory /opt/dcelocal

Whether you entered yes or no, the following lines show:

    Creating DCE local directory structure

    Removing old DCE local databases as directed.

    Created new DCE local database directory /opt/dcelocal

    Creating DCE File Links

    Created cdsl for DCE local directory /var/dcelocal

    Created cdsl for Kerberos directory /krb5

    Created cdsl for SIA directory /etc/sia

    Created cdsl for Kerberos 5 configuration file /etc/krb5.conf

    Adding DCE Setup desktop icon

There will be output for each member, as follows:

Configuring "DCE Runtime Services V4.1" (DCERTS410) on member0

    Creating local DCE File Links      (member1)

    Copyright (c) Entegrity Solutions, Inc.      2000, 2001

    Copyright (c) Digital Equipment Corporation, 1996, 1997, 1998, 1999

    All Rights Reserved.  Unpublished rights reserved

    under the copyright laws of the United States.

    Possession, use, or copying of the software and

    media is authorized only pursuant to a valid written

    license from Entegrity Solutions, Inc.

    RESTRICTED RIGHTS LEGEND   Use, duplication, or

    disclosure by the U.S. Government is subject to

    restrictions as set forth in Subparagraph (c)(1)(ii)

    of DFARS 252.227-7013, or in FAR 52.227-19, as

    applicable.

    Creating DCE File Links

Configuring "DCE Security Server V4.1" (DCESEC410) on member0

    Copyright (c) Entegrity Solutions, Inc.      2000, 2001

    Copyright (c) Digital Equipment Corporation, 1996, 1997, 1998, 1999

    All Rights Reserved.  Unpublished rights reserved

    under the copyright laws of the United States.

    Possession, use, or copying of the software and

    media is authorized only pursuant to a valid written

    license from Entegrity Solutions, Inc.

    RESTRICTED RIGHTS LEGEND   Use, duplication, or

    disclosure by the U.S. Government is subject to

    restrictions as set forth in Subparagraph (c)(1)(ii)

    of DFARS 252.227-7013, or in FAR 52.227-19, as

    applicable.

Creating DCE File Links

Configuring "DCE Cell Directory Server V4.1" (DCECDS410) on member0

======================================================================

Installation of all the requested DCE subsets is completed.

You have installed the DCE software which requires further action 

to configure and start it. To do so please invoke "/usr/sbin/dcesetup" 

and select option 1 (Configure DCE services) from the main menu.

======================================================================

Copyright (c) Entegrity Solutions, Inc.      2000, 2001

    Copyright (c) Digital Equipment Corporation, 1996, 1997, 1998, 1999

    All Rights Reserved.  Unpublished rights reserved

    under the copyright laws of the United States.

    Possession, use, or copying of the software and

    media is authorized only pursuant to a valid written

    license from Entegrity Solutions, Inc.

    RESTRICTED RIGHTS LEGEND   Use, duplication, or

    disclosure by the U.S. Government is subject to

    restrictions as set forth in Subparagraph (c)(1)(ii)

    of DFARS 252.227-7013, or in FAR 52.227-19, as

    applicable.

    Creating DCE File Links

Configuring "DCE Application Developers Kit V4.1" (DCEADK410) on member0

    Creating local DCE File Links      (member1)

======================================================================

Installation of all the requested DCE subsets is completed.

======================================================================

    Copyright (c) Entegrity Solutions, Inc.      2000, 2001

    Copyright (c) Digital Equipment Corporation, 1996, 1997, 1998, 1999

    All Rights Reserved.  Unpublished rights reserved

    under the copyright laws of the United States.

    Possession, use, or copying of the software and

    media is authorized only pursuant to a valid written

    license from Entegrity Solutions, Inc.

    RESTRICTED RIGHTS LEGEND   Use, duplication, or

    disclosure by the U.S. Government is subject to

    restrictions as set forth in Subparagraph (c)(1)(ii)

    of DFARS 252.227-7013, or in FAR 52.227-19, as

    applicable.

    Creating DCE File Links

Configuring "DCE Command Reference Manual Pages V4.1" (DCEMAN410) on 
member0

    Creating local DCE File Links (member1) 

    Copyright (c) Entegrity Solutions, Inc.      2000, 2001

    Copyright (c) Digital Equipment Corporation, 1996, 1997, 1998, 1999

    All Rights Reserved.  Unpublished rights reserved

    under the copyright laws of the United States.

    Possession, use, or copying of the software and

    media is authorized only pursuant to a valid written

    license from Entegrity Solutions, Inc.

    RESTRICTED RIGHTS LEGEND   Use, duplication, or

    disclosure by the U.S. Government is subject to

    restrictions as set forth in Subparagraph (c)(1)(ii)

    of DFARS 252.227-7013, or in FAR 52.227-19, as

    applicable.

Creating DCE File Links

Configuring "DCE Application Developers Manual Pages V4.1" (DCEADKMAN410) 
on member0

    Creating local DCE File Links      (member1)

======================================================================

Installation of all the requested DCE subsets is completed.

======================================================================

Configuring "DCE Runtime Services V4.1" (DCERTS410) on member1

    Creating local DCE File Links      (member1)

======================================================================

Installation of all the requested DCE subsets is completed.    (member1)

======================================================================

Configuring "DCE Security Server V4.1" (DCESEC410) on member1

======================================================================

Installation of all the requested DCE subsets is completed.

======================================================================

Configuring "DCE Cell Directory Server V4.1" (DCECDS410) on member1

======================================================================

Installation of all the requested DCE subsets is completed.

======================================================================

Configuring "DCE Application Developers Kit V4.1" (DCEADK410) on member1

    Creating local DCE File Links      (member1)

======================================================================

Installation of all the requested DCE subsets is completed.

======================================================================

Configuring "DCE Command Reference Manual Pages V4.1" (DCEMAN410) on 
member1

    Creating local DCE File Links (member1) 

======================================================================

Installation of all the requested DCE subsets is completed.

======================================================================

Configuring "DCE Application Developers Manual Pages V4.1" (DCEADKMAN410) 
on member1

    Creating local DCE File Links      (member1)

======================================================================

Installation of all the requested DCE subsets is completed.

======================================================================

• To verify that the subsets you selected have been installed, enter the following command:
  

  # setld -i | grep DCE | grep"_ _installed"
  

• Be sure the old subset (kit) is deleted (see page24)
  

The initial steps resemble those in Section 1.7. The following introductory information was added:

Be sure that DCE Runtime (DCERTTS410) is installed prior to, or at the same time as, the DFS subsets. Installing DFS subsets later is similar to the original installation of DCE. But, for configuration, use dfssetup instead of dcesetup. See Entegrity DCE for Tru64 UNIX Distributed File Service (DFS) Configuration Guide.

NOTE: For cluster installations, the installation scripts first install the common files to shared cluster locations, then to the member template area (member 0), and then onto each of the members in member specific locations. Configuration does not begin until all the installations are complete.

STEPS

1. Log in as superuser (login name root) to the system on which you are installing the DCE software.

2. You can load the subsets in the DCE software either by changing directories to where the software is placed, then entering the setld command OR you can enter the setld command followed by the location where the software is placed, as in the following examples:

   # cd <kit_location>
   

   # setld -l 
   

   If you mounted the DCE CDROM on the /mnt/ directory, then the kit location is /mnt/kit.

   OR
   

   # setld -l  <kit_location> 
   

   # setld -l /mnt/kit
   

   After several seconds, the installation procedure displays the names of the optional subsets and prompts you to specify the subsets that you want to install.

   The subsets listed below are optional:
   

   There may be more optional subsets than can be presented on a single 
   

   screen. If this is the case, you can choose subsets screen by screen
   

   or all at once on the last screen. All of the choices you make will
   

   be collected for your confirmation before any subsets are installed.
   

        1) DCE DFS Base V4.1                                                       
   

        2) DCE DFS Kernel Binaries V4.1                                            
   

        3) DCE DFS Man Pages V4.1                                                  
   

        4) DCE DFS NFS-DFS Secure Gateway Server V4.1                              
   

        5) DCE DFS Utilities/Debug V4.1                                            
   

   Or you may choose one of the following options:
   

        6) ALL of the above 
   

        7) CANCEL selections and redisplay menus
   

        8) EXIT without installing any subsets 
   

   Estimated free diskspace(MB) in root:285.6 usr:275.6 var:1102.8
   

   Enter your choices or press RETURN to redisplay menus.
   

   Enter your choices or press RETURN to redisplay menus.
   

   Choices (for example, 1 2 4-6):1-5
   

   Choose the DFS subsets: 1-5

        1) DCE DFS Base V4.1                                                       
   

        2) DCE DFS Kernel Binaries V4.1                                            
   

        3) DCE DFS Man Pages V4.1                                                  
   

        4) DCE DFS NFS-DFS Secure Gateway Server V4.1                              
   

        5) DCE DFS Utilities/Debug V4.1 
   

3. Next, the installation procedure lets you verify your choice. You see the following display:

   You are installing the following optional subsets:
   

           DCE DFS Base V4.1
   

           DCE DFS Kernel Binaries V4.1
   

           DCE DFS Man Pages V4.1
   

           DCE DFS NFS-DFS Secure Gateway Server V4.1
   

           DCE DFS Utilities/Debug V4.1
   

   Estimated free diskspace(MB) in root:285.6 usr:246.8 var:1102.8
   

   Is this correct? (y/n):  
   

   Checking file system space required to install selected subsets:
   

   File system space checked OK.
   

   5 subsets will be installed.
   

   Loading subset 1 of 5 ...
   

   DCE DFS Base V4.1
   

      Copying from . (disk)
   

      Verifying
   

   Loading subset 2 of 5 ...
   

   DCE DFS Kernel Binaries V4.1
   

      Copying from . (disk)
   

      Verifying
   

   Loading subset 3 of 5 ...
   

   DCE DFS Utilities/Debug V4.1
   

      Copying from . (disk)
   

      Verifying
   

   Loading subset 4 of 5 ...
   

   DCE DFS Man Pages V4.1
   

      Copying from . (disk)
   

      Verifying
   

   Loading subset 5 of 5 ...
   

   DCE DFS NFS-DFS Secure Gateway Server V4.1
   

      Copying from . (disk)
   

      Verifying
   

   5 of 5 subsets installed successfully.
   

         Creating DCE File Links
   

   Configuring "DCE DFS Base V4.1" (DCEDFS410) on member0
   

         Creating local DCE File Links      (member1)
   

   Installation of the DCE DFS Base V4.1 (DCEDFS410)
   

   subset is complete.
   

   Modifying /sys/conf/files due to change in Tru64 UNIX V5.0 configuration.
   

   Configuring "DCE DFS Kernel Binaries V4.1" (DCEDFSBIN410) on member0
   

   Installation of the DCE DFS Kernel Binaries V4.1 (DCEDFSBIN410)
   

   subset is complete.
   

   To configure DFS services, you must first build a DFS kernel.  Type
   

   `doconfig' and choose the DCEDFS kernel option from the menu (along with
   

   any others you desire).  Copy the resulting kernel to /vmunix, reboot,
   

   then run `/usr/sbin/dfssetup' to configure DFS, if necessary. 
   

       Creating DCE File Links
   

   Configuring "DCE DFS Utilities/Debug V4.1" (DCEDFSUTL410) on member0
   

       Creating local DCE File Links      (member1)
   

   Installation of the DCE DFS Utilities/Debug V4.1 (DCEDFSUTL410)
   

   subset is complete.
   

       Creating DCE File Links
   

   Configuring "DCE DFS Man Pages V4.1" (DCEDFSMAN410) on member0
   

       Creating local DCE File Links      (member1)
   

   Installation of the DCE/DFS Man Pages V4.1 (DCEDFSMAN410)
   

   subset is complete.
   

   Creating DCE File Links
   

   Configuring "DCE DFS NFS-DFS Secure Gateway Server V4.1" 
   (DCEDFSNFSSRV410) on member0
   

   Installation of the DCE DFS NFS-DFS Secure Gateway Server V4.1 
   (DCEDFSNFSSRV410)
   

   subset is complete.
   

   ======================================================================
   

   Installation of all the requested DCE subsets is completed.
   

   You have installed the DCE software which requires further action 
   

   to configure and start it. To do so please invoke "/usr/sbin/dcesetup" 
   

   and select option 1 (Configure DCE services) from the main menu.
   

   ======================================================================
   

   Configuring "DCE DFS Base V4.1" (DCEDFS410) on member1
   

         Creating local DCE File Links      (member1)
   

   Installation of the DCE DFS Base V4.1 (DCEDFS410)
   

   subset is complete.
   

   ======================================================================
   

   Installation of all the requested DCE subsets is completed.
   

   ======================================================================
   

   Configuring "DCE DFS Kernel Binaries V4.1" (DCEDFSBIN410) on member1
   

   Installation of the DCE DFS Kernel Binaries V4.1 (DCEDFSBIN410)
   

   subset is complete.
   

   To configure DFS services, you must first build a DFS kernel.  Type
   

   `doconfig' and choose the DCEDFS kernel option from the menu (along with
   

   any others you desire).  Copy the resulting kernel to /vmunix, reboot,
   

   then run `/usr/sbin/dfssetup' to configure DFS, if necessary. 
   

   ======================================================================
   

   Installation of all the requested DCE subsets is completed.
   

   ======================================================================
   

   Configuring "DCE DFS Utilities/Debug V4.1" (DCEDFSUTL410) on member1
   

       Creating local DCE File Links      (member1)
   

   Installation of the DCE DFS Utilities/Debug V4.1 (DCEDFSUTL410)
   

   subset is complete.
   

   ======================================================================
   

   Installation of all the requested DCE subsets is completed.
   

   ======================================================================
   

   Configuring "DCE DFS Man Pages V4.1" (DCEDFSMAN410) on member1
   

       Creating local DCE File Links      (member1)
   

   Installation of the DCE/DFS Man Pages V4.1 (DCEDFSMAN410)
   

   subset is complete.
   

   ======================================================================
   

   Installation of all the requested DCE subsets is completed.
   

   ======================================================================
   

   Configuring "DCE DFS NFS-DFS Secure Gateway Server V4.1" 
   (DCEDFSNFSSRV410) on member1
   

   Installation of the DCE DFS NFS-DFS Secure Gateway Server V4.1 
   (DCEDFSNFSSRV410)
   

   subset is complete.
   

   ======================================================================
   

   Installation of all the requested DCE subsets is completed.
   

   ======================================================================
   

   At this point, the installation is completed. However a new DFS kernel must be created and the DFS must be configured before DFS can be utilized.

4. To configure DFS services, you must first build a DFS kernel.
   • Type the 'doconfig' command and choose the DCEDFS kernel option from the menu (along with any others you desire).

   • Copy the resulting kernel to /vmunix,

   • Reboot, using the new kernel,

5. Run '/usr/sbin/dfssetup' to configure DFS.

   (Remember that DCE had to have been configured before installing DFS.)

   Procedures to configure DFS are explained in Net Crusader Distributed File Service (DFS) Configuration Guide.

DFS databases are preserved from one version to another; if you did not recreate the dcelocal directory during installation of the DCE Runtime Services Kit. Choice is explained at Chapter 1.11 on page 28

1.13 Installing DCE in a DMS Environment

Dataless Management System (DMS) is not supported in a clustered environment, but works in a non-clustered environment. Entegrity DCE for Tru64 UNIX versions 4.0 and 4.1 support DMS in that non clustered environment.

Entegrity DCE for Tru64 UNIX 4.1 allows you to install DCE on a Dataless Management System client. For detailed information on DMS, see the section on Dataless Management Services in the Tru64 UNIX System & Network Management Guide; the DMS section is in the chapter, "Sharing Software on a Local Area Network."

1.13.1 Hardware Requirements for a DMS Installation

Hardware requirements are the same as those for a regular DCE installation, listed on Section 1.3.1 on page 11.

1.13.2 Software Requirements

To install DCE in a DMS environment, you must have the base Tru64 UNIX Operating System plus the following optional subsets installed:

Required by DMS:

• OSFINET Additional Networking Services
  
• OSFDMS Dataless Management Services
  

Required by DCE:

• OSFINCLUDE Standard Header Files
  
• OSFDCMT Documentation Preparation Tools
  
• OSFPGMR Standard Programmer Commands
  

1. If this is a first-time installation, create the DMS environment using the DMU tool by installing the base Tru64 UNIX operating system plus the optional subsets required by DCE. (These are listed in the previous section.) If this is an update installation and you want to preserve the DMS client system's DCE database, refer to Section 1.5 on page 13 before attempting the installation.

2. Using the DMU tool, run the following option:

   CONFIGURE software environments
   

   This option sets up directories in the DMS environment that are required for successful installation of DCE.

3. Install the DCE product into the DMS environment using the following DMU option:

   i)  INSTALL software environments
   

   Remember that you must not choose /usr as the location for the DCE database, because DMS mounts /usr as a read-only partition for the client.

4. Create your DMS client(s) using the following DMU option:

   a)  ADD a client
   

5. You should now be able to boot the client system(s) and complete the configuration phase of the installation on the client. At this time, you are asked whether you want to mount the DCE database on a local partition (on the DMS client), rather than keeping it on an NFS mounted partition. Since DCE assumes "local filesystem security," you must mount the DCE database on the DMS client unless security is not a concern. If security is not an issue, you can leave the DCE database on an NFS mounted partition. For more information, see Section 1.15 on page 55.

6. Add all the licenses required for Tru64 UNIX and DCE to the client.

7. Configure DCE on the DMS client using dcesetup. It is assumed that DMS clients will be configured as DCE clients. Although it is possible to configure a DMS client system as a DCE server, this is not recommended.

The following is a sample script from a DMU session showing the installation of DCE into a client environment. All user entries appear in boldface type.

:/alt> dmu

*** DMU Main Menu ***

Choices without key letters are not available.

    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
     ) LIST registered clients
     ) MODIFY a client
     ) REMOVE a client
    s) SHOW software environments
    x) EXIT

Enter your choice: i

DMU Software Installation Menu:

    1)  Install software into a new area
    2)  Add software into an existing area
    3)  Perform configuration phase on an existing area
    4)  Return to previous menu

Enter your choice: 2

You have chosen to add a product to an existing environment.

The existing environment is /alt/dms/dms0.alpha.

Enter the device special file name or the path of the directory where the 
software is located (for example, /mnt/ALPHA/BASE): /mnt/ALPHA/BASE

The subsets listed below are optional:

    There may be more optional subsets than can be presented on a single 
screen. If this is the case, you can choose subsets screen by screen or all 
at once on the last screen. All of the choices you make will be collected for 
your confirmation before any subsets are installed.

     1) DCE Application Developers Kit V4.1
     2) DCE Application Developers Manual Pages V4.1 
     3) DCE Cell Directory Server V4.1
     4) DCE Command Reference Manual Pages V4.1  
     5) DCE DFS Base V4.1
     6) DCE DFS Kernel Binaries V4.1
     7) DCE DFS Man Pages V4.1
     8) DCE DFS NFS-DFS Secure Gateway Server V4.1
     9) DCE DFS Utilities/Debug V4.1
    10) DCE Runtime Services V4.1
    11) DCE Security Server V4.1

--- MORE TO FOLLOW ---

Enter your choices or press RETURN to display the next screen.

Choices (for example, 1 2 4-6): 

Or you may choose one of the following options:

    12) ALL of the above 

    13) CANCEL selections and redisplay menus

    14) EXIT without installing any subsets 

Enter your choices or press RETURN to redisplay menus.

Choices (for example, 1 2 4-6): 12

You are installing the following optional subsets:

        DCE Application Developers Kit V4.1
        DCE Application Developers Manual Pages V4.1                           
        DCE Cell Directory Server V4.1
        DCE Command Reference Manual Pages V4.1
        DCE DFS Base V4.1
        DCE DFS Kernel Binaries V4.1
        DCE DFS Man Pages V4.1
        DCE DFS NFS-DFS Secure Gateway Server V4.1
        DCE DFS Utilities/Debug V4.1
        DCE Runtime Services V4.1
        DCE Security Server V4.1

Is this correct? (y/n): y

Checking file system space required to install selected subsets:

File system space checked OK.

11 subset(s) will be installed.

Loading 1 of 11 subset(s)....

DCE Runtime Services V4.1

   Copying from /DCE410_kit (disk)
        Working....Thu Oct  1 08:37:47 EDT 2000
   Verifying
        Working....Thu Oct  1 08:38:35 EDT 2000

Loading 2 of 11 subset(s)....

DCE Security Server V4.1
   Copying from /DCE410_kit (disk)
   Verifying

Loading 3 of 11 subset(s)....

DCE Cell Directory Server V4.1
   Copying from /DCE410_kit (disk)
   Verifying

Loading 4 of 11 subset(s)....

DCE Application Developers Kit V4.1
   Copying from /DCE410_kit (disk)
   Verifying

Loading 5 of 11 subset(s)....

DCE Command Reference Manual Pages V4.1
   Copying from /DCE410_kit (disk)
   Verifying

Loading 6 of 11 subset(s)....

DCE Application Developers Manual Pages V4.1
   Copying from /DCE410_kit (disk)
        Working....Thu Oct  1 08:39:35 EDT 2000
   Verifying

Loading 7 of 11 subset(s)....

DCE DFS Base V4.1
   Copying from /DCE410_kit (disk)
   Verifying

Loading 8 of 11 subset(s)....

DCE DFS Kernel Binaries V4.1
   Copying from /DCE410_kit (disk)
   Verifying

Loading 9 of 11 subset(s)....

DCE DFS Utilities/Debug V4.1
   Copying from /DCE410_kit (disk)
   Verifying

Loading 10 of 11 subset(s)....

DCE DFS Man Pages V4.1
   Copying from /DCE410_kit (disk)
   Verifying

Loading 11 of 11 subset(s)....

DCE DFS NFS-DFS Secure Gateway Server V4.1
   Copying from /DCE410_kit (disk)
   Verifying

11 of 11 subset(s) installed successfully.

Copyright (c) Digital Equipment Corporation, 1993, 1994, 1995, 1996
All Rights Reserved.  Unpublished rights reserved under the copyright laws of 
the United States.

Possession, use, or copying of the software and media is authorized only 
pursuant to a valid written license from Digital Equipment Corporation.

RESTRICTED RIGHTS LEGEND   Use, duplication, or disclosure by the U.S. 
Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) 
of DFARS 252.227-7013, or in FAR 52.227-19, as applicable.

    =============================================================

    Beginning configuration of DCE Version 4.1.  

    You will be asked a few questions before configuration can proceed. 

    On-line help is available where the prompt contains a "?" choice.

=============================================================

IMPORTANT: 

For SECURITY reasons, you may want to make sure that the location you will 
type now is native to this host; i.e., is not NFS mounted!

Please enter the location for new DCE local databases, or press <RETURN> 
for the default location [/var]: /var

    =============================================================

There will be no more questions asked for the remainder of the 
configuration.

    =============================================================

    Creating DCE local directory structure

    Removing old DCE local databases as directed.

    Created new DCE local database directory /opt/dcelocal

    Creating DCE File Links

    Adding DCE Setup desktop icon

    Creating DCE File Links

    Creating DCE File Links

    Creating DCE File Links

    Creating DCE File Links

    Creating DCE File Links

Use the DMU Main Menu to create a client.

:/alt> dmu

*** DMU Main Menu ***

Choices without key letters are not available.

    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
     ) LIST registered clients
     ) MODIFY a client
     ) REMOVE a client
    s) SHOW software environments
    x) EXIT

Enter your choice: a

You have chosen to add a client for dataless service.

The following conditions must be met to add a client:

     1. You must know the client processor's hostname.
     2. The client's hostname must be in your system's host database(s)
     3. You must know the client's interface type and subnet mask.
     4. You must know the type of kernel build area.
     5. You must know the swap device and partition on the client.
     6. You must know the client's hardware Ethernet or FDDI address.
     7. If the client and server reside on different subnets, you will need 
the address of the gateway(s) that the client can use to communicate with the 
server.

Do you want to continue? (y/n) [y]: 

Enter the client processor's hostname or press RETURN to quit: myhost

Enter the path to contain the root file system. [/clients/myhost]: 

Enter the swap device and partition on myhost. [rz0b]: rz11g

Enter the swap device drive type for rz11g. [RZ26]: rz56

Enter the network interface for myhost (16.32.40.20). [ln0]: 

Enter the subnet mask for ln0. [255.255.255.0]: 255.255.0.0

Enter the type of kernel build area for myhost. 

You may select [F]ull, [P]artial, [N]one or [H]elp for more information. [P]: 

You have specified the following configuration for myhost:

        ROOT:  /clients/myhost
 SWAP_DEVICE:  /dev/rz11g
   SWAP_TYPE:  RZ56
  BUILD_TYPE:  Partial
   INTERFACE:  ln0 (16.32.40.20)
 SUBNET_MASK:  255.255.0.0

Is this correct? (y/n) [y]: 

The existing environment is /alt/dms/dms0.alpha.

The following environment will be installed from /alt/dms/dms0.alpha:

Description

   'Digital DCE V4.1 for Digital UNIX DCEADK410'
   'Digital DCE V4.1 for Digital UNIX DCEADKMAN410'
   'Digital DCE V4.1 for Digital UNIX DCECDS410'
   'Digital DCE V4.1 for Digital UNIX DCEDFS410'
   'Digital DCE V4.1 for Digital UNIX DCEDFSBIN410'
   'Digital DCE V4.1 for Digital UNIX DCEDFSMAN410'
   'Digital DCE V4.1 for Digital UNIX DCEDFSNFSSRV410'
   'Digital DCE V4.1 for Digital UNIX DCEDFSUTL410'
   'Digital DCE V4.1 for Digital UNIX DCEMAN410'
   'Digital DCE V4.1 for Digital UNIX DCERTS410'
   'Digital DCE V4.1 for Digital UNIX DCESEC410'
   'Digital UNIX V4.1 Operating System (Rev 375)'

Is that correct? (y/n) [y]: 

Enter the client processor's hardware network address.  For example, 
08-00-2b-02-67-e1: 08-00-2b-2c-32-05

Checking file system space required for client root and var file 
systems...done.

Creating the root and var filesystems for myhost.

				Working....Thu Oct  1 08:45:05 EDT 2000

				Working....Thu Oct  1 08:47:06 EDT 2000

Client myhost has been added.

You can use the DMU Main Menu to obtain information about the preceding operation.

*** DMU Main Menu ***

    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
    l) LIST registered clients
    m) MODIFY a client
    r) REMOVE a client
    s) SHOW software environments
    x) EXIT

Enter your choice: s

1  /alt/dms/dms0.alpha

   'Digital DCE V4.1 for Digital UNIX DCEADK410'
   'Digital DCE V4.1 for Digital UNIX DCEADKMAN410'
   'Digital DCE V4.1 for Digital UNIX DCECDS410'
   'Digital DCE V4.1 for Digital UNIX DCEDFS410'
   'Digital DCE V4.1 for Digital UNIX DCEDFSBIN410'
   'Digital DCE V4.1 for Digital UNIX DCEDFSMAN410'
   'Digital DCE V4.1 for Digital UNIX DCEDFSNFSSRV410'
   'Digital DCE V4.1 for Digital UNIX DCEDFSUTL410'
   'Digital DCE V4.1 for Digital UNIX DCEMAN410'
   'Digital DCE V4.1 for Digital UNIX DCERTS410'
   'Digital DCE V4.1 for Digital UNIX DCESEC410'
   'Digital UNIX V4.1410 Operating System (Rev 375)'

*** DMU Main Menu ***

    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
    l) LIST registered clients
    m) MODIFY a client
    r) REMOVE a client
    s) SHOW software environments
    x) EXIT

Enter your choice: l

The following clients are registered for /alt/dms/dms0.alpha:

myhost

After exiting from the DMU session, the next step is to boot the client and perform client configuration.

The following is a sample of output from booting the DMS client system:

>>>boot ez0

*** SYSTEM CONFIGURATION ***

Configuring "Base System " (OSFBASE425)

Configuring "Base System - Hardware Support " (OSFHWBASE425)

Configuring "Compiler Back End " (OSFCMPLRS425)

Configuring "Kernel Header and Common Files " (OSFBINCOM425)

Configuring "Standard Kernel Modules " (OSFBIN425)

Configuring "Hardware Kernel Header and Common Files" (OSFHWBINCOM425)

Configuring "Hardware Kernel Modules " (OSFHWBIN425)

Configuring "Basic Networking Services " (OSFCLINET425)

Configuring "NFS(tm) Utilities " (OSFNFS425)

Configuring "Local Printer Support " (OSFPRINT425)

Configuring "Basic X Environment " (OSFX11425)

Configuring "CDE Minimum Runtime Environment " (OSFCDEMIN425)

Configuring "CDE Desktop Environment " (OSFCDEDT425)

Configuring "LK201 Keyboard Support " (OSFKBDLK201425)

Configuring "LK401 Keyboard Support " (OSFKBDLK401425)

Configuring "LK411 Keyboard Support " (OSFKBDLK411425)

Configuring "LK421 Keyboard Support " (OSFKBDLK421425)

Configuring "LK444 Keyboard Support " (OSFKBDLK444425)

Configuring "PCXAL Keyboard Support " (OSFKBDPCXAL425)

Configuring "X Servers Base " (OSFSER425)

Configuring "X Servers for PCbus " (OSFSERPC425)

Configuring "X Servers for TurboChannel " (OSFSERTC425)

Configuring "X Servers for Open3D " (OSFSER3D425)

Configuring "X Fonts " (OSFMITFONT425)

Configuring "DECwindows 100dpi Fonts " (OSFFONT15425)

Configuring "DECwindows 75dpi Fonts " (OSFFONT425)

Configuring "Adobe Fonts " (OSFDPSFONT425)

Configuring "Old X Environment " (OSFOLDX11425)

Configuring "CDE Mail Interface " (OSFCDEMAIL425)

Configuring "Tcl Commands " (OSFTCLBASE425)

Configuring "Tk Toolkit Commands " (OSFTKBASE425)

Configuring "Java V1.1.4 Environment " (OSFJAVA425)

Configuring "Netscape Navigator Gold V3.04 " (OSFNETSCAPE425)

Configuring "Base System Management Applications and Utilities" 
(OSFSYSMAN425)

Configuring "Basic Networking Configuration Applications" (OSFNETCONF425)

Configuring "NFS(tm) Configuration Application " (OSFNFSCONF425)

Configuring "Graphical Base System Management Utilities" (OSFXSYSMAN425)

Configuring "Graphical System Administration Utilities" (OSFXADMIN425)

Configuring "Graphical Print Configuration Application" (OSFXPRINT425)

Configuring "Additional Networking Services " (OSFINET425)

Configuring "Dataless Management Services " (OSFDMS425)

Configuring "Doc. Preparation Tools " (OSFDCMT425)

Configuring "Doc. Preparation Tools Extensions " (OSFDCMTEXT425)

Configuring "Standard Programmer Commands " (OSFPGMR425)

Configuring "Standard Header Files " (OSFINCLUDE425)

Configuring "DCE Runtime Services V4.1" (DCERTS410)

    This appears to be a DMS installation.
    Is this a DMS installation? (y/n/?) [y]: 

You are installing DCE on a DMS client system.

DMS assumes that all partitions other than swap are NFS mounted from the DMS 
server system.

Digital STRONGLY recommends that you do not use an NFS mounted directory to 
store DCE data - DCE security relies on 'local filesystem' security to 
maintain the integrity of the DCE database.

You will now be given the option of mounting dcelocal on a partition residing 
on the DMS client system. If you choose to keep DCE databases mounted on the 
DMS server, the security of your DCE database may be compromised.

You may mount dcelocal on a partition residing on the DMS client system at a 
later time if you wish. See the instructions in the DCE Installation and 
Configuration Guide entitled "Mounting a local partition for DCE in the DMS 
Environment"

Please note that any data currently on the local partition will be lost.

Do you wish to mount a local filesystem to hold the DCE database at this 
time?  (y/n/?) [y]: n

Configuring "DCE Security Server V4.1" (DCESEC410)

DCESEC410 includes support for the License Management Facility. 

A Product Authorization Key (PAK) is necessary for the use of this product.

For information on registering and activating the PAK, refer to the DCE 
Installation and Configuration Guide or Guide to Software Licensing 

*** WARNING: myhost doesn't have proper license for DCESEC410. ***

*** WARNING: Install correct PAK before running dcesetup. ***

Configuring "DCE Cell Directory Server V4.1" (DCECDS410)

DCECDS410 includes support for the License Management Facility. 
A Product Authorization Key (PAK) is necessary for the use of this product.

For information on registering and activating the PAK, refer to the DCE 
Installation and Configuration Guide or Guide to Software Licensing 

*** WARNING: myhost doesn't have proper license for DCECDS410. ***

*** WARNING: Install correct PAK before running dcesetup. ***

Configuring "DCE Application Developers Kit V4.1" (DCEADK410)

DCEADK410 includes support for the License Management Facility. 

A Product Authorization Key (PAK) is necessary for the use of this product.

For information on registering and activating the PAK, refer to the DCE 
Installation and Configuration Guide or Guide to Software Licensing 

*** WARNING: myhost doesn't have proper license for DCEADK410. ***

*** WARNING: Install correct PAK before running dcesetup. ***

Configuring "DCE Command Reference Manual Pages V4.1" (DCEMAN410)

Configuring "DCE Application Developers Manual Pages V4.1" (DCEADKMAN410)

Configuring "DCE DFS Base V4.1" (DCEDFS410)

Installation of the DCE DFS Base V4.1 (DCEDFS410) subset is complete.

Configuring "DCE DFS Kernel Binaries V4.1" (DCEDFSBIN410)

Installation of the DCE DFS Kernel Binaries V4.1 (DCEDFSBIN410) subset is 
complete.

To configure DFS services, you must first build a DFS kernel.  Type

'doconfig' and choose the DCEDFS kernel option from the menu (along with

any others you desire).  Copy the resulting kernel to /vmunix, reboot,

then run '/usr/sbin/dfssetup' to configure DFS, if necessary. 

Configuring "DCE DFS Utilities/Debug V4.1" (DCEDFSUTL410)

Installation of the DCE DFS Utilities/Debug V4.1 (DCEDFSUTL410) subset is 
complete.

Configuring "DCE DFS Man Pages V4.1" (DCEDFSMAN410)

Installation of the DCE/DFS Man Pages V4.1 (DCEDFSMAN410) subset is complete.

Configuring "DCE DFS NFS-DFS Secure Gateway Server V4.1" (DCEDFSNFSSRV410)

Installation of the DCE DFS NFS-DFS Secure Gateway Server V4.1 
(DCEDFSNFSSRV410) subset is complete.

=============================================================

Installation of all the requested DCE subsets is completed.

You have installed the DCE software which requires further action to 
configure and start it. To do so please invoke "/usr/sbin/dcesetup" and 
select option 1 (Configure DCE services) from the main menu.

=============================================================

1.14 Re-Installing DCE in a DMS Environment over an Older Version of DCE

Because the DMS software installation process cannot identify where the DCE database resides on a client system, special processing is required if you want to retain your DMS client's DCE database when you upgrade software in the DMS environment. The following section presents the procedure that is required to preserve a DCE database for a DMS client system.

Before upgrading software, log in to each DMS client system and perform the following steps, where SYSTEM_NAME is the name of the DMS client :

1. Stop the DCE daemons that are running on the client:

   dcesetup stop
   

2. Perform a Clean operation from DCEsetup on the client:

   dcesetup clean
   

3. Change the directory to the local DCE area with the command :

   cd /opt/dcelocal
   

4. Create a tar file of the DCE area with the following command:

   tar cvf /SYSTEM_NAME_dcedb.tar
   

5. Create a list of files in the DCE area with the command :

   find . > /SYSTEM_NAME_dcedb_before.dif
   

6. Change the directory to the /krb5 directory with the command :

   cd /krb5
   

7. Create a tar file of the /krb5 directory with the command :

   tar cvf /SYSTEM_NAME_krb5db.tar ./
   

8. Move the files /SYSTEM_NAME_dcedb.tar, /SYSTEM_NAME_krb5db.tar, and /SYSTEM_NAME_dcedb_before.dif to a safe place on the server.

   NOTE: Do NOT store these files in the DMS /clients or /dmsN.alpha areas; if you do, they may be deleted during the upgrade.)

Next, install the software in the DMS environment. This requires that you delete and recreate each client.

Boot the client systems and complete the installation and configuration passes, but do NOT run dcesetup.

Log in to each client and perform the following steps, where SYSTEM_NAME is the name of the DMS client:

1. Copy SYSTEM_NAME_dcedb.tar, /SYSTEM_NAME_krb5db.tar, and SYSTEM_NAME_dcedb_before.dif to the client's / (root) directory.

2. Change directories to the local DCE area with the command:

   cd /opt/dcelocal
   

3. Create a list of files in the area with the command:

   find . > /SYSTEM_NAME_dcedb_after.dif
   

4. With the following command, create a list of files to be extracted from the tar file created from the original DCE database:

   diff /SYSTEM_NAME_dcedb_after.dif \
   /SYSTEM_NAME_dcedb_before.dif | grep ">" | \
   awk '{print $2}' > /dcedb_extract.lis
   

5. Do the extraction from the tar files as follows :

   tar -xvf /SYSTEM_NAME_dcedb.tar -R /dcedb_extract.lis
   

6. Change the directory to /krb5 with the command :

   cd /krb5
   

7. Do the extraction from the krb5 tar file as follows:

   tar -xvf /SYSTEM_NAME_krb5db.tar
   

You should now have an upgraded version of the DCE software with the original DCE database in place. After testing is complete, you can delete the following files:

/SYSTEM_NAME_dcedb.tar, /SYSTEM_NAME_dcedb_before.dif,

/SYSTEM_NAME_dcedb_after.dif, and /dcedb_extract.lis

1.15 Mounting a Local Partition for DCE in the DMS Environment

To mount a local partition for DCE in the DMS Environment, perform the steps in the following example. Substitute the name of your local partition for rz3g wherever rz3g appears.

1. Find a local partition on the DMS client system. To obtain a list of disk partitions available on the DMS client, enter the following command:

   ls /dev/rz*
   

2. Create a mount point for the local partition with the following:

   mkdir /dcedms
   

3. Create a disklabel for the disk/partition:

   disklabel -s -F rz3g unused
   

4. Create a new file system on the local partition (note that this command erases ALL data currently on that partition):

   newfs -F /dev/rz3g
   

5. Just to be sure, perform an fsck on the partition:

   fsck /dev/rz3g
   

6. Mount the local partition for read/write:

   mount -w /dev/rz3g /dcedms
   

7. Identify the actual location of the DCE database by following the softlink from /opt/dcelocal :

   ls -l /opt/dcelocal
   

   The output returned is similar to the following:

   lrwxrwxrwx 1 root system  13 Aug 27 11:15 /opt/dcelocal -> /var/dcelocal
   

   The actual location in this case is /var/dcelocal.

8. Copy the DCE database from the NFS mounted partition (in this example, /var/dcelocal) to the local partition:

   cp -R -p /var/dcelocal /dcedms
   

9. If the copy was successful, remove the old DCE database from the NFS mounted partition (in this example, /var/dcelocal):

   rm -r /var/dcelocal
   

10. Create a softlink from the old NFS mounted dcelocal (/var/dcelocal in this example) to the new dcelocal area on the client system:

    ln -s /dcedms/dcelocal /var/dcelocal
    

11. Modify the /etc/fstab file on the client system so that the local DCE database is automatically mounted on a client reboot by adding the following line to /etc/fstab (rz3g is the local partition in this example):

    '/dev/rz3g     /dcedms ufs     rw 1 2
    

[Previous] [Next] [Contents] [Index]

To make comments or ask for help, contact support@entegrity.com.

Copyright © 1997-2004 Entegrity Solutions Corporation & its subsidiaries