Requesting Committed or Candidate Configuration Information Using NETCONF
In a NETCONF session with a device running Junos OS, to request information from the candidate configuration, a client application includes the <source> tag element and <candidate/> tag within the <rpc> and <get-config> tag elements:
To request information from the active configuration—the one most recently committed on the device—a client application includes the <source> tag element and <running/> tag within the <rpc> and <get-config> tag elements:
 | Note: If requesting the entire configuration, the application omits the <filter> tag element. |
The NETCONF server encloses its reply in <rpc-reply>, <data>, and <configuration> tag elements. In the opening <configuration> tag, it includes the xmlns attribute to specify the namespace for the enclosed tag elements.
When returning information from the candidate configuration, the NETCONF server also includes attributes that indicate when the configuration last changed (they appear on multiple lines here only for legibility):
junos:changed-localtime represents the time of the last change as the date and time in the device’s local time zone.
junos:changed-seconds represents the time of the last change as the number of seconds since midnight on 1 January 1970.
When returning information from the active configuration, the NETCONF server also includes attributes that indicate when the configuration was committed (they appear on multiple lines here only for legibility):
junos:commit-localtime represents the commit time as the date and time in the device’s local time zone.
junos:commit-seconds represents the commit time as the number of seconds since midnight on 1 January 1970.
junos:commit-user specifies the Junos OS username of the user who requested the commit operation.
