NSO translating XML service in different ways for IOS and IOS XE

[miguelmendesjorge]

Hello,

I have searched and found that IOS's NED is the same to be used either for IOS or IOS XE devices. However, I am facing a problem on the service I am developing that NSO translates the XML code into different CLI commands depending if it is an IOS or IOS XE device. For example:

<enable xmlns="urn:ios">
   <secret>
      <secret>12345</secret>
   </secret>
</enable>

If I apply this on an IOS device and do

commit dry-run outformat native

This is how it will be translated on an IOS device:

enable secret 12345

And this is how the command is translated on an IOS XE device:

enable secret 9 12345

Which brings me an error on the IOS XE device, reverting the entire template appliance:

ERROR: The secret you entered is not a valid encrypted secret.
To enter an UNENCRYPTED secret, do not specify type 9 encryption.
When you properly enter an UNENCRYPTED secret, it will be encrypted.

I am using the IOS NED as recommended for both device types. How can I overcome this problem?

Thank you.

[vleijon]

This looks right. It looks like this is a potential NED issue, I would try writing a ticket with more details and the device trace logs.

Looking at the device traces might help you understand what goes wrong too.