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>Search


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


Executing display ntp-service trace on a Clock-Synchronized ME60 Timed Out As the NTP Server Was Incorrectly Configured

Publication Date:  2013-10-26 Views:  98 Downloads:  0
Issue Description

Networking information:

ME60------------Third-party equipment (NTP server)


Problem description:

The ME60 had successfully synchronized its clock with the NTP server, but time-out was displayed after a technician ran the display ntp-service trace command. The command output is as follows:

[ME60]display ntp-service status                                  
 clock status: synchronized                                                     
 clock stratum: 3                                                               
 reference clock ID:                                            
 nominal frequency: 100.0000 Hz                                                 
 actual frequency: 100.0005 Hz                                                  
 clock precision: 2^17                                                          
 clock offset: 149.2925 ms                                                      
 root delay: 35.22 ms                                                           
 root dispersion: 143.24 ms                                                     
 peer dispersion: 128.33 ms                                                     
 reference time: 06:13:30.888 UTC May 4 2010(CF8A398A.E38012DF)    
[HY-HP-BAS-1.M.ME60]display ntp-service trace                                   
 server ,stratum 3, offset 0.145230, synch distance 0.16109           *Timeout* 
Handling Process

To address the issue, Huawei performed the following operations and observed the following information:

1. Checked the configurations on the ME60.

The configurations are as follows:

interface LoopBack0
ip address
ntp-service source-interface loopBack0
ntp-service unicast-server  

No error was found.

2. Ruled out that ntp trace packets were discarded by the intermediate devices.

ntp trace packets are normal UDP packets and used the port (port 123) on which the NTP synchronization status was checked. Therefore, ntp trace packets could not be discarded by the intermediate devices, because the ME60 had synchronized its clock with the NTP server.

3. Configured an ACL and printed the ip debug information (for details, see the attachment).

The IP address of the NTP server in the ntp Receiving packet was, whereas that displayed in the output of the display ntp trace command was (the NTP server's interface IP address).

The ME60 processes only packets sent by As a result, the execution of the display ntp trace command timed out.

4. Checked the configurations on the NTP server.

The NTP server was incorrectly configured.
Root Cause
The NTP server was incorrectly configured.
Correct the configurations on the NTP server.