- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2020 01:45 AM - edited 07-05-2021 11:30 AM
he same corresponding log consistently occurs.
The 172.x.7.x server has a preference for peer group.
Switch 1 switch 2 The same log occurs.
Why is this happening?
%DAEMON-3-SYSTEM_MSG: NTP: Peer 172.x.7.x with stratum 2 selected - ntpd[29687]
%DAEMON-3-SYSTEM_MSG: NTP: Peer 172.x.4.x with stratum 2 selected - ntpd[29687]
Solved! Go to Solution.
- Labels:
-
Other Wireless Topics
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2020 03:30 AM
@HyungyuLee47255 Hello,
If you configure multiple NTP servers, the client will prefer the NTP server with the lowest stratum value, so it is necessary to add "prefer" to a NTP that you want take it.
Check this other conversation about:
But if your configuration it is ok, maybe it is a bug:
https://quickview.cloudapps.cisco.com/quickview/bug/CSCvk38553
Best practices to configure NTP:
*** Rate All Helpful Responses ***
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2020 03:30 AM
@HyungyuLee47255 Hello,
If you configure multiple NTP servers, the client will prefer the NTP server with the lowest stratum value, so it is necessary to add "prefer" to a NTP that you want take it.
Check this other conversation about:
But if your configuration it is ok, maybe it is a bug:
https://quickview.cloudapps.cisco.com/quickview/bug/CSCvk38553
Best practices to configure NTP:
*** Rate All Helpful Responses ***
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2020 06:20 AM
I set it up. prefer.
I also checked the bug link.
If you set logging level daemon 2 among bug links, only critical logs are collected, not err logs.
That's why we need a fundamental solution.
