I typically use 3 external as servers and then have the core peer with
themselves. I don't think that will help in this case but it does seem like
something is borked.
On Tue, Nov 2, 2021 at 8:42 AM Lukas Tribus wrote:
> I don't think you will get anywhere without actually capturing the
>
After checking in multiple times throughout the day yesterday and seeing that
the clock is synchronized still even though those error messages keep popping
up I just filtered the log messages.
I don't really understand why IOS XR is so aggressive with NTP requests. All I
am trying to do is
I don't think you will get anywhere without actually capturing the
entire NTP traffic between the host and the NTP server and analyzing
it.
Lukas
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
To answer your question:
ntpd 4.2.6p5 on RHEL 7.
I think what I have learned most of all in 2021 is that I don't really like any
of Cisco's operating systems very much.
Thanks,
-Drew
-Original Message-
From: Julien Goodwin
Sent: Tuesday, November 2, 2021 4:04 AM
To: Drew Weaver ;
On 2/11/21 2:01 am, Drew Weaver wrote:
> Okay so I've been trying to figure out exactly what IOS XR has a problem with
> regarding our internal NTP servers.
>
> I was seeing things like this:
>
> RP/0/RSP0/CPU0:Oct 31 15:18:37.422 EDT: ntpd[263]: %IP-IP_NTP-5-HP_CONN_LOST
> : High priority
Okay so I've been trying to figure out exactly what IOS XR has a problem with
regarding our internal NTP servers.
I was seeing things like this:
RP/0/RSP0/CPU0:Oct 31 15:18:37.422 EDT: ntpd[263]: %IP-IP_NTP-5-HP_CONN_LOST :
High priority NTP peer connection lost - Stratum 2->3.
