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

Failure to Timely Synchronize the Clock of the NE80E (NTP Server) with that of the Client

Publication Date:  2012-07-27 Views:  40 Downloads:  0
Issue Description
 NE80E―NE40E: The NE80E acts as the NTP server and NE40E acts as the NTP client. The clock of the NE80E and that of the NE40E are synchronous. However, after the user modifies the time on the NE80E, the time of the NE40E is not synchronous to that of the NE80E. After viewing the NTP state on the NE40E, you will find the following:
<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: xxxxx ms : This is the difference between the time on NE80E and that on NE40E. 


 
Alarm Information
 Null 
Handling Process
 The cycle is automatically adjusted by the NTP internal algorithm and cannot be manually synchronized. If manual trigger is required, you can only delete the original NTP configuration on the client and then reconfigure NTP to realize immediate synchronization.
Delete the configuration:
[zhangdk_using]undo ntp-service unicast-server x.x.x.x―(x.x.x.x: IP address of the server end)
Recover the configuration:
[zhangdk_using]ntp-service unicast-server x.x.x.x―(x.x.x.x: IP address of the server end) 
 
Root Cause
 This is a normal symptom. The protocol specifies that the time synchronization needs about four cycles.
[zhangdk_using]display ntp-service sessions
source reference stra reach poll now offset delay disper
********************************************************************************
[12345]188.0.3.2 LOCAL(0) 8 377 1024 8 -2 7.9 0.9
note: 1 source(master),2 source(peer),3 selected,4 candidate,5 configured,
6 vpn-instance
poll indicates the time cycle. The synchronization needs 4 x 1024s. 
 
Suggestions
 Null 

END