OSF DCE Administration Guide--Core Components

Managing the DCE DST
The serverentry attribute specifies the CDS entry name where bindings for the server
are exported. If you change the setting of this attribute, the entry is also modified in the
namespace. The following is an example command that sets the serverentry attribute
value:
dcecp> dts modify - change {serverentry /.:/hosts/cyclops/dts_ref_node}
The serverprincipal attribute specifies the principal name of the server that is used for
authentication. If you change the name by using dcecp, you must create a matching
principal name and account in the security service registry. When you do this, you must
add the new principal name to the existing DTS server group (dts-servers). The
machine principal must be a member of this authorization group. See Chapter 31 of this
guide for further information on creating a new principal account and Chapter 30 for
information on adding a principal name to an existing server group.
The following example command sets the serverprincipal attribute:
dcecp> dts modify -change {serverprincipal /.:/hosts/ajax/dts_machine}
25.6 Management Tasks Specific to Servers
Managing DTS servers involves some special tasks. These tasks include the following:
• Setting a server’s epoch
• Assigning the courier role to a server
• Designating a server as a global server
• Setting the attributes for a connection to a time-provider
The following subsections describe these server-specific tasks.
25.6.1 Designating Global and Courier Servers
If your network has WAN links or is an extended LAN, you may need to use global and
courier servers to synchronize the nodes in separate network segments. To synchronize
nodes across a network, you assign global roles to some servers and courier roles to
selected local servers. (See Chapter 23 for advice on planning the location of global and
local courier servers.) To assign server roles, follow the instructions in the following
subsections.
124243 Tandem Computers Incorporated 25− 17