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.
Determine What Code to Automate There are multiple ways to automate. A working example provides a template structure that you can quickly modify and customize for efficiency and effectiveness. Version control enables you to use a working example, tweak it little by little, and then run...
Part 4 of 5 of Making Scripts Robust Previous Article: Making Scripts Robust: Handling Routing Engine Switchovers Next Article: Making Scripts Robust: Managing Retries NOTE: This applies to SLAX version 1.0 and higher. Recovering from Power Loss or Routing...
For commit, op, or event scripts, use the following. 1 < ?xml version= "1.0" encoding="us-ascii"?> < junoscript version= "1.0" > 2 < request-script-refresh-from > 3 < type >commit/op/event</ type > 4 ...
Run an op Script Over NETCONF The following example demonstrates how to run an op script over NETCONF: 1 % cat sample.netconf 2 < rpc > 3 < op-script > 4 < script >sample</ script > 5 < ...
Overview Opening a remote connection to a NETCONF-compliant device. This applies to SLAX version 1.0 and higher. Feature Prior to Junos OS Release 11.4, on-box scripts could only use Junoscript, a proprietary protocol, to form remote connections, which limited the range of...
Distribute Puppet and Synchronize Junoscripts You can use Puppet to distribute Junoscripts across multiple devices when grouped as Access Devices, Core Devices, and so on. To distribute Junoscripts across multiple devices (on top of your existing and working Puppet environment): ...
For commit, op, or event scripts, use the following. 1 <?xml version="1.0" encoding="us-ascii"?> <junoscript version="1.0"> 2 <request-script-refresh-from> 3 <type>commit/op/event</type> 4 <file...