Junos 10.3 Junos XML Management Protocol Guide
72
When the
database="committed"
configuration. Elements added to the active configuration by the most recent commit
are marked with the
junos:changed="changed"
and optionally
inherit
groups
for Configuration Groups" on page 74.
It does not make sense to combine the
The
junos:changed="changed"
is the default output format.
The application can also include the
identifiers (as described in "Requesting an Indicator for Identifiers" on page 73).
The following example shows how to request change indicators for configuration elements
at the
[edit system syslog]
indicates that a log file called
commit.
Client Application
Junos XML Protocol Server
<rpc>
<get-configuration changed="changed">
<configuration>
<system>
<syslog/>
</system>
</configuration>
</get-configuration>
</rpc>
<rpc-reply xmlns:junos="URL ">
<configuration junos:changed-seconds=" seconds " \
<system junos:changed="changed">
</system>
</configuration>
</rpc-reply>
attribute is included, the output is from the active
attribute.
, which are described in "Specifying the Output Format
attribute with the
changed
attribute appears only in Junos XML-tagged output, which
attribute after requesting an indicator for
changed
hierarchy level in the candidate configuration. The output
has been configured since the last
interactive-commands
junos:changed-localtime="timestamp" junos:changed="changed">
<syslog junos:changed="changed">
<file>
<name>messages</name>
<contents>
<name>any</name>
<info/>
</contents>
</file>
<file junos:changed="changed">
<name junos:changed="changed">interactive-commands</name>
<contents>
<name junos:changed="changed">interactive-commands</name>
<notice junos:changed="changed"/>
</contents>
</file>
</syslog>
attribute.
format="text"
Copyright © 2010, Juniper Networks, Inc.