防火墙F1060 NTP时间同步问题
- 1关注
- 1收藏，3527浏览
问题描述：
配置如下，但防火墙配置时钟源为203.107.6.88，但display ntp status显示同步LOCAL,时间不同步，为什么？
[ZJ-NBHDSSC-FW-F1060-iStack-01]disp cur | include ntp
clock protocol ntp context 1
ntp-service enable
ntp-service source Route-Aggregation1
ntp-service refclock-master 2
ntp-service unicast-server 203.107.6.88 source Route-Aggregation1
- 2019-01-29提问
- 举报
-
(0)
最佳答案
开启下debug ntp看下报文交换吧，看下是不是有acl限制。
- 2019-01-29回答
- 评论(1)
- 举报
-
(0)
*Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/ACL: -COntext=1; Access restrict: 0x00000008. *Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/AUTH: -COntext=1; Received a packet at 77246, from 203.107.6.88, mode 4, key ID 00000000, length 48, authentication result 0 *Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/PARAM: -COntext=1; Clock filter param: number 8, offset -28773.545928, delay 0.024841, dispersion 0.004058, jitter 0.002101, burst 0 *Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; endpoint -1, -28773.575340 *Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; endpoint 0, -28773.545928 *Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; endpoint 1, -28773.516515 *Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; peer 203.107.6.88, offset -28773.545928, low -28773.575340, high -28773.516515, flags 00000401 *Jan 30 00:45:46:455 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; Survivor 203.107.6.88, distance 2.004050 *Jan 30 00:45:46:455 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; Combine offset 0.000000000, jitter 0.000001907 *Jan 30 00:45:46:455 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SYNCH: -COntext=1; Synchronized to peer 127.127.1.0 *Jan 30 00:45:46:455 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; Clock update at 77246, sample 77186, session ID 32164, offset 0.000000 *Jan 30 00:45:46:455 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/ADJUST: -COntext=1; Reset clock state, time count difference 60, state 5->5, poll 6, count 0, offset 0.000 *Jan 30 00:45:46:455 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/ADJUST: -COntext=1; Adjust local clock: offset 0.000000000 jitter 0.000001907 freq 0.000 stab 0.000 poll 6 *Jan 30 00:45:50:428 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/REFCLOCK: -COntext=1; Reference clock sent a packet to 127.127.1.0 at 77250. *Jan 30 00:45:50:428 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/REFCLOCK: -COntext=1; Reference clock received a packet from 127.127.1.0 at 77250. *Jan 30 00:45:50:428 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/PARAM: -COntext=1; Clock filter param: number 8, offset 0.000000, delay 0.000000, dispersion 0.000928, jitter 0.000002, burst 0
防火墙的域间策略放通了么？
- 2019-01-29回答
- 评论(1)
- 举报
-
(0)
放通了，可以ping通 203.107.6.88，disp ntp sessions也显示offset有数据的啊
放通了，可以ping通 203.107.6.88，disp ntp sessions也显示offset有数据的啊
解决了，ntp-service refclock-master 2 这个改成ntp-service refclock-master 4 ，当服务器端的时钟层数大于或等于客户端的时钟层数时，客户端将不会与其同步。
- 2019-01-29回答
- 评论(0)
- 举报
-
(0)
编辑答案
亲~登录后才可以操作哦!
确定你的邮箱还未认证，请认证邮箱或绑定手机后进行当前操作
举报
×
侵犯我的权益
×
侵犯了我企业的权益
×
- 1. 您举报的内容是什么？（请在邮件中列出您举报的内容和链接地址）
- 2. 您是谁？（身份证明材料，可以是身份证或护照等证件）
- 3. 是哪家企业？（营业执照，单位登记证明等证件）
- 4. 您与该企业的关系是？（您是企业法人或被授权人，需提供企业委托授权书）
抄袭了我的内容
×
原文链接或出处
诽谤我
×
- 1. 您举报的内容以及侵犯了您什么权益？（请在邮件中列出您举报的内容、链接地址，并给出简短的说明）
- 2. 您是谁？（身份证明材料，可以是身份证或护照等证件）
对根叔社区有害的内容
×
不规范转载
×
举报说明
*Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/ACL: -COntext=1; Access restrict: 0x00000008. *Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/AUTH: -COntext=1; Received a packet at 77246, from 203.107.6.88, mode 4, key ID 00000000, length 48, authentication result 0 *Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/PARAM: -COntext=1; Clock filter param: number 8, offset -28773.545928, delay 0.024841, dispersion 0.004058, jitter 0.002101, burst 0 *Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; endpoint -1, -28773.575340 *Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; endpoint 0, -28773.545928 *Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; endpoint 1, -28773.516515 *Jan 30 00:45:46:454 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; peer 203.107.6.88, offset -28773.545928, low -28773.575340, high -28773.516515, flags 00000401 *Jan 30 00:45:46:455 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; Survivor 203.107.6.88, distance 2.004050 *Jan 30 00:45:46:455 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; Combine offset 0.000000000, jitter 0.000001907 *Jan 30 00:45:46:455 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SYNCH: -COntext=1; Synchronized to peer 127.127.1.0 *Jan 30 00:45:46:455 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/SELECT: -COntext=1; Clock update at 77246, sample 77186, session ID 32164, offset 0.000000 *Jan 30 00:45:46:455 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/ADJUST: -COntext=1; Reset clock state, time count difference 60, state 5->5, poll 6, count 0, offset 0.000 *Jan 30 00:45:46:455 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/ADJUST: -COntext=1; Adjust local clock: offset 0.000000000 jitter 0.000001907 freq 0.000 stab 0.000 poll 6 *Jan 30 00:45:50:428 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/REFCLOCK: -COntext=1; Reference clock sent a packet to 127.127.1.0 at 77250. *Jan 30 00:45:50:428 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/REFCLOCK: -COntext=1; Reference clock received a packet from 127.127.1.0 at 77250. *Jan 30 00:45:50:428 2019 ZJ-NBHDSSC-FW-F1060-iStack-01 NTP/7/PARAM: -COntext=1; Clock filter param: number 8, offset 0.000000, delay 0.000000, dispersion 0.000928, jitter 0.000002, burst 0