Junos NED handling of leaf-list order

[equinix]

Hi,

When updating leaf-list (ordered-by=user), the tags “insert” and “name” are generated in the RPC triggered to the device. This RPC is failing with latest Juniper versions.

We checked with the Juniper team and they’re asking us to use “value” instead of “name” tag to conform with the RFC 6020. Is there a way to change this tag from "name" to "value"?

We have Netconf NEDs for other vendors where we see NSO uses the tags "insert" and "value" as per the RFC. So we're really not sure why it behaves differently for the lagacy Junos NED provided by Cisco.

Any help is much appreciated!!

<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"

     message-id="6">

  <edit-config xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">

    <target>

      <candidate/>

    </target>

    <config>

      <configuration xmlns=http://xml.juniper.net/xnm/1.1/xnm>

        <policy-options>

          <community>

            <name>TEST-COMMUNITY</name>

            <members insert="after"  name="24656:*">64317:*</members>

          </community>

        </policy-options>

      </configuration>

    </config>

  </edit-config>

</rpc>

Thanks,

Mithun

[huayyang]

the bu-made juniper ned does have some special handling for juniper devices, what you describe sounds like you need to get help from ned team via tac