Ntp Client

Test suite to check NTP client using VRF, PBR, authentication and RTC synchronization

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

Test NTP Service

Description

DUT0 is configured to obtain time information from a static configured NTP server

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.215.200.100/24
set protocols static route 0.0.0.0/0 next-hop 10.215.200.50
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.215.200.50/24

Step 3: Ping IP address 10.215.200.100 from DUT0:

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

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

Step 4: Run command set date 2024-02-25 12:00:00 at DUT0 and expect this output: Step 5: Run command set date ntp 10.215.200.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:

Sun
Show output
Mon 26 Feb 2024 20:17:03 UTC +00:00

Step 7: Run command set date 2024-02-25 12:00:00 at DUT0 and expect this output: Step 8: Run command system ntp status at DUT0 and check if output contains the following tokens:

NTP is not running
Show output
NTP is not running

Step 9: Set the following configuration in DUT0:

set system ntp server address 10.215.200.100 max-poll 4
set system ntp server address 10.215.200.100 min-poll 3

Step 10: Run command system ntp status at DUT0 and check if output contains the following tokens:

10.215.200.100
Show output
     remote           refid      st t when poll reach   delay   offset   jitter
===============================================================================
 10.215.200.100  .INIT.          16 u    -    8    0   0.0000   0.0000   0.0001

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

Sun
Show output
Mon 26 Feb 2024 20:17:13 UTC +00:00

Test NTP Service Specific VRF

Description

DUT0 is configured to obtain time information from an NTP server via VRF (Virtual Routing and Forwarding).

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.215.200.100/24
set protocols static route 0.0.0.0/0 next-hop 10.215.200.50
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.215.200.50/24
set interfaces ethernet eth0 vrf WAN
set system vrf WAN

Step 3: Ping IP address 10.215.200.100 from DUT0:

admin@DUT0$ ping 10.215.200.100 vrf WAN count 1 size 56 timeout 1
Show output
ping: Warning: source address might be selected on device other than WAN.
PING 10.215.200.100 (10.215.200.100) from 10.215.200.50 WAN: 56(84) bytes of data.
64 bytes from 10.215.200.100: icmp_seq=1 ttl=64 time=0.951 ms

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

Step 4: Run command set date 2024-02-25 12:00:00 at DUT0 and expect this output: Step 5: Run command set date ntp 10.215.200.100 vrf WAN at DUT0 and expect this output:

Show output
Date was successfully updated!

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

Sun
Show output
Mon 26 Feb 2024 20:17:24 UTC +00:00

Step 7: Run command set date 2024-02-25 12:00:00 at DUT0 and expect this output: Step 8: Set the following configuration in DUT0:

set system ntp server address 10.215.200.100 max-poll 4
set system ntp server address 10.215.200.100 min-poll 3
set system ntp server address 10.215.200.100 local-vrf WAN
set system ntp server address 10.215.200.100 local-address 10.215.200.50

Step 9: Run command system ntp status at DUT0 and check if output contains the following tokens:

10.215.200.100
Show output
     remote           refid      st t when poll reach   delay   offset   jitter
===============================================================================
 10.215.200.100  .INIT.          16 u    -    8    0   0.0000   0.0000   0.0001

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

Sun
Show output
Mon 26 Feb 2024 20:17:34 UTC +00:00

Test NTP Service Specific VRF and PBR

Description

Simple scenario to check NTP service using a specific VRF and PBR (Policy Based Routing).

Scenario

Step 1: Run command set date 2024-02-25 12:00:00 at DUT0 and expect this output: Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.215.200.100/24
set protocols static route 0.0.0.0/0 next-hop 10.215.200.50
set system ntp master prefer
set system ntp master stratum 3

Step 3: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.215.200.50/24
set interfaces ethernet eth0 vrf WAN
set system vrf WAN
set interfaces dummy dum0 address 192.168.0.1/24
set interfaces dummy dum0 vrf LAN
set interfaces ethernet eth0 traffic policy in LOCVRF_POL
set traffic policy LOCVRF_POL rule 1 set vrf LAN
set traffic policy LOCVRF_POL rule 1 selector LOCVRF_SEL
set traffic selector LOCVRF_SEL rule 1 protocol udp
set protocols vrf LAN static route 0.0.0.0/0 interface eth0
set system vrf LAN
set system ntp server address 10.215.200.100 max-poll 4
set system ntp server address 10.215.200.100 min-poll 3
set system ntp server address 10.215.200.100 local-vrf LAN
set system ntp server address 10.215.200.100 local-interface dum0

Step 4: Ping IP address 10.215.200.100 from DUT0:

admin@DUT0$ ping 10.215.200.100 vrf WAN count 1 size 56 timeout 1
Show output
ping: Warning: source address might be selected on device other than WAN.
PING 10.215.200.100 (10.215.200.100) from 10.215.200.50 WAN: 56(84) bytes of data.
64 bytes from 10.215.200.100: icmp_seq=1 ttl=64 time=0.887 ms

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

Step 5: Run command system ntp status at DUT0 and check if output contains the following tokens:

10.215.200.100
Show output
     remote           refid      st t when poll reach   delay   offset   jitter
===============================================================================
 10.215.200.100  .INIT.          16 u    -    8    0   0.0000   0.0000   0.0001

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

