L3VPN service creation is failing on LSA setup: Hi All,I am trying to create a L3VPN service on TSDN M4 LSA setup. Attaching the error screenshot.Set up details:NSO LSA:CFS: admin/Ovatest123@RFS-62: admin/Ovatest123@RFS-63: admin/Ovatest123@CNC Server: admin/Ovatest123@Thank you,Kanchan
Hello Kanchan,On your CFS node, I can see the following :<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">admin@ncs% show devices device rfs-62 config devices deviceNo entries found.</pre></div></div>It seems like your rfs-62 config has not been synced with your CFS node.I would suggest to try a sync-from on your CFS node targeting your RFS node as suggested here :This may be a duplicate of Not a problem, just for reference.Let me know if this fixes your issue!Thanks,Isaac KimThanks Isaac for the quick response, that worked and fixed the issue.But I am wondering when I did the installation I made sure to sync RFS with CFS nodes. How come they are not in sync now. Is there a way CFS and RFS can be in sync without user manually perform the sync?Hmm that is weird. This LSA install procedure has been validate by our QA, so I assume that this issue wouldn't be a problem.But if we have already seen two of these issues via JSD from LSA install, that may indicate a problem or maybe we can add a validation after the sync step to make sure the RFS node is in-sync on CFS node.I will request our team to review the LSA CFS Install procedure again and I will update this ticket if we find anything.Thanks,Isaac KimI also remember I faced a similar issue on M2 or M3 and somebody from your team suggest to use "set devices device lower-nso-* out-of-sync-commit-behaviour accept " on CFS node.Can I still use this command to keep RFS and cFS nodes in sync?NSO has the following definition for "out-of-sync-commit-behaviour":<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">3418  leaf out-of-sync-commit-behaviour {3419   type enumeration {3420    reject;3421    accept;3422   }3423   description3424   "Specifies the behaviour of a commit operation involving a3425   device that is out of sync with NCS. Value accept assumes that3426   the device's sync state is unknown and it is cleared on commit.3427   The behaviour is to reject such commits.";3428  }</pre></div></div>But the RFS sync step of the LSA CFS install procedure should resolve the device sync state as we do a sync-from operation on RFS node. I wouldn't recommend to change the "out-of-sync-commit-behaviour" for RFS node to accept.If you still have that email thread, would you be able post any explanation we gave for that recommendation?Thanks,Isaac KimHi Isaac,From CFS installation procedure, Under section: RFS OnBoarding Stepsstep: Onboard RFS device onto CFS device treeThis steps requires RFS to add "out-of-sync-commit-behaviour" as accept.So should I ignore this step?Hello Kanchan,Sorry that was my misunderstanding."out-of-sync-commit-behaviour" should be set to accept as part of our LSA install procedure.In the meantime, I will ask our QA team to review the LSA CFS install procedure again to see if there is any sync issue after full install procedure is completed.I will provide updates here.Thanks,Isaac KimHello Kanchan,I believe I have found the source of the issue.After LSA install, when you onboard new devices to RFS node, you must execute a sync-from on your CFS node.I reviewed the wiki, and this step is not defined as part of the procedure.I will add a note at the end of CFS install procedure to remind users of this sub-procedure when onboarding new devices.I will update this ticket once these documentation changes are complete.Let me know if this is a satisfactory solution.Thanks,Isaac KimHello Crystal and Kanchan,I have added the necessary information in a separate section in CFS install wiki here : Let me know if this is okay.Thanks,Isaac KimThanks Isaac for the quick help on this issue. Sure I will perform sync-from on CFS after onboarding the new devices.Great! In that case, I will mark this ticket as closed.If you have any remaining related questions, feel free to reopen this ticket.Thanks,Isaac KimDocumentation updated here :