Ntp Client
Test suite to check NTP client using VRF, PBR, authentication and RTC synchtonozation
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 1Show 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.480 ms --- 10.215.200.100 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.480/0.480/0.480/0.000 ms
Step 4: Run command set date 2023-10-29 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 serverShow output
sntp 4.2.8p12@1.3728-o (1) 2023-10-29 12:00:00.118292 (+0000) +91690.200935 +/- 61134.748133 10.215.200.100 s4 no-leap
Step 6: Run command show date at DUT0 and check if output does not contain the following tokens:
SunShow output
Mon Oct 30 13:28:10 UTC 2023
Step 7: Run command set date 2023-10-29 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 runningShow 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.100Show output
remote refid st t when poll reach delay offset jitter ============================================================================== 10.215.200.100 .INIT. 16 u - 8 0 0.000 0.000 0.000
Step 11: Run command show date at DUT0 and check if output does not contain the following tokens:
SunShow output
Mon Oct 30 13:28:20 UTC 2023
Test NTP Service Specific VRF
Description
DUT0 is configured to obtain time information from 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 1Show 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.465 ms --- 10.215.200.100 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.465/0.465/0.465/0.000 ms
Step 4: Run command set date 2023-10-29 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
sntp 4.2.8p12@1.3728-o (1) 2023-10-29 12:00:00.099684 (+0000) +91706.560997 +/- 61145.654841 10.215.200.100 s4 no-leap
Step 6: Run command show date at DUT0 and check if output does not contain the following tokens:
SunShow output
Mon Oct 30 13:28:27 UTC 2023
Step 7: Run command set date 2023-10-29 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.100Show output
remote refid st t when poll reach delay offset jitter ============================================================================== 10.215.200.100 .INIT. 16 u - 8 0 0.000 0.000 0.000
Step 10: Run command show date at DUT0 and check if output does not contain the following tokens:
SunShow output
Mon Oct 30 13:28:37 UTC 2023
Test NTP Service Specific VRF and PBR
Description
Simple test to check NTP service using a specific VRF and PBR (Policy Based Routing).
Scenario
Step 1: Run command set date 2023-10-29 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 1Show 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.507 ms --- 10.215.200.100 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.507/0.507/0.507/0.000 ms
Step 5: Run command system ntp status at DUT0 and check if output contains the following tokens:
10.215.200.100Show output
remote refid st t when poll reach delay offset jitter ============================================================================== 10.215.200.100 .INIT. 16 u - 8 0 0.000 0.000 0.000
Step 6: Run command show date at DUT0 and check if output does not contain the following tokens:
SunShow output
Mon Oct 30 13:28:53 UTC 2023
Test RTC Synchronization
Description
Tests 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 1Show 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.418 ms --- 10.215.200.100 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.418/0.418/0.418/0.000 ms
Step 4: Run command set date 2023-10-29 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 serverShow output
sntp 4.2.8p12@1.3728-o (1) 2023-10-29 12:00:00.097227 (+0000) +91739.353623 +/- 61167.516591 10.215.200.100 s4 no-leap
Step 6: Run command show date at DUT0 and check if output does not contain the following tokens:
SunShow output
Mon Oct 30 13:28:59 UTC 2023
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: 1698672539.703835 Trying to open: /dev/rtc0 Using the rtc interface to the clock. Last drift adjustment done at 1698672539 seconds after 1969 Last calibration done at 1698672539 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 - 1698672539.707292 is too far past 1698672539.500000 (0.207292 > 0.001000) 1698672540.500000 is close enough to 1698672540.500000 (0.000000 < 0.002000) Set RTC to 1698672540 (1698672539 + 1; refsystime = 1698672539.000000) Setting Hardware Clock to 13:29:00 = 1698672540 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 1698672539 0.000000 1698672539 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: 1698672540.617325 Trying to open: /dev/rtc0 Using the rtc interface to the clock. Last drift adjustment done at 1698672539 seconds after 1969 Last calibration done at 1698672539 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: 2023/10/30 13:29:01 Hw clock time : 2023/10/30 13:29:01 = 1698672541 seconds since 1969 Time since last adjustment is 2 seconds Calculated Hardware Clock drift is 0.000000 seconds Calling settimeofday(1698672541.000000, 0)
Step 9: Run command show date at DUT0 and check if output does not contain the following tokens:
SunShow output
Mon Oct 30 13:29:01 UTC 2023
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 1Show 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.606 ms --- 10.215.200.100 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.606/0.606/0.606/0.000 ms
Step 4: Run command set date 2023-10-29 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 serverShow output
sntp 4.2.8p12@1.3728-o (1) 2023-10-29 12:00:00.092765 (+0000) +91748.392660 +/- 61173.542616 10.215.200.100 s4 no-leap
Step 6: Run command show date at DUT0 and check if output does not contain the following tokens:
SunShow output
Mon Oct 30 13:29:08 UTC 2023
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: 1698672548.700292 Trying to open: /dev/rtc0 Using the rtc interface to the clock. Last drift adjustment done at 1698672548 seconds after 1969 Last calibration done at 1698672548 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: 2023/10/30 13:29:09 Hw clock time : 2023/10/30 13:29:09 = 1698672549 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 1698672549.500000 is close enough to 1698672549.500000 (0.000000 < 0.001000) Set RTC to 1698672549 (1698672549 + 0; refsystime = 1698672549.000000) Setting Hardware Clock to 13:29:09 = 1698672549 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 1698672549 0.000000 1698672549 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: 1698672549.603304 Trying to open: /dev/rtc0 Using the rtc interface to the clock. Last drift adjustment done at 1698672549 seconds after 1969 Last calibration done at 1698672549 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: 2023/10/30 13:29:10 Hw clock time : 2023/10/30 13:29:10 = 1698672550 seconds since 1969 Time since last adjustment is 1 second Calculated Hardware Clock drift is 0.000000 seconds Calling settimeofday(1698672550.000000, 0)
Step 9: Run command show date at DUT0 and check if output does not contain the following tokens:
SunShow output
Mon Oct 30 13:29:10 UTC 2023
Test NTP Service With Client Authentication Only
Description
DUT0 is configured to use NTP authentication. NTP server is configured without authentication. Optaining the time should fail because of crypto failure. In that case the test succeeeds.
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 md5 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 2023-10-29 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:
Crypto NAKShow output
sntp 4.2.8p12@1.3728-o (1) Crypto NAK = 0x00000000 from 10.215.200.100 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 md5 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 md5 unencryptedKey set system ntp trusted-key 1
Step 3: Run command set date 2023-10-29 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
sntp 4.2.8p12@1.3728-o (1) 2023-10-29 12:00:01.252324 (+0000) +91762.491929 +/- 61182.942129 10.215.200.100 s4 no-leap
Step 5: Run command show date at DUT0 and check if output does not contain the following tokens:
SunShow output
Mon Oct 30 13:29:24 UTC 2023