CNC M4 pacakges are referencing NETCONF NED in bootstrap files: CNC M4 pacakges are referencing NETCONF NED in bootstrap files.This should be changed to CLI NED.admin@ncs> show configuration cisco-sr-te-cfp:cfp-configurations dynamic-device-mapping cisco-ios-cli-6.77:cisco-ios-cli-6.77 { python-impl-class-name sr_te_multi_vendors.IosXE;}dynamic-device-mapping cisco-iosxr-nc-7.315:cisco-iosxr-nc-7.315 { python-impl-class-name sr_te_multi_vendors.NativeXR;}dynamic-device-mapping cisco-iosxr-nc-7.3:cisco-iosxr-nc-7.3 { python-impl-class-name sr_te_multi_vendors.NativeXR;}dynamic-device-mapping cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4 { python-impl-class-name sr_te_multi_vendors.NativeXR;}dynamic-device-mapping cisco-iosxr-nc-7.5:cisco-iosxr-nc-7.5 { python-impl-class-name sr_te_multi_vendors.UMXR;}admin@ncs> more SR-multi-vendor-iosxe-cli.xml<config xmlns="http://tail-f.com/ns/config/1.0"> <cfp-configurations xmlns="http://cisco.com/ns/nso/cfp/cisco-tsdn-sr-te"> <dynamic-device-mapping> <ned-id>cisco-ios-cli-6.77:cisco-ios-cli-6.77</ned-id> <python-impl-class-name>sr_te_multi_vendors.IosXE</python-impl-class-name> </dynamic-device-mapping> </cfp-configurations></config>more SR-multi-vendor-iosxr-netconf.xml <config xmlns="http://tail-f.com/ns/config/1.0"> <cfp-configurations xmlns="http://cisco.com/ns/nso/cfp/cisco-tsdn-sr-te"> <dynamic-device-mapping> <ned-id>cisco-iosxr-nc-7.3:cisco-iosxr-nc-7.3</ned-id> <python-impl-class-name>sr_te_multi_vendors.NativeXR</python-impl-class-name> </dynamic-device-mapping> <dynamic-device-mapping> <ned-id>cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4</ned-id> <python-impl-class-name>sr_te_multi_vendors.NativeXR</python-impl-class-name> </dynamic-device-mapping> <dynamic-device-mapping> <ned-id>cisco-iosxr-nc-7.315:cisco-iosxr-nc-7.315</ned-id> <python-impl-class-name>sr_te_multi_vendors.NativeXR</python-impl-class-name> </dynamic-device-mapping> <dynamic-device-mapping> <ned-id>cisco-iosxr-nc-7.5:cisco-iosxr-nc-7.5</ned-id> <python-impl-class-name>sr_te_multi_vendors.UMXR</python-impl-class-name> </dynamic-device-mapping> </cfp-configurations></config>
Hello,CLI NEDs are Native to TSDN and can be used at all times (has nothing to do with the above output/bootstrap)TSDN additionally provides option to test Netconf NEDs as seen in the above output created by the bootstrap files.If you do not want to use Netconf NEDs then not loading these bootstrap files will suffice.Please let me know if this helps.Thank you.Can we skip dynamic mapping configuration for CLI NED's?Yes, we can skip dynamic mapping configuration for CLI NED's because CLI is native and will work without any bootstrap configloaded in.Thanks for the update.For CLI NED update wiki as to not require explicit dynamic mapping configuration Thank you. The wiki has been updatedYou will see a comment as below which indicates that the bootstrap files are optional.Please let me know if I may close this ticket.<tt>## CFP Multi-Vendor Dynamic Mapping - Optional</tt><tt>for</tt><tt>CLI NED but required</tt><tt>for</tt><tt>NETCONF NED ##</tt><tt>==========================================================================================</tt><tt>load merge SR-multi-vendor-iosxr-netconf.xml</tt><tt>load merge L3VPN-multi-vendor-iosxr-netconf.xml</tt><tt>load merge L2VPN-multi-vendor-iosxr-netconf.xml</tt><tt>load merge IETF-TE-multi-vendor-iosxr-netconf.xml</tt>Closing ticket as issue is clarified.Updated Wiki with Information about CLI being native to TSDN and no bootstrap config required in the case of CLI.