Rtc

This scenario shows how to configure NTP client/server authentication.

../../../../_images/client.svg

Test RTC Synchronization

Description

Checks that RTC is working properly on machines that have an RTC device.

Scenario

Step 1: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address 10.100.0.100/24
set protocols static route 0.0.0.0/0 next-hop 10.100.0.50
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set system ntp master prefer
set system ntp master stratum 3

Step 2: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 10.100.0.50/24
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Ping IP address 10.100.0.100 from DUT0:

admin@DUT0$ ping 10.100.0.100 count 1 size 56 timeout 1
Show output
PING 10.100.0.100 (10.100.0.100) 56(84) bytes of data.
64 bytes from 10.100.0.100: icmp_seq=1 ttl=64 time=0.541 ms

--- 10.100.0.100 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.541/0.541/0.541/0.000 ms

Step 4: Run command set date 2025-02-18 12:00:00 at DUT0 and expect this output: Step 5: Run command set date ntp 10.100.0.100 at DUT0 and check if output does not contain the following tokens:

skipping this server
Show output
Date was successfully updated!

Step 6: Run command show date at DUT0 and check if output does not contain the following tokens:

Tue
Show output
Wed 19 Feb 2025 21:05:33 +00:00

Step 7: Run command set date hwclock from-system debug at DUT0 and expect this output:

Show output
hwclock from util-linux 2.38.1
System Time: 1739999133.890804
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1739999133 seconds after 1969
Last calibration done at 1739999133 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
RTC type: 'rtc_cmos'
Using delay: 0.500000 seconds
missed it - 1739999133.893313 is too far past 1739999133.500000 (0.393313 > 0.001000)
1739999134.500000 is close enough to 1739999134.500000 (0.000000 < 0.002000)
Set RTC to 1739999134 (1739999133 + 1; refsystime = 1739999133.000000)
Setting Hardware Clock to 21:05:34 = 1739999134 seconds since 1969
ioctl(RTC_SET_TIME) was successful.
Not adjusting drift factor because the --update-drift option was not used.
New /etc/adjtime data:
0.000000 1739999133 0.000000
1739999133
UTC

Step 8: Run command set date hwclock to-system debug at DUT0 and expect this output:

Show output
hwclock from util-linux 2.38.1
System Time: 1739999134.652293
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1739999133 seconds after 1969
Last calibration done at 1739999133 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2025/02/19 21:05:35
Hw clock time : 2025/02/19 21:05:35 = 1739999135 seconds since 1969
Time since last adjustment is 2 seconds
Calculated Hardware Clock drift is 0.000000 seconds
Calling settimeofday(NULL, 0) to lock the warp_clock function.
Calling settimeofday(1739999135.000000, NULL) to set the System time.

Step 9: Run command show date at DUT0 and check if output does not contain the following tokens:

Tue
Show output
Wed 19 Feb 2025 21:05:35 +00:00

Test RTC Synchronization With Drift

Description

Tests that RTC is working properly on machines that have an RTC device (while adjusting the drift too).

Scenario

Step 1: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address 10.100.0.100/24
set protocols static route 0.0.0.0/0 next-hop 10.100.0.50
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set system ntp master prefer
set system ntp master stratum 3

Step 2: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 10.100.0.50/24
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Ping IP address 10.100.0.100 from DUT0:

admin@DUT0$ ping 10.100.0.100 count 1 size 56 timeout 1
Show output
PING 10.100.0.100 (10.100.0.100) 56(84) bytes of data.
64 bytes from 10.100.0.100: icmp_seq=1 ttl=64 time=8.02 ms

--- 10.100.0.100 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 8.018/8.018/8.018/0.000 ms

Step 4: Run command set date 2025-02-18 12:00:00 at DUT0 and expect this output: Step 5: Run command set date ntp 10.100.0.100 at DUT0 and check if output does not contain the following tokens:

skipping this server
Show output
Date was successfully updated!

Step 6: Run command show date at DUT0 and check if output does not contain the following tokens:

Tue
Show output
Wed 19 Feb 2025 21:05:48 +00:00

Step 7: Run command set date hwclock from-system update-drift debug at DUT0 and expect this output:

Show output
hwclock from util-linux 2.38.1
System Time: 1739999148.771438
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1739999147 seconds after 1969
Last calibration done at 1739999147 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2025/02/19 21:05:49
Hw clock time : 2025/02/19 21:05:49 = 1739999149 seconds since 1969
Time since last adjustment is 2 seconds
Calculated Hardware Clock drift is 0.000000 seconds
RTC type: 'rtc_cmos'
Using delay: 0.500000 seconds
1739999149.500000 is close enough to 1739999149.500000 (0.000000 < 0.001000)
Set RTC to 1739999149 (1739999149 + 0; refsystime = 1739999149.000000)
Setting Hardware Clock to 21:05:49 = 1739999149 seconds since 1969
ioctl(RTC_SET_TIME) was successful.
Not adjusting drift factor because it has been less than four hours since the last calibration.
New /etc/adjtime data:
0.000000 1739999149 0.000000
1739999149
UTC

Step 8: Run command set date hwclock to-system debug at DUT0 and expect this output:

Show output
hwclock from util-linux 2.38.1
System Time: 1739999149.658661
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1739999149 seconds after 1969
Last calibration done at 1739999149 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2025/02/19 21:05:50
Hw clock time : 2025/02/19 21:05:50 = 1739999150 seconds since 1969
Time since last adjustment is 1 second
Calculated Hardware Clock drift is 0.000000 seconds
Calling settimeofday(NULL, 0) to lock the warp_clock function.
Calling settimeofday(1739999150.000000, NULL) to set the System time.

Step 9: Run command show date at DUT0 and check if output does not contain the following tokens:

Tue
Show output
Wed 19 Feb 2025 21:05:50 +00:00