Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Requesting a Configuration Hierarchy Level or Container Object Without an Identifier Using NETCONF

 

In a NETCONF session with a device running Junos OS, to request complete information about all child configuration elements at a hierarchy level or in a container object that does not have an identifier, a client application emits a <filter> tag element that encloses the tag elements representing all levels in the configuration hierarchy from the root (represented by the <configuration> tag element) down to the immediate parent level of the level or container object, which is represented by an empty tag. The entire request is enclosed in an <rpc> tag element:

For information about the <source> tag element, see Specifying the Source for Configuration Information Requests Using NETCONF.

The NETCONF server returns the requested section of the configuration in <data> and <rpc-reply> tag elements. For information about the attributes in the opening <configuration> tag, see Specifying the Source for Configuration Information Requests Using NETCONF.

The application can also request additional configuration elements of the same or other types by including the appropriate tag elements in the same <get-config> tag element. For more information, see Requesting Multiple Configuration Elements Simultaneously Using NETCONF.

The following example shows how to request the contents of the [edit system login] hierarchy level in the candidate configuration.