Need help in Decoupling Netconf template from Functional pack : There is a requirement to decouple the Netconf template we package along with FP. If we load this template manually it throws error. Need help in fixing this error. I have attached the template. Following is the error. nso@ncs# config Entering configuration mode terminalnso@ncs(config)# load merge cisco-tm-tc-native-um-template.xmlLoading.Error: on line 7: no mount id exists for: /ncs:devices/ncs:device[ncs:name='{/name}']/ncs:confignso@ncs(config)# nso@ncs(config)# 
 Based on the template, it seems like this is a service template which is intended to be applied with the context of your TM TC service.Why are we trying to load this service template from NSO CLI? The service template should be automatically loaded when the TM TC package is loaded into NSO.Thanks,Isaac KimYes, it is a service template but if we have this loaded as part of TMTC package, the installation will fail if there is no netconf ned package installed. That is because this template has reference of netconf ned package. The requirement is to load TM-TC package even if there is no netconf ned package installed.What you could try is using an if-ned-id condition inside the template to protect the XR NC namespace. This should get rid of the NC NED dependency afaik.For example:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java"><config xmlns=></span> <devices xmlns=></span>  <device>   <name>{/name}</name>   <?set DEVICE = {/name} ?>   <config>     <?-ned-id cisco-iosxr-nc-7.3:cisco-iosxr-nc-7.3           cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4           <OTHER SUPPORTED NEDS FOR THIS NAMESPACE>?>        <telemetry xmlns=></span>      ...     <?end?></pre></div></div>But what this will mean is that if this template is applied and there are no matching NEDs for this if-ned-id condition, nothing inside the if-ned-id block will be pushed to device. If the service code applies different templates based on NED type, this should be okay.Please try this out and let me know if it works. Again this fix is for loading the package into NSO when there is no NC NED present, not for NSO CLI load merge.Thanks,Isaac Kimthe package installation is failing with following error admin@ncs# *** ALARM package-load-failure: cisco-tm-tc-native-um-template.xml:9 unknown ned-id: cisco-iosxr-nc-7.3:cisco-iosxr-nc-7.3, cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4Hi Moksha,Upon further evaluation, it seems like TM-TC is already setup for multivendor support.cisco-tm-tc-fp -> Native NED Support + Service Logictm-tc-multivendors -> Multivendor NED SupportIf NC NED is not the native NED for cisco-tm-tc-fp and we want to decouple the dependency from cisco-tm-tc-fp, we should move the related files to tm-tc-multivendors.Thanks,Isaac KimA solution was provided to submitter and absorbed.