Can't create services for "netconf ned" devices: When tying to create l2vpn evpn or l2vpn p2p services with endpoint(s) on the devices having Netconf NED the following error is shown:errors: reason: Python cb_validate error. STATUS_CODE: TSDN-L2VPN-408 REASON: Router NED not supported CATEGORY: user SEVERITY: ERROR Context [name = Router NED not supported: cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4, message = Missing dynamic device mapping state = {'Device': '172.16.1.116', 'Service': 'L2vpn-p2p-1001', 'Device NED ID': 'cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4'}] . paths: /cisco-flat-L2vpn-fp-internal-local-site:flat-L2vpn-internal-local-site-service{L2vpn-p2p-1001 172.16.1.116}. path: /cisco-flat-L2vpn-fp-internal-local-site:flat-L2vpn-internal-local-site-service{L2vpn-p2p-1001 172.16.1.116}Can you please check the issue?NSO: 10.56.116.100Version 5.5.2.7 + M6Devices were added via DLM-NSO sync
Hi Leonid, What is credentials to log on this NSOHi Linh,10.56.116.100 ( nso/Public1234!) Thanks,Arun.M.GHi Arun,The l2vpn payload is not there and I don't see the issue. Please share the payload.Thanks,LinhPlease find the attached payload. It has device endpoints with 172.16.1.115 ( cli ned) and 172.16.1.117 ( netconf ned). It throws error while trying to configure. It seems that multi-vendor files are applied in a incorrect sequence. It should be applied after kicker xml file.It deleted flat-L2vpn multi-vendor configuration and reapplied it. The L2vpn service is working fine after thatPer Arun, the issue resolved.