Request the Complete Configuration Using NETCONF
In a NETCONF session with a device running Junos OS, to request
the entire candidate configuration or the complete configuration in
the open configuration database, a client application encloses <get-config> and <source> tag elements and the <candidate/> tag
in an <rpc> tag element:
<rpc>
<get-config>
<source>
<candidate/>
</source>
</get-config>
</rpc>
]]>]]>
If a client application issues the Junos XML protocol <open-configuration> operation to open a specific
configuration database before executing the <get-config> operation, setting the source to <candidate/> retrieves the configuration data from the open configuration database.
Otherwise, the server returns the configuration data from the candidate
configuration.
To request the entire active configuration, a client application
encloses <get-config> and <source> tag elements and the <running/> tag in an <rpc> tag element:
<rpc>
<get-config>
<source>
<running/>
</source>
</get-config>
</rpc>
]]>]]>
The NETCONF server encloses its reply in <rpc-reply>, <data>, and <configuration> tag elements. For information about the attributes in the opening <configuration> tag, see Specify the Source for Configuration Information Requests Using NETCONF.
<rpc-reply xmlns="URN" xmlns:junos="URL">
<data>
<configuration attributes>
<!-- Junos XML tag elements representing the configuration -->
</configuration>
</data>
</rpc-reply>
]]>]]>