Sorry meant "I believe that you could drop the NTP master on B as this
causes confusion in NTP and just use the *NTP server*,
On Mon, Dec 19, 2011 at 8:31 AM, Bill Lake wrote:
> I think you want router B's time to be close to or the same as router A's,
> I believe that you could drop the NTP mas
I think you want router B's time to be close to or the same as router A's,
I believe that you could drop the NTP master on B as this causes confusion
in NTP and just use the NTP master, to ensure the clock is closest to
router A on newer routers use the update calendar or manually set time on
older
Hi Mohammed,
Unfortunately I got the same result with the ntp peer.
If you get a chance, try it out next time you jump on a proctorlab session
and let me know what your findings are
Thanks!
Romain
On Thu, Dec 15, 2011 at 5:59 PM, Mohd Baqari wrote:
> On RTR B:
>
> 1. Instead of ntp server you
On RTR B:
1. Instead of ntp server you need to use ntp peer
2. You need to enable ntp access-group peer.
Do this and lets see the output.
Regards,
Mohammed Al Baqari
Sent from my iPhone
On Dec 16, 2011, at 12:48 AM, romain mullier wrote:
>
> Hi,
>
> Can anyone explain which are the circums
Hi,
Can anyone explain which are the circumstances that make your NTP flagged
as falseticker?
The requirement is this:
Router A is NTP server.
Router B synchronizes its clock with router A. If router A is unavailable
then Router B uses its own internal clock.
So basically Router B can synchroniz
