A <get-config> operation is supported with the <running> datastore only.
Subtree filtering for basic subtree selection is supported for XML content layer <get-config> requests. Post-filtering of the selected subtrees is not supported.
The subtree filtering behavior is as follows:
Attribute match expressions, as defined in section 6.2.2 of RFC 6241, are not supported.
Only containers are supported as selection nodes, as defined in section 6.2.4 of RFC 6241. Empty leaf nodes or list name nodes are not supported as selection nodes.
Nodes that represent lists must also include content match nodes for all keys of the list; for example, <configure><router><interface><interface-name>abc</interface-name>.
A selection node that is a list, without also specifying the key, is not supported; for example, <configure><router><interface/> is not supported. An alternative is to request the parent containment node that contains the wanted list node; for example, <configure><router> instead of <configure><router><interface/>.
Content match nodes, as defined in section 6.2.5 of RFC 6241, are only supported for key leaves; for example, <configure><router><interface> <interface-name>abc</interface-name>.
Content match nodes that are leaves but are not also keys result in an error (not silently ignored).
A <get-config> request that specify a non-existent list node or presence container results in a reply that contains no data for those list nodes or containers. An <rpc-error> is not sent in this case.
See the following sections for examples of <get-config> request and response messages: