close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
- play_arrow NETCONF XML Management Protocol Overview
  - NETCONF XML Management Protocol and Junos XML API Overview
  - Advantages of Using the NETCONF XML Management Protocol and Junos XML API
- play_arrow NETCONF and Junos XML Tags Overview
play_arrow Manage NETCONF Sessions
- play_arrow NETCONF Session Overview
- play_arrow Manage NETCONF Sessions
- play_arrow NETCONF Tracing Operations
  - NETCONF and Junos XML Protocol Tracing Operations Overview
  - Example: Trace NETCONF and Junos XML Protocol Session Operations
- play_arrow NETCONF Protocol Operations and Attributes
- play_arrow NETCONF Request and Response Tags
- play_arrow Junos XML Protocol Elements Supported in NETCONF Sessions
- play_arrow Junos XML Protocol Element Attributes Supported in NETCONF Sessions
play_arrow Manage Configurations Using NETCONF
play_arrow Request Operational and Configuration Information Using NETCONF
- play_arrow Request Operational Information Using NETCONF
  - Request Operational Information Using NETCONF
  - Specify the Output Format for Operational Information Requests in a NETCONF Session
- play_arrow Request Configuration Information Using NETCONF
play_arrow NETCONF Utilities
- play_arrow NETCONF Perl Client
  - Understanding the NETCONF Perl Client and Sample Scripts
  - Install the NETCONF Perl Client
- play_arrow Develop NETCONF Perl Client Applications
play_arrow YANG
- play_arrow YANG Overview
- play_arrow Create and Use Non-Native YANG Modules
play_arrow OpenDaylight Integration
- play_arrow Configure OpenDaylight Integration
  - Configure Interoperability Between MX Series Routers and OpenDaylight
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

keyboard_arrow_right

Create Translation Scripts for YANG Configuration Models

date_range 29-Nov-23

arrow_backward

arrow_forward

You can load YANG modules on Junos devices to add data models that are not natively supported by the OS but can be supported by translation. When you extend the configuration hierarchy with nonnative YANG data models, you must also supply one or more translation scripts that provide the logic to map the nonnative configuration syntax to the corresponding Junos OS syntax.

Translation scripts perform two main functions:

Convert the configuration data corresponding to the nonnative YANG data models into Junos OS syntax
Add the translated configuration data as a transient change in the checkout configuration during the commit operation

Translation scripts can be written in either Python or SLAX and are similar to commit scripts in structure. For information about creating SLAX and Python scripts that generate transient changes in the configuration, see the Automation Scripting User Guide.

You use the request system yang add or request system yang update commands to add YANG modules and their associated translation scripts to a new or existing YANG package on the device. After you add the modules and translation scripts to the device, you can configure the statements and hierarchies in the data model added by those modules. When you load and commit the configuration data, the device calls the script to perform the translation and generate the transient configuration change.

This topic discusses the general structure for translation scripts. The specific translation logic required in the actual script depends on the custom hierarchies added to the schema and is beyond the scope of this topic.

To create the framework for translation scripts that are used on Junos devices:

In your favorite editor, create a new file that uses the .slax or .py file extension, as appropriate.
Include the necessary boilerplate required for that script’s language, which is identical to the boilerplate for commit scripts, and also include any required namespace declarations for your data models.
- SLAX code:
  version 1.0; ns junos = "http://xml.juniper.net/junos/*/junos"; ns xnm = "http://xml.juniper.net/xnm/1.1/xnm"; ns jcs = "http://xml.juniper.net/junos/commit-scripts/1.0"; ns prefix = "namespace"; import "../import/junos.xsl"; match configuration { /* * insert your code here */ }
- Python code:
  from junos import Junos_Context from junos import Junos_Configuration import jcs if __name__ == '__main__': /* * insert your code here */
Note:
Translation scripts must fully qualify identifiers for nonnative YANG data models in the translation code.

Note:
For information about commit script boilerplate code, see Required Boilerplate for Commit Scripts and the Automation Scripting User Guide.

Add code that maps the nonnative configuration data into the equivalent Junos OS syntax and stores the translated configuration data in a variable.

