- play_arrow Overview
- play_arrow Junos XML Management Protocol and Junos XML API Overview
- play_arrow Junos XML Protocol and Junos XML Tags Overview
- XML and Junos OS Overview
- XML Overview
- XML and Junos XML Management Protocol Conventions Overview
- Map Junos OS Commands and Command Output to Junos XML Tag Elements
- Map Configuration Statements to Junos XML Tag Elements
- Using Configuration Response Tag Elements in Junos XML Protocol Requests and Configuration Changes
- play_arrow Junos XML Protocol and JSON Overview
-
- play_arrow Manage Junos XML Protocol Sessions
- play_arrow Junos XML Protocol Session Overview
- play_arrow Manage Junos XML Protocol Sessions
- Satisfy the Prerequisites for Establishing a Connection to the Junos XML Protocol Server
- Configure clear-text or SSL Service for Junos XML Protocol Client Applications
- Connect to the Junos XML Protocol Server
- Start a Junos XML Protocol Session
- Authenticate with the Junos XML Protocol Server for Cleartext or SSL Connections
- Send Requests to the Junos XML Protocol Server
- Parse the Junos XML Protocol Server Response
- Parse Response Tag Elements Using a Standard API in NETCONF and Junos XML Protocol Sessions
- How Character Encoding Works on Juniper Networks Devices
- Handle an Error or Warning in Junos XML Protocol Sessions
- Halt a Request in Junos XML Protocol Sessions
- Lock, Unlock, or Create a Private Copy of the Candidate Configuration Using the Junos XML Protocol
- Terminate a Junos XML Protocol Session
- End a Junos XML Protocol Session and Close the Connection
- Sample Junos XML Protocol Session
- play_arrow Junos XML Protocol Tracing Operations
- play_arrow Junos XML Protocol Operations
- play_arrow Junos XML Protocol Processing Instructions
- play_arrow Junos XML Protocol Response Tags
- play_arrow Junos XML Element Attributes
- active
- count
- delete
- inactive
- insert
- junos:changed
- junos:changed-localtime
- junos:changed-seconds
- junos:commit-localtime
- junos:commit-seconds
- junos:commit-user
- junos:group
- junos:interface-range
- junos:key
- junos:position
- junos:total
- matching
- protect
- recurse
- rename
- replace
- replace-pattern
- start
- unprotect
- xmlns
-
- play_arrow Manage Configurations Using the Junos XML Protocol
- play_arrow Change the Configuration Using the Junos XML Protocol
- Request Configuration Changes Using the Junos XML Protocol
- Upload and Format Configuration Data in a Junos XML Protocol Session
- Upload Configuration Data as a File Using the Junos XML Protocol
- Upload Configuration Data as a Data Stream Using the Junos XML Protocol
- Define the Format of Configuration Data to Upload in a Junos XML Protocol Session
- Specify the Scope of Configuration Data to Upload in a Junos XML Protocol Session
- Replace the Configuration Using the Junos XML Protocol
- Create, Modify, or Delete Configuration Elements Using the Junos XML Protocol
- Create New Elements in Configuration Data Using the Junos XML Protocol
- Merge Elements in Configuration Data Using the Junos XML Protocol
- Replace Elements in Configuration Data Using the Junos XML Protocol
- Replace Only Updated Elements in Configuration Data Using the Junos XML Protocol
- Delete Elements in Configuration Data Using the Junos XML Protocol
- Rename Objects In Configuration Data Using the Junos XML Protocol
- Reorder Elements In Configuration Data Using the Junos XML Protocol
- Protect or Unprotect a Configuration Object Using the Junos XML Protocol
- Change a Configuration Element’s Activation State Using the Junos XML Protocol
- Change a Configuration Element’s Activation State Simultaneously with Other Changes Using the Junos XML Protocol
- Replace Patterns in Configuration Data Using the NETCONF or Junos XML Protocol
- play_arrow Commit the Configuration on a Device Using the Junos XML Protocol
- Verify Configuration Syntax Using the Junos XML Protocol
- Commit the Candidate Configuration Using the Junos XML Protocol
- Commit a Private Copy of the Configuration Using the Junos XML Protocol
- Commit a Configuration at a Specified Time Using the Junos XML Protocol
- Commit the Candidate Configuration Only After Confirmation Using the Junos XML Protocol
- Commit and Synchronize a Configuration on Redundant Control Planes Using the Junos XML Protocol
- Log a Message About a Commit Operation Using the Junos XML Protocol
- View the Configuration Revision Identifier for Determining Synchronization Status of Devices with NMS
- play_arrow Ephemeral Configuration Database
- Understanding the Ephemeral Configuration Database
- Unsupported Configuration Statements in the Ephemeral Configuration Database
- Enable and Configure Instances of the Ephemeral Configuration Database
- Commit and Synchronize Ephemeral Configuration Data Using the NETCONF or Junos XML Protocol
- Managing Ephemeral Configuration Database Space
-
- play_arrow Junos XML Protocol Utilities
- play_arrow Develop Junos XML Protocol C Client Applications
-
- play_arrow Configuration Statements and Operational Commands
Request Commit-Script-Style XML Configuration Data Using the Junos XML Protocol
On devices running Junos OS, to view the current configuration
in Extensible Markup Language (XML), you issue the show configuration
| display xml
operational mode command. To view the configuration
in commit-script-style XML, you use the show configuration |
display commit-scripts view
command. This command displays the
configuration in the format that would be input to a commit script.
In a Junos XML protocol session with a device running
Junos OS, to request that the server display the configuration as
commit-script-style XML data, a client application includes the commit-scripts="view"
attribute in the <get-configuration/>
tag or opening <get-configuration>
tag. It encloses the request
in an <rpc>
tag element:
<rpc> <get-configuration commit-scripts="view"/> <!-- OR --> <get-configuration commit-scripts="view"> <!-- tag elements for the configuration elements to return --> </get-configuration> </rpc>
To view the configuration with commit script changes applied,
including both transient and non-transient changes, issue the show configuration | display commit-scripts
operational mode
command on a device running Junos OS. Starting in Junos OS Release
12.1, you can also request this data through the Junos XML protocol
server.
To request that the Junos XML protocol server display
the configuration with commit script changes applied, including both
transient and non-transient changes, a client application includes
the commit-scripts="apply"
attribute in
the <get-configuration/>
tag or opening <get-configuration>
tag. It encloses the request
in an <rpc>
tag element:
<rpc> <get-configuration commit-scripts="apply"/> <!-- OR --> <get-configuration commit-scripts="apply"> <!-- tag elements for the configuration elements to return --> </get-configuration> </rpc>
To view the configuration with commit script changes applied,
but exclude transient changes, issue the show configuration |
display commit-scripts no-transients
operational mode command
on a device running Junos OS. Starting in Junos OS Release 12.1, you
can also request this data through the Junos XML protocol server.
To request that the Junos XML protocol server display
the configuration with commit script changes applied, but exclude
transient changes, a client application includes the commit-scripts="apply-no-transients"
attribute in the <get-configuration/>
tag or opening <get-configuration>
tag. It encloses the request
in an <rpc>
tag element:
<rpc> <get-configuration commit-scripts="apply-no-transients"/> <!-- OR --> <get-configuration commit-scripts="apply-no-transients"> <!-- tag elements for the configuration elements to return --> </get-configuration> </rpc>
The commit-scripts
attribute
can be combined with one or more of the following other attributes
in the <get-configuration/>
tag or opening <get-configuration>
tag:
changed
, which is described in Requesting Change Indicators for Configuration Elements Using the Junos XML Protocol.database
, which is described in Specifying the Source for Configuration Information Requests in a Junos XML Protocol Session.format
, when usingcommit-scripts="apply"
orcommit-scripts="apply-no-transients"
.groups
, which is described in Specifying the Output Format for Configuration Groups and Interface Ranges Using the Junos XML Protocol.inherit
, which is described in Specifying the Output Format for Configuration Groups and Interface Ranges Using the Junos XML Protocol.interface-ranges
, which is described in Specifying the Output Format for Configuration Groups and Interface Ranges Using the Junos XML Protocol.junos:key
, which is described in Requesting Identifier Indicators for Configuration Elements Using the Junos XML Protocol.
You do not need to include the changed
, groups
or inherit
attributes with the commit-scripts="view"
attribute. The commit-scripts-style XML view includes the junos:changed="changed"
attribute in the XML tags,
and it displays the output with inheritance applied. The tag elements
inherited from user-defined groups or interface ranges are displayed
within the inheriting tag elements, and the XML tags already include
the junos:group
attribute. To explicitly
display the junos:interface-range
attribute
in the commit-scripts-style view, you must include the interface-ranges="interface-ranges"
attribute in the <get-configuration>
tag.
If you specify a value of commit-scripts="apply"
or commit-scripts="apply-no-transients"
, you can specify an output format of formatted ASCII text by also
including the format="text"
attribute.