Content match node on a leaf-list

A content match node can be performed on a leaf-list but SR OS requires that all of the leaf-list elements and nodes must be specified. The full configuration (equivalent to the classic CLI command admin display-config or the MD-CLI command admin show configuration) can be obtained using a <get-config> request both when a <filter> tag is not present and when the <configure> tag is present inside a <filter> tag.

The following example shows a content match node on a lead-list when the <filter> tag is not present.

     <?xml version="1.0" encoding="UTF-8"?>
     <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
         <get-config>
             <source><running/></source>
         </get-config>
     </rpc>
     ]]>]]>

     <?xml version="1.0" encoding="UTF-8"?>
     <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
         <get-config>
             <source><candidate/></source>
         </get-config>
     </rpc>
     ]]>]]>

The following example shows a content match node on a lead-list when only the <configure> tag is present inside the <filter> tag.

     <?xml version="1.0" encoding="UTF-8"?>
     <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
         <get-config>
             <source><running/></source>
             <filter>
                 <configure xmlns="urn:nokia.com:sros:ns:yang:sr:conf"/>
             </filter>
         </get-config>
     </rpc>
     ]]>]]>

     <?xml version="1.0" encoding="UTF-8"?>
     <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
         <get-config>
             <source><candidate/></source>
             <filter>
                 <configure xmlns="urn:nokia.com:sros:ns:yang:sr:conf"/>
             </filter>
         </get-config>
     </rpc>
     ]]>]]>