What email address or phone number would you like to use to sign in to Docs.com?
If you already have an account that you use with Office or other Microsoft services, enter it here.
Or sign in with:
Signing in allows you to download and like content, and it provides the authors analytical data about your interactions with their content.
Embed code for: 18.7 Network Time Protocol
Select a size
18.7 Network Time Protocol
Network Time Protocol Section 18: Implementing Device Hardening Correct time within networks is important for many reasons, including the following: Correct time allows tracking of events in the network in the correct order. Clock synchronization is critical for the correct interpretation of events within syslog data. Clock synchronization is critical for digital certificates. Networks use NTP to synchronize the clocks of various devices across a network. NTP can obtain the correct time from an internal or external time source. For example, it can obtain the time from a local master clock, a master clock on the Internet, or a GPS or atomic clock. A secure method of providing accurate time for the network is to implement your own private network master clocks, synchronized to UTC, using satellite or radio. However, if you do not wish to implement your own master clocks because of cost or other reasons, other clock sources are available on the Internet. You can configure a Cisco router as an NTP server, from which other devices (NTP clients) obtain their time settings. A router can act as an NTP server and client. You can also configure a router as an NTP peer. If a device is configured as an NTP peer, it will peer with another system and accept the time from that system; however, the peer configuration only needs to be configured on the device that will obtain the time from another system. For example, in the figure, the Branch router could be configured to obtain its time from the NTP Master Server. The Branch router would be the NTP client of the NTP Master Server. Router R1 could then be configured as an NTP peer of the Branch router. Up Next: Configuring NTP