leaf-list edit-config is not same to modulechange

[dwdengwei]

this is edit-config synce-config this is recv module change, right is PRC AND PRS, but only is PRS , and only the first is wrong, change other parameter and exec edit-config once again is right, what's wrong with this netopeer2-server 2.1.46

[michalvasko]

You will need to provide more information before I can help you. Were there any instances of acceptance-list-of-ssm stored before the edit-config? What exactly are you printing in the second screenshot?

[dwdengwei]

get --filter-xpath /sync DATA

<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <sync xmlns="urn:o-ran:sync:1.0">
    <sync-status>
      <sync-state>FREERUN</sync-state>
      <frequency-error>0.0</frequency-error>
      <supported-reference-types>
        <item>PTP</item>
      </supported-reference-types>
      <supported-reference-types>
        <item>SYNCE</item>
      </supported-reference-types>
    </sync-status>
    <sync-capability>
      <sync-t-tsc>CLASS_B</sync-t-tsc>
    </sync-capability>
    <ptp-config>
      <domain-number>24</domain-number>
      <accepted-clock-classes>
        <clock-classes>6</clock-classes>
      </accepted-clock-classes>
      <accepted-clock-classes>
        <clock-classes>7</clock-classes>
      </accepted-clock-classes>
      <ptp-profile>G_8275_1</ptp-profile>
      <delay-asymmetry>0</delay-asymmetry>
      <g-8275-1-config>
        <multicast-mac-address>FORWARDABLE</multicast-mac-address>
        <delay-asymmetry>0</delay-asymmetry>
      </g-8275-1-config>
    </ptp-config>
    <ptp-status>
      <reporting-period>10</reporting-period>
      <lock-state>UNLOCKED</lock-state>
      <clock-class>255</clock-class>
      <clock-identity>0x0000000000000800</clock-identity>
      <partial-timing-supported>false</partial-timing-supported>
      <sources>
        <local-port-number>0</local-port-number>
        <state>DISABLED</state>
        <two-step-flag>true</two-step-flag>
        <leap61>false</leap61>
        <leap59>false</leap59>
        <current-utc-offset-valid>false</current-utc-offset-valid>
        <ptp-timescale>true</ptp-timescale>
        <time-traceable>true</time-traceable>
        <frequency-traceable>true</frequency-traceable>
        <source-clock-identity>0x16fffe93608c0001</source-clock-identity>
        <source-port-number>128</source-port-number>
        <current-utc-offset>37</current-utc-offset>
        <priority1>128</priority1>
        <clock-class>255</clock-class>
        <clock-accuracy>33</clock-accuracy>
        <offset-scaled-log-variance>20061</offset-scaled-log-variance>
        <priority2>128</priority2>
        <grandmaster-clock-identity>0x008016fffe93608c</grandmaster-clock-identity>
        <steps-removed>0</steps-removed>
        <time-source>32</time-source>
      </sources>
    </ptp-status>
    <synce-config>
      <acceptance-list-of-ssm>PRC</acceptance-list-of-ssm>
      <acceptance-list-of-ssm>PRS</acceptance-list-of-ssm>
      <ssm-timeout>1</ssm-timeout>
    </synce-config>
    <synce-status>
      <lock-state>UNLOCKED</lock-state>
      <sources>
        <local-port-number>0</local-port-number>
        <state>DISABLED</state>
        <quality-level>0</quality-level>
      </sources>
    </synce-status>
  </sync>
</data>

before edit-config, get content default acceptance-list-of-ssm leaf-list value is PRC and PRS

edit-config test value is same as default , but result first size is 1, value is PRS; second size is 2, value is PRC and PRS

[dwdengwei]

[michalvasko]

Still not really sure what is happening but looking at when netopeer2 v2.1.46 was released, all you may need to do is update all the libraries and the server, it is quite old by now. If that does not help, we can debug this further.