chenhui
Reply WATTA Created Nov 4, 2020 06:48:45
(0)
(0)
Hi, NTP server 10.223.38.1 syncronize the time to the reference clock ID 223.255.185.2, which means all the switches will syncronize to this NTP server. The offset value displayed from the output of command display ntp status indicates the value to the 223.255.185.2. Example https://support.huawei.com/hedex/hdx.do?docid=EDOC1100020548&id=dc_cfg_ntp_0023&lang=en might help you clear the difference between that two value.
WATTA
Reply chenhui Created Nov 4, 2020 07:09:57
(0)
(0)
Hi that's clear i have new question. the clock offset value in display ntp status is related with display ntp trace or not ? As above i try to display ntp status it's show reference clock ID: 10.223.38.1 and the clock offset: -520.9136 ms but when i try to ntp trace it's show server 10.223.38.1, stratum 2, offset -0.2285 s i'm not clear in this issue
chenhui
Reply WATTA Created Nov 4, 2020 11:41:07
(0)
(0)
Hi, The offset displayed in the output of command display ntp status is the offset between the local system clock and the NTP server, while the offset displayed in the output of command display ntp trace is offset to the superior reference clock. In your situation, I think, that first offset value is the difference between the CE switch and 223.255.185.2, and the second one is the difference between the CE and 10.223.38.1 itself.
WATTA
Reply chenhui Created Nov 5, 2020 02:01:14
(0)
(0)
Hi, " In your situation, I think, that first offset value is the difference between the CE switch and 223.255.185.2 " That mean why i recive NTP spike in NTP status right ? How i can fix the NTP spike ? because i think this is the root cause of ntp state change in my CE switch. |
|
chenhui
Reply WATTA Created Nov 4, 2020 06:48:45
(0)
(0)
Hi, NTP server 10.223.38.1 syncronize the time to the reference clock ID 223.255.185.2, which means all the switches will syncronize to this NTP server. The offset value displayed from the output of command display ntp status indicates the value to the 223.255.185.2. Example https://support.huawei.com/hedex/hdx.do?docid=EDOC1100020548&id=dc_cfg_ntp_0023&lang=en might help you clear the difference between that two value.
WATTA
Reply chenhui Created Nov 4, 2020 07:09:57
(0)
(0)
Hi that's clear i have new question. the clock offset value in display ntp status is related with display ntp trace or not ? As above i try to display ntp status it's show reference clock ID: 10.223.38.1 and the clock offset: -520.9136 ms but when i try to ntp trace it's show server 10.223.38.1, stratum 2, offset -0.2285 s i'm not clear in this issue
chenhui
Reply WATTA Created Nov 4, 2020 11:41:07
(0)
(0)
Hi, The offset displayed in the output of command display ntp status is the offset between the local system clock and the NTP server, while the offset displayed in the output of command display ntp trace is offset to the superior reference clock. In your situation, I think, that first offset value is the difference between the CE switch and 223.255.185.2, and the second one is the difference between the CE and 10.223.38.1 itself.
WATTA
Reply chenhui Created Nov 5, 2020 02:01:14
(0)
(0)
Hi, " In your situation, I think, that first offset value is the difference between the CE switch and 223.255.185.2 " That mean why i recive NTP spike in NTP status right ? How i can fix the NTP spike ? because i think this is the root cause of ntp state change in my CE switch. |