Novell OPEN ENTERPRISE SERVER - PLANNING AND IMPLEMENTATION GUIDE 12-2010 Implementation Manual page 107

Planning and implementation guide
Hide thumbs Also See for OPEN ENTERPRISE SERVER - PLANNING AND IMPLEMENTATION GUIDE 12-2010:
Table of Contents

Advertisement

Time Synchronization Compatibility
Table 12-3
Module
TIMESYNC NLM (NetWare)
XNTPD NLM (NetWare)
xntpd daemon (SLES 10)
eDirectory
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
Upgrading from NetWare to OES 2
The OES 2 SP3 Migration Tool can migrate time synchronization services from NetWare to Linux.
For more information, see
OES 2 SP3: Migration Tool Administration
Compatibility
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.
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.
"Migrating Timesync/NTP from NetWare to NTP on OES 2
Guide.
101.
Linux" in the
Network Services 107

Advertisement

Table of Contents
loading

This manual is also suitable for:

Open enterprise server 2 sp3

Table of Contents