Issue with Dispatch map in LSA utils: Hi CFP team,For tm-tc fp, we tested our changes using dispatch map from core-fp-common package.admin@ncs% show dispatch-map dispatch-map 10.64.96.113 {  ned-id  cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38;  rfs-node rfs-1;}dispatch-map rfs-1 {  ned-id cisco-nso-nc-5.7:cisco-nso-nc-5.7;}admin@ncs% If Im not wrong, the limitation with this dispatch map is that there is no sync option and it gets updated only by Netconf notifications enabled. I went through srte fp, looks like you moved to dispatch map from lsa utils package. What is expectation from user with respect to dispatch map. Is it okay enforce them to add devices only after setting up Netconf notifications between CFS and RFS or are we supposed to use the dispatch map from LSA utils package.Im facing issues using dispatch map from lsa utils. I replaced the node information frompath "/core-fp-common:dispatch-map/core-fp-common:device" to "/ncs:devices/lsa-utils:lsa/lsa-utils:dispatch-map/lsa-utils:device/lsa-utils:name"Sometimes, the variable information I set in template is not getting settime="2022-03-08 01:27:35.745495" level=error msg=""or I see an illegal reference error. Can someone help me debug this issue.Regards,Moksha
Hi Raja,Dispatch-map primarily gets updated with netconf-notifications. We do have sync option as well.Below action can be used to sync dispatch map from the CFS NODE request devices lsa dispatch-map sync remote-nso <rfs-node-name>Please resolve this issue. Thnx