NetWare Directory Services

8-19
Implementing NetWare Directory Services
Implementing NDS on Various Sizes of Networks
Time Services
Because most large-sized networks maintain high levels of WAN
connectivity, which span time zones and international datelines, time
services support requires careful planning.
It is critical to have a constant reference of time in order for NDS
synchronization to take place. Time is also important to the proper execution
of certain events and features, such as network backups and time-based
security.
You should use one Reference time server and a group of Primary time
servers as the basis for network time services. This ensures that a proper and
accurate time reference is available at all times.
Determine which servers within your organization provide system-wide
services, such as directories or applications that are accessed by the entire
organization. From the servers you identify, select one to function as the
Reference time server and set up the others as Primary time servers.
Each geographically distinct site should have at least one Primary time
server.
All other NetWare servers in the network should be set up as Secondary time
servers.
The Reference time server should be adjusted periodically by an outside
time source, possibly the U.S. Naval Observatory Clock in Annapolis,
Maryland.
Partitions
Partitioning of large-sized networks should follow a multi-tiered partition
plan.
Each division-level Organizational Unit has its own partition representing
that container and its objects. Each lower-level Organizational Unit is the
root for a partition that includes itself and all the other container and leaf
objects beneath it in that branch of the tree.
The [Root] and Organization objects should form one partition. This
partitioning structure ensures that all the critical access points in the tree are
available and can be replicated for redundancy.