close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
- play_arrow Junos Automation Scripts Overview
- play_arrow Junos XML Management Protocol and Junos XML API Overview
play_arrow Automation Scripting Using XSLT
- play_arrow XSLT Overview
- play_arrow Standard XPath and XSLT Functions Used in Automation Scripts
- play_arrow Standard XSLT Elements and Attributes Used in Automation Scripts
play_arrow Automation Scripting Using SLAX
- play_arrow SLAX Overview
- play_arrow SLAX Statements
- play_arrow The libslax Distribution for Automation Scripting
play_arrow Automation Scripting Using Python
- play_arrow Python Overview
play_arrow Automation Script Input
- play_arrow Global Parameters in Automation Scripts
  - Global Parameters and Variables in Junos OS Automation Scripts
play_arrow Extension Functions and Named Templates for Automation Scripts
play_arrow Manage Automation Scripts
- play_arrow Store and Enable Scripts
- play_arrow Configure a Remote Source for Scripts
- play_arrow Configure the Session Protocol for Scripts
  - Understanding the Session Protocol in Automation Scripts
  - Example: Specify the Session Protocol for a Connection within Scripts
- play_arrow Control Execution of Scripts
- play_arrow Synchronize Scripts Between Routing Engines
- play_arrow Convert Scripts Between SLAX and XSLT
  - Convert Scripts Between SLAX and XSLT
play_arrow Commit Scripts
- play_arrow Commit Scripts Overview
  - Commit Script Overview
  - How Commit Scripts Work
- play_arrow Create and Execute Commit Scripts
- play_arrow Generate a Custom Warning, Error, or System Log Message Using Commit Scripts
- play_arrow Generate Persistent or Transient Configuration Changes Using Commit Scripts
- play_arrow Create Custom Configuration Syntax with Commit Script Macros
- play_arrow Commit Script Examples
- play_arrow Junos XML and XSLT Tag Elements Used in Commit Scripts
- play_arrow Troubleshoot Commit Scripts
play_arrow Op Scripts
- play_arrow Op Scripts Overview
  - Op Script Overview
  - How Op Scripts Work
- play_arrow Create and Execute Op Scripts
- play_arrow Op Script Examples
- play_arrow Provision Services Using Service Template Automation
  - Service Template Automation Overview
  - Example: Configure Service Template Automation
- play_arrow Troubleshoot Op Scripts
  - Trace Op Script Processing on Devices Running Junos OS
  - Trace Script Processing on Devices Running Junos OS Evolved
play_arrow Event Policies and Event Scripts
play_arrow SNMP Scripts
- play_arrow SNMP Scripts Overview
  - SNMP Scripts Overview
- play_arrow Create and Execute SNMP Scripts
- play_arrow SNMP Script Example
  - Example: Process Unsupported OIDs with an SNMP Script
- play_arrow Troubleshoot SNMP Scripts
  - Trace SNMP Script Processing on Devices Running Junos OS
  - Trace Script Processing on Devices Running Junos OS Evolved
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

Control the Execution of Commit Scripts in the QFabric System

date_range 14-Jul-21

arrow_backward

arrow_forward

This document describes the tasks that affect the way commit scripts are executed. In the QFabric system, commit scripts are stored in the in the /pbdata/mgd_shared/partition-ip/var/db/scripts/commit directory that is shared among Director devices in a Director group.

To determine which commit scripts are currently enabled on the QFabric system, use the show command to display the files included at the [edit system scripts commit] hierarchy level. To ensure that the enabled files are on the device, list the contents of the /pbdata/mgd_shared/partition-ip/var/db/scripts/commit directory using the file list operational mode command.

See the following tasks:

Enabling Commit Scripts to Execute

The commit operation requires that all scripts be included in configuration at the [edit system scripts commit file] hierarchy level for all QFabric Director devices.

If you need to temporarily remove a script from a commit operation but do not want to remove it from the configuration permanently, you may configure the optional statement at the [edit system scripts commit file filename] hierarchy level to enable the commit operation to succeed even if a script is missing from the commit script directory.

CAUTION:

When you include the optional statement at the [edit system scripts commit file filename] hierarchy level, no error message is generated during the commit operation if the file does not exist. As a result, you might not be aware that a script has not been executed as expected.

The filename of a commit script written in SLAX or Python must include the .slax or .py file extension, respectively, for the script to be executed.

To enable a commit script to execute during a commit operation:

Ensure that the commit script is located in the correct directory: /pbdata/mgd_shared/partition-ip/var/db/scripts/commit directory on the Director device.

Configure the commit script.

content_copy zoom_out_map
[edit system scripts commit]
user@switch# set file filename <optional>

Commit the configuration.

content_copy zoom_out_map
[edit system scripts commit]
user@switch# top
[edit]
user@switch# commit

Removing Commit Scripts from the Configuration

You can prevent a commit script from executing during a commit operation by removing the script’s filename from the [edit system scripts commit] hierarchy in the configuration.

Note:

You can also deactivate a script using the deactivate statement instead of removing it from the configuration. Deactivated scripts may be reactivated later.

To prevent a commit script from executing during a commit operation:

Delete the commit script filename from the [edit system scripts commit] hierarchy level in the configuration.
```
[edit system scripts commit]
user@switch# delete file filename
```

Commit the configuration.

content_copy zoom_out_map
[edit system scripts commit]
user@switch# top
[edit]
user@switch# commit

(Optional) Remove the commit script from the /pbdata/mgd_shared/ directory on the Director device.

Best Practice:
Although removing the commit script is not necessary, we recommend deleting unused files from the system.

Deactivating Commit Scripts

Deactivating a commit script results in its being marked as inactive in the configuration. The script is not executed during the commit operation, but you can reactivate the script by using the activate statement.

To deactivate the commit script:

Deactivate the script.

content_copy zoom_out_map
[edit]
user@switch# deactivate system scripts commit file filename

Commit your changes.
```
[edit]
user@switch# commit
```

Verify that the commit script is deactivated.

content_copy zoom_out_map
[edit]
user@switch# show system scripts commit
inactive: file config-check.slax

Activating Inactive Commit Scripts

Deactivating a commit script results in its being marked as inactive in the configuration and is therefore not executed during the commit operation.

To activate an inactive commit script:

Activate the script.

content_copy zoom_out_map
[edit]
user@switch#  activate system scripts commit file filename

Commit your changes.
```
[edit]
user@switch# commit
```

arrow_backward PREVIOUS Control the Execution of Commit Scripts During Commit Operations

NEXT arrow_forward Configure Checksum Hashes for a Commit Script

Automation Scripting User Guide

ON THIS PAGE

Control the Execution of Commit Scripts in the QFabric System

Enabling Commit Scripts to Execute

Removing Commit Scripts from the Configuration

Deactivating Commit Scripts

Activating Inactive Commit Scripts

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Automation Scripting User Guide

ON THIS PAGE

Control the Execution of Commit Scripts in the QFabric System

Enabling Commit Scripts to Execute

Removing Commit Scripts from the Configuration

Deactivating Commit Scripts

Activating Inactive Commit Scripts

Related Documentation

Stay in touch