ntp同步异常
- 0关注
- 0收藏，672浏览
问题描述：
ntp同步异常，下面是debugg信息
组网及组网描述：
*May 6 17:51:11:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/PACKET_SEND: -COntext=1;
packet to 10.207.30.61, length: 48
leap: 3, version: 4, mode: 3, vrfindex: 1
stratum: 16, poll: 6, precision: 2^-20
rdel: 0.000, rdsp: 0.854, refid: INIT
reftime: 00000000.00000000 Mon, Jan 1 1900 8:00:00.000
orgtime: ebc3e948.b868e4f1 Tue, May 6 2025 9:50:00.720
rectime: ebc459ce.1664be11 Tue, May 6 2025 17:50:06.087
xmttime: ebc45a0f.16449fce Tue, May 6 2025 17:51:11.086
*May 6 17:51:11:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/PACKET_RECV: -COntext=1;
packet from 10.207.30.61 to 10.31.60.76 on M-GigabitEthernet1/0/0
leap: 0, version: 4, mode: 4, vrfindex: 1
stratum: 4, poll: 6, precision: 2^-24
rdel: 40.421, rdsp: 1.495, refid: 10.207.47.55
reftime: ebc3e7ad.a7be8f47 Tue, May 6 2025 9:43:09.655
orgtime: ebc45a0f.16449fce Tue, May 6 2025 17:51:11.086
rectime: ebc3e989.b85b4aa3 Tue, May 6 2025 9:51:05.720
xmttime: ebc3e989.b85cac2a Tue, May 6 2025 9:51:05.720
inptime: ebc45a0f.16627f00 Tue, May 6 2025 17:51:11.087
*May 6 17:51:11:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/ACL: -COntext=1; Access restrict: 0x00000004.
*May 6 17:51:11:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/AUTH: -COntext=1; Received a packet at 582389, from 10.207.30.61, mode 4, key ID 00000000, length 48, authentication result 0
*May 6 17:51:11:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/PARAM: -COntext=1; Clock filter param: number 8, offset -28805.367059, delay 0.000435, dispersion 0.000971, jitter 0.000773, burst 0
*May 6 17:51:11:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/SELECT: -COntext=1; peer 10.207.30.60, flash 0x00001000, flags 0x00000621, reach 239, root distance 0.024101
*May 6 17:51:11:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/SELECT: -COntext=1; peer 10.207.30.61, flash 0x00001000, flags 0x00000601, reach 223, root distance 0.023667
*May 6 17:51:11:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/ADJUST: -COntext=1; Reset clock state, time count difference 57, state 1->1, poll 1, count 0, offset 0.000
*May 6 17:51:21:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/PACKET_SEND: -COntext=1;
packet to 10.207.30.60, length: 48
leap: 3, version: 4, mode: 3, vrfindex: 1
stratum: 16, poll: 6, precision: 2^-20
rdel: 0.000, rdsp: 0.137, refid: INIT
reftime: 00000000.00000000 Mon, Jan 1 1900 8:00:00.000
orgtime: ebc3e950.b860077e Tue, May 6 2025 9:50:08.720
rectime: ebc459d6.166032dc Tue, May 6 2025 17:50:14.087
xmttime: ebc45a19.1644badf Tue, May 6 2025 17:51:21.086
*May 6 17:51:21:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/PACKET_RECV: -COntext=1;
packet from 10.207.30.60 to 10.31.60.76 on M-GigabitEthernet1/0/0
leap: 0, version: 4, mode: 4, vrfindex: 1
stratum: 4, poll: 6, precision: 2^-24
rdel: 40.894, rdsp: 0.854, refid: 10.207.47.55
reftime: ebc3e927.bc512638 Tue, May 6 2025 9:49:27.735
orgtime: ebc45a19.1644badf Tue, May 6 2025 17:51:21.086
rectime: ebc3e993.b855c246 Tue, May 6 2025 9:51:15.720
xmttime: ebc3e993.b8572f90 Tue, May 6 2025 9:51:15.720
inptime: ebc45a19.1662521a Tue, May 6 2025 17:51:21.087
*May 6 17:51:21:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/ACL: -COntext=1; Access restrict: 0x00000004.
*May 6 17:51:21:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/AUTH: -COntext=1; Received a packet at 582399, from 10.207.30.60, mode 4, key ID 00000000, length 48, authentication result 0
*May 6 17:51:21:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/PARAM: -COntext=1; Clock filter param: number 8, offset -28805.367143, delay 0.000430, dispersion 0.000991, jitter 0.000780, burst 0
*May 6 17:51:21:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/SELECT: -COntext=1; peer 10.207.30.60, flash 0x00001000, flags 0x00000621, reach 223, root distance 0.023287
*May 6 17:51:21:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/SELECT: -COntext=1; peer 10.207.30.61, flash 0x00001000, flags 0x00000601, reach 223, root distance 0.023817
*May 6 17:51:21:087 2025 AHHN2-PSC-S7F7-PODM-M-IPS-T5000-1 NTP/7/ADJUST: -COntext=1; Reset clock state, time count difference 10, state 1->1, poll 1, count 0, offset 0.000
- 2025-05-06提问
- 举报
-
(0)
最佳答案
debug信息中NTP的stratum值为16（未同步状态）
1. 检查NTP配置层数
若设备配置了本地参考时钟（如ntp-service refclock-master），需确保其stratum值合理。例如：
# 正确示例：本地时钟层数设置为2（需低于上游NTP服务器的层数）
[H3C] ntp-service refclock-master 2
若层数过高（如设置为3，而服务器为2），会导致同步失败。
2. 验证安全策略放行NTP
确保安全策略允许NTP协议：
[H3C] security-policy ip
[H3C-security-policy-ip] rule 10 name ntp
[H3C-security-policy-ip-10-ntp] service ntp
[H3C-security-policy-ip-10-ntp] action pass
3. 检查NTP版本一致性
若服务器使用NTPv3，客户端需显式指定版本：
[H3C] ntp-service unicast-server 10.207.30.61 version 3
4. 确认clock protocol配置
删除可能导致冲突的本地时钟协议：
[H3C] undo clock protocol none # 避免强制使用本地时钟
[H3C] clock protocol ntp context 1 # 确保context编号与实际一致
5. 检查网络连通性
执行ping 10.207.30.61验证NTP服务器可达性，并检查中间设备（防火墙/路由）的ACL或策略是否拦截NTP（UDP 123端口）。
关键日志解析：
stratum: 16表示设备未同步到有效时钟源。
refid: INIT表明未选择参考时钟，需检查服务器可达性及配置。
若服务器回复但设备未处理，可能因安全策略或版本不匹配丢弃报文。
- 2025-05-06回答
- 评论(1)
- 举报
-
(0)
什么问题导致的呢？
亲~登录后才可以操作哦!
确定你的邮箱还未认证，请认证邮箱或绑定手机后进行当前操作
举报
×
侵犯我的权益
×
侵犯了我企业的权益
×
- 1. 您举报的内容是什么？（请在邮件中列出您举报的内容和链接地址）
- 2. 您是谁？（身份证明材料，可以是身份证或护照等证件）
- 3. 是哪家企业？（营业执照，单位登记证明等证件）
- 4. 您与该企业的关系是？（您是企业法人或被授权人，需提供企业委托授权书）
抄袭了我的内容
×
原文链接或出处
诽谤我
×
- 1. 您举报的内容以及侵犯了您什么权益？（请在邮件中列出您举报的内容、链接地址，并给出简短的说明）
- 2. 您是谁？（身份证明材料，可以是身份证或护照等证件）
对根叔社区有害的内容
×
不规范转载
×
举报说明
什么问题导致的呢？