Planning and Configuring HP DCE 1.7

2-6 Planning and Conﬁguring HP DCE 1.7

Migrating to HP DCE 1.7

Migrating the Cell Directory Service from HP DCE 1.3.1

Migrating the Cell Directory Service

from HP DCE 1.3.1

NOTE This section applies only to migrating from HP DCE 1.3.1 to HP DCE 1.7

(because HP DCE 1.3.1 is based on OSF DCE 1.0.3).

You should be aware of the following CDS considerations when migrating

to HP DCE 1.7:

• Installation of HP DCE 1.7 automatically attempts to preserve any

CDS deﬁned cached servers from previous conﬁgurations of HP DCE.

However, if a newly migrated HP DCE 1.7 node returns warnings

about being unable to locate a CDS server, it may be necessary to

manually specify the server location with a dcecp cdscache create

command.

• To make full use of HP DCE 1.7 features, the directory version

number of the root directory must be manually advanced to 4.0 after

all CDS servers in the cell have been upgraded to HP DCE 1.7. (To

determine the current directory version number, use the dcecp

directory show /.: command, and look for the

CDS_DirectoryVersion attribute.)

The procedure for doing this is discussed in “Managing CDS

Directories - Upgrading the Directory Version on a Directory”, in the

OSF DCE Administration Guide — Core Components. This procedure

makes use of the following dcecp commands:

dcecp> directory modify /.: -add {CDS_UpgradeTo 4.0}

dcecp> directory synchronize /.:

dcecp> clearinghouse verify /.:/clearinghouse_name

dcecp> directory synchronize /.:

Note that the dcecp clearinghouse verify command must be run

for every clearinghouse in the cell, and must be run directly on the

CDS server node hosting each clearinghouse. The command will not

work from a remote node.