Sun
Show output
Mon 26 Feb 2024 20:17:52 UTC +00:00

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.215.200.100/24
set protocols static route 0.0.0.0/0 next-hop 10.215.200.50
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.215.200.50/24

Step 3: Ping IP address 10.215.200.100 from DUT0:

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

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

Step 4: Run command set date 2024-02-25 12:00:00 at DUT0 and expect this output: Step 5: Run command set date ntp 10.215.200.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:

Sun
Show output
Mon 26 Feb 2024 20:18:04 UTC +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.33.1
System Time: 1708978684.747977
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1708978684 seconds after 1969
Last calibration done at 1708978684 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 - 1708978684.752195 is too far past 1708978684.500000 (0.252195 > 0.001000)
1708978685.500000 is close enough to 1708978685.500000 (0.000000 < 0.002000)
Set RTC to 1708978685 (1708978684 + 1; refsystime = 1708978684.000000)
Setting Hardware Clock to 20:18:05 = 1708978685 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 1708978684 0.000000
1708978684
UTC

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

Show output
hwclock from util-linux 2.33.1
System Time: 1708978685.612826
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1708978684 seconds after 1969
Last calibration done at 1708978684 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: 2024/02/26 20:18:06
Hw clock time : 2024/02/26 20:18:06 = 1708978686 seconds since 1969
Time since last adjustment is 2 seconds
Calculated Hardware Clock drift is 0.000000 seconds
Calling settimeofday(1708978686.000000, 0)

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

Sun
Show output
Mon 26 Feb 2024 20:18:06 UTC +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.215.200.100/24
set protocols static route 0.0.0.0/0 next-hop 10.215.200.50
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.215.200.50/24

Step 3: Ping IP address 10.215.200.100 from DUT0:

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

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

Step 4: Run command set date 2024-02-25 12:00:00 at DUT0 and expect this output: Step 5: Run command set date ntp 10.215.200.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:

Sun
Show output
Mon 26 Feb 2024 20:18:16 UTC +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.33.1
System Time: 1708978696.751804
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1708978696 seconds after 1969
Last calibration done at 1708978696 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: 2024/02/26 20:18:17
Hw clock time : 2024/02/26 20:18:17 = 1708978697 seconds since 1969
Time since last adjustment is 1 second
Calculated Hardware Clock drift is 0.000000 seconds
RTC type: 'rtc_cmos'
Using delay: 0.500000 seconds
1708978697.500000 is close enough to 1708978697.500000 (0.000000 < 0.001000)
Set RTC to 1708978697 (1708978697 + 0; refsystime = 1708978697.000000)
Setting Hardware Clock to 20:18:17 = 1708978697 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 1708978697 0.000000
1708978697
UTC

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

Show output
hwclock from util-linux 2.33.1
System Time: 1708978697.611579
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1708978697 seconds after 1969
Last calibration done at 1708978697 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: 2024/02/26 20:18:18
Hw clock time : 2024/02/26 20:18:18 = 1708978698 seconds since 1969
Time since last adjustment is 1 second
Calculated Hardware Clock drift is 0.000000 seconds
Calling settimeofday(1708978698.000000, 0)

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

Sun
Show output
Mon 26 Feb 2024 20:18:18 UTC +00:00

Test NTP Service With Client Authentication Only

Description

DUT0 is configured to use NTP authentication. An NTP server is configured without auth. Optaining the time should fail due to crypto failure.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.215.200.50/24
set system ntp authentication-key 1 key unencryptedKey

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.215.200.100/24
set protocols static route 0.0.0.0/0 next-hop 10.215.200.50
set system ntp master prefer
set system ntp master stratum 3

Step 3: Run command set date 2024-02-25 12:00:00 at DUT0 and expect this output: Step 4: Run command set date ntp 10.215.200.100 key 1 at DUT0 and check if output contains the following tokens:

no eligible servers
Show output
no eligible servers
program finished with error
  CLI Error: Command error

Test NTP Service With Client And Server Authentication

Description

NTP client and NTP server are configured to use the same authentication key. Optaining time information should succeed.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.215.200.50/24
set system ntp authentication-key 1 key unencryptedKey

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.215.200.100/24
set protocols static route 0.0.0.0/0 next-hop 10.215.200.50
set system ntp master prefer
set system ntp master stratum 3
set system ntp authentication-key 1 key unencryptedKey
set system ntp trusted-key 1

Step 3: Run command set date 2024-02-25 12:00:00 at DUT0 and expect this output: Step 4: Run command set date ntp 10.215.200.100 key 1 at DUT0 and expect this output:

Show output
Date was successfully updated!

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

Sun
Show output
Mon 26 Feb 2024 20:18:46 UTC +00:00

Test NTP Service With Wrong Authentication

Description

NTP client and NTP server are configured to use different authentication key. Optaining time information should fail.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.215.200.50/24
set system ntp authentication-key 1 key wrongKey

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.215.200.100/24
set protocols static route 0.0.0.0/0 next-hop 10.215.200.50
set system ntp master prefer
set system ntp master stratum 3
set system ntp authentication-key 1 key unencryptedKey
set system ntp trusted-key 1

Step 3: Run command set date 2024-02-25 12:00:00 at DUT0 and expect this output: Step 4: Run command set date ntp 10.215.200.100 key 1 at DUT0 and check if output contains the following tokens:

no eligible servers
Show output
no eligible servers
program finished with error
  CLI Error: Command error