31.3 Coexistence and Migration of Time Synchronization Services

The time synchronization modules in Novell Open Enterprise Server (OES) have been designed to ensure that new OES servers, running on either NetWare or Linux, can be introduced into an existing network environment without disrupting any of the products and services that are in place.

Both the Linux and NetWare installs automate the time synchronization process where possible, as explained in Section 31.4, Implementing Time Synchronization.

This section discusses the issues involved in the coexistence and migration of time synchronization in OES in the following sections:

For a general discussion of coexistence and migration issues in OES, see the OES Coexistence and Migration Guide .

31.3.1 Coexistence

This section provides information regarding the coexistence of the OES time synchronization modules with existing NetWare or Linux networks, and with previous versions of the Timesync NLM. This information can help you confidently install new OES servers into your current network.


The following table summarizes the compatibility of OES time synchronization modules with other time synchronization modules and eDirectory. These compatibilities are illustrated in Figure 31-5 and Figure 31-6.



Timesync NLM (NetWare)

Can consume time from

  • All previous versions of Timesync. However, the NetWare 4.2 Timesync NLM should not be used as a time source.

  • Any Timesync or NTP daemon.

Can provide time to

  • All previous versions of Timesync.

  • Any Timesync or NTP daemon.


Can consume time from

  • Any NTP daemon.

Can provide time to

  • All previous versions of Timesync.

  • Any NTP daemon.

xntpd daemon (SLES 9)

Can consume time from

  • Any NTP daemon.

Can provide time to

  • Any NTP daemon.


eDirectory gets its time synchronization information from the host OS (Linux or NetWare), not from the time synchronization modules.

Coexistence Issues

If you have NetWare servers earlier than version 5.1, you need to install at least one later version NetWare server to bridge between the Timesync NLM on the earlier server and any OES Linux servers you have on your network. This is because the earlier versions of Timesync can’t consume or provide NTP time packets and the xntpd daemon on Linux can’t provide or consume Timesync packets.

Fortunately, the Timesync NLM in NetWare 5.1 and later can both consume and provide Timesync packets. And the XNTPD NLM can provide Timesync packets when required.

This is explained in Compatibility with Earlier Versions of NetWare.

31.3.2 Migration

The following sections explain time synchronization issues associated with migration.

Migration Path

Your migration path depends on the platform you are migrating data to.

NetWare to NetWare

Time synchronization configuration settings are all migrated by the NetWare Migration Wizard (both Timesync and XNTPD modules) because all associated modules and configuration files reside on sys:system.

NetWare to Linux

There is no direct server migration from NetWare to Linux. However, if XNTPD is used for time synchronization on NetWare, the contents of the sys:system\ntp.conf file works unchanged on a Linux server as /etc/ntp.conf, if the configuration is valid on the network where the Linux server resides.

Migration Tools

Use the following tools for migrating services.

NetWare Migration Wizard

All time synchronization files are migrated with the sys:system directory and work unchanged on the new server. See the Server Migrations in the Novell Server Consolidation and Migration Toolkit Administration Guide for more information.

iManager Migrate Plug-in

If you decide you want to use only NTP as your time synchronization protocol, you can use the iManager > Time Synchronization > Migration plug-in to migrate NetWare 6.5 and OES NetWare servers from Timesync to NTP.

For more information, see Migrating TimeSync Servers to NTP in the Novell Network Time Protocol Administration Guide for OES .

Earlier versions of NetWare cannot be migrated using the plug-in. However, settings are migrated with the OS via the NetWare Migration Wizard.

Recommended Procedure

Follow the instructions for the migration module you are using.

Migration Issues