To request the entire candidate configuration, 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>
]]>]]>
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 <configuration>, <data>, and <rpc-reply> tag elements. For information about the attributes in the opening <configuration> tag, see Requesting Information from the Committed or Candidate Configuration.
<rpc-reply xmlns="URN" xmlns:junos="URL">
<data>
<configuration attributes>
<!- - JUNOS XML tag elements representing the configuration - ->
</configuration>
</data>
</rpc-reply>
]]>]]>