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

Disable and Enable YANG Translation Scripts on Devices Running Junos OS

date_range 29-Nov-23

arrow_backward

arrow_forward

You can load standard (IETF, OpenConfig) or custom YANG data models on devices running Junos OS to add data models that are not natively supported by Junos OS but can be supported by translation. When you extend the configuration hierarchy with nonnative data models, you must also supply one or more translation scripts. Tranlation scripts perform two main functions:

Map the custom configuration syntax defined by the YANG data model to the corresponding Junos OS syntax
Add the translated data to the checkout configuration as a transient change during the commit operation

When you add translation scripts to the device with a new or existing YANG package, they are enabled by default. You can disable the translation scripts in a YANG package at any time without removing the package and associated files from the device, which can be useful for troubleshooting translation issues. After you disable translation for a package and commit the configuration, the configuration data associated with the YANG data models in that package can be present in the active configuration, but the configuration has no impact on the functioning of the device.

When translation is disabled, you can still configure and commit the statements and hierarchies in the data models added by that package. However, the device does not commit the corresponding Junos OS configuration statements as transient changes during the commit operation for any statements in the data models added by that package, even for those statements that were committed prior to disabling translation.

To disable translation scripts for a given YANG package that is installed on a device running Junos OS:

Issue the request system yang disable command, and specify the package identifier.
```
user@host> request system yang disable package-name
```

Verify that the status of the translation scripts in the package is disabled.

content_copy zoom_out_map
user@host> show system yang package package-name
Package ID            :package-name
YANG Module(s)        :modules
Translation Script(s) :translation scripts
Translation script status is disabled

Note:

When you disable translation for a package, the device retains any transient configuration changes that were committed prior to disabling translation until the next commit operation.

Note:

In configuration mode, you can issue the show | display translation-scripts translated-config command to verify which configured statements from nonnative YANG data models will be translated and committed during a commit operation. The command output does not include (and the device does not commit) the corresponding Junos OS configuration for those data models for which translation has been disabled.

To enable translation scripts for a given YANG package that is installed on a device running Junos OS:

Issue the request system yang enable command, and provide the package identifier.
```
user@host> request system yang enable package-name
```

Verify that the status of the translation scripts in the package is enabled.

content_copy zoom_out_map
user@host> show system yang package package-name
Package ID            :package-name
YANG Module(s)        :modules
Translation Script(s) :translation scripts
Translation script status is enabled

arrow_backward PREVIOUS Create Translation Scripts for YANG Configuration Models

NEXT arrow_forward Commit and Display Configuration Data for Nonnative YANG Modules

NETCONF XML Management Protocol Developer Guide

Disable and Enable YANG Translation Scripts on Devices Running Junos OS

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

Disable and Enable YANG Translation Scripts on Devices Running Junos OS

Related Documentation

Stay in touch