Difference between revisions of "DistOS-2011W NTP"
(Created page with "=Introduction= Describe the system(s) that you examined or compared. Why did you choose them? Be sure to specify a thesis that you argue in the rest of the document. Since th…") |
|||
| Line 1: | Line 1: | ||
=Introduction= | =Introduction= | ||
1. Introduction: | |||
1.1 Context/Background | |||
Network Time Protocol (NTP) synchronizes clocks of hosts and routers. According to NIST estimates there are 10-20 million NTP servers and clients deployed in the internet and its tributaries all over the world. NTP software has been ported to almost every workstation and server platform available today – from PCs to Cray’s – UNIX, Windows, VMS and embedded systems, even home routers and battery backup systems. | |||
NTP provides nominal accuracies of low tens of milliseconds on WANs, sub milliseconds on LANs and sub microseconds using a precision time source such as cesium oscillator or GPS receiver. Our time protocol was designed over the LAN and our goal was to achieve sub milliseconds of accuracy. | |||
1.2 Importance | |||
Precision of time is very important in the computer world. Following are some example why it is so important to maintain a precise and accurate time. | |||
Network monitoring, measurement and control, Distributed database transaction journaling and logging, Secure document timestamps with cryptographic certification, Radio and TV programming lunch and monitoring, Stock market buy and sell orders, Distributed network gaming and training, etc. | |||
1.3 Definition of the problem | |||
My goal was to acquire time accuracy in the Linux lab assuming that all the computers do not have internet connection. To time synchronize all the computers I had to build our own hierarchy of NTP servers and clients. | |||
1.4 Summary of the result | |||
An efficient hierarchy of NTP server and client has been implemented. Precision of | |||
Sub milliseconds were achieved. | |||
1.5 Outline of the report | |||
Detailed background information and the structure of our time protocol are provided in Section | |||
2. The development setup and code explanation is reviewed in Section 3. Details of which server/client contains which files are given in section 4. My contributions in this implementation are described in Section 5. | |||
=Systems/Programs in the Space= | =Systems/Programs in the Space= | ||
Revision as of 15:44, 21 February 2011
Introduction
1. Introduction:
1.1 Context/Background
Network Time Protocol (NTP) synchronizes clocks of hosts and routers. According to NIST estimates there are 10-20 million NTP servers and clients deployed in the internet and its tributaries all over the world. NTP software has been ported to almost every workstation and server platform available today – from PCs to Cray’s – UNIX, Windows, VMS and embedded systems, even home routers and battery backup systems.
NTP provides nominal accuracies of low tens of milliseconds on WANs, sub milliseconds on LANs and sub microseconds using a precision time source such as cesium oscillator or GPS receiver. Our time protocol was designed over the LAN and our goal was to achieve sub milliseconds of accuracy.
1.2 Importance
Precision of time is very important in the computer world. Following are some example why it is so important to maintain a precise and accurate time.
Network monitoring, measurement and control, Distributed database transaction journaling and logging, Secure document timestamps with cryptographic certification, Radio and TV programming lunch and monitoring, Stock market buy and sell orders, Distributed network gaming and training, etc.
1.3 Definition of the problem
My goal was to acquire time accuracy in the Linux lab assuming that all the computers do not have internet connection. To time synchronize all the computers I had to build our own hierarchy of NTP servers and clients.
1.4 Summary of the result
An efficient hierarchy of NTP server and client has been implemented. Precision of Sub milliseconds were achieved.
1.5 Outline of the report Detailed background information and the structure of our time protocol are provided in Section 2. The development setup and code explanation is reviewed in Section 3. Details of which server/client contains which files are given in section 4. My contributions in this implementation are described in Section 5.
Systems/Programs in the Space
Give an overview of the area you are examining. What systems/programs are out there?
Evaluated Systems/Programs
Describe the systems individually here - their key properties, etc. Use subsections to describe different implementations if you wish. Briefly explain why you made the selections you did.
Experiences/Comparison (multiple sections)
In multiple sections, describe what you learned.
Discussion
What was interesting? What was surprising? Here you can go out on tangents relating to your work
Conclusion
Summarize the report, point to future work.
References
Give references in proper form (not just URLs if possible, give dates of access).