Provision policy failed on LSA setup with illegal reference: I have a LSA setup with 1 CFS and 2 RFS. PE-A is associated with rfs-29. I am able to onboard LSA providers and devices to CW cluster. When provision an sr-te policy either from CNC UI or NSO, both failed the validation with illegal reference.Steps:1. from NSO commit manager load the payload xml file (attached) 2. Click "Native Config" tab   The following error message shows:"errors: reason: illegal reference. paths: /ncs:devices/device{rfs-29}/config/cisco-sr-te-cfp-internal:sr-te/cisco-sr-te-cfp-sr-policies-internal:policies/policy{srte_c_401_ep_100.100.10.3 PE-A}/head-end. path: /ncs:devices/device{rfs-29}/config/cisco-sr-te-cfp-internal:sr-te/cisco-sr-te-cfp-sr-policies-internal:policies/policy{srte_c_401_ep_100.100.10.3 PE-A}/head-end"
 Hello, Please kindly share the setup info so I may verify the devices/config.CFS: 172.23.213.30RFS: 172.23.213.29 ; 172.23.213.39id/pw: root/Vtsisco@123!Let me know if you need any other information.Hello, I have been able to load the policy succesfully on rfs-29.rfs-29 was out of sync and thus the policy error is seen as above.There are alarms to indicate the rfs-29 was down for sometime (PE-A may have been onboarded during that time).Under CFS - the dispatch map contained the device but the config under the rfs node wasnt showing the device:admin@ncs% show devices lsa dispatch-mapdevice PE-A {ned-id  cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38;remote-node rfs-29;}admin@ncs% show devices device rfs-29 config devices deviceNo entries found.When a compare config was requested, it indicated the device rfs-29 was out of sync.I have executed a sync-from on the rfs nodeadmin@ncs% request devices device rfs-29 sync-fromresult trueNow, the policy is onboarded successfully.admin@ncs% show sr-te policies policy srte_c_401_ep_100.100.10.3head-end PE-A;tail-end 100.100.10.3;color 401;binding-sid 11111;path 401 { dynamic { metric-type latency; pce; }}Thanks Janaki for finding the device OOS issue and resolve it. I went ahead and provision an L2vpn service from CNC and it stuck in "In-Progress" state. Cross launch to NSO the plan data showed 5/8 completed. Screenshots attached. Can you help to take a look?Hi Crystal, after investigation it seemed like the redeploy of service did not happen correctly. Everything else seemed to be in place, the logs indicate that the kickers etc were triggered properly but for some unknown reason the redeploy did not go through fully.When I redeployed the service it worked well and I also deleted the config and re-loaded it which also worked well.Please verify and let me know.Thanks Janaki for investigating the issue. I went ahead and delete the L2vpn service from CNC UI. But the entry still showed on CNC UI. When I cross launch to view in NSO, NSO UI showed "path does not exist". There seems to be a disconnect between CNC and NSO. Can you check if the correct status has been sent to CNC?Thanks.Hi Crystal, Sure! I can look at it, but it would be better to track this above issue in a new ticket.Please kindly proceed with opening up another ticket for troubleshooting this issue.Can you please confirm if the original issue with the illegal reference is fixed so I may proceed with closing this ticket?Please let me know.Sure Janaki. The illegal reference issue is resolved. You can close this ticket. I will open new ticket to track the other issue. Thanks again for your help.Thank you!rfs-29 was out of sync and thus the policy error is seen as above. Alarms indicate node had lost connectivity which resulted in the out of sync. Issue was fixed on the setup by manually running a sync from on the rfs-29 node.