SLAX sample code:

content_copy zoom_out_map
match configuration {
 
    /* translation code */
 
    var $final = {
       /*
        * translated configuration
        */
    }
}

Python sample code:

content_copy zoom_out_map
if __name__ == '__main__':
 
    /* translation code */
 
    final = """
           /*
            * Junos XML elements representing translated configuration
            */
    """     

Add the translated content to the checkout configuration as a transient configuration change by calling the jcs:emit-change() template in SLAX scripts or the jcs.emit_change() function in Python scripts with the translated configuration and transient-change tag as arguments.
- SLAX sample code:
  match configuration { /* translation code */ var $final = { /* * translated configuration */ } call jcs:emit-change($content=$final, $tag='transient-change'); }
- Python sample code:
  if __name__ == '__main__': /* translation code */ final = """ /* * Junos XML elements representing translated configuration */ """ jcs.emit_change(final, "transient-change", "xml")
Note:
In SLAX scripts, you can also generate the transient change by emitting the translated configuration inside of a <transient-change> element instead of calling the jcs:emit-change() template.

On the device, perform the following tasks before adding the translation script to a YANG package:

If the translation script is written in Python, enable the device to execute unsigned Python scripts by configuring the language python or language python3 statement, as appropriate for the Junos OS release.
```
[edit]
user@host# set system scripts language (python | python3)
```
Note:
Starting in Junos OS Release 20.2R1 and Junos OS Evolved Release 22.3R1, the device uses Python 3 to execute YANG action and translation scripts. In earlier releases, Junos OS only uses Python 2.7 to execute these scripts, and Junos OS Evolved uses Python 2.7 by default to execute the scripts.
Download the script to the device, and optionally validate the syntax.
```
user@host> request system yang validate translation-script script
```

Before you can use translation scripts on a device, you must add the scripts and associated modules to a new or existing YANG package by issuing the request system yang add or request system yang update command. After the modules and scripts are added, the translation scripts are automatically invoked when you commit configuration data in the corresponding data models.

When you configure statements that correspond to third-party YANG data models, for example, OpenConfig or custom YANG data models, the following features are not supported:

Using configure batch or configure private mode
Configuring statements under the [edit groups] hierarchy

The active and candidate configurations contain the configuration data for the nonnative YANG data models in the syntax defined by those models. However, because the translated configuration data is committed as a transient change, the active and candidate configurations do not explicitly display the translated data in the Junos OS syntax when you issue the show or show configuration commands. To apply YANG translation scripts when you view the configuration, use the | display translation-scripts filter.

To view the complete post-inheritance configuration with the translated data (transient changes) explicitly included, append the | display translation-scripts filter to the show configuration command in operational mode or the show command in configuration mode. To view just the nonnative configuration data after translation, use the | display translation-scripts translated-config filter.

In configuration mode, to display just the changes to the configuration data corresponding to nonnative YANG data models before or after translation scripts are applied, append the configured-delta or translated-delta keyword, respectively, to the show | display translation-scripts command. In both cases, the XML output displays the deleted configuration data, followed by the new configuration data.

For more information about the | display translation-scripts filter, see Commit and Display Configuration Data for Nonnative YANG Modules.

Change History Table

Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.

Release

Description

22.3R1

Starting in Junos OS Evolved Release 22.3R1, Junos OS Evolved uses Python 3 to execute YANG action and translation scripts.

20.2R1

Starting in Junos OS Release 20.2R1, Junos OS uses Python 3 to execute YANG action and translation scripts.

arrow_backward PREVIOUS Managing YANG Packages and Configurations During a Software Upgrade or Downgrade

NEXT arrow_forward Disable and Enable YANG Translation Scripts on Devices Running Junos OS

NETCONF XML Management Protocol Developer Guide

Create Translation Scripts for YANG Configuration Models

Change History Table

Stay in touch

Helped me install or use the product
Accelerated my deployment

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

NETCONF XML Management Protocol Developer Guide

Create Translation Scripts for YANG Configuration Models

Related Documentation

Change History Table

Stay in touch