topic Re: ntp client sync is not able to sync up, due to long root dist time in ICX Switches

ntp client sync is not able to sync up, due to long root dist time

Mats — Mon, 26 Feb 2024 10:44:18 GMT

Logs looks similar, this old one,

Debug: Aug 11 23:09:16 NTP: UDP ports are opened
Debug: Aug 11 23:09:21 NTP: ntp_peer_unfit: dist exceeded - root dist 15.9443 of peer x.x.x.6 has exceeded max dist 1.50096000
Debug: Aug 11 23:09:21 NTP: ntp_peer_unfit: unreachable - peer x.x.x.6 is not reachable [peer->reach 0

Really need the ntp maxdist option,

sw version: 10.0.10aT243.

Any suggestion?

rgds/Mats

Re: ntp client sync is not able to sync up, due to long root dist time

Mayank — Mon, 26 Feb 2024 11:07:14 GMT

Hi Mats,

Thank you for posting your query.

I understand that ntp client sync is not able to sync up, due to long root dist time

The time source seems behind several routers causing delay in synchronization or not reliable, Pls try with another ntp server closest to your location.Try setting the time manually then try NTP again. It looks like the time difference between switch and ntp server has exceeded that max difference allowed.

Moving Forward If this issue is not resolved , Please log a ticket with the below link so that we will help you further.

https://support.ruckuswireless.com/contact-us

I hope this information helps you

Please feel free to leave us a message if any concerns

Re: ntp client sync is not able to sync up, due to long root dist time

Mats — Mon, 26 Feb 2024 12:04:04 GMT

Hi,

No access, to any public/other ntp server, hence the question, regarding maxdist.

I'll log a ticket.

Thanks/Mats

Re: ntp client sync is not able to sync up, due to long root dist time

Mayank — Mon, 26 Feb 2024 13:08:41 GMT

Hi Mats,

Ack and Noted.

Thanks