From: Chris Larson (clarson52@comcast.net)
Date: Tue Apr 06 2004 - 20:23:02 GMT-3
I think the rfc calls the mode symmetric from what I recall. It is
equivalent to the peer mode on a Cisco router. If I remember correctly, that
is what would be required to sync time and be synced or act as a client and
a server. It makes sense. For example, at the enterprise level you may want
all your devices to get time from an internal source or 2. Those 2 sources
would be peered with some outside stratum 1 or 2 sources and each other. In
the event of a disconnect with the outside for whatever reason your devices
will still source time from the 2 internal NTP devices and they will
continue to agree on a time to serve until their external peers are
reachable again in which case they will slowly drift to an agreement with
them.
There is a summary paper about it at www.supertechnetworks.com I believe in
the library. If not I will get it there.
Chris
----- Original Message -----
From: "Tim Last" <packtmon@yahoo.com>
To: "Group Study" <ccielab@groupstudy.com>
Sent: Tuesday, April 06, 2004 12:46 PM
Subject: NTP
> Hi guys,
>
> Does it make any sense for a rtr to be both a NTP master and client at the
same time?
>
> For example,
>
> Internet---------R1(NTP Master)------------R2(NTP client -gets sync from
R1)
>
> In this example, R1 gets it's time from an authoritative time source on
the Internet, so R1 is an NTP client. But, R1 is also configured as a NTP
Master from which R2 gets it's time.
>
> Thanks in advanced
>
> Do you Yahoo!?
> Yahoo! Mail - More reliable, more storage, less spam
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon May 03 2004 - 19:48:43 GMT-3