Written by Douglas McPhersonSolutions Consultant at Juniper
This is part 1 of 5 of Making Scripts Robust.
Previous Article: Best Practices Series: Design Considerations for “Long-Lived” On-box SLAX Scripts
Next Article: Making Scripts Robust: Checking Status
This applies to SLAX version 1.0 and higher.
This is the second in a series of best practices intended to reduce the work required to implement your Junos automation, while making the automation more robust and easier to support.
Feedback and questions are welcome on the TechWiki.
Now that you are running your long-lived script (see SLAX: Design Consideration for Long-Lived On-box SLAX Scripts), your next step is to ensure that it will continue to run without supervision. This will ensure you do not need to manually restart your script any time your router reboots or performs an RE switchover. In this article you will learn the following techniques you can apply that will allow your scripts to run reliably and give you time for more important tasks: