Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Processing Large Configurations Against Commit Scripts

 

In the standard commit model, when you perform a commit operation and commit scripts are in use, the management process (mgd) exports the post-inheritance candidate configuration in XML format and passes it as input to the commit script. The script driver then processes this configuration file against the configured commit scripts and returns any generated actions to the management process.

If the configuration is large, the script driver might have trouble reading the configuration into memory during the commit operation. When this occurs, you can configure the direct-access statement at the [edit system scripts commit] hierarchy level to enable the script driver to retrieve the candidate configuration directly from the configuration database. We recommend configuring the direct-access statement only if the configuration is large, because directly accessing the configuration data is more processor-intensive compared to the standard commit model and can affect system performance.

Note

Junos OS supports configuring the direct-access statement only when SLAX and XSLT commit scripts are configured. It does not support configuring the direct-access statement when Python commit scripts are also configured.

To enable the script driver to directly access the candidate configuration, include the direct-access statement at the [edit system scripts commit] hierarchy level.