28.06.2014 Views

Discussion

Discussion

Discussion

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

You can also have all the routers synchronize time (chime) with each other. This is<br />

only practical for relatively small networks of, say, less than 50 routers. (For larger<br />

networks, you may want to have all the routers in a region or POP chime with each<br />

other.) You still want to have some stratum 1 clocks someplace in the mix. This<br />

arrangement allows the entire network to keep reasonable time even if some or all of<br />

the stratum 1 clocks go down for a while.<br />

Note that you can configure both server and peer statements on the same router.<br />

NTP automatic time synchronization works only if the times on the two systems are<br />

very close. Very close means between 128 milliseconds and 128 seconds apart. Time<br />

differences less than 128 milliseconds are dealt with by slowly slewing the time<br />

(speeding up or slowing down the clock), which means that the time is always monotonically<br />

increasing. Between 128 milliseconds and 128 seconds, the time is stepped,<br />

which means that it may go backward. Above this, the time is not changed at all. If<br />

the time is more than 1,000 seconds off, NTP records a system log message:<br />

Mar 16 16:41:41 5htp-fxp0 xntpd[28243]: time error 4217 over 1000 seconds; set<br />

clock manually<br />

If the time is this far off, you need to reset the clock manually:<br />

aviva@router1# set date ntp<br />

This command uses the NTP servers that you have configured. You do not have to<br />

reboot the router for the new time to take effect.<br />

On an operational note, one system will not synchronize to another that is not itself<br />

synchronized. Because the synchronization process is recursive, there must be an<br />

authoritative time source as the stratum 1 clock or all systems will be free running.<br />

An NTP purist will ensure that there are at least three or, better yet, four, independent<br />

sources of time available (traceable to three different stratum 1 servers) because<br />

this allows “false tickers” to be detected and discarded. At least two independent<br />

sources are needed for robustness, because if that one stratum 1 server goes down,<br />

the entire synchronization tree will basically come apart and all systems will free run<br />

in the mean time. Normally this isn’t too serious, but if the stratum 1 server never<br />

comes back, there will be no time synchronization whatsoever.<br />

6.5 Authenticating NTP<br />

Problem<br />

You want to make sure that the router gets time updates only from known and<br />

trusted NTP servers.<br />

This is the Title of the Book, eMatter Edition<br />

Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.<br />

Authenticating NTP | 187

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!