Novell OPEN ENTERPRISE SERVER 2 SP2 - ADMINISTRATION, Руководство по внедрению, Страница: 112 / 288

112 OES 2 SP2: Planning and Implementation Guide
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
Changing Time Synchronization Settings on a SLES 10 Server
This method works both in the GUI and at the command prompt and is the most reliable method for
ensuring a successful NTP implementation.
1 Launch YaST on your SLES 10 server by either navigating to the application on the desktop or
typing
yast
at the command prompt.
2 Click Network Services > NTP Client .
3 In the NTP Client Configuration dialog box, click Complex Configuration .
4 Modify the NTP time settings as your needs require.
Changing Time Synchronization Settings on a NetWare Server
Time synchronization settings and their modification possibilities are documented in the following
administration guides:
Š Timesync: NW 6.5 SP8: Network Time Synchronization Administration Guide
Š
NTP: NW 6.5 SP8: NTP Administration Guide
12.3.6 Daylight Saving Time
For information about daylight saving time (DST), see the DST Master TID on the Novell Support
site (http://www.novell.com/support/php/
search.do?cmd=displayKC&docType=kc&externalId=3094409)
12.4 Discovery Services
Various discovery mechanisms are usually available on an OES 2 network.
Š
DNS/DHCP
Š Directory services
Š
Local host configuration files
Š Service Location Protocol (SLP services)
Š
Universal Description, Discovery, and Integration (UDDI) server
Some systems are designed to leverage only a single discovery technology. Others choose among
the various providers. And some use different technologies in combination with each other.
Š
Section 12.4.1, “Novell SLP and OpenSLP,” on page 112
Š
Section 12.4.2, “WinSock and Discovery Is NetWare only,” on page 113
Š
Section 12.4.3, “UDDI and Discovery,” on page 113
Š
Section 12.4.4, “CIMOM and Discovery,” on page 113
12.4.1 Novell SLP and OpenSLP
NetWare 3 and 4 used the IPX-based Service Advertising Protocol (SAP) as the discovery
mechanism. All the servers advertised their services automatically. If a server went offline, the SAP
information on the network was dynamically refreshed.