Alcatel-Lucent 7450 System Management Manual page 355

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 details of subtree filter
support are as follows:
Example 1 — The following request will return an error:
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
</rpc>
]]>]]>
Reply:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
7450 ESS System Mangement Guide
• Attribute match expressions (section 6.2.2 of RFC 6241) are not supported. See
details below about content match nodes.
• Only containers are supported as selection nodes (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 desired list node; for
example, <configure><router> instead of <configure><router><interface/>.
• Content match nodes (section 6.2.5 of RFC 6241) are only supported for key leafs; for
example, <configure><router><interface><interface-name>abc</interface-name>.
∅ Content match nodes that are leafs but are not also keys will result in an error (not
silently ignored).
<get-config>
<source>
<running/>
</source>
<filter>
<configure>
</configure>
</filter>
</get-config>
<rpc-error>
<router>
<interface>
<interface-name>abc</interface-name>
<delayed-enable>30</delayed-enable>
</interface>
</router>
NETCONF
Page 355