No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

The Time Update in the NTP Server Fails to Be Synchronized to the Clients Due to the NTP Implementation Mechanism

Publication Date:  2012-07-27 Views:  31 Downloads:  0
Issue Description
A large number of NE40Es are attached to the NE80E as NTP clients. The NE80E is the NTP server. Previously, the time is the same on the server and the clients. One day, the user finds that the clock on the NE80E is inaccurate and so manually adjusts the time. Then the user finds that the time update on the NE80E is not synchronized to the clients. After the dis ntp-service status command is executed on an NE40E, the following information is displayed:
<R1_NE40E>dis ntp-service status
clock status: synchronized
clock stratum: 8
reference clock ID: LOCAL(0)
nominal frequency: 100.0000 Hz
actual frequency: 100.0000 Hz
clock precision: 2^18
clock offset: 71223 ms This value is just the time difference between the NE80E and NE40Es. 
 
Alarm Information
Null
Handling Process
Delete NTP settings from the NE40E and then reconfigure the settings. After these operations, the clock on the NE40E is immediately synchronized.
Run the following command to delete NTP settings:
[R5-NE40E]undo ntp-service unicast-server x.x.x.x----------------- (x.x.x.x stands for the IP address of the server)
Run the following command to restore the NTP settings:
[R5-NE40E]ntp-service unicast-server x.x.x.x----------------- (x.x.x.x stands for the IP address of the server) 
 
Root Cause
The time lag between the server and the clients is normal. The time update on the NTP server is synchronized to the clients after about four cycles. Therefore, it takes some time for the clients to implement automatic clock synchronization. Run the dis ntp-service sessions command on the NE40E. The value below poll is the duration of a cycle, expressed in seconds. The cycle is automatically adjusted through the internal algorithm of NTP. The clocks cannot be manually synchronized. If manual triggering is required, you have to delete NTP settings from the clients and then reconfigure the settings. After these operations, the clocks can be synchronized.
<R5-NE40E>dis ntp-service sessions 
        source          reference       stra reach poll  now offset delay disper
********************************************************************************
 [12345]11.11.11.1      LOCAL(0)           8  377 1024 1007     -0   19.4   15.8
Suggestions
Null

END