Schedule
The following scenario shows how to configure alarm schedules to be able to program custom actions in the system triggered by a timer. Timers can be executed periodically or just once, depending on the configuration.
Periodic Schedule
Description
In this example, a schedule is configured in DUT0 to enable and disable an alarm every minute.
Scenario
Step 1: Set the following configuration in DUT0 :
set system alarm ALARM set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system schedule SCHED alarm ALARM set system schedule SCHED disable second 28 set system schedule SCHED enable second 23
Step 2: Run the command system schedule show on DUT0 and check whether the output matches the following regular expressions:
SCHED\s+(enable|disable).*leftShow output
---------------------------------------------------------------------- Schedule State Next Left Last Passed ---------------------------------------------------------------------- SCHED enable Wed 2026-06-03 11:02:23 UTC 8s left - - SCHED disable Wed 2026-06-03 11:02:28 UTC 13s left - -
Note
The output of the above command should show the “enable” and “disable” entries in the table with a “Left” value, since the schedule is pending.
Step 3: Run the command system alarm ALARM show on DUT0 and check whether the output contains the following tokens:
trueShow output
---------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------- ALARM true 2026-06-03 11:02:23.428579+00:00 1 15.37
Step 4: Run the command system alarm ALARM show on DUT0 and check whether the output contains the following tokens:
falseShow output
------------------------------------------------------------------------------------------------------------ Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ------------------------------------------------------------------------------------------------------------ ALARM false 2026-06-03 11:02:28.433071+00:00 2026-06-03 11:02:23.428579+00:00 2 33.67
Step 5: Run the command system schedule show on DUT0 and check whether the output matches the following regular expressions:
SCHED\s+(enable|disable).*leftShow output
------------------------------------------------------------------------------------------------ Schedule State Next Left Last Passed ------------------------------------------------------------------------------------------------ SCHED enable Wed 2026-06-03 11:03:23 UTC 53s left Wed 2026-06-03 11:02:23 UTC 5s ago SCHED disable Wed 2026-06-03 11:03:28 UTC 58s left Wed 2026-06-03 11:02:28 UTC 993ms ago
Note
The output of the above command should show the “enable” and “disable” entries in the table with a “Left” value, since the schedule is periodic.
Schedule Script Execution
Description
In this example, a schedule is configured in DUT0 to program the execution of a script that automatically changes the system configuration.
Scenario
Step 1: Set the following configuration in DUT0 :
set system advisor ADVISOR1 test ALARM set system advisor ADVISOR2 test 'not ALARM' set system alarm ALARM set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system schedule SCHED alarm ALARM set system schedule SCHED disable day 3 set system schedule SCHED disable hour 11 set system schedule SCHED disable minute 2 set system schedule SCHED disable month 6 set system schedule SCHED disable second 49 set system schedule SCHED disable year 2026 set system schedule SCHED enable day 3 set system schedule SCHED enable hour 11 set system schedule SCHED enable minute 2 set system schedule SCHED enable month 6 set system schedule SCHED enable second 44 set system schedule SCHED enable year 2026 set system script SCRIPT1 advisor ADVISOR1 set system script SCRIPT1 configuration 'set system description \'Test Description\'' set system script SCRIPT2 advisor ADVISOR2 set system script SCRIPT2 configuration 'delete system description \'Test Description\''
Step 2: Run the command system alarm ALARM show on DUT0 and check whether the output contains the following tokens:
trueShow output
---------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------- ALARM true 2026-06-03 11:02:44.439165+00:00 1 10.18
Note
The output of the above command should show that the alarm was activated according to the “enable” time configured.
Step 3: Run the command show version on DUT0 and check whether the output matches the following regular expressions:
Description:.*Test DescriptionShow output
OS vendor: Teldat OS name: OSDx OS version: v4.2.10.1 OS Linux kernel: 6.12.90 OS built by: jenkins@diana OS build date: Wed Jun 3 07:58:33 UTC 2026 OS installation: physical OS boot mode: user License: VM_BASE Firewall eth-Rate-Permit-Full Hardware vendor: QEMU Hardware model: VM Hardware OEM model: Standard PC (i440FX + PIIX, 1996) Hardware version: pc-i440fx-7.2 Hardware UUID: f5af3efe-083f-55bb-b51c-8f037a33d582 Hardware architecture: amd64 Hardware fwid: iso Hardware base MAC: de:ad:be:ef:6c:00 Hardware cpu: 1 x QEMU Virtual CPU version 2.5+ (4 cores) Last reboot reason: Panic Date: Wed 03 Jun 2026 11:02:45 +00:00 Uptime: 1:07:45 CPU load (1m, 5m, 15m): 0.12 0.19 0.16 CPU usage % (1m): 3.35 Storage usage (kB): 419508/8144384 Memory usage (kB): 416972/1572528 Users logged in: 1 Mode (current/next boot): user/user Hostname: osdx Description: Test Description
Note
The output of the above command should show the system description configured by the script.
Step 4: Run the command system alarm ALARM show on DUT0 and check whether the output contains the following tokens:
falseShow output
------------------------------------------------------------------------------------------------------------ Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ------------------------------------------------------------------------------------------------------------ ALARM false 2026-06-03 11:02:49.451264+00:00 2026-06-03 11:02:44.439165+00:00 2 38.99
Note
The output of the above command should show that the alarm was deactivated according to the “disable” time configured.
Step 5: Run the command system schedule show on DUT0 and check whether the output matches the following regular expressions:
SCHED\s+(enable|disable)\s+-\s+-\s+[a-zA-Z]{3}Show output
--------------------------------------------------------------------- Schedule State Next Left Last Passed --------------------------------------------------------------------- SCHED disable - - Wed 2026-06-03 11:02:49 UTC 361ms ago SCHED enable - - Wed 2026-06-03 11:02:44 UTC 5s ago
Note
The output of the above command should show the “enable” and “disable” entries in the table without a “Next” or “Left” value, since the schedule is configured to be executed just once.
Step 6: Run the command show version on DUT0 and check whether the output does not match the following regular expressions:
Description:.*Test DescriptionShow output
OS vendor: Teldat OS name: OSDx OS version: v4.2.10.1 OS Linux kernel: 6.12.90 OS built by: jenkins@diana OS build date: Wed Jun 3 07:58:33 UTC 2026 OS installation: physical OS boot mode: user License: VM_BASE Firewall eth-Rate-Permit-Full Hardware vendor: QEMU Hardware model: VM Hardware OEM model: Standard PC (i440FX + PIIX, 1996) Hardware version: pc-i440fx-7.2 Hardware UUID: f5af3efe-083f-55bb-b51c-8f037a33d582 Hardware architecture: amd64 Hardware fwid: iso Hardware base MAC: de:ad:be:ef:6c:00 Hardware cpu: 1 x QEMU Virtual CPU version 2.5+ (4 cores) Last reboot reason: Panic Date: Wed 03 Jun 2026 11:02:49 +00:00 Uptime: 1:07:49 CPU load (1m, 5m, 15m): 0.11 0.19 0.16 CPU usage % (1m): 2.90 Storage usage (kB): 419508/8144384 Memory usage (kB): 416620/1572528 Users logged in: 1 Mode (current/next boot): user/user Hostname: osdx
Note
The output of the above command should show the script has removed the system description.