ON THIS PAGE
<get-config>
Usage
<rpc> <get-config> <source> <( candidate | running )/> </source> </get-config> <get-config> <source> <( candidate | running )/> </source> <filter type="subtree"> <configuration> <!-- tag elements for each configuration element to return --> </configuration> </filter> </get-config> </rpc> ]]>]]>
Description
Request configuration data from the NETCONF server.
The child tag elements <source>
and <filter>
specify the source and scope of data to
display:
To display the entire active configuration, enclose the
<source>
tag element and<running/>
tag in the<get-config>
tag element.To display either the entire candidate configuration or all configuration data in the open configuration database, enclose the
<source>
tag element and<candidate/>
tag in the<get-config>
tag element.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 display one or more sections of the configuration hierarchy (hierarchy levels or configuration objects), enclose the appropriate child tag elements in the
<source>
and<filter>
tag elements.
Contents
<candidate/> |
Specify the open configuration database, or if there is no open database, the candidate configuration. |
<configuration> |
Enclose tag elements that specify which configuration elements to return. |
<filter> |
Enclose the To specify the configuration elements to return, include within
the |
<running/> |
Specify the active (mostly recently committed) configuration. |
<source> |
Enclose the tag that specifies the source of the configuration
data. To specify either the candidate configuration or an open configuration
database, include the |