Novell OPEN ENTERPRISE SERVER 2 SP2 - ADMINISTRATION, Implementation Manual, Page: 109 / 288

Network Services 109
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
Table 12-3
Time Synchronization Compatibility
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 2
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” on page 103 .
Upgrading from NetWare to OES 2
The OES 2 SP21 Migration Tool can migrate time synchronization services from NetWare to Linux.
For more information, see “
Migrating Timesync/NTP from NetWare to NTP on OES 2 Linux ” in the
OES 2 SP2: Migration Tool Administration Guide .
Module Compatibility
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.
XNTPD NLM (NetWare) Can consume time from
Š
Any NTP daemon.
Can provide time to
Š
All previous versions of Timesync.
Š
Any NTP daemon.
xntpd daemon (SLES 10) Can consume time from
Š
Any NTP daemon.
Can provide time to
Š
Any NTP daemon.
eDirectory eDirectory gets its time synchronization information from the host
OS (Linux or NetWare), not from the time synchronization modules.