PreviousNext

Setting Clerk and Server Attribute Values

Once you have created a new clerk or server on a node, you will want to set certain of the entity's attribute values.

If you reconfigure a node to be a server, you need to match the epoch (the epoch attribute value) of the newly-created server to the epoch that is shared by the preexisting servers in the network segment. You want to do this so that the new server can synchronize immediately with these servers. Instructions for changing server epoch numbers with are given in Matching Server Epochs.

You may also want to check the rest of the attributes that apply only to servers to see that they complement the value settings of the attributes for preexisting servers. For instance, if the server has an external time provider, you may want to check the checkinterval attribute. This attribute specifies the amount of time that the server waits before synchronizing with the other servers on the LAN.

If you have changed your mind about a server's courier role since you created the server, you can modify the courierrole attribute value.

If you created a clerk, you may want to check the new clerk's attribute values against those of the preexisting clerks and server's in the network.

General instructions for modifying the attributes of DTS clerks and DTS servers are covered in Modifying Clerk and Server Attributes.