Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
Use event and op script Boilerplates For SLAX version 1.0 and higher, you can use new script boilerplates with SLAX 1.1 in Junos OS 12.2 Release and later
The Event and Op Script Boilerplates page contains a boilerplate for event and op scripts for use with SLAX 1.1 in Junos OS Release 12.2 and later
The Event and Op Script Boilerplates page contains a boilerplate for event and op scripts for use with SLAX 1.1 in Junos OS Release 12.2 and later...#FAQ #event-script #Slax
The disable-interface script is an example that demonstrates how a configuration can be committed from an op-script. This script will deactivate interface 'ge-0/0/2' upon receiving a PING TEST FAILED event, which is generated by rpm when the ping test fails. The ability to commit configuration from an op-script is effective in Junos 9.3
Demonstrate How to Commit a Configuration from an Op Script For SLAX version 1.0 and higher, you can use the disable-interface script to demonstrate how you can commit a configuration from an op script
Overview Sometimes you have the requirement to prevent that multiple instances of a single SLAX script run in parallel. This might be the case, when an event-script is called by interval (e.g. every 60 seconds) but was not finished before next interval. In this article I would like to explain one proposal to prevent multiple parallel executions of a SLAX script
Writing rtt Details into an Accounting Profile File For SLAX version 1.0 and higher, the op script runs every 5 minutes, pinging the remote host and writing the rtt details into an accounting profile file . This op script is similar to op-ping-rtt.slax but without using jcs:syslog(), which is available in Junos OS Release 9.0 and later
Description This script runs intermittently via a generated event and fetches the output of " show system buffers "
Overview Script to capture ID of existing events...To help with this problem, I created the attached event script: capture-pseudo-events.slax
Overview This event script mimics Cisco's absolute vty timeout functionality...Description This script works in Junos 9.2 or later. It uses jade auth success as the generated event to cause the script to be run every 60 seconds