Provisioning L3/L2 vpn services throws illegal reference from NSO UI but same service payload works from ncs_cli: Hi Janaki,As discussed over Webex call, as part of this cdets - CSCwe53683 changes I am hitting below error when provisioning service from NSO UI.The same service payload when loaded and merged from ncs_cli works fine without any validation error.I am opening a JIRA ticket to resolve this discrepancy between NSO UI and ncs_cli.So, from Drop10 TSDN image onwards, we need to first create route-policy that will auto-create route-profile-identifiers.Services referring to this route-policy and route-profile identifiers will allow provisioning only if these entities are pre-existing in NSO and CNC.Tried to create route-policy first and then service provisioning from nso UI works fine.NSO logs have been collected and posted in box location - Thanks,Gomathi.
Attaching payloads with vpn profiles, route-profile-identifiers, l3vpn service all in one single payload that worked on ncs_cli without any error.  Hi Gomathi,The payload is working for me in the UI too similar to cliThanksSahithiVerified that NSO UI and NSO CLI are working consistently in use case where1. Load RP (without routing-profile-indetifiers)2. Load Service3. Error is seen "Illegal Ref --"Attached verification screenshots.Resolution Notes:> When the service and the route-policy is loaded at the same time without creating routing-profile-identifiers, user will see an Illegal Ref Error.> This behavior comes from CDETS CSCwe53683 (VPN profiles are not auto created like cnc 4.x).> User will have to modify any payloads that manually create the routing-profile-identifier and instead first create the route-policies, NSO will auto-create identifiers and then load the service.Please let us know if we can assist further.The validation error was displayed from UI but not from ncs_cli when Janaki and me tried to load the payload and commit. @Janaki - can you confirm that we were able to commit the full payload during debugging?Showed the output of "show | compare" to Sahithi yesterday where all config changes were accepted to be pushed to device from ncs_cli.Shared the NSO setup details to Janaki during debugging the issue. Not sure how it got fixed on ncs_cli as well after that.I have shared the NSO logs with all the transactions performed. Hope it has the trace logs of the commit performed with full payload as reference point.