networking:ntp
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| networking:ntp [2021/07/07 07:23] – bstafford | networking:ntp [2021/09/23 10:23] (current) – removed bstafford | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== NTP ====== | ||
| - | * There is a dedicated page for [[networking: | ||
| - | * There is a dedicated page to [[infoblox: | ||
| - | |||
| - | **DO NOT** use burst or iburst against public NTP servers unless they are announced they accept it (e.g. don't use it against *.ntp.org servers). More details [[networking: | ||
| - | |||
| - | **DO NOT** configure your system to use leap-smearing NTP servers as well as non-leap-smearing NTP servers at the same time. e.g. do not combine Google NTP with Cloudflare NTP. See [[ntp_pools# | ||
| - | |||
| - | NTP overview from an NTP [[https:// | ||
| - | ===== NTP Timezones ===== | ||
| - | * [[https:// | ||
| - | * [[https:// | ||
| - | * [[https:// | ||
| - | |||
| - | ===== Windows NTP ===== | ||
| - | **REMEMBER** It is important to note that W32Time will only actively synchronize with one time source at a time, even though you are able to list more than one time source. ([[https:// | ||
| - | |||
| - | Most NTP implementations would poll all the servers to choose the best sample, but as of Server 2008, Windows doesn' | ||
| - | |||
| - | ==== Test Windows NTP ==== | ||
| - | You can test NTP manually using Windows using the following command (where 192.168.1.1 is the IP of the NTP server). | ||
| - | < | ||
| - | |||
| - | ==== Resync Windows NTP ==== | ||
| - | Resynchronize the clock | ||
| - | < | ||
| - | |||
| - | ==== Show Windows NTP Timezone ==== | ||
| - | Show current timezone settings | ||
| - | < | ||
| - | |||
| - | ==== Show Windows NTP External Servers ==== | ||
| - | List external NTP servers (peers) | ||
| - | < | ||
| - | or | ||
| - | < | ||
| - | |||
| - | ==== Stop and Start Windows NTP ==== | ||
| - | < | ||
| - | < | ||
| - | |||
| - | ==== Manually set Windows NTP ==== | ||
| - | < | ||
| - | |||
| - | ===== Linux NTP ===== | ||
| - | ==== Set Linux Time ==== | ||
| - | < | ||
| - | |||
| - | ==== Check Status ==== | ||
| - | Check status of NTP on Ubuntu 16.04+ | ||
| - | < | ||
| - | If NTP is not on, try the following command | ||
| - | < | ||
| - | |||
| - | ===== Show NTP Status ===== | ||
| - | < | ||
| - | < | ||
| - | < | ||
| - | -p prints peers and -n means it will print IP and not FQDN | ||
| - | |||
| - | The * character is used to mark which peer you are currently synced to. | ||
| - | ===== Refid ===== | ||
| - | |||
| - | From [[https:// | ||
| - | |||
| - | Reference ID (refid) is a 32-bit code identifying the particular server or reference clock. | ||
| - | |||
| - | For packet stratum 0 (unspecified or invalid), this is a four-character ASCII [RFC1345] string, called the "kiss code", used for debugging and monitoring purposes. | ||
| - | |||
| - | For stratum 1 (reference clock), this is a four-octet, left-justified, | ||
| - | |||
| - | ^ ID ^ Clock Source ^ | ||
| - | | INIT | Initialising. NTP Server not yet reached. | | ||
| - | | LOCL | The local system clock | | ||
| - | | LCL | undisciplined local clock | | ||
| - | | LOCL | Undisciplined local clock | | ||
| - | | GOOG | means it is using one of Google' | ||
| - | | FB.. | means it is using Facebook time servers | | ||
| - | | MRS | is a multi-reference clock | | ||
| - | | SHM | means Shared Memory Driver | | ||
| - | | ATOM | with ATOM PPS | | ||
| - | | DCFa | DCF77 (with amplitude modulation) | | ||
| - | | DCFp | DCF77 (with phase modulation/ | ||
| - | | GPSs | GPS (with shared memory access - Meinberg) | | ||
| - | | GPSi | GPS (with interrupt based access - Meinberg) | | ||
| - | | GLNs | GPS/GLONASS (with shared memory access - Meinberg) | | ||
| - | | GLNi | GPS/GLONASS (with interrupt based access - Meinberg) | | ||
| - | | GOES | Geosynchronous Orbit Environment Satellite | | ||
| - | | GPS | Global Position System | | ||
| - | | GAL | Galileo Positioning System | | ||
| - | | PPS | Generic pulse-per-second | | ||
| - | | IRIG | Inter-Range Instrumentation Group | | ||
| - | | WWVB | LF Radio WWVB Ft. Collins, CO 60 kHz | | ||
| - | | DCF | LF Radio DCF77 Mainflingen, | ||
| - | | HBG | LF Radio HBG Prangins, HB 75 kHz | | ||
| - | | MSF | LF Radio MSF Anthorn, UK 60 kHz | | ||
| - | | JJY | LF Radio JJY Fukushima, JP 40 kHz, Saga, JP 60 kHz | | ||
| - | | LORC | MF Radio LORAN C station, 100 kHz | | ||
| - | | TDF | MF Radio Allouis, FR 162 kHz | | ||
| - | | CHU | HF Radio CHU Ottawa, Ontario | | ||
| - | | WWV | HF Radio WWV Ft. Collins, CO | | ||
| - | | WWVH | HF Radio WWVH Kauai, HI | | ||
| - | | NIST | NIST telephone modem | | ||
| - | | ACTS | NIST telephone modem | | ||
| - | | USNO | USNO telephone modem | | ||
| - | | PTB | European telephone modem | | ||
| - | | MRS | Multi Reference Sources | | ||
| - | |||
| - | |||
| - | |||
| - | ===== Burst and iBurst ===== | ||
| - | Using the burst option against a public server is considered abuse. Do not use this option with public NTP servers. Use it only for applications within your own organization. | ||
| - | |||
| - | Burst and iBurst are only relevant if the NTP Servers you are synchronising to actually support these features, if not they can be switched off. | ||
| - | |||
| - | The ' | ||
| - | |||
| - | The ' | ||
| - | |||
| - | |||
| - | Microsoft only support Simple Network Time Protocol (sntp) which is compatible with NTP clients but does not offer all the functionality of NTP (including Burst and iBurst). Microsoft servers will just ignore the burst and iburst options. | ||
| - | |||
| - | |||
networking/ntp.1625642604.txt.gz · Last modified: (external edit)
