9.1 XNTPD

This section provides solutions to problems you might encounter when using XNTPD.

XNTPD -T slp does not update ntp.conf

Problem: You are looking for a server that is advertising its Timesync SINGLE time source service that is in a different tree.
Action: To verify this:

  1. Enter display slp services timesync.novell at the server console to display a list of servers advertising the Timesync SINGLE service.

  2. If you know the tree name of your server, then enter display slp services timesync.novell://treename==mytreename.

XNTPD broadcast functionality is not working

Problem: You are using an incorrect subnet broadcast ID.
Action: Ensure that you have specified the correct subnet broadcast address.
Action: Use showipconf in NTPQ.

Unable to configure XNTPD remotely using XNTPDC

Problem: You do not have the proper keys to authenticate to the server.
Action: Ensure that you have the request key ID and the key of the server you are trying to configure. You can obtain the request key ID from the ntp.conf file and the request key from the ntp.keys file. Both files are located in the sys:\etc directory.

XNTPD cannot obtain time in the broadcast/multicast mode

Problem: You have not authenticated to broadcast/multicast server.
Action: Start XNTPD with the -A option. This disables authentication.
Action: Obtain the time provider's key, copy it to ntp.keys file, and mark it as a trusted key in ntp.conf. Ensure that this key is present in the broadcast/multicast server.

XNTPD takes a long time to synchronize

Problem: The polling interval is too big, so the polls are too far apart. XNTPD needs 5 successful polls (offset lesser then 150 ms) to transit into synchronized mode. By default, XNTPD has the minpoll value set to 4. This means that every poll is 2 power 4 seconds away. Hence, XNTPD syncs in, at best, 5 * (2 power 4) seconds.
Action: Minimize the polling interval by using minpoll. Set minpoll equal to 4 in the ntp.conf. file while giving the time provider details. For example: server IP address minpoll 4
Action: Use XNTPD with the -S option or stepclock in the ntp.conf. file to synchronize within 10 seconds. For more information, see -S or stepclock.

Unable to enable the debug message with XNTPD

Problem: Unable to get the debug message with XNTPD.
Action: To enable the debug message with XNTPD, enter the following at the command prompt:

Load XNTPD -D 4

Time does not synchronize if XNTPD is loaded without the -A parameter in the multicast mode

Problem: In the multicast mode, time is not synchronized if XNTPD is loaded without the -A parameter.
Action: If you load XNTPD with the -A parameter, it means that you are loading XNTPD with authentication disabled.

By default, in the broadcast/multicast mode, XNTPD starts with authentication enabled. This is because XNTPD can obtain time only from a server it trusts and the trust is achieved only through authentication.

If there are no masquerading servers in the subnet/network, you can start XNTPD with authentication disabled (-A option).

Action: Obtain the time provider's key, copy it to the ntp.keys file, and mark it as a trusted key in the ntp.conf file. Ensure that this key is present in the broadcast/multicast server.

Time does not synchronize in the broadcast/multicast mode it takes time from the local clock

Problem: A local clock is not a very reliable time source and it cannot be broadcast or multicast.
Action: Use the prefer keyword when using a local clock as follows: server 127.127.1.0 prefer

XNTPD hangs while loading

Action: Ensure that XNTPD, NTPQ, NTPDate, and XNTPDC have unloaded successfully.

XNTPD goes out of synch frequently

Action: Run XNTPD with the -S option

XNTPD exits after 5 to 10 minutes

Problem: The time offset between the client and server is too big, so XNTPD does not adjust the clock and it exits.
Action: Start XNTPD with the -S option.