L2NM EVPN service stuck in provisioning state in XE setup: Provisioned an L2NM EVPN service from CAT UI and the service is stuck in provisioning state. The following error seen in NSO UI. Should we send notification to CNC so the provisioning can fail instead of stuck?Service Alarm : /cisco-flat-L2vpn-fp-internal-local-site:flat-L2vpn-internal-local-site-service{L2NM-L2VPN_NM-EVPN-VPWS-SRTE-230-internal ASR920-1-PE7}: Python cb_validate error. STATUS_CODE: TSDN-L2VPN-408REASON: Router NED not supportedCATEGORY: userSEVERITY: ERRORContext [name = Router NED not supported: cisco-ios-cli-6.74:cisco-ios-cli-6.74, message = Missing dynamic device mapping
Any updates?Had a webex meeting with the reporter.For the mentioned error seen on the NSO , dynamic-device-mappings was missing for `cisco-ios-cli-6.74. Corrected the same.Payload for the bootrap configuration for the dynamic mappings `L2VPN-multi-vendor-iosxe-cli.xml` is mentioned in the following wiki . L2VPN EVPN service type is not supported for IOSXE. Please refer to the device support matrix for more details: Regarding Failure notification not received in this failure case , reporter will file CDET .CSCvz40738 opened to track the issue.