Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

export-format

Syntax

Hierarchy Level

Description

Specify the default implementation of the serialization to use for exported data in the given format. This statement only affects device configuration data that is displayed in the requested format.

Options

json

Define which implementation of the serialization to use for configuration data emitted in JavaScript Object Notation (JSON) format.

Acceptable values include:

  • ietf—JSON data is emitted according to the encoding rules defined in Internet drafts draft-ietf-netmod-yang-json-09, JSON Encoding of Data Modeled with YANG, and draft-ietf-netmod-yang-metadata-06, Defining and Using Metadata with YANG.

  • verbose—JSON data is emitted in verbose format, which emits all objects as JSON arrays.

    You can configure the verbose statement starting in Junos OS Release 16.1R1, even though the statement is not exposed in the Junos OS CLI until a later release.

  • Default: ietf in Junos OS Release 16.1R1 and later; verbose in earlier releases.
Note:

Starting in Junos OS Release 17.3R1, OpenConfig supports the operational state emitted by daemons directly in JSON format in addition to XML format. To configure JSON compact format, use the following command: set system export-format state-data json compact.

This CLI command converts XML format to compact JSON format. Else, it emits the JSON in non-compact format.

Required Privilege Level

maintenance—To view or add this statement in the configuration.

Release Information

Statement introduced in Junos OS Release 16.1.

Related Documentation