<get-configuration>

Specify that the junos:changed="changed" attribute should appear in the opening tag of each changed configuration element.

The attribute appears in the opening tag of every parent tag element in the path to the changed configuration element, including the top-level opening <configuration> tag. If the changed configuration element is represented by a single (empty) tag, the junos:changed="changed" attribute appears in the tag. If the changed element is represented by a container tag element, the junos:changed="changed" attribute appears in the opening container tag and also in each child tag element enclosed in the container tag element.

The database attribute can be combined with the changed="changed" attribute to request either the candidate or active configuration:

• When the candidate configuration is requested (the database="candidate" attribute is included or the database attribute is omitted completely), elements added to the candidate configuration after the last commit operation are marked with the junos:changed="changed" attribute.

• When the active configuration is requested (the database="committed" attribute is included), elements added to the active configuration by the most recent commit are marked with the junos:changed="changed" attribute.

  Note:

  When a commit operation succeeds, the server removes the junos:changed="changed" attribute from all tag elements. However, if warnings are generated during the commit, the attribute is not removed. In this case, the junos:changed="changed" attribute appears in tag elements that changed before the commit operation as well as on those that changed after it.

An example of a commit-time warning is the message explaining that a configuration element will not actually apply until the device is rebooted. The warning appears in the tag string that the server returns to confirm the success of the commit, enclosed in an <xnm:warning> tag element.

To remove the junos:changed="changed" attribute from elements that changed before the commit, take the action necessary to eliminate the cause of the warning, and commit the configuration again.

Request that the NETCONF or Junos XML protocol server display commit-script-style XML data. The value of the attribute determines the output. Acceptable values are:

• apply—Display the configuration with commit script changes applied, including both transient and non-transient changes. The output is equivalent to the CLI output when using the | display commit-scripts option.

• apply-no-transients—Display the configuration with commit script changes applied, but exclude transient changes. The output is equivalent to the CLI output when using the | display commit-scripts no-transients option.

• view—Display the configuration in the XML format that is input to a commit script. This is equivalent to viewing the configuration with the attributes inherit="inherit", groups="groups", and changed="changed". The output is equivalent to the CLI output when using the | display commit-scripts view option.

Request that the NETCONF or Junos XML protocol server display the differences between the active or candidate configuration and a previously committed configuration (the comparison configuration).

The compare attribute can be combined with the database attribute to indicate whether the candidate configuration or the active configuration is compared to the previously committed configuration. If you omit the database attribute, the comparison uses the candidate configuration.

The compare attribute accepts the following values, which indicate the method used to reference the comparison configuration:

• configuration-revision—Reference the comparison configuration by its configuration revision identifier string, which you define in the configuration-revision="revision-id" attribute.

• rollback—Reference the comparison configuration by its rollback index, which you define in the rollback="rollback-number" attribute.

If you include the compare attribute but either omit the corresponding configuration-revision or rollback attribute or provide an invalid configuration revision identifier, the server uses the most recently committed configuration as the comparison configuration.

When you compare the candidate configuration to the active configuration, the compare operation returns XML output. For all other comparisons, it returns the output as text using a patch format. When you compare the candidate configuration to the active configuration, you can display the differences in text, XML, or JSON format by including the appropriate value for the format attribute in the request. You can display the differences in XML format starting in Junos OS Release 15.1R1, and you can display the differences in JSON format starting in Junos OS Release 16.1R1.

Specify the configuration from which to display data as one of the following:

• candidate—The candidate configuration.

• committed—The active configuration (the one most recently committed).

The database attribute takes precedence over the database-path attribute, if both are included.

Within a commit script, this attribute specifies the path to the session’ s pre-inheritance candidate configuration. The only acceptable value is $junos-context/commit-context/database-path.

For normal configuration sessions, the commit script retrieves the normal, pre-inheritance candidate configuration. For private configuration sessions, the commit script retrieves the private, pre-inheritance candidate configuration.

If you include both the database and the database-path attributes, the database attribute takes precedence.

Specify the format in which the NETCONF or Junos XML protocol server returns the configuration data. Acceptable values are:

• json—Configuration statements are formatted using JavaScript Object Notation (JSON). Starting in Junos OS Release 16.1, devices running Junos OS emit JSON-formatted configuration data using a new default implementation for serialization.

  Note:

  Starting in Junos OS Releases 16.1R4, 16.2R2, and 17.1R1, integers in Junos OS configuration data emitted in JSON format are not enclosed in quotation marks. In earlier releases, integers in JSON configuration data were treated as strings and enclosed in quotation marks.

• set—Configuration statements are formatted as Junos OS configuration mode set commands.

• text—Configuration statements are formatted as ASCII text, using the newline character, tabs and other white space, braces, and square brackets to indicate the hierarchical relationships between the statements. This is the format used in configuration files stored on a device running Junos OS and displayed by the CLI show configuration command.

• xml—Configuration statements are represented by the corresponding Junos XML tag elements. This is the default value if the format attribute is omitted.

Specify that the junos:group="group-name" attribute appear in the opening tag for each configuration element that is inherited from a configuration group. The group-name variable specifies the name of the configuration group from which that element was inherited.

The only acceptable value for the groups attribute is groups. When you specify the groups attribute, you must also specify the inherit attribute.

Specify how the NETCONF or Junos XML protocol server displays statements that are defined in configuration groups and interface ranges. If the inherit attribute is omitted, the output uses the <groups>, <apply-groups>, and <apply-groups-except> tag elements to represent user-defined configuration groups and uses the <interface-range> tag element to represent user-defined interface ranges; it does not include tag elements for statements defined in the junos-defaults group.

The acceptable values are:

• defaults—The output does not include the <groups>, <apply-groups>, and <apply-groups-except> tag elements, but instead displays tag elements that are inherited from user-defined groups and from the junos-defaults group as children of the inheriting tag elements.

• inherit—The output does not include the <groups>, <apply-groups>, <apply-groups-except>, and <interface-range> tag elements, but instead displays tag elements that are inherited from user-defined groups and ranges as children of the inheriting tag elements. The output does not include tag elements for statements defined in the junos-defaults group.

Specify that the junos:interface-ranges="source-interface-range" attribute appear in the opening tag for each configuration element that is inherited from an interface range. The source-interface-range variable specifies the name of the interface range.

The only acceptable value for the interface-ranges attribute is interface-ranges. When you specify the interface-ranges attribute, you must also specify the inherit attribute.

Specify that the junos:key="key" attribute appear in the opening tag of each element that serves as an identifier for a configuration object. The only acceptable value is key.