Device mapped to different RFS throwing error message & not able to sync: Hi Team,Device mapped to different RFS throwing error message ; not able to sync.TB2-PE-C device is added to RFS-2, but in the sync it's throwing error message for PE-C on rfs-1admin@ncs% request devices sync-fromsync-result {  device rfs-1  result false  info illegal reference devices device rfs-1 config l2vpn-rr-parent-route-policy bgp_in TB2-PE-C device}sync-result {  device rfs-2  result true}admin@ncs% show devices lsa dispatch-mapdevice TB2-P-BOTTOMLEFT {  ned-id   cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4;  remote-node rfs-2;}device TB2-P-BOTTOMRIGHT {  ned-id   cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4;  remote-node rfs-1;}device TB2-P-TOPLEFT {  ned-id   cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4;  remote-node rfs-1;}device TB2-P-TOPRIGHT {  ned-id   cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38;  remote-node rfs-1;}device TB2-PE-A {  ned-id   cisco-iosxr-nc-7.5:cisco-iosxr-nc-7.5;  remote-node rfs-1;}device TB2-PE-B {  ned-id   cisco-iosxr-nc-7.5:cisco-iosxr-nc-7.5;  remote-node rfs-1;}device TB2-PE-C {  ned-id   cisco-iosxr-nc-7.5:cisco-iosxr-nc-7.5;  remote-node rfs-2;}device TB2-PE-D {  ned-id   cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38;  remote-node rfs-1;}device TB2-PE-E {  ned-id   cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38;  remote-node rfs-1;}device rfs-1 {  ned-id cisco-nso-nc-5.7:cisco-nso-nc-5.7;  local;}device rfs-2 {  ned-id cisco-nso-nc-5.7:cisco-nso-nc-5.7;  local;}admin@ncs% exitadmin@ncs> show devices listNAME       ADDRESS    DESCRIPTION NED ID       ADMIN STATE-----------------------------------------------------------------------------TB2-P-BOTTOMLEFT 10.194.63.192 -      cisco-iosxr-nc-7.4 unlockedTB2-PE-C     10.194.63.196 -      cisco-iosxr-nc-7.5 unlockedadmin@ncs> show devices listNAME        ADDRESS    DESCRIPTION NED ID        ADMIN STATE--------------------------------------------------------------------------------TB2-P-BOTTOMRIGHT 10.194.63.193 -      cisco-iosxr-nc-7.4  unlockedTB2-P-TOPLEFT   10.194.63.190 -      cisco-iosxr-nc-7.4  unlockedTB2-P-TOPRIGHT   10.194.63.191 -      cisco-iosxr-cli-7.38 unlockedTB2-PE-A      10.194.63.194 -      cisco-iosxr-nc-7.5  unlockedTB2-PE-B      10.194.63.195 -      cisco-iosxr-nc-7.5  unlockedTB2-PE-D      10.194.63.214 -      cisco-iosxr-cli-7.38 unlockedTB2-PE-E      10.194.63.213 -      cisco-iosxr-cli-7.38 unlocked
Setup details:CFS-10.194.63.169RFS1-10.194.63.170RFS2-10.194.63.242Credentials: admin/Vtsisco@123!Hi RageshIt looks like the device was moved from one rfs node to another.Can you please let us know the exact steps you followed?Thanks.Hi Nikhil,Devices are onboarded to NSO via DLM-NSO sync, first time TB2-PE-C onboarded on rfs-1 ; the second time while attaching the device are onboarded to rfs-2.Hi Nikhil,We need the server for sanity, Please let us know the status of the issue.Hi RageshIt looks like an issue and we are checking it. The parent route policy is not getting cleared during the clean-up/deletion of the service.For a workaround, please delete the parent route policies from both the rfs node(steps below) and then do the device sync-from.<ol>Go to the rfs node.unhide tsdndelete l2vpn-rr-parent-route-policycommit</ol>Let us know if that resolves the issue.Thanks.Hi RageshPlease let us know if you were able to do the devices sync-from using the above steps.We have also created an internal Jira ticket() to look into the issue.Thanks,NikhilHi Nikhil,As discussed, raised bug for the issue, Please take a look on the issue.Closing the issue. Cdet() has been filed for this issue.