External error in the NED implementation for device for custom L2VPN Service

[Andrew Melsom]

Hi All

Trying to learn Cisco NSO, I have a lab with 7 IOSXR 9000v Routers and a single NSO server but am getting an error that I cant figure out, Any help would be most appreciated.

admin@ncs(config)# commit dry-run outformat native                 
native {
    device {
        name XR1-Edingborough
        data l2vpn
              xconnect group b
               p2p 100
                interface GigabitEthernet0/0/0/2
                neighbor evpn evi 200 target 1 source 1
                 !
               exit
              exit
             exit
    }
    device {
        name XR7-Poole
        data l2vpn
              xconnect group b
               p2p 100
                interface GigabitEthernet0/0/0/2
                neighbor evpn evi 200 target 1 source 1
                 !
               exit
              exit
             exit
    }
}

Error

admin@ncs(config)# commi
Aborted: External error in the NED implementation for device XR1-Edingborough: command: 
RP/0/RP0/CPU0:Edingborough(config)#  xconnect group b 
                                     ^
% Invalid input detected at '^' marker.
 [ l2vpn / ]

Manual Config Test

RP/0/RP0/CPU0:Edingborough(config)#l2vpn
RP/0/RP0/CPU0:Edingborough(config-l2vpn)# xconnect group b
RP/0/RP0/CPU0:Edingborough(config-l2vpn-xc)#  p2p 100
RP/0/RP0/CPU0:Edingborough(config-l2vpn-xc-p2p)#   interface GigabitEthernet0/$
RP/0/RP0/CPU0:Edingborough(config-l2vpn-xc-p2p)#   neighbor evpn evi 200 targe$
RP/0/RP0/CPU0:Edingborough(config-l2vpn-xc-p2p-pw)#commi
Fri May  1 16:38:35.716 UTC

Package Version

admin@ncs# show packages package oper-status    
                                                                                                        PACKAGE                
                          PROGRAM                                                                       META     FILE          
                          CODE     JAVA           PYTHON         BAD NCS  PACKAGE  PACKAGE  CIRCULAR    DATA     LOAD   ERROR  
NAME                  UP  ERROR    UNINITIALIZED  UNINITIALIZED  VERSION  NAME     VERSION  DEPENDENCY  ERROR    ERROR  INFO   
-------------------------------------------------------------------------------------------------------------------------------
cisco-iosxr-cli-7.18  X   -        -              -              -        -        -        -           -        -      -      
l2vpn                 X   -        -              -              -        -        -        -           -        -      -      

IOS Version

Spoiler

admin@ncs# show packages package oper-status
PACKAGE
PROGRAM META FILE
CODE JAVA PYTHON BAD NCS PACKAGE PACKAGE CIRCULAR DATA LOAD ERROR
NAME UP ERROR UNINITIALIZED UNINITIALIZED VERSION NAME VERSION DEPENDENCY ERROR ERROR INFO
-------------------------------------------------------------------------------------------------------------------------------
cisco-iosxr-cli-7.18 X - - - - - - - - - -
l2vpn X - - - - - - - - - -

Thanks

All

[yfherzog · Accepted solution]

The error message means that the NED received an unexpected answer from the device.

You did good trying to follow the same procedure directly on the device.

One additional tool for that is the NED trace.

You can enable it by entering config mode and configuring this for your device:

admin@ncs(config)# devices device xr-1 trace raw 
admin@ncs(config-device-xr-1)# commit

You should then repeat the same exercise as before (configuring the xconnect using NSO).

On the logs directory (if this is a local install then it's under the runtime directory, on a system install by default, it's under /var/log/ncs), you should now see a file with name containing the NED and device names.

Follow the trace to confirm the sequence of commands the NED is running on the device.

If it's the same as the ones that you do, then there must be something other than the sequence of commands that is not the same between what the NED is doing and what you're doing manually.

You might also be able to see more details about the error message coming from the device.

One possibility might be the users being used.

It might be that the NED is using a different user comparing to yours (dictated by the authgroup you assigned to the device), and that user is missing some privileges.

[Andrew Melsom]

Thank you!

That trace is a very handy tool that I was not aware existed, and allowed me to see that it was something as simple as a permissions issue, and not being able to execute the command on the Router.