Most of you will know that Time Synchronization is one of the key elements for a proper working eDirectory Tree. Now that Novell has multiple OS systems (NetWare and Linux) its time to use NTP rather than Timesync for your time synchronization.
In the "old" NetWare days we only used timesync.nlm for the time synchronization in our network. We used the monitor.nlm tool to configure it. We had primary, secondary and reference time servers to build the timesynch "tree".
Now that we have more than one OS in our network we still would like to use one type of Timesynch method to synchronize time between all the servers we have.
In this lab I will configure my OES Linux server to be the Time Provider for the OES NetWare server that coexists in the same DA-CORP eDirectory TREE.
The first thing we have to do is to configure the NetWare server so it will get its time from the OES Linux server.
From the NetWare server console enter: monitor
From the menu list select "Server Parameters". In this menu scroll down and select "Time"
Now configure the following:
TIMESYNC configuration source: ON
TIMESYNC Time source: 10.200.200.1:123; make sure to use the semi-colon
TIMESYNC Type: Secondary
Exit the monitor tool, when you are asked to save the settings choose Yes.
From the NetWare Server console enter:
set timesync restart flag=on
After a couple of seconds you will see the message "TIMESYNC Restart flag action was SUCCESSFUL.
Now we have to start the NTP Deamon on the OES Linux Server. First make sure the NTP deamon is installed.
Open Yast and enter the Root password if necessary. Under the Software menu click "install Remove Software"".
In the Search field enter NTP.
Make sure the 3 boxes are checked as the figure above. If Not, click them and install them.
Now we are sure the NTP deamon is installed.
Now we have to start the NTP deamon so the OES NetWare server can get its time from the NTP OES Linux server.
To start the NTP Deamon, open a terminal window:
Enter "su" and the root user password.
Enter "rcxntpd start"
The time deamon will be started. To check if it is running enter:
As you can see the Deamon is still running ok.
Now you have to make sure the NTP Deamon starts when you reboot the server. Enter:
chkconfig xntpd on
Now the runlevel will be changed and it will start automatically when the server is started.
Now we need to check if the time synchronization between the two Servers is ok.
You can do this with the following command.
Open a terminal window, enter "su" and the root password.
Then, ndsrepair -T
As you can see in the above picture, the time is properly synchronized between the two servers.
You can also check this from the NetWare server console.
Enter "dsrepair" at the console and choose "Time Synchronization"
The next screen tells you the time is in sync. As you can see the DA1.OESlinux server is a non-NetWare server. The DA2 server is the secondary time server.
There is also a time debug console screen. In here you can see a bit more what happens. Change to the Time Debug screen.
As you can see there is more information in here.
^^^Polled server 10.200.200.1:123 NTP Source
offset.h = FFFFFFFF offset.l = EC87160B
Uniform Adjustment Requested: -76 Milliseconds
This server is configured as a SECONDARY
Sat Apr 7 14:41:50 2007
The first line tells you that the 10.200.200.1 is the NTP Provider of the server. This is the server where the time is coming from.
If the time synchronization is ok, the NetWare server will Poll for its time every 7 minutes. See TID2917323 for information on what happens to the poll interval if timesync is lost between the servers.
Once you have configured the NTP provider in your network, you can connect all servers in your network to use the server as the time provider.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.