Basic Process for Using Commit Scripts

You follow this process to use commit scripts:

1. Write a commit script.

This manual provides procedural steps and examples for writing scripts that generate error, warning, or system log messages and configuration changes. For detailed examples, see Commit Script Examples.

2. Copy the script to the /var/db/scripts/commit directory. Only users in the superuser JUNOS login class can access and edit files in the /var/db/scripts/commit directory.

If a platform has dual Routing Engines and you want the script to take effect on both Routing Engines, you must copy the script to the /var/db/scripts/commit directory on each Routing Engine. The commit synchronize command does not automatically copy the scripts from one Routing Engine directory into the other Routing Engine directory.

3. Enable the script by including the file statement at the [edit system scripts commit] hierarchy level. Only users in the superuser class can configure commit scripts.

[edit system scripts commit]

file filename.xsl;

4. Issue the commit command.

The JUNOS software provides several tools to manage and monitor commit script operation, including source control, traceoptions, and monitoring commands. For more information, see Configuring and Troubleshooting Commit Scripts.