Script
Test to check advisor scripts
Configuration Script
Description
In this scenario, an advisor is triggered to activate the automatic script. When the advisor is changed to true, the automatic script associated with the advisor is executed, aplying the commands in the active configuration.
Scenario
Step 1: Set the following configuration in DUT0 :
set system advisor ADVISOR1 test false set system cli configuration logging global info set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system script SCRIPT_1 advisor ADVISOR1 set system script SCRIPT_1 configuration 'set system description \'advisor applied\''
Step 2: Modify the following configuration lines in DUT0 :
set system advisor ADVISOR1 test true
Step 3: Run command show running at DUT0 and check if output contains the following tokens:
set system description 'advisor applied'Show output
# Teldat OSDx VM version v4.2.9.2 # Thu 16 Apr 2026 16:46:04 +00:00 # Warning: Configuration has not been saved set system advisor ADVISOR1 test true set system cli configuration logging global info set system description 'advisor applied' set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system script SCRIPT_1 advisor ADVISOR1 set system script SCRIPT_1 configuration 'set system description \'advisor applied\''
Operational Script
Description
In this scenario, an advisor is triggered to activate the automatic script. When the advisor is changed to true, the automatic script associated with the advisor is executed, proccessing the operational commands in the specified order.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.215.200.50/24 set system advisor ADVISOR1 test false set system cli configuration logging global info set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system script SCRIPT_1 advisor ADVISOR1 set system script SCRIPT_1 operational 1 command 'show version' set system script SCRIPT_1 operational 2 command 'license show'
Step 2: Modify the following configuration lines in DUT0 :
set system advisor ADVISOR1 test true
Step 3: Run command system journal show | cat at DUT0 and check if output contains the following tokens:
v4.2.9.2Show output
Apr 16 16:46:10.336895 osdx systemd-journald[126917]: Runtime Journal (/run/log/journal/a3fecc5be5e949c7a083b0adeea4bb21) is 1.8M, max 13.8M, 11.9M free. Apr 16 16:46:10.338475 osdx systemd-journald[126917]: Received client request to rotate journal, rotating. Apr 16 16:46:10.338600 osdx systemd-journald[126917]: Vacuuming done, freed 0B of archived journals from /run/log/journal/a3fecc5be5e949c7a083b0adeea4bb21. Apr 16 16:46:10.351430 osdx OSDxCLI[217678]: User 'admin' executed a new command: 'system journal clear'. Apr 16 16:46:10.595183 osdx OSDxCLI[217678]: User 'admin' executed a new command: 'system coredump delete all'. Apr 16 16:46:10.897879 osdx OSDxCLI[217678]: User 'admin' entered the configuration menu. Apr 16 16:46:11.019861 osdx OSDxCLI[217678]: User 'admin' added a new cfg line: 'set system script SCRIPT_1 advisor ADVISOR1'. Apr 16 16:46:11.078594 osdx OSDxCLI[217678]: User 'admin' added a new cfg line: 'set system advisor ADVISOR1 test false'. Apr 16 16:46:11.229203 osdx OSDxCLI[217678]: User 'admin' added a new cfg line: 'set system cli configuration logging global info'. Apr 16 16:46:11.342741 osdx OSDxCLI[217678]: User 'admin' added a new cfg line: 'set system script SCRIPT_1 advisor ADVISOR1'. Apr 16 16:46:11.504274 osdx OSDxCLI[217678]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 address 10.215.200.50/24'. Apr 16 16:46:11.591307 osdx OSDxCLI[217678]: User 'admin' added a new cfg line: 'set system script SCRIPT_1 operational 1 command "show version"'. Apr 16 16:46:11.693047 osdx OSDxCLI[217678]: User 'admin' added a new cfg line: 'set system script SCRIPT_1 operational 2 command "license show"'. Apr 16 16:46:11.797428 osdx OSDxCLI[217678]: User 'admin' added a new cfg line: 'show working'. Apr 16 16:46:11.878593 osdx ubnt-cfgd[224023]: inactive Apr 16 16:46:11.925376 osdx INFO[224031]: FRR daemons did not change Apr 16 16:46:11.928476 osdx modulelauncher[1641]: + Received data: ['217678', 'osdx.utils.xos', 'set_console_log_level', 'info'] Apr 16 16:46:11.956377 osdx OSDxCLI[217678]: Signal 10 received Apr 16 16:46:12.061883 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Apr 16 16:46:12.120911 osdx WARNING[224125]: No supported link modes on interface eth0 Apr 16 16:46:12.122631 osdx modulelauncher[224125]: osdx.utils.xos cmd error: /sbin/ethtool -A eth0 autoneg on Apr 16 16:46:12.122646 osdx modulelauncher[224125]: Command '/sbin/ethtool -A eth0 autoneg on' returned non-zero exit status 76. Apr 16 16:46:12.124022 osdx modulelauncher[224125]: osdx.utils.xos cmd error: /sbin/ethtool -s eth0 autoneg on advertise Pause off Asym_Pause off -- Apr 16 16:46:12.124034 osdx modulelauncher[224125]: Command '/sbin/ethtool -s eth0 autoneg on advertise Pause off Asym_Pause off --' returned non-zero exit status 75. Apr 16 16:46:12.137219 osdx cfgd[1833]: [217678]Completed change to active configuration Apr 16 16:46:12.149170 osdx OSDxCLI[217678]: User 'admin' committed the configuration. Apr 16 16:46:12.188188 osdx OSDxCLI[217678]: User 'admin' left the configuration menu. Apr 16 16:46:12.408092 osdx OSDxCLI[217678]: pam_unix(cli:session): session opened for user admin(uid=1000) by admin(uid=1000) Apr 16 16:46:12.408878 osdx OSDxCLI[217678]: pam_unix(cli:session): session closed for user admin Apr 16 16:46:12.409206 osdx OSDxCLI[217678]: User 'admin' entered the configuration menu. Apr 16 16:46:12.509728 osdx OSDxCLI[217678]: pam_unix(cli:session): session opened for user admin(uid=1000) by admin(uid=1000) Apr 16 16:46:12.511229 osdx cfgd[1833]: Execute action [syntax] for node [system advisor ADVISOR1] Apr 16 16:46:12.511712 osdx OSDxCLI[217678]: pam_unix(cli:session): session closed for user admin Apr 16 16:46:12.512003 osdx OSDxCLI[217678]: User 'admin' added a new cfg line: 'set system advisor ADVISOR1 test true'. Apr 16 16:46:12.626454 osdx OSDxCLI[217678]: pam_unix(cli:session): session opened for user admin(uid=1000) by admin(uid=1000) Apr 16 16:46:12.636364 osdx OSDxCLI[217678]: pam_unix(cli:session): session closed for user admin Apr 16 16:46:12.637414 osdx OSDxCLI[217678]: User 'admin' added a new cfg line: 'show changes'. Apr 16 16:46:12.723035 osdx OSDxCLI[217678]: pam_unix(cli:session): session opened for user admin(uid=1000) by admin(uid=1000) Apr 16 16:46:12.736562 osdx ubnt-cfgd[224176]: inactive Apr 16 16:46:12.761053 osdx cfgd[1833]: [217678]must validation for [system login user admin role] was skipped Apr 16 16:46:12.761068 osdx cfgd[1833]: Execute action [commit-subtree] for node [system advisor ADVISOR1] Apr 16 16:46:12.771921 osdx INFO[224184]: FRR daemons did not change Apr 16 16:46:12.772169 osdx cfgd[1833]: Execute action [end] for node [system advisor ADVISOR1] Apr 16 16:46:12.778203 osdx cfgd[1833]: [217678]Completed change to active configuration Apr 16 16:46:12.780384 osdx OSDxCLI[217678]: pam_unix(cli:session): session closed for user admin Apr 16 16:46:12.780759 osdx OSDxCLI[217678]: User 'admin' committed the configuration. Apr 16 16:46:12.782071 osdx INFO[224192]: SCRIPT SCRIPT_1 operations: Apr 16 16:46:12.788005 osdx OSDxCLI[224198]: Tecla::GetLine tcgetattr error Apr 16 16:46:12.788011 osdx OSDxCLI[224198]: User 'admin' has logged in. Apr 16 16:46:12.803131 osdx OSDxCLI[224198]: User 'admin' executed a new command: 'show version'. Apr 16 16:46:12.806136 osdx OSDxCLI[224198]: User 'admin' has logged out. Apr 16 16:46:12.806146 osdx OSDxCLI[224198]: Tecla::GetLine tcgetattr error Apr 16 16:46:12.807984 osdx INFO[224192]: Operation 1 'show version ': OS vendor: Teldat OS name: OSDx OS version: v4.2.9.2 OS Linux kernel: 6.12.73 OS built by: jenkins@diana OS build date: Thu Apr 16 14:07:02 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: 26ca32bf-75db-51c5-9ab7-fc6bb330c2f3 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: Thu 16 Apr 2026 16:46:12 +00:00 Uptime: 2:01:42 CPU load (1m, 5m, 15m): 0.33 0.25 0.18 CPU usage % (1m): 6.34 Storage usage (kB): 418700/8144384 Memory usage (kB): 420248/1572696 Users logged in: 1 Mode (current/next boot): user/user Hostname: osdx Apr 16 16:46:12.822024 osdx OSDxCLI[217678]: User 'admin' left the configuration menu. Apr 16 16:46:12.825297 osdx OSDxCLI[224206]: Tecla::GetLine tcgetattr error Apr 16 16:46:12.825303 osdx OSDxCLI[224206]: User 'admin' has logged in. Apr 16 16:46:12.829891 osdx OSDxCLI[224206]: Tecla::GetLine tcgetattr error Apr 16 16:46:12.833545 osdx OSDxCLI[224206]: Tecla::GetLine tcgetattr error Apr 16 16:46:12.833798 osdx OSDxCLI[224206]: User 'admin' executed a new command: 'license show'. Apr 16 16:46:12.835104 osdx OSDxCLI[224206]: User 'admin' has logged out. Apr 16 16:46:12.835112 osdx OSDxCLI[224206]: Tecla::GetLine tcgetattr error Apr 16 16:46:12.836206 osdx INFO[224192]: Operation 2 'license show ': License: VM_BASE Firewall eth-Rate-Permit-Full +-----------------+----------+----------+ | License Item | Status | Validity | +-----------------+----------+----------+ | CELL | Disabled | - | | Firewall | Enabled | Forever | | RD-ETSI | Disabled | - | | RD-FCC | Disabled | - | | RD-NOM | Disabled | - | | RD-ROW | Disabled | - | | WLAN | Disabled | - | | Windbit | Disabled | - | | eth-Rate-Permit | Full | Forever | +-----------------+----------+----------+ Apr 16 16:46:12.976876 osdx OSDxCLI[217678]: pam_unix(cli:session): session opened for user admin(uid=1000) by admin(uid=1000)
Simple Script Execution
Description
In this scenario, an automatic script is activated directly without any advisor triggering. The script is activated using the system script <txt> activate command.
Scenario
Step 1: Set the following configuration in DUT0 :
set system advisor ADVISOR1 test false set system cli configuration logging global info set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system script SCRIPT_1 advisor ADVISOR1 set system script SCRIPT_1 configuration 'set interfaces dummy dum0' set system script SCRIPT_1 configuration 'set interfaces dummy dum1'
Step 2: Run command system script SCRIPT_1 activate at DUT0.
Step 3: Run command interfaces dummy show at DUT0 and check if output matches the following regular expressions:
dum0.*\ndum1Show output
----------------------------------------------------------------- Name IP Address Admin Oper Vrf Description ----------------------------------------------------------------- dum0 fe80::c4a8:cfff:fe3d:f164/64 up up dum1 fe80::4cfa:1bff:fe76:3faa/64 up up
Multiple Triggers Script
Description
In this scenario, an advisor is triggered multiple times to activate the automatic script. When the advisor is changed to true, the automatic script associated with the advisor is executed, proccessing the operational commands in the specified order.
Scenario
Step 1: Set the following configuration in DUT0 :
set system advisor ADVISOR1 test false set system cli configuration logging global info set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system script SCRIPT_1 advisor ADVISOR1 set system script SCRIPT_1 configuration 'set system description \'advisor applied\'' set system script SCRIPT_1 number-of-triggers 3
Note
Wait for the advisor to turn on. After that, wait for the advisor to turn off. This produces only one trigger.
Step 2: Modify the following configuration lines in DUT0 :
set system advisor ADVISOR1 test true
Step 3: Modify the following configuration lines in DUT0 :
set system advisor ADVISOR1 test false
Step 4: Expect a failure in the following command:
Run command show running at DUT0 and check if output contains the following tokens:
set system description 'advisor applied'Show output
# Teldat OSDx VM version v4.2.9.2 # Thu 16 Apr 2026 16:46:26 +00:00 # Warning: Configuration has not been saved set system advisor ADVISOR1 test false set system cli configuration logging global info set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system script SCRIPT_1 advisor ADVISOR1 set system script SCRIPT_1 configuration 'set system description \'advisor applied\'' set system script SCRIPT_1 number-of-triggers 3
Note
Wait for the advisor to turn on. After that, wait for the advisor to turn off. This produces only one trigger.
Step 5: Modify the following configuration lines in DUT0 :
set system advisor ADVISOR1 test true
Step 6: Modify the following configuration lines in DUT0 :
set system advisor ADVISOR1 test false
Step 7: Expect a failure in the following command:
Run command show running at DUT0 and check if output contains the following tokens:
set system description 'advisor applied'Show output
# Teldat OSDx VM version v4.2.9.2 # Thu 16 Apr 2026 16:46:28 +00:00 # Warning: Configuration has not been saved set system advisor ADVISOR1 test false set system cli configuration logging global info set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system script SCRIPT_1 advisor ADVISOR1 set system script SCRIPT_1 configuration 'set system description \'advisor applied\'' set system script SCRIPT_1 number-of-triggers 3
Note
Wait for the advisor to turn on. After that, wait for the advisor to turn off. This produces only one trigger.
Step 8: Modify the following configuration lines in DUT0 :
set system advisor ADVISOR1 test true
Step 9: Modify the following configuration lines in DUT0 :
set system advisor ADVISOR1 test false
Step 10: Run command show running at DUT0 and check if output contains the following tokens:
set system description 'advisor applied'Show output
# Teldat OSDx VM version v4.2.9.2 # Thu 16 Apr 2026 16:46:29 +00:00 # Warning: Configuration has not been saved set system advisor ADVISOR1 test false set system cli configuration logging global info set system description 'advisor applied' set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system script SCRIPT_1 advisor ADVISOR1 set system script SCRIPT_1 configuration 'set system description \'advisor applied\'' set system script SCRIPT_1 number-of-triggers 3
Script Invalid Paths
Description
Test that checks invalid configurational and operational commands script execution on an advisor
Scenario
Step 1: Set the following configuration in DUT0 :
set system advisor ADVISOR1 test false set system cli configuration logging global info set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system script SCRIPT_1 advisor ADVISOR1
Step 2: Expect a failure in the following command:
Run command set system script SCRIPT_1 configuration 'set potato' at DUT0 and expect this output:
Show output
Value validation failed CLI Error: Command error
Step 3: Set the following configuration in DUT0 :
set system advisor ADVISOR1 test false set system cli configuration logging global info set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set system script SCRIPT_1 advisor ADVISOR1 set system script SCRIPT_1 operational 1 command 'system potato'
Step 4: Run command system script SCRIPT_1 activate at DUT0 and expect this output:
Step 5: Run command system journal show | grep "CLI Error: Invalid token *" at DUT0 and check if output contains the following tokens:
CLI Error: Invalid token [potato]Show output
CLI Error: Invalid token [potato]