1. Checking Whether the NTP Status Is Normal

Run the display ntp-service status command to check whether the NTP status is normal.

[HUAWEI] display ntp-service status
clock status: unsynchronized
clock stratum: 16
reference clock ID: none
nominal frequency: 100.0000 Hz
actual frequency: 99.9995 Hz
clock precision: 2^18
clock offset: 0.0000 ms
root delay: 0.00 ms
root dispersion: 0.00 ms
peer dispersion: 0.00 ms
reference time: 14:25:55.477 UTC Jun 9 2010(CFBA22F3.7A4B76F6)

 
The clock status field indicates the clock status:
synchronized: The local clock is synchronized to an NTP server or clock source. If the clock status is synchronized, NTP clock synchronization is normal, and no action is required.
unsynchronized: The local clock is not synchronized to any NTP server. If the clock status is unsynchronized, an NTP clock synchronization error occurs. Go to the next step.
 

2. Checking Whether the Switch Can Communicate Normally with the NTP Server

Ping the NTP server from the switch to check whether the switch can communicate normally with the NTP server.

[HUAWEI] ping 20.1.14.1
PING 20.1.14.1: 56data bytes, press CTRL_C to break
Request time out
Request time out
Request time out
Request time out
Request time out
--- 20.1.14.1 ping statistics ---
5 packet(s) transmitted
0 packet(s) received
100.00% packet loss

 
 
If the switch cannot ping the NTP server, fix the ping failure. If the switch is directly connected to the NTP server, locate the fault according to “A Switch Cannot Be Pinged by a Directly Connected Device” in the Revelations of Troublesolving. If they are indirectly connected, check whether there are reachable routes between them, and whether there are policy-based routing restrictions on the switch, NTP server, and intermediate device.
 

3. Checking Whether the NTP Authentication Configuration Is Correct

Run the display current-configuration configuration ntp command to check whether the NTP configuration is correct.

[HUAWEI] display current-configuration configuration ntp
#ntp-service authentication enable //Enable NTP authentication.ntp-service authentication-keyid 1 authentication-mode md5 cipher @%@%*=$5;Ev+kSvxe^;%p@,J#*b:@%@% //Set the NTP authentication key.
ntp-service unicast-server 189.53.1.1 preference
ntp-service unicast-server 189.53.156.90
#
return

 
If NTP authentication is not configured on the switch, go to the next step.
If NTP authentication is configured on the switch, check whether the NTP authentication modes and keys on the switch and NTP server are the same.
If they are different, ensure that NTP authentication modes and keys on the switch and NTP server are the same. For example, the NTP authentication modes of the switch and NTP server are both md5, and their shared keys are both huawei.
 

[HUAWEI] ntp-service authentication-keyid 1 authentication-mode md5 cipher huawei

4. Checking Whether NTP Session Information Is Correct

Check whether NTP session information is correct.
Run the display ntp-service sessions verbose command to check detailed NTP session information.
 

<HUAWEI> display ntp-service sessions verbose
clock source: 189.53.1.1
clock stratum: 4
clock status: configured, master, sane, valid
reference clock ID: 10.72.80.150
local mode: client, local poll: 64, current poll: 64
peer mode: server, peer poll: 64, now: 25
offset: 9.7170 ms, delay: 39.16 ms, disper: 0.26 ms
root delay: 190.22 ms, root disper: 93.11 msreach: 377, sync dist: 0.214, sync state: 3
precision: 2^17, version: 3, peer interface: wildcard
reftime: 08:41:59.430 UTC Oct 13 2016(DBA9C757.6E2E5DE1)
orgtime: 08:43:59.175 UTC Oct 13 2016(DBA9C7CF.2CFE047D)
rcvtime: 08:43:59.200 UTC Oct 13 2016(DBA9C7CF.334373F3)
xmttime: 08:43:59.146 UTC Oct 13 2016(DBA9C7CF.256B65A9)
filter delay :  0.04   0.05   0.00   0.00   0.00   0.00   0.00   0.00
filter offset:  0.01   0.00   0.00   0.00   0.00   0.00   0.00   0.00
filter disper:  0.00   0.00  16.00  16.00  16.00  16.00  16.00  16.00

 
 
The reach field indicates the number of packets received from the NTP server. If this field displays 0, the switch does not receive any packet from the NTP server. Check NTP packet statistics. If this field does not display 0, go to the next step to collect information and seek technical support.
 
Check whether NTP packets are sent and received normally.
Run the display ntp-service statistics packet command to check NTP packet statistics.

<HUAWEI> display ntp-service statistics packet
NTP IPv4 Packet Statistical Information
---------------------------------------
Sent                                  : 100   //Number of sent packets
Send failures                      : 10
Received                              : 1000  //Number of received packets
Processed                          : 800
Dropped                            : 200
Validity test failures          : 50
Authentication failures      : 20
Invalid packets                 : 50
Access denied                   : 50
Rate-limited                    : 0
Processing delay                : 50
Interface disabled              : 0
Max dynamic association reached : 0
Server disabled                 : 0
Others                          : 0
Last 2 packets drop reasons:
[2011-11-24 12:19:26-08:00] Global drop: NTP service disabled for interface.
[2011-11-24 12:20:30-08:00] Global drop: NTP service disabled for interface.

 
 
Check NTP packet statistics multiple times. If the Sent field value keeps increasing but the Received field value does not increase, the switch sends request packets but does not receive any response from the NTP server. Locate the fault on the NTP server.
 

5. Collecting Information and Seeking Technical Support

If the fault persists, collect related information and seek technical support.
Collecting Fault Information
Collect operation results of the preceding steps and record the results in a file.
Collect all diagnostic information and export the information to a file.
 
Run the display diagnostic-information file-name command in the user view to collect diagnostic information and save the information to a file.

<HUAWEI> display diagnostic-information dia-info.txt
Now saving the diagnostic information to the device
100%
Info: The diagnostic information was saved to the device successfully.

 
 
When the diagnostic file is generated, you can export the file from the device using FTP, SFTP, or SCP.
 
NOTICE:
You can run the dir command in the user view to check whether the file is generated.
You can also run the display diagnostic-information command and save terminal logs in a diagnostic file on a disk.
If this command displays a long output, press Ctrl+C to abort this command.
This command displays diagnostic information, which helps locate faults but may affect system performance. For example, CPU usage may become high. Therefore, do not use this command when the system is running properly.
Running the display diagnostic-information command simultaneously on multiple terminals connected to the device is prohibited. This is because CPU usage of the device may obviously increase and the device performance may be degraded.
 
Collect the log and trap information on the device and export the information to files.
Run the save logfile all command in the user view to save the logs in the user log buffer area and diagnostic log buffer area to the user log file and diagnostic log file, respectively.

<HUAWEI> save logfile all
Info: Save logfile successfully.
Info: Save diagnostic logfile successfully.

 
 
When the diagnostic file is generated, you can export the file from the device using FTP, SFTP, or SCP.
NOTE:
You can also run the display logbuffer and display trapbuffer commands to view the log and trap information on the device, and save the information in diagnostic files on a disk.
If you need more technical support, please feel free to contact csd@telecomate.com.
 
NOTE:
Technical support personnel will provide instructions for you to submit all the collected information and files, so that they can locate faults.