custom-template-events and dispatch-map-update subscription fail in M8: Deploy LSA setup. On CFS node, step 8 of "RFS OnBoarding Steps". It showed the following result:admin@ncs> show devices device rfs-195 netconf-notifications subscription                      FAILURE                                NAME               STATUS  REASON   ERROR INFO                         ------------------------------------------------------------------------------------------------------------------rfs-cisco-custom-template-events failed  subscribe Failed to create subscription: bad_element: no such stream rfs-dispatch-map-update      failed  subscribe Failed to create subscription: bad_element: no such stream rfs-kicker-events         running -     -   Both step3 and step4 the commit are successful. step3: Configure Netconf notification subscriptionstep4: Configure RFS notification settingIt will be great if you can help to take a look.Here is the NSO node info.:CFS: 2001:420:10e:201d:172:23:85:194RFS-195: 2001:420:10e:201d:172:23:85:195RFS-196: 2001:420:10e:201d:172:23:85:196id/pw: admin/Vtsisco@123!
Hi CrystalI checked the setup and found that the dispatch-map-update and custom-template-events under event streaming were not configured on the RFS nodes. For configuring the streams please refer point 2 and 3 under section "Configure ncs.conf on RFS node" in the below url:I have configured the above missing streams on the RFS node 195 and thenetconf notifications subscription verification is successful now for this node.Please follow the above mentioned steps to configure the same for RFS node 196. Restart the ncs on RFS and then CFS after configuring the streams.Thanks, NikhilUser missed to configure the streams on the RFS node and hence the issue was coming. Updated the details on one RFS node and the issue no more exists.Issue is resolved with Nikhil's help.Here are the steps:1. Updated ncs.conf on rfs nodes by follow point 2 and 3 under section Configure ncs.conf in the following wiki:2. restart ncs on rfs and cfs nodes.