Query on error opaque term node

[meghna-doshi]

Hi, We are seeing sometimes some warning/error of "parsing opaque term node" while doing subtree filtering get-data on operational data store:

2022-07-26T19:32:55.412716156Z netopeer2-server|INFO "netopeer2-server-log" [INF]: LY: Parsing opaque term node "bSChannelBwUL" with invalid value "". 2022-07-26T19:32:55.412735369Z netopeer2-server|INFO "netopeer2-server-log" [INF]: LY: Parsing opaque term node "bSChannelBwDL" with invalid value "". 2022-07-26T19:32:55.413110943Z netopeer2-server|INFO "netopeer2-server-log" [INF]: SR: Published event "rpc" "/ietf-netconf-nmda:get-data" with ID 7 priority 0 for 1 subscribers. 2022-07-26T19:32:55.413304808Z netopeer2-server|INFO "netopeer2-server-log" [INF]: SR: Processing "/ietf-netconf-nmda:get-data" "rpc" event with ID 7 priority 0 (remaining 1 subscribers). 2022-07-26T19:32:55.524775507Z netopeer2-server|INFO "netopeer2-server-log" [INF]: SR: Successful processing of "rpc" event with ID 7 priority 0 (remaining 0 subscribers). 2022-07-26T19:32:55.524795608Z netopeer2-server|INFO "netopeer2-server-log" [INF]: SR: Event "rpc" with ID 7 priority 0 succeeded. 2022-07-26T19:32:55.525154076Z netopeer2-server|INFO "netopeer2-server-log" [INF]: NP: Session 1: thread 1 event new RPC.

What does this error mean ??? 2022-07-26T19:32:55.412716156Z netopeer2-server|INFO "netopeer2-server-log" [INF]: LY: Parsing opaque term node "bSChannelBwUL" with invalid value ""

Though we get proper response:

GetData

<xml version="1.0" encoding="UTF-8"?><rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1658863975282">
   <get-data xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-nmda" xmlns:ds="urn:ietf:params:xml:ns:yang:ietf-datastores">
      <datastore>ds:operational</datastore>
      <subtree-filter>
         <ManagedElement xmlns="urn:3gpp:sa5:_3gpp-common-managed-element">
            <id>1</id>
            <GNBDUFunction xmlns="urn:3gpp:sa5:_3gpp-nr-nrm-gnbdufunction">
               <id>1</id>
               <NRCellDU xmlns="urn:3gpp:sa5:_3gpp-nr-nrm-nrcelldu">
                  <id>cellindex_1</id>
                  <attributes>
                     <bSChannelBwUL/>
                     <bSChannelBwDL/>
                  </attributes>
               </NRCellDU>
            </GNBDUFunction>
         </ManagedElement>
      </subtree-filter>
   </get-data>
</rpc>

response:

GetData

<xml version="1.0" encoding="UTF-8"?><rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1658863975282">
   <data xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-nmda">
      <ManagedElement xmlns="urn:3gpp:sa5:_3gpp-common-managed-element" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="create">
         <id>1</id>
         <GNBDUFunction xmlns="urn:3gpp:sa5:_3gpp-nr-nrm-gnbdufunction">
            <id>1</id>
            <NRCellDU xmlns="urn:3gpp:sa5:_3gpp-nr-nrm-nrcelldu">
               <id>cellindex_1</id>
               <attributes>
                  <bSChannelBwDL>20</bSChannelBwDL>
                  <bSChannelBwUL>20</bSChannelBwUL>
               </attributes>
            </NRCellDU>
         </GNBDUFunction>
      </ManagedElement>
   </data>
</rpc-reply>

[michalvasko]

All it says is that nodes <bSChannelBwUL/> and <bSChannelBwDL/> are not normally valid without a value but are fine in a filter so they are parsed into special opaque nodes. You can create only valid standard data nodes.