Figure 70 Configuring Device A as the NTP server of Device B
3.Verifying the configuration
After the configuration, you can see that the current system time displayed on the System Time page is the same for Device A and Device B.
Configuration guidelines
A device can act as a server to synchronize the clock of other devices only after its clock has been synchronized. If the clock of a server has a stratum level higher than or equal to that of a client's clock, the client will not synchronize its clock to the server's.
The synchronization process takes a period of time. Therefore, the clock status may be unsynchronized after your configuration. In this case, you can refresh the page to view the clock status later on.
If the system time of the NTP server is ahead of the system time of the device, and the difference between them exceeds the Web idle time specified on the device, all online Web users are logged out because of timeout.
Configuring the system time at the CLI
You must synchronize your device with a trusted time source by using NTP or changing the system time before you run it on the network. Network management depends on an accurate system time setting, because the timestamps of system messages and logs use the system time. For NTP configuration, see Network Management and Monitoring Configuration Guide.
In a
IMPORTANT:
If you reboot the device, the system time and date are restored to the factory default. To ensure an accurate system time setting, you must change the system time and date or configure NTP for the device.
